Editorial Standards

Last updated: 1 September 2026.

1. Who writes for this site

Every article is written by an engineer on the Mangobaz Editorial Team — the same in-house team that ships production work for clients. We do not accept guest posts, paid placements, or uncredited rewrites.

2. Our editorial process

1. Topic selection. We pick topics we have hands-on experience with. If we have not built or operated something, we either build a small prototype first or we do not publish the article.
2. Research. We read the official documentation (MDN, Microsoft Learn, OWASP, W3C, vuejs.org) and at least two corroborating sources before drafting.
3. Draft. The lead author drafts the article. We aim for 1,500–2,500 words per in-depth tutorial; pillar pages reach 2,500–4,000 words.
4. Peer technical review. A second engineer on the team reads the draft, runs every code sample in a clean environment, and flags any factual or technical issue.
5. Test in a fresh environment. Every code sample is executed on a freshly cloned machine before publication. If it does not work, we fix it before publishing.
6. Publish. The article is published with a publish date, a "last tested" date, the framework and runtime versions used, and structured data (Article + BreadcrumbList + HowTo schema where applicable).
7. Maintain. We re-test the article quarterly. YMYL articles (security, payments, production deployment) are re-tested at least annually and immediately when the upstream framework ships a major version.

3. What "tested" means

When we say a code sample is tested, we mean it ran on a clean machine with the versions listed in the article and produced the output we describe. We do not mean "we typed it into a text editor and it looks right". We link to runnable code where the framework supports it (CodePen, StackBlitz, GitHub Gists).

4. Sources and citations

Every non-trivial factual claim links to a primary source. We prefer, in order:

1. Official framework documentation (MDN, Microsoft Learn, vuejs.org, react.dev, php.net).
2. Standards bodies (W3C, ECMA-262, WHATWG).
3. Security authorities (OWASP, NIST, PCI-DSS, NCSC).
4. Well-regarded secondary sources (CSS-Tricks for browser-compat tables, web.dev for performance, official vendor blog posts).

If a secondary source contradicts an official one, we follow the official source and explain the discrepancy.

5. Use of AI

We use AI tools in our editorial workflow in three ways:

1. Outline generation. AI drafts the table of contents and section headings. A human editor rewrites every heading.
2. Repetitive drafting. AI drafts boilerplate sections (introduction, prerequisites, conclusion, FAQ blocks). A human rewrites them.
3. Prose polish. AI suggests alternate phrasings, fixes spelling and grammar, and proposes headline variants. We accept or reject; we never publish AI output verbatim.

Every published article is then reviewed and technically verified by a human engineer before going live. We do not publish content that has not been read by a human reviewer with relevant expertise.

6. Independence

We do not accept payment in exchange for tutorials or reviews. We do not write content on behalf of vendors. Where we mention a product we use, it is because we use it — not because the vendor asked us to. If a vendor ever sends us review units, software licences, or travel sponsorship for a conference, we disclose it on the relevant article.

7. Affiliate links

Where we use affiliate links (for example, to a book on Amazon or a hosting service), the link carries rel="sponsored" and a visible "(affiliate link)" note. We only link to products we have personally used. Affiliate commissions never affect our technical recommendations.

8. Corrections policy

We take errors seriously. If you spot a typo, an out-of-date API call, or a broken code sample, please email team@mangobaz.com or use the contact form. We aim to fix reported errors within seven days; security-critical errors within 24 hours. Material corrections are dated and noted at the foot of the article.

9. Comment moderation

This Site does not currently host public comments below articles, to keep moderation overhead manageable and to avoid spam. Reader feedback is welcomed via email and is reviewed by the editorial team. If we enable public comments in the future, they will be moderated against the rules on this page.

10. Reader contributions

If you would like to propose a correction, a code improvement, or a new article, email team@mangobaz.com. Substantive contributions that meet our editorial bar will be credited to you on the article.

11. Accessibility

We aim to meet WCAG 2.1 AA. Every page has a skip-to-content link, semantic landmarks (<article>, <section>, <nav>, <main>, <header>, <footer>), descriptive alt text on images, sufficient colour contrast, and focus-visible outlines. If you find an accessibility issue, please report it.

12. Updates to this page

We may revise these standards. Material changes are highlighted at the top of this page for at least 30 days.