docs(gh-pages): migrate site to jekyll format

[ReenigneArcher]

Description

This PR moves the product page over to the upcoming Jekyll style.

TODO:

• merge feat(build): use jekyll and restyle website LizardByte.github.io#186
• update branches to master in workflow (see comments below)
• update branch protection rules

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[Copilot]

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

Files not reviewed (1)

• gh-pages-template/index.html: Language not supported

Comments suppressed due to low confidence (2)

gh-pages-template/assets/js/item_loader.js:9

• The variable 'platforms_container' was previously declared without 'let'. Ensure that this change does not cause issues with its usage elsewhere in the code.

let platforms_container = document.getElementById("platforms-container")

gh-pages-template/assets/js/item_loader.js:339

• The changes to the script loading sequence in the 'initialize' function should be covered by tests to ensure the new order does not introduce any issues.

initialize()

[sonarqubecloud]

Quality Gate failed

Failed conditions
2 New issues
2 New Code Smells (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[ReenigneArcher]

Description

This PR moves the product page over to the upcoming Jekyll style.

TODO:

• merge feat(build): use jekyll and restyle website LizardByte.github.io#186
• update branches to master in workflow (see comments below)
• update branch protection rules

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[Copilot]

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

Files not reviewed (1)

• gh-pages-template/index.html: Language not supported

Comments suppressed due to low confidence (2)

gh-pages-template/assets/js/item_loader.js:9

• The variable 'platforms_container' was previously declared without 'let'. Ensure that this change does not cause issues with its usage elsewhere in the code.

let platforms_container = document.getElementById("platforms-container")

gh-pages-template/assets/js/item_loader.js:339

• The changes to the script loading sequence in the 'initialize' function should be covered by tests to ensure the new order does not introduce any issues.

initialize()

[sonarqubecloud]

Quality Gate failed

Failed conditions
2 New issues
2 New Code Smells (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[ReenigneArcher]

Description

This PR moves the product page over to the upcoming Jekyll style.

TODO:

• merge feat(build): use jekyll and restyle website LizardByte.github.io#186
• update branches to master in workflow (see comments below)
• update branch protection rules

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[Copilot]

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

Files not reviewed (1)

• gh-pages-template/index.html: Language not supported

Comments suppressed due to low confidence (2)

gh-pages-template/assets/js/item_loader.js:9

• The variable 'platforms_container' was previously declared without 'let'. Ensure that this change does not cause issues with its usage elsewhere in the code.

let platforms_container = document.getElementById("platforms-container")

gh-pages-template/assets/js/item_loader.js:339

• The changes to the script loading sequence in the 'initialize' function should be covered by tests to ensure the new order does not introduce any issues.

initialize()

[sonarqubecloud]

Quality Gate failed

Failed conditions
2 New issues
2 New Code Smells (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[ReenigneArcher]

Description

This PR moves the product page over to the upcoming Jekyll style.

TODO:

• merge feat(build): use jekyll and restyle website LizardByte.github.io#186
• update branches to master in workflow (see comments below)
• update branch protection rules

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[Copilot]

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

Files not reviewed (1)

• gh-pages-template/index.html: Language not supported

Comments suppressed due to low confidence (2)

gh-pages-template/assets/js/item_loader.js:9

• The variable 'platforms_container' was previously declared without 'let'. Ensure that this change does not cause issues with its usage elsewhere in the code.

let platforms_container = document.getElementById("platforms-container")

gh-pages-template/assets/js/item_loader.js:339

• The changes to the script loading sequence in the 'initialize' function should be covered by tests to ensure the new order does not introduce any issues.

initialize()

[sonarqubecloud]

Quality Gate failed

Failed conditions
2 New issues
2 New Code Smells (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[ReenigneArcher]

Description

This PR moves the product page over to the upcoming Jekyll style.

TODO:

• merge feat(build): use jekyll and restyle website LizardByte.github.io#186
• update branches to master in workflow (see comments below)
• update branch protection rules

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[Copilot]

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

Files not reviewed (1)

• gh-pages-template/index.html: Language not supported

Comments suppressed due to low confidence (2)

gh-pages-template/assets/js/item_loader.js:9

• The variable 'platforms_container' was previously declared without 'let'. Ensure that this change does not cause issues with its usage elsewhere in the code.

let platforms_container = document.getElementById("platforms-container")

gh-pages-template/assets/js/item_loader.js:339

• The changes to the script loading sequence in the 'initialize' function should be covered by tests to ensure the new order does not introduce any issues.

initialize()

[sonarqubecloud]

Quality Gate failed

Failed conditions
2 New issues
2 New Code Smells (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[ReenigneArcher]

Description

This PR moves the product page over to the upcoming Jekyll style.

TODO:

• merge feat(build): use jekyll and restyle website LizardByte.github.io#186
• update branches to master in workflow (see comments below)
• update branch protection rules

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[Copilot]

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

Files not reviewed (1)

• gh-pages-template/index.html: Language not supported

Comments suppressed due to low confidence (2)

gh-pages-template/assets/js/item_loader.js:9

• The variable 'platforms_container' was previously declared without 'let'. Ensure that this change does not cause issues with its usage elsewhere in the code.

let platforms_container = document.getElementById("platforms-container")

gh-pages-template/assets/js/item_loader.js:339

• The changes to the script loading sequence in the 'initialize' function should be covered by tests to ensure the new order does not introduce any issues.

initialize()

[sonarqubecloud]

Quality Gate failed

Failed conditions
2 New issues
2 New Code Smells (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[ReenigneArcher]

Description

This PR moves the product page over to the upcoming Jekyll style.

TODO:

• merge feat(build): use jekyll and restyle website LizardByte.github.io#186
• update branches to master in workflow (see comments below)
• update branch protection rules

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[Copilot]

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

Files not reviewed (1)

• gh-pages-template/index.html: Language not supported

Comments suppressed due to low confidence (2)

gh-pages-template/assets/js/item_loader.js:9

• The variable 'platforms_container' was previously declared without 'let'. Ensure that this change does not cause issues with its usage elsewhere in the code.

let platforms_container = document.getElementById("platforms-container")

gh-pages-template/assets/js/item_loader.js:339

• The changes to the script loading sequence in the 'initialize' function should be covered by tests to ensure the new order does not introduce any issues.

initialize()

[sonarqubecloud]

Quality Gate failed

Failed conditions
2 New issues
2 New Code Smells (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[ReenigneArcher]

Description

This PR moves the product page over to the upcoming Jekyll style.

TODO:

• merge feat(build): use jekyll and restyle website LizardByte.github.io#186
• update branches to master in workflow (see comments below)
• update branch protection rules

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[Copilot]

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

Files not reviewed (1)

• gh-pages-template/index.html: Language not supported

Comments suppressed due to low confidence (2)

gh-pages-template/assets/js/item_loader.js:9

• The variable 'platforms_container' was previously declared without 'let'. Ensure that this change does not cause issues with its usage elsewhere in the code.

let platforms_container = document.getElementById("platforms-container")

gh-pages-template/assets/js/item_loader.js:339

• The changes to the script loading sequence in the 'initialize' function should be covered by tests to ensure the new order does not introduce any issues.

initialize()

[sonarqubecloud]

Quality Gate failed

Failed conditions
2 New issues
2 New Code Smells (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE