Guest Post Guidelines

Complete guidelines for pitching and writing a guest article for OmniColor. If you have read our Write for Us page and want the full detail, this is it.

Topics We Publish

We publish articles that fit these categories:

Color Theory & Science

  • Color harmony — complementary, analogous, triadic and beyond
  • Color perception — how the eye and brain process color
  • Color spaces — sRGB, Adobe RGB, Display P3, CIE Lab, OKLCH
  • Color difference — Delta E, perceptual uniformity
  • Color psychology — proven vs assumed claims

Design & Development

  • Design system color architecture
  • CSS color — modern syntax, custom properties, functions
  • Gradients — linear, radial, conic, mesh, animated
  • Accessibility — WCAG 2.2, APCA, color blindness
  • Framework color systems — Tailwind, Material, Bootstrap

Practical Guides

  • Building a brand color palette
  • Extracting colors from images
  • Implementing dark mode
  • Designing accessible interfaces
  • Choosing colors for data visualization

Topics We Do NOT Publish

We will not accept articles about:

  • "Top 10 best [color tools]" listicles
  • Product reviews or comparisons
  • Sponsored content or anything with promotional intent
  • Content that duplicates existing OmniColor articles
  • Content that has already been published elsewhere
  • AI-generated content presented as original writing
  • Content that primarily exists for SEO or backlinks
  • Content that contradicts established color science
  • Content that promotes paid tools without clear disclosure

Article Requirements

Length

  • Short articles: 800-1,200 words
  • Standard articles: 1,200-2,000 words
  • In-depth guides: 2,000-4,000 words

Length should be driven by content, not padded to hit a target. A tight 900-word article beats a bloated 2,000-word one.

Structure

  • H1: Clear, descriptive headline (sentence case)
  • Introduction: 2-3 sentences establishing the topic and why it matters
  • 2-4 H2 sections: Each covering a distinct sub-topic
  • H3 subsections: Where useful for breaking down H2s
  • Examples: Real color values, code samples, use cases
  • Conclusion: 1-2 paragraphs with actionable next steps
  • Author bio: 1-2 sentences

Formatting Requirements

  • Headings: Sentence case ("Color theory basics", not "Color Theory Basics")
  • Oxford comma: "red, green, and blue" not "red, green and blue"
  • Code blocks: Specify the language for syntax highlighting
  • Inline code: Use for values, commands and short code snippets
  • Links: Descriptive link text, never "click here"
  • Lists: Use for parallel items or sequential steps
  • Emphasis: Use bold for key terms, italic for emphasis — never for style alone

Technical Accuracy

Every factual claim must be verifiable:

  • Color formulas — cite the W3C CSS Color Module Level 4 or other primary specification
  • WCAG claims — cite the W3C WCAG 2.2 specification
  • Research papers — cite with a link to the abstract or DOI
  • Statistics — cite the original source, not another blog post
  • Browser support — verify with Can I Use or MDN

If you are unsure about a claim, either verify it or remove it. We will fact-check everything before publication.

Originality

Articles must be original — no exceptions:

  • Not previously published anywhere (including your own blog)
  • Not AI-generated content presented as your writing (AI-assisted drafting is fine, but you must substantially edit and verify)
  • Not a rewritten version of an article from another site
  • Not submitted to multiple sites simultaneously

We run every submission through plagiarism checks.

Author Byline

Accepted articles are published with:

  • Author name (your real name)
  • 1-2 sentence bio
  • One link to your website, portfolio or relevant profile (no promotional links)

We do not accept articles from anonymous authors or ghostwritten content presented under someone else's name.

Links Policy

Legitimate links are encouraged:

  • Source citations: Link to primary sources (W3C, MDN, research papers)
  • One self-link: You may link once to your own relevant work (e.g., your portfolio, a related article you wrote)
  • No affiliate links
  • No paid links
  • No links to competitors
  • No links to irrelevant sites

Links are subject to editorial review. We may remove links that do not meet these criteria.

Rights

By submitting an article for publication:

  • You confirm the article is your original work
  • You grant OmniColor a permanent, non-exclusive license to publish and distribute the article in any medium
  • You retain copyright and may republish on your own site after 90 days, with attribution back to OmniColor
  • You confirm you have permission for any third-party content included
  • You agree to our editing for clarity, accuracy and SEO

Editorial Process

  1. Pitch: You send a pitch (see below) with topic, outline and credentials
  2. Response: We respond within 10 business days — accepted, declined or request for revisions
  3. Draft: If accepted, you write the full article (typically 2-4 weeks)
  4. Editorial review: Our team reviews for accuracy, clarity, formatting
  5. Revisions: You may be asked to revise 1-2 times
  6. Publication: We schedule and publish — you are notified when live

How to Pitch

Send to editorial@omnicolor.pages.dev with subject "Guest Post Pitch — [Topic]".

Include:

  • Proposed title
  • Short outline (3-5 bullets of what you will cover)
  • Your credentials — 1 paragraph on your background and why you are qualified
  • 2-3 writing samples — links to previously published work
  • Estimated length and turnaround time

Do not send the full article in the initial pitch — send it only after acceptance.

What We Do NOT Pay

OmniColor does not currently pay for guest articles. This is disclosed upfront so there is no misunderstanding:

  • We are a small independent project
  • Advertising revenue covers infrastructure, not contributor payments
  • What we offer: byline, bio, one backlink, permanent attribution

If this ever changes, we will update this page prominently.

Common Rejection Reasons

  • Topic already covered on OmniColor
  • Pitch is too vague or too broad
  • Content is not technically accurate
  • Article is primarily promotional
  • Writer's credentials are insufficient for the topic
  • Writing quality is not up to standard
  • Article appears to be AI-generated without substantial editing

If we reject your pitch, you may pitch again with a different topic.

Contact

All guest post inquiries: editorial@omnicolor.pages.dev

See Also