Spmis use case penn

[anthonymarkQA]

Added SPMIS use case taking reference from Farmer registry use case md file
Removed installer guides as well and retained debian as the default version
added a description in getting started section of both spmis and farmer registry to install their correspondping base modules to start

[gemini-code-assist]

Summary of Changes

Hello @anthonymarkQA, 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 significantly enhances the OpenSPP documentation by introducing a comprehensive guide for the Social Protection Management Information System (SP-MIS) use case, detailing its concepts, implementation within OpenSPP, and setup steps. Concurrently, it refines the installation process by removing Docker and PyPI specific guides, standardizing on the Debian/Ubuntu installation. The changes also include updated initial setup instructions for both the new SP-MIS and the Farmer Registry, ensuring users are clearly guided on installing necessary base modules.

Highlights

• New SP-MIS Use Case Documentation: A new, detailed documentation page has been added for the Social Protection Management Information System (SP-MIS) use case, providing a comprehensive overview of its principles, OpenSPP's role, and implementation guidance.
• Streamlined Installation Guides: The installation documentation has been streamlined by removing the Docker and PyPI specific guides, retaining only the Debian/Ubuntu installation as the primary method.
• Updated Module Installation Instructions: Initial setup instructions for both the new SP-MIS and the existing Farmer Registry use cases have been updated to clearly guide users on installing their respective base modules from the OpenSPP instance's Apps section.
• Documentation Link Refinements: Several internal documentation links related to data import and export have been updated and consolidated for improved navigation and clarity.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 a new use case document for Social Protection Management Information Systems (SP-MIS) and streamlines the installation guides by removing the Docker and PyPI options, focusing on Debian packages. It also updates instructions in the Farmer Registry and the new SP-MIS use case. My review found a couple of minor issues in the documentation links, including a typo and an inconsistent path, for which I've provided suggestions to ensure all links are correct and consistent across the documentation.

[gemini-code-assist]

There are a couple of issues with the links in this section:

1. There's a typo in the path for "Configuring Areas". It should be administration instead of admininstration.
2. The link for "Importing Initial Data" seems to be incorrect. Based on other changes in this PR and the available files, it should point to import_export_registrant_data.

Suggested change

	* Configuring Areas {doc}`../../user_guide/admininstration/import_areas`.
	* Importing Initial Data: {doc}`../../user_guide/registry_management/export_data` and {doc}`../../user_guide/registry_management/import_data`.
	* Importing Initial Data: {doc}`../../user_guide/registry_management/import_export_data`.
	* Configuring Areas {doc}`../../user_guide/administration/import_areas`.
	* Importing Initial Data: {doc}`../../user_guide/registry_management/import_export_registrant_data`.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud