Review workflow
Content Review Policy
Review process
Each new page should be checked for clear structure, correct links, working metadata, and alignment with the site's purpose before publication. The review should confirm that the page is useful on its own and also fits the broader site architecture.
Tool validation
Tool pages should be tested with representative input to confirm the UI behaves as expected. Validation should include common success cases, clear error handling, and any browser behavior that affects the user experience.
Guide and article review
Guides and articles should be reviewed for technical accuracy, helpful examples, and links to the correct related pages. If a post describes a workflow or standard, the page should reflect the current implementation and avoid stale assumptions.
Update frequency
Core pages should be revisited whenever the site changes materially and at regular intervals for freshness. Pages with changing technical behavior should be updated sooner than evergreen reference content.
User feedback handling
Feedback that reports bugs, confusing output, or outdated instructions should be triaged and evaluated against the live page. Corrections should be made when the issue is confirmed and the fix should be reflected in both content and behavior where needed.
Quality standards
Published content should be accurate, concise, and free from unnecessary hype. The final review should confirm that the page is readable on mobile, includes the expected trust signals, and gives the user a clear next step.