Editorial policy

How we write and check what we publish

XCODX publishes developer guides, error fixes, comparisons and product documentation. This page explains who writes them, where the facts come from, how they are checked before they go live, how we use AI tools, and what happens when we get something wrong.

Effective: 10 November 2026Last updated: 10 November 2026

01 Who writes it

Everything on xcodx.io is published by the XCODX.io team, the same people who build the XCODX Studio editor, the online compiler and the framework playgrounds. Articles are credited to the team rather than to an individual. More about who we are and why we build XCODX is on the About page.

Because we write about the tools we build and use every day, most articles are grounded in work we can run and check: the code in a guide is the kind of code you can paste into the editor, and the error messages in a fix are the ones the tools actually print.

02 What we publish, and why

  • Guides and best practices that explain a language, framework or technique end to end.
  • Error fixes that name the exact error text, the causes behind it and the fix for each cause.
  • Comparisons and library round-ups that help you choose between tools.
  • Product pages and documentation for the editor, the compiler, the playgrounds and the Help Center.

Each page is meant to answer one question well for a developer who needs the answer now. Each tool page explains a different way to work with that technology, and each article covers one topic.

03 Research and sources

Facts come from primary sources first: official documentation and release notes (for example MDN, react.dev, vuejs.org, nodejs.org, php.net and each product's own pages), the specification where one exists, and the tools' own output. For claims about what is current or popular, we use recent, dated sources such as official changelogs, the State of JS and State of CSS surveys, and package download statistics.

Anything that changes often, such as version numbers, prices, feature lists and "best of the year" picks, is re-checked at the time of writing and dated in the article where it matters.

04 Checks before an article is published

An article ships only when all of the following are true:

  • Every factual claim has been checked against a current, authoritative source. If a fact cannot be verified, it is left out or clearly hedged; numbers are never guessed.
  • Nothing is invented or out of date.
  • Comparisons state the genuine strengths and weaknesses of each side.
  • The structure is clear: one topic, a direct answer near the top, and headings that match what the reader is looking for.
  • The prose is original and free of filler. We do not pad an article to reach a word count.
  • The article links to related material and ends with a useful next step.

05 How we use AI tools

We use AI assistants to help gather and cross-check sources and to help draft and edit text. They do not decide what is true. Every AI-assisted draft goes through the same research and checks described above, and claims that cannot be traced to a reliable source are removed before publishing.

We do not use AI to mass-produce pages, to invent authors, reviews or experiences, or to rewrite other sites' content.

06 Comparisons and our own product

Some articles compare XCODX with other online editors such as CodePen, CodeSandbox, StackBlitz, JSFiddle, Replit and VS Code for the Web. We make XCODX, so we have an obvious interest in those comparisons. To keep them useful anyway, we describe each competitor accurately, say where it is the better choice (for example a larger community or full cloud virtual machines), and never misrepresent another product.

Our articles contain no paid placements and no affiliate links. Products and libraries are included because they are relevant, not because anyone paid for them.

07 Advertising and independence

XCODX is free and is funded by advertising served by Google AdSense. Ads are placed automatically by Google, appear in clearly separate ad units, and are never written to look like our content. Advertisers have no say in what we write. We do not show ads inside the full-screen editor and compiler workspaces or on our policy pages. Details of how advertising uses cookies are in our Privacy Policy and Cookie Policy.

08 Dates, updates and corrections

Every article shows the date it was first published and, when it has been materially revised, the date it was last updated. We revisit articles when the tools they describe change.

If you find a mistake, please email hello@xcodx.io with the page address and what is wrong. We check every report; when a correction is needed we fix the article and update its date.

09 What we will not publish

  • Content copied, scraped or lightly reworded from other websites.
  • Pages that exist only to rank for a search phrase without helping the reader.
  • Fake reviews, invented quotes, invented statistics or made-up author profiles.
  • Advice outside software development presented as professional advice. See our Disclaimer.

10 Contact

Questions about this policy, a correction, or a topic you would like us to cover? Email hello@xcodx.io or use the contact page.