> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jadenet.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Contributing to the guide

> Keep JADE-ELS documentation accurate through evidence-based updates, review, and release notes.

The guide lives with the application source so documentation changes can be reviewed with product changes. Each page is an MDX file and navigation is controlled by `docs.json`.

## When to update documentation

* A menu, field, status, action, validation, or workflow changes.
* A role or permission changes what users can see or do.
* A report or export changes parameters or meaning.
* A new module, integration, or document type is released.
* Support identifies a recurring question or error.
* A screenshot no longer matches the supported version.

## Required evidence

Provide at least one of:

* approved process-owner description;
* current application screenshot with non-production/sanitized data;
* test case or acceptance criterion;
* implemented menu/view/action identifier;
* release note or issue reference.

## Contribution workflow

<Steps>
  <Step title="Open a documentation change">Name the affected page, application version, user role, and reason.</Step>
  <Step title="Update task-first content">Describe what the user is trying to achieve, prerequisites, steps, result, and control checks.</Step>
  <Step title="Use sanitized evidence">Remove customer, employee, financial, credential, and shipment-sensitive data from screenshots.</Step>
  <Step title="Validate links and navigation">Confirm every page in `docs.json` exists and every local link/image resolves.</Step>
  <Step title="Obtain process-owner review">Operations, Finance, HR, Security, or another accountable owner reviews behavior and terminology.</Step>
  <Step title="Record the change">Add a short entry to the documentation changelog and update the coverage matrix when evidence status changes.</Step>
</Steps>

## Writing standard

* When an English source page changes, update its Bahasa Indonesia (id) and Japanese (ja) counterparts in the same documentation change. If a translation cannot be completed immediately, record it explicitly in the content-status page.
* Use the exact menu and action label shown in the supported application version.
* Start steps with an action verb.
* Separate saving, approval, posting, payment, and closing.
* State prerequisites and expected result.
* Add warnings only for meaningful operational, financial, or security risk.
* Label screenshots with their captured version.
* Avoid claims about legal compliance, uptime, encryption, or retention unless formally verified.

## Definition of done

A page is publishable when its purpose, audience, prerequisites, procedure, expected outcome, error/control notes, links, evidence level, and owner review are complete.