Editorial Standards
Last updated:
Jsonic publishes developer guides on JSON, JSON Schema, JWT, and related data formats. These standards describe how each guide is researched, written, reviewed, and updated. They also describe how to report errors, what we will and will not cover, and how we monetize the site.
Scope
We cover JSON itself (RFC 8259, ECMA-404), JSON Schema, JWT/JWK/JWE, related serialization formats (YAML, TOML, CSV, XML, Protobuf, MessagePack), and language-specific parsing and serialization in JavaScript, TypeScript, Python, Go, Rust, Java, Kotlin, Swift, C#, PHP, Ruby, Dart, and Bash. We do not cover unrelated web-development topics, framework tutorials beyond their JSON handling, or general programming theory.
Source Tiering
Every factual claim is sourced. We tier sources by authority:
- Tier 1 — Primary sources. RFC and IETF specs, ECMA standards, W3C specs, official language and library documentation (e.g., docs.python.org, MDN,
cppreference.com), and source code of the implementations we describe. Every guide cites at least one Tier 1 source. - Tier 2 — Primary research. Reproducible benchmarks we ran ourselves, our own test results across runtime versions, and published methodology from third-party benchmarks (e.g., TechEmpower, bun-bench).
- Tier 3 — Reputable engineering writing. Engineering blogs from companies maintaining the library or runtime in question.
- Not cited. Stack Overflow answers, AI-generated content from other sites, and tutorials that do not themselves cite primary sources.
Methodology
Each guide follows a fixed process. (1) Identify the user query and the top three ranking competitors. (2) Identify what the top results do not cover. (3) Write to a content brief with a direct first-paragraph answer, a Key Facts box with specific numbers, at least one comparison table or decision matrix where applicable, and a FAQ section answering real People-Also-Ask queries. (4) Validate every code example by running it against the current stable release of the library or runtime described. (5) Cite all sources inline using anchor tags rather than footnotes.
Update Cadence
Every guide is reviewed at least once per year. Guides covering rapidly-changing topics (recent framework releases, library APIs in active development) are reviewed every six months or whenever a major version ships. The visible “Last updated” line on each guide reflects the most recent substantive edit, not file-level metadata changes.
Correction Policy
If you find an inaccuracy, broken example, or outdated reference, report it. We respond within 7 days. Corrections that change a factual claim are noted in the guide's edit history. Cosmetic edits (typos, formatting, dead-link replacements) are made silently. Open a GitHub issue at github.com/leeht/jsonic or email hello@jsonic.io— please include the URL of the guide and a quote of the specific text in question.
Authorship and Conflicts of Interest
Guides currently publish under the “Jsonic” collective byline. We are transitioning to individual author bylines with biographies and verifiable public identities; until that work is complete, the editorial team takes joint responsibility for every guide. We do not accept paid placements, sponsored content, guest posts, or backlinks-for-pay. No guide recommends a product because of an affiliate relationship.
Monetization Disclosure
The site is monetized with Google AdSense. Ads appear in clearly demarcated containers and do not influence editorial coverage. AdSense uses cookies for personalization; the full data-collection details are in our privacy policy. No content on the site contains affiliate links. If that ever changes, every affiliate link will carry rel="sponsored" and a first-fold disclosure consistent with FTC 16 CFR §255.5.
Accessibility and Reproducibility
Every code example is plain-text and selectable. Diagrams are described in adjacent prose so the content is usable without rendered images. We do not paywall any content. The site does not require an account, and all tools run client-side without uploading user data.