Editorial Policy

Purpose and scope

OnUML content is written to help readers complete a diagramming task, understand a technical distinction, or diagnose a reproducible problem. Articles should state their purpose clearly and avoid unsupported claims, invented results, and unnecessary filler.

Sources and verification

• Official documentation, specifications, and project repositories are preferred for technical claims.
• Material claims should be traceable to a source or to a reproducible example shown in the article.
• Testing or first-hand experience is only described when the method and relevant limitations can be stated.
• Sources must not be invented, misquoted, or cited for claims they do not support.

Examples and code

Code and diagram examples are designed to be small enough to inspect and adapt. Examples should distinguish language behavior from editor-specific behavior, identify important prerequisites, and avoid presenting a simplified example as proof that a production system is correct.

Assisted tools

Automated and AI-assisted tools may support research organization, drafting, editing, or quality checks. OnUML remains responsible for the published result. Assisted output does not replace source verification, factual review, or correction of material errors.

Authorship and transparency

A byline identifies the accountable publishing identity used for an article. When a public pen name is used, its profile states that fact rather than presenting invented credentials or employment history.

Updates and corrections

Articles may be updated when software behavior, documentation, links, or recommended workflows change. Substantive updates should change the visible updated date. Confirmed material errors are corrected as soon as practical; minor copy edits do not require a correction note.

To report an issue, use the contact page and include the article URL, disputed statement, and supporting evidence.