Merge pull request #67 from OpenSPP/fix-more-build-errors

anthonymarkQA · web-flow · commit 7a51d1c6298a · 2025-08-29T16:01:24.000+08:00
further error log cleanup
diff --git a/docs/contributing/review_status_dashboard.md b/docs/contributing/review_status_dashboard.md
@@ -68,7 +68,7 @@ To see the review status system in action:
 
 ### Test Pages
 
-- **Approved**: {doc}`../getting_started/installation_pypi`
+- **Approved**: {doc}`../getting_started/installation_deb`
 - **Reviewed**: {doc}`../community/code_of_conduct`  
 - **Needs Review**: {doc}`../overview/concepts/user_management`
 
diff --git a/docs/getting_started/index.md b/docs/getting_started/index.md
@@ -35,5 +35,4 @@ hidden: true
 
 installation_deb
 module_installation
-poc_and_pilot
 ```
diff --git a/docs/overview/index.md b/docs/overview/index.md
@@ -12,6 +12,7 @@ Welcome to the OpenSPP overview section. This section provides high-level inform
 - {doc}`features/index`  
 - {doc}`use_cases/index`  
 - {doc}`case_studies/index`
+- {doc}`concepts/index`
 - {doc}`poc_and_pilot`
 
 
@@ -24,5 +25,6 @@ Welcome to the OpenSPP overview section. This section provides high-level inform
 features/index
 use_cases/index
 case_studies/index
+concepts/index
 poc_and_pilot
 ```
diff --git a/docs/overview/use_cases/index.md b/docs/overview/use_cases/index.md
@@ -18,5 +18,4 @@ This section provides entry points for OpenSPP's main use cases.
 farmer_registry
 social_registry
 sp_mis
-social-protection-management-information-system
 ```
diff --git a/docs/reference/technical/index.md b/docs/reference/technical/index.md
@@ -19,11 +19,4 @@ security
 backup
 performance
 monitoring
-audit_logs
-cycle_manager
-deduplication_manager
-eligibility_manager
-entitlement_manager
-notification_manager
-program_manager
 ```
diff --git a/docs/user_guide/administration/index.md b/docs/user_guide/administration/index.md
@@ -17,7 +17,6 @@ This section contains administrative tasks and system management guides.
 user_access
 service_points
 managing_custom_fields
