Editorial policy

Each indexed page should solve a distinct task. Exact conversion pages serve immediate tool intent, while guides cover comparisons, implementation details, object-key transformations, or framework boundaries. We avoid creating additional near-duplicate pages unless usage or Search Console data shows a distinct need.

Primary documentation is preferred for claims about language style, browser APIs, libraries, frameworks, and serialization behavior. Secondary sources may add context, but they do not replace authoritative documentation for technical facts. Converter-specific claims are checked against the site’s implementation and tests.

Code examples and edge cases should be reproducible. Guide pages show their publication and last-reviewed dates, and those dates are changed only when the underlying page has actually been published or substantively reviewed. Review metadata is not backdated for SEO.

When a reported issue can be reproduced, we update the relevant converter rule, example, source, or explanation and add regression coverage when practical. Framework or platform guidance is revisited when upstream documentation changes materially.

Automation or AI may assist drafting, translation, code review, or quality checks. Automated output is not treated as a source. Published technical claims should still be supported by reproducible behavior, repository tests, or primary documentation, and localization is checked for untranslated English leakage.