[Backport 5.0.x] Review documentation (#2274)

[allyoucanmap]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @allyoucanmap, 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 backports a series of documentation and theme-related improvements to the 5.0.x branch. The changes aim to enhance the accuracy and consistency of the project's JSDoc, update tutorial content to reflect recent architectural shifts in plugin configuration and styling, and modernize the overall theme structure to align with MapStore's current design patterns. This ensures that developers and users have access to up-to-date and clear guidance.

Highlights

• Documentation Clarity: Several JSDoc comments for internal components and utility functions have been updated with the @ignore tag, indicating they are not intended for public API documentation.
• Plugin Documentation Structure: The JSDoc for CreateDataset and Favorites plugins has been refactored to use @module instead of @memberof plugins and @class, aligning with a more modern documentation approach.
• Tutorial Updates: Multiple tutorial files have been revised to reflect current best practices, including changes to CSS variable naming conventions (gn- to ms-), updated plugin configuration examples, and a streamlined development setup by removing local GeoNode development instructions.
• Theme Modernization: The theme.html file has undergone a significant overhaul, replacing older GeoNode-specific UI elements with MapStore-style components and updating CSS variable prefixes from gn- to ms- for consistency.

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 backports several documentation updates. The changes include updating JSDoc comments to hide internal components using @ignore, aligning plugin examples with their correct names, and significantly revising tutorials to reflect new APIs and a new theming system based on MapStore. The documentation for creating custom resource pages and overriding local configurations has been modernized. I've found one minor issue in the theme customization tutorial page where an incorrect prefix is being used, which I've commented on.