docs: [DHIS2-18603] add Bulk data entry Plugin developer portal docs

docs/developer/bulk-data-entry-plugin/developer-details.mdx

@@ -0,0 +1,37 @@
+---
+title: Developer Details (Bulk Data Entry Plugin)
+sidebar_label: Developer details
+id: developer-details
+---
+
+Here are some details for developers who want to develop a bulk data entry plugin for the DHIS2 Capture app.
+
+## Plugin Interface
+
+The plugin receives the following props:
+
+```ts
+type BulkDataEntryPluginProps = {|
+    pluginSource: string,    
+    configKey: string,  
+    dataKey?: string,        
+    onComplete: () => void,
+    onDefer: () => void,
+    trackedEntityIds?: Array<string>,
+|};
+```
+
+### Exiting the Plugin
+
+To exit the Plugin and return to the Program overview or Search pages, use the `onDefer` function provided as a prop. This will place the Plugin in an idle state until further action is taken.
+
+```ts
+onDefer();
+```
+
+### Closing the Plugin
+
+To ensure proper cleanup and resource management, use the `onComplete` function provided as a prop to close the plugin. This will clear the selected configuration from `IndexedDB`.
+```ts
+onComplete();
+```

docs/developer/bulk-data-entry-plugin/introduction.mdx

@@ -0,0 +1,16 @@
+---
+title: What is the Bulk Data Entry Plugin?
+sidebar_label: Introduction
+id: introduction
+---
+
+The Bulk Data Entry Plugin is an extension point that can be accessed through the Search page or Working list page in Capture app. This extension point enables developers to create and configure plugins for custom bulk operations on tracked entities carried over from the working list page or added manually in the plugin itself.
+The main reason for developing this extension point in the DHIS2 Capture app was to support a plugin for bulk data entry in a grid form, adding new events to all tracked entities in a list, including applying same values for a column or copy and pasting values from a row to another. The aim is to reduce time spent on data entry, for example secondary from paper forms.
+
+Some plugin use cases for the extension point can include:
+
+1. Enter data for multiple tracked entities at the same time (Forthcoming core Capture plugin)
+2. Validate and update data across multiple tracked entity records simultaneously
+3. Update the status of multiple events in one go
+4. Merging or deduplicating tracked entities
+5. Any other custom bulk operations or changes your workflow might require

docs/developer/bulk-data-entry-plugin/manual-setup.mdx

@@ -0,0 +1,108 @@
+---
+title: Manual Setup (Bulk Data Entry Plugin)
+sidebar_label: Manual setup
+id: manual-setup
+---
+
+To enable bulk data entry functionality, you need to configure the data store in your DHIS2 instance. Follow these steps:
+
+1. Access your DHIS2 Data Store Management app
+2. Create a new key called `bulkDataEntry` in the `capture` namespace
+3. The data store interface should look similar to this:
+
+![Data store management app](../resources/data-store-management-bulk-data-entry-empty.png)
+
+## Configuration Structure
+
+In the `bulkDataEntry` key you created, you can store your bulk data entry form configurations. The structure is as follows:
+
+```json title="capture/bulkDataEntry"
+{
+    "version": 1,
+    "config": []
+}
+```
+
+The `version` field indicates the configuration version as a number. The `config` array contains one or more bulk data entry configuration objects. Below is an example showcasing three different configurations:
+
+```json title="capture/bulkDataEntry"
+{
+    "version": 1,
+    "config": [
+        {
+            "title": {
+                "en": "Routine visit"
+            },
+            "dataKey": "routineVisit",
+            "subtitle": {
+                "en": "Covers all patient visit forms"
+            },
+            "configKey": "routineVisit",
+            "programId": "IpHINAT79UW",
+            "pluginSource": "https://debug.dhis2.org/dev/api/apps/routine-visit/plugin.html"
+        },
+        {
+            "title": {
+                "es": "Tratamiento",
+                "en": "Treatment",
+                "fr": "Traitement",
+                "nb": "Behandling"
+            },
+            "configKey": "treatment",
+            "programId": "IpHINAT79UW",
+            "pluginSource": "https://debug.dhis2.org/dev/api/apps/treatment/plugin.html"
+        },
+        {
+            "title": {
+                "en": "Case based surveillance"
+            },
+            "subtitle": {
+                "en": "Covers ad-hoc visits and RMNCH238972"
+            },
+            "configKey": "caseBasedSurveillance",
+            "programId": "uy2gU8kT1jF",
+            "pluginSource": "https://debug.dhis2.org/dev/api/apps/case-based-surveillance/plugin.html"
+        }
+    ]
+}
+```
+
+### Configuration Fields
+
+Each configuration object requires the following fields:
+
+| Field | Required | Description |
+|-------|----------|-------------|
+| `configKey` | Yes | An identifier for the configuration. Must be unique per `programId`. Will be passed to the plugin. |  
+| `programId` | Yes |  The identifier of the program where this bulk data entry will be available. |
+| `pluginSource` | Yes | The URL of the plugin. Must point to a valid plugin installed on the instance and follow the pattern: https://{instance-url}/api/apps/{plugin-name}/plugin.html. |
+| `title` | Yes | The display title of the configuration. Supports multiple languages using locale codes (e.g., "en", "es"). |
+| `subtitle` | No | An optional subtitle for the configuration. Supports multiple languages using locale codes. |
+| `dataKey` | No | An optional identifier that is not used internally by the app but is passed through to the plugin. This property is intended for advanced usage and can be used by the plugin to maintain separate in-progress caches for a given `configKey`. |
+
+## Selecting a Plugin Configuration
+
+Once configured, bulk data entry plugins are accessible in multiple locations throughout the Capture app. You'll find them displayed as widgets on both the Program overview and Search pages:
+
+![Widget bulk data entry main page](../resources/widget-bulk-data-entry-main-page.png)
+![Widget bulk data entry search page](../resources/widget-bulk-data-entry-search-page.png)
+
+The plugins can also be accessed via dropdown menus from the tracked entities working lists or the program stages working lists:
+
+![Dropdown menu bulk data entry program stage working lists](../resources/dropdown-menu-bulk-data-entry-program-stage-working-lists.png)
+![Dropdown menu bulk data entry tracked entities working lists](../resources/dropdown-menu-bulk-data-entry-tracked-entities-working-lists.png)
+
+After the user selects a plugin configuration, it is stored in `IndexedDB` for the duration of use.
+
+### Passing Tracked Entities to the Plugin
+
+The plugin receives tracked entities through the `trackedEntityIds` prop - an array containing the IDs of selected tracked entities.
+
+### Cleanup and Disposal
+
+To exit the Plugin and return to the Program overview or Search pages, use the `onDefer` function provided as a prop. This will place the Plugin in an idle state until further action is taken.
+
+![Widget bulk data entry main page](../resources/widget-bulk-data-entry-main-page-idle.png)
+![Widget bulk data entry search page](../resources/widget-bulk-data-entry-search-page-idle.png)
+
+To ensure proper cleanup and resource management, use the `onComplete` function provided as a prop to close the plugin. This will clear the selected configuration from `IndexedDB`.