Editorial and Corrections Policy

Scope

This policy applies to editorial content published by Frontman, including blog posts, comparisons, tutorials, technical explainers, research notes, and product announcements. Product documentation and legal documents follow their own review processes, but use the same standards for accuracy, source attribution, and corrections.

Editorial Independence and Conflicts

Frontman publishes about AI coding agents, browser automation, frontend development, and products that may compete with Frontman. When an author works on Frontman or has another material relationship with a subject, the article must disclose that relationship near the beginning of the page.

A Frontman product relationship does not determine the recommendation. Comparisons should state where another option is stronger, identify Frontman's limitations, and distinguish products that solve different jobs instead of forcing them into one ranking.

Frontman does not currently publish paid placements, sponsored rankings, or affiliate links in editorial articles. If that changes, the affected page will identify the sponsor or affiliate relationship before the relevant recommendation.

Sources and Claims

Volatile claims about product capabilities, command syntax, pricing, licenses, maintenance status, security behavior, and release history should use primary sources whenever available. Preferred sources include official documentation, public repositories, changelogs, standards, and vendor security notices.

Articles should distinguish among:

• behavior verified through direct testing;
• capabilities documented by a primary source;
• author analysis or opinion; and
• facts that remain uncertain or could not be independently verified.

We do not present a proposed test as a completed benchmark. We do not turn absence of documentation into proof that a capability does not exist. When evidence is incomplete, the article should say what was checked and what remains unknown.

Comparisons and Reviews

Comparison criteria should follow the searcher's workflow rather than a raw feature count. Reviews should give a recommendation early, explain the evaluation method, cover meaningful limitations, and include use-when and skip-when guidance for each option.

When Frontman appears in a comparison, the article must disclose that we built it. Claims about Frontman's behavior should link to inspectable documentation or source where practical. Competitor claims should receive the same source standard.

AI-Assisted Writing

We may use AI tools for research organization, drafting, editing, code examples, and quality checks. A named human author remains responsible for the published article, including its claims, citations, recommendations, disclosures, and corrections.

AI-generated language is not treated as evidence. Product claims still require a reliable source or clearly labeled direct test. We remove generic filler, unsupported certainty, fabricated experience, and citations that do not support the associated claim.

Publication and Updates

Every blog post shows a named author and publication date. Time-sensitive articles should include a visible source-check date in the body. We add a last-updated date after a substantive review or change, not merely to create a freshness signal.

Substantive updates include changed recommendations, corrected facts, revised commands, new test evidence, material product changes, or significant additions. Minor spelling and formatting fixes do not require a new update date.

Corrections

Readers can report an error by emailing [email protected] or opening an issue in the Frontman GitHub repository. A useful report includes the page URL, disputed passage, supporting source, and date observed.

We review correction reports against primary evidence. Material factual errors are corrected promptly. When a correction changes the article's conclusion, recommendation, or interpretation of evidence, we update the visible modified date and add a correction note describing what changed. Minor typographical fixes may be corrected without a public note.

We do not silently remove accurate criticism, disclosed limitations, or unfavorable comparisons because a vendor objects to them. We will revise a claim when stronger evidence shows it is wrong or materially incomplete.

Contact

Questions about this policy or a published article can be sent to [email protected]. Company and contact details are available in the Impressum and on the Contact page.