Content structure and editorial conventions

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

Content map

The shared-hosting package mirrors these directories. Keep equivalent articles synchronized before release. Preserve the monetary text and its provenance: OpenForex Standards are issued by the OpenForex Society, the core of the OpenForex Foundation. Publish implementation explanations as related reference articles.

Page structure

Begin with a descriptive title and a short explanation of the page's purpose. State publication status, document version where applicable, and revision date. Develop the subject with concrete definitions, responsibilities, examples, and limitations. End with contextual links that help the reader continue.

Present OpenForex Standards as the Society's ratified, working standards. Use Standards reference, Community guidance, or Operational guide to identify a page's purpose without downgrading the authority of the Standard. Reserve Draft and Review for new amendments or submissions that are genuinely under consideration.

Links and routes

The PHP portal identifies articles by a page query containing the directory and extensionless filename. For example, the kernel page is linked as OFS-Kernel. Use explicit routes when linking between documents so links work under a subdirectory installation.

The optional Wiki.js seed utility has a separate path map. PHP query links are not automatically translated into Wiki.js routes. Review and adapt those links before importing this publication into another engine.

Formatting supported by the portal

The reader supports headings, paragraphs, emphasis, code, fenced code blocks, basic lists, simple tables, blockquotes, and HTTP or internal page links. It is a small renderer, not a complete Markdown implementation. Check the rendered result when using nested structures or complex tables.

Editorial quality

Define abbreviations at first use. State units beside numerical values. Distinguish source claims, explanatory interpretation, and new proposals. Give synthetic examples a visible label. Prefer links to concrete documents over unsupported mentions of a charter, committee, or approved release.

See the page template, contribution guide, and brand guide.