-
Notifications
You must be signed in to change notification settings - Fork 4
Updated screenshots for Module installation #99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Summary of ChangesHello @jannahadlaon, I'm Gemini Code Assist1! 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 focuses on enhancing the clarity and accuracy of the module installation documentation. It updates existing screenshot references for the Farmer Registry and introduces new visual aids for the Social Registry, ensuring that users have up-to-date and comprehensive guides for module setup. Highlights
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request updates the screenshots for the module installation guides for the Farmer Registry and Social Registry. My review includes suggestions to improve filename consistency for images and to fix a minor grammatical inconsistency in the documentation steps. Also, please note that while the pull request description mentions updates for 'SP-MIS installation', no changes for that module are included in this PR.
| 2. In the Apps menu, search for {doc}`spp_base_farmer_registry </reference/modules/spp_base_farmer_registry>` or "OpenSPP Farmer Registry Base" | ||
|
|
||
|  | ||
|  |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The filename for this image uses mixed case (spp_Farmer1.jpg). For consistency with other images in the documentation (like 12-social_inst_base01.jpg and 01-apps-ui.jpg), it's better to use all lowercase for filenames (e.g., spp_farmer1.jpg). This helps avoid potential issues on case-sensitive filesystems and improves maintainability. Please consider renaming the image file to use all lowercase.
|  | |
|  |
| 3. Click the **Activate** button to install the module and its dependencies. | ||
|
|
||
|  | ||
|  |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar to the comment above, the filename for this image uses mixed case (spp_Farmer2.jpg). For consistency, it's better to use all lowercase for filenames (e.g., spp_farmer2.jpg).
|  | |
|  |
|
|
||
|  | ||
|
|
||
| 3. Click the **Activate** button to install the module and its dependencies |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For grammatical consistency, please add a period at the end of this sentence. Other steps in the documentation follow this convention.
| 3. Click the **Activate** button to install the module and its dependencies | |
| 3. Click the **Activate** button to install the module and its dependencies. |
|
|
reviewed. looks good to me. |



Updated screenshots for Module installation. The screenshots were updated for the following modules: