Editorial Policy

Last updated: January 10, 2025

Our commitment

OmniFonts publishes technical articles, guides, and reference content about typography, fonts, CSS, and web performance. This content exists to help designers and developers make accurate decisions. To earn and keep that trust, every article must be:

  • Accurate — verifiable against primary sources
  • Original — not a rewrite of an existing article
  • Useful — solving a real problem, not padding word count
  • Honest — including clear statements of limitations and unknowns

Authorship

OmniFonts publishes under a collective byline: OmniFonts Editorial Team. We do not invent individual author personas or fabricate credentials. Articles are researched, written, and reviewed by the team, and the team is accountable for the content.

You can read more about our editorial team and sourcing standards on the Authors page.

Sources we use

Technical claims are verified against primary sources, including:

  • The Unicode Standard — for character encoding, Unicode blocks, script coverage, and text processing claims
  • The OpenType Specification — for font tables, format internals, and metadata claims
  • The W3C CSS Fonts Module — for CSS property syntax, font descriptors, and browser behaviour
  • WCAG 2.2 — for accessibility claims, contrast ratios, and readability guidance
  • MDN Web Docs — for browser support and API documentation
  • Real browser testing — for any behavioural claim, we test in Chrome, Firefox, Safari, and Edge

Where a claim cannot be verified against a primary source, we state it as observation rather than fact, or remove it.

Review process

Every article goes through the following process before publication:

  1. Research — gather sources, test claims, gather real examples
  2. Draft — write the article with original examples, not lorem ipsum or fabricated data
  3. Technical review — every code sample is executed, every browser behaviour claim is tested
  4. Editorial review — readability, structure, clarity, and factual consistency check
  5. Fact-check — every statistic, quote, and citation is verified against its source
  6. Publication — with publication date and version tracking

Corrections

We make mistakes. When we discover an error, or when a reader reports one, we:

  1. Verify the error against primary sources
  2. Update the article to correct the error
  3. Add a correction note explaining what was changed (for substantive corrections)
  4. Update the "Last updated" date

Minor typo corrections are made silently. Substantive corrections (changed facts, changed recommendations) are noted. If you find an error, use the Contact page to report it.

AI disclosure

OmniFonts uses AI-assisted tooling for drafting and editing support, but every published article is:

  • Researched by a human against primary sources
  • Verified for technical accuracy through real testing
  • Reviewed and edited by a human editor before publication

We do not publish AI-generated content that has not been verified. We do not use AI to fabricate authors, credentials, statistics, or citations. Every claim in every article is either verified against a primary source or stated as observation.

Independence and funding

OmniFonts is funded by the site operator and, when enabled, by standard display advertising (AdSense). Advertising does not influence editorial content. We do not accept payment for positive reviews, do not accept sponsored posts presented as editorial, and do not recommend tools or services in exchange for compensation. If we ever introduce affiliate links or sponsored content, it will be clearly disclosed at the top of the article and in the article body.

What we do not do

  • We do not fabricate research, statistics, tests, or citations
  • We do not publish thin content — articles that repeat what already exists elsewhere without adding original value
  • We do not keyword-stuff — articles are written for readers, not for search engines
  • We do not generate hundreds of programmatic pages to capture long-tail queries without substantive content on each page
  • We do not use fake authors or credentials — the team byline represents real people doing real review
  • We do not publish AI-generated content that has not been human-verified

Content categories

The OmniFonts blog covers the following categories, all with original, verified content:

  • Font Guides
  • Typography Tutorials
  • Font Psychology
  • Font Comparisons
  • Web Typography
  • CSS Font Tutorials
  • Google Fonts Guides
  • Font Licensing
  • Font Formats
  • Typography Design
  • Font Pairing
  • Accessibility
  • Developer Resources
  • Typography Research
  • Design Trends

Not all categories have published articles yet. Empty categories are honest — we publish when we have substantive content, not to fill a schedule.

Reader interaction

We welcome corrections, questions, and feedback at the Contact page. We do not publish reader comments, because comments require moderation infrastructure and can introduce unverified content into an otherwise curated space.

Updates and review cadence

Technical content ages. We review and update existing articles as specifications change or as browser behaviour changes. Articles showing a "Last updated" date more than 2 years ago should be treated with appropriate caution — we do our best to keep things current, but standards evolve.

Contact

For editorial questions, corrections, or feedback, use the Contact page. For privacy questions, see the Privacy Policy. For licensing questions, see the Licensing page.