chore/add versioned documentation with auto detection in docs v48

[Killusions]

Only for testing #752

---

• I confirm that this MR follows the contribution guidelines.

[gemini-code-assist]

Summary of Changes

Hello @Killusions, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a comprehensive system for managing and serving versioned documentation. It includes a backend script to merge and sort documentation version metadata, ensuring all available versions are correctly represented. Additionally, a frontend script automatically redirects users to the latest documentation version, improving navigation and ensuring consistent access to up-to-date content.

Highlights

• Version Metadata Management Script: A new Node.js script (.github/scripts/merge-versions.mjs) has been added to manage and merge documentation version metadata (versions.json). This script ensures proper sorting and deduplication of 'latest', 'preview', and specific 'vX' versions, which is crucial for maintaining an accurate version selector.
• Client-Side Version Redirection: A new JavaScript file (docs/_src/js/version-redirect.js) has been introduced to automatically redirect users to the /latest/ version of the documentation if they access a non-versioned path or the root. This enhances user experience by ensuring they always land on the most current documentation by default.
• MkDocs Integration: The mkdocs.yml configuration has been updated to include the new version-redirect.js script in its extra_javascript section. This integration ensures that the client-side version redirection logic is active on the deployed documentation site.

Ignored Files

• Ignored by pattern: .github/workflows/** (2)
  • .github/workflows/publish-documentation.yaml
  • .github/workflows/release.yaml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces versioning for the documentation by adding two new scripts and updating the mkdocs.yml configuration. A Node.js script (merge-versions.mjs) is added to merge and sort documentation versions, and a client-side JavaScript file (version-redirect.js) handles redirection to the correct versioned path.

The changes are well-implemented. The redirect script is robust, and the merge script correctly handles different version formats and edge cases. I've provided a couple of suggestions for the merge-versions.mjs script and one for version-redirect.js to improve code maintainability and readability by reducing duplication and simplifying complex conditions. Overall, this is a solid contribution.

[Killusions]

Tested and works, closing

[github-actions]

Documentation.
Examples.
Playwright report.

Coverage Reports:

• element-ng
• element-translate-ng

[Killusions]

Seems to still work, closing

[github-actions]

[Killusions]

Works, closing again