# Contribution and publication workflow

Publication: OpenForex Society / OpenForex Foundation. Updated 2026-09-24.

## Prepare
Identify the affected page and classify the change as editorial, technical, governance, or implementation evidence. Explain a concrete problem and the expected result. Use the [RFC process](?page=seed-content/rfc-proposals/index) for substantive behavior or authority changes.

Work from a known source revision when one is available. Preserve attribution and keep a copy of the original text for comparison. A public repository URL is configured separately; no remote submission occurs when local files are edited.

## Review
Editors check clarity, status, references, and links. Domain reviewers check assumptions, equations, numeric behavior, and compatibility. Approval of a standard or governance rule requires the authorized process and a decision record.

| Change type | Evidence to include |
| --- | --- |
| Editorial | Before-and-after wording and source reference |
| Technical | Changed behavior, assumptions, examples, and affected versions |
| Simulation | Frozen inputs, method, precision, results, and limitations |
| Implementation | Source revision, reproducible checks, and unsupported cases |
| Governance | Authority, affected roles, alternatives, and decision rationale |

## Prepare the publication
Update status and date accurately. Keep the foundational source text separate from commentary. Synchronize root and shared-hosting articles, check new links, and inspect the article in the reader. Check that no credentials, private information, or unlicensed copied material entered the publication.

## Verify
Check PHP syntax if code changed. Request each new page and asset, verify unknown pages return 404, and confirm Markdown downloads. For content, review tables, code blocks, quotation formatting, headings, and search discoverability. Record any unperformed visual or integration checks instead of presenting them as passed.

## Release and correction
Record the published revision and its review evidence. Keep prior releases recoverable through the chosen source-control or backup process. If an error is found, identify affected claims, publish the correction, and update dependent examples.

Use the [content map](?page=docs/content-structure) and [contribution guide](?page=seed-content/developers/contribution-guide) throughout the process.