-using_audit_logs
 import_areas
 hardware_integration
 ```
diff --git a/docs/user_guide/administration/using_audit_logs.md b/docs/user_guide/administration/using_audit_logs.md
diff --git a/docs/user_guide/index.md b/docs/user_guide/index.md
@@ -39,7 +39,6 @@ Administrative tasks and system management:
 - {doc}`administration/user_access`
 - {doc}`administration/service_points`
 - {doc}`administration/managing_custom_fields`
-- {doc}`administration/using_audit_logs`
 - {doc}`administration/import_areas`
 - {doc}`administration/hardware_integration`
 
diff --git a/docs/user_guide/pos_usage.md b/docs/user_guide/pos_usage.md
@@ -103,7 +103,7 @@ Point of sales that do not belong to any area will display as minimized. Click t
 
 ### Starting Point of sale in Web view
 
-The POS application is viewable in either web view or mobile view, this section will be covering the web view, for mobile view, proceed here: [Starting Point of sale in Mobile view](#starting-point-of-sale-in-mobile-view).
+The POS application is viewable in either web view or mobile view, this section will be covering the web view, for mobile view, proceed to **Starting Point of sale in Mobile view** of this document.
 
 The POS application can be operated by either an **Administrator** or a **POS Operator** role.
 
@@ -145,7 +145,7 @@ The transaction is now complete. If you wish to start a new transaction, click o
 
 ### Starting Point of sale in Mobile view
 
-The POS application is viewable in either web view or mobile view. This section will cover the Mobile view, for Web view, proceed here: [Starting Point of sale in Web view](#starting-point-of-sale-in-web-view).
+The POS application is viewable in either web view or mobile view. This section will cover the Mobile view, for Web view, proceed to **Starting Point of sale in Web view** of this document
 
 Click on the upper left box icon to bring up the menu, then click **Point of Sale.**
 
diff --git a/docs/user_guide/program_management/allocate_funds.md b/docs/user_guide/program_management/allocate_funds.md
@@ -16,7 +16,7 @@ This tutorial covers the step-by-step procedure on how to allocate funds for a p
 To allocate funds for a project, you need to:
 
 - Have a System administrator or the appropriate program user role that enables you to create programs and allocate funds. Learn more in this guide: {doc}`../administration/user_access`.
-- Have existing individual records in your registry, either by creating records manually or importing records into OpenSPP. Learn more in this guide: {doc}`../registry_management/import_data` or {doc}`../registry_management/register_individual`.
+- Have existing individual records in your registry, either by creating records manually or importing records into OpenSPP. Learn more in this guide: {doc}`../registry_management/import_export_registrant_data` or {doc}`../registry_management/register_individual`.
 - An existing Program where individuals are registered. Learn more in this guide: {doc}`create_program`.
 
 ## Objective
diff --git a/docs/user_guide/program_management/create_cycle.md b/docs/user_guide/program_management/create_cycle.md
@@ -27,7 +27,7 @@ By the end of this tutorial, you will have gained a deeper understanding of conf
 
 To begin configuring cycles and preparing entitlements in OpenSPP, Login into your OpenSPP account, then select an existing program.
 
-Please note that any configuration changes made to your program will not impact cycles that have already been approved. Such changes will only apply to cycles created after the modifications. However, if you are already satisfied with the current program configurations, you may proceed to [Creating Cycle](#creating-cycle).
+Please note that any configuration changes made to your program will not impact cycles that have already been approved. Such changes will only apply to cycles created after the modifications. However, if you are already satisfied with the current program configurations, you may proceed to **Creating Cycle** section of this document.
 
 ### Editing Program Configuration
 
@@ -155,15 +155,15 @@ Click on the **Approve** button to approve the cycle.
 
 ![](create_program_cycle_prepare_entitlements/24.png)
 
-Please note that enabling Auto-approve entitlements in the program’s [Cycle manager](#cycle-manager) configuration auto approves the entitlements upon approving the cycle. Therefore, you may skip Approving entitlements if this is enabled.
+Please note that enabling Auto-approve entitlements in the program’s **Cycle manager** configuration auto approves the entitlements upon approving the cycle. Therefore, you may skip Approving entitlements if this is enabled.
 
 ![](create_program_cycle_prepare_entitlements/25.png)
 
 If entitlements were not auto approved successfully. It could be that the [Allocate funds](https://docs.openspp.org/tutorial/user_guides/allocate_funds.html) for the program are insufficient or missing. See the documentation Allocate funds for more details.
 
 ### Approving Entitlements
 
-After approving a cycle, the next step is to approve the entitlements. Please note that only the assigned user with correct access rights is able to approve entitlements for the cycle. This is set during the creation of the program, however it can also be changed in the **Entitlement Validation Group** dropdown within the [Entitlement manager](#entitlement-manager) of the program configuration.
+After approving a cycle, the next step is to approve the entitlements. Please note that only the assigned user with correct access rights is able to approve entitlements for the cycle. This is set during the creation of the program, however it can also be changed in the **Entitlement Validation Group** dropdown within the **Entitlement manager** of the program configuration.
 
 Login to OpenSPP with correct user role to approve the entitlements. After clicking on the program, select a cycle by clicking on the green button beside it and click on **Approve entitlement**. A yellow warning message appears if processes are still running. Make sure to click **Refresh** within the yellow warning message. Repeat every now and then until the yellow warning message disappears. It is important to let the warning message resolve before proceeding into the next step as it might otherwise cause data discrepancy.
 
diff --git a/docs/user_guide/program_management/create_program.md b/docs/user_guide/program_management/create_program.md
@@ -7,9 +7,6 @@ migration-notes: "Added during 2025 documentation reorganization"
 
 # Creating a Program
 
-
-
----
 ## Introduction
 
 This tutorial offers a comprehensive, step-by-step guide for establishing a social protection program using the OpenSPP platform. It is designed to assist users in configuring programs according to specific objectives and operational requirements.
@@ -21,7 +18,7 @@ To create a social protection program using OpenSPP, you need to:
 - Have a clear understanding of the goals and objectives of your social protection program.
 - Prepare the details of your program in advance. This includes deciding on the program name, the target beneficiary types, and the specific benefits that will be offered.
 - Have an access role as a system administrator or global program manager to perform tasks in this tutorial. Learn more about this in the documentation {doc}`../administration/user_access`.
-- Have existing groups or individuals in your registry either through manual creation or through import. Learn more about this in the documentation {doc}`../registry_management/import_data`.
+- Have existing groups or individuals in your registry either through manual creation or through import. Learn more about this in the documentation {doc}`../registry_management/import_export_registrant_data`.
 
 ## Objective
 
@@ -83,7 +80,7 @@ The **Entitlement Manager** defines what should be distributed to the beneficiar
 
 ### Import Registrants
 
-The **Import Registrants** feature allows you to import registrant records into the new program as part of the program creation and is triggered by selecting **Yes** in the final step. If the option **No** is selected, this import needs to be done afterwards. Learn more about this in the documentation {doc}`enroll_beneficiaries`.
+The **Import Registrants** feature allows you to import registrant records into the new program as part of the program creation and is triggered by selecting **Yes** in the final step. If the option **No** is selected, this import needs to be done afterwards. Learn more about this in the documentation {doc}`enrol_beneficiaries`.
 
 After choosing whether to import the registrants as part of the program creation or not, click **Create**.
 
diff --git a/docs/user_guide/program_management/create_program_cycle_prepare_entitlements/26.png b/docs/user_guide/program_management/create_program_cycle_prepare_entitlements/26.png
diff --git a/docs/user_guide/registry_management/dms.md b/docs/user_guide/registry_management/dms.md
@@ -12,7 +12,7 @@ In this tutorial, you will learn how to use the Document Management System featu
 
 ## Prerequisites  
 To utilize the DMS feature, you need to:  
-- Have existing individual records in your registry, either by creating records manually or importing records into OpenSPP. Learn more about this in the guide  {doc}`register_individual` or {doc}`import_data`
+- Have existing individual records in your registry, either by creating records manually or importing records into OpenSPP. Learn more about this in the guide  {doc}`register_individual` or {doc}`import_export_registrant_data`
 - By default, the system administrator has sufficient permission to access the DMS. Learn more about this in the guide {doc}`../administration/user_access`
 - Ensure that the DMS module `spp_dms` is properly installed and activated. Note that the Change_request (`spp_change_request`) module automatically installs and activates the DMS module.  
 - A change request must have an attached document.
@@ -49,18 +49,18 @@ To preview attached documents, navigate to `DMS → Files`. All attached documen
 > **Note:** The number shown next to each change request or directory represents the total number of documents attached to that specific request or directory.  
 ![](dms/dms_attachments_count.png)
 
-##### Preview document  
+#### Preview document  
 To preview a document, click on the eye button. A window should appear displaying a preview of the document.  
 ![](dms/dms_appear_as_pdf.png)
 
-##### Download document
+#### Download document
 To download a document from a directory, click on a directory and it should display all documents associated with the directory.  
 ![](dms/dms_download_attachment_from_files.png)
 
 Click on the document you wish to download and click on the download icon.  
 ![](dms/dms_download_button.png)
 
-##### Edit document attachment  
+#### Edit document attachment  
 It is also possible to edit a document attachment in a change request. Click on the directory or change request you wish to update.  
 ![](dms/dms_select_change_request.png)
 
diff --git a/docs/user_guide/registry_management/identity_management.md b/docs/user_guide/registry_management/identity_management.md
@@ -15,7 +15,7 @@ This guide offers a comprehensive, step-by-step overview for Operations Admins a
 
 To configure ID and generate QR code, you need to:
 
-- Have existing individual records in your registry, either by creating records manually {doc}`register_individual` or importing records into OpenSPP {doc}`import_data`.
+- Have existing individual records in your registry, either by creating records manually {doc}`register_individual` or importing records into OpenSPP {doc}`import_export_registrant_data`.
 - Have an access role as an **Operations Admin** or **Administrator**. Learn more in this guide: {doc}`../administration/user_access`.
 - Make sure that the module **OpenSPP POS: ID Redemption** is installed and activated.
 
diff --git a/docs/user_guide/registry_management/using_change_requests.md b/docs/user_guide/registry_management/using_change_requests.md
@@ -14,7 +14,7 @@ This guide explains how to update registrant information in OpenSPP using the Ch
 ## Prerequisites
 
 Before submitting or approving change requests, ensure the following:
-- Have existing individual records in your registry, either by creating records manually {doc}`register_individual` or importing records into OpenSPP {doc}`import_data`.
+- Have existing individual records in your registry, either by creating records manually {doc}`register_individual` or importing records into OpenSPP {doc}`import_export_registrant_data`.
 - Assign appropriate roles to Change Request validators. You can learn how to perform these tasks in the {doc}`../administration/user_access` document under the **Configuring Roles** section:
   - **Local Validator**: Add the group name under the Groups tab: `Change Request Module Access / Change Request Validator Local`.
   - **HQ Validator**: Add the group name under the Groups tab: `Change Request Module Access / Change Request Validator HQ`.
diff --git a/docs/user_guide/registry_management/using_event_data.md b/docs/user_guide/registry_management/using_event_data.md
@@ -35,7 +35,7 @@ The `spp_event_data_program_membership` module enhances OpenSPP by integrating t
 
 To utilize and manage Event Data, ensure the following prerequisites are met:
 
-- Individual or group records already exist in your registry. For more information, refer to {doc}`register_individual` or {doc}`import_data`.
+- Individual or group records already exist in your registry. For more information, refer to {doc}`register_individual` or {doc}`import_export_registrant_data`.
 - The `spp_event_data` module (OpenSPP Event Data) is installed and activated.
 - If specific event types are required (such as program membership events), ensure that any related modules (e.g., `spp_event_data_program_membership`) are also installed and activated.
 - To access demonstration features, the `spp_event_demo` module should be activated.
