CSS-Tricks vs In Plain English for frontend content placement

If you’re choosing between CSS-Tricks and In Plain English for frontend content placement, the best choice depends on your goal:

CSS-Tricks

Best for: established frontend authority, deep technical content, niche dev audience
Why place content there:

• Strong reputation in the frontend/CSS/JS space
• Good fit for technical tutorials, advanced patterns, and implementation-heavy posts
• Audience tends to be more experienced and likely to appreciate detail
• Better if your content is meant to build authority or target developers specifically

Potential downside:

• More demanding editorial tone; content usually needs to be polished and highly practical
• Audience may be less forgiving of surface-level or overly promotional pieces

In Plain English

Best for: broad developer reach, approachable tutorials, easier readability
Why place content there:

• More accessible, beginner-friendly style
• Good for high-level frontend guides, “how-to” posts, and educational content
• Often better for discoverability and a wider dev audience
• Works well if you want content that is simple, clear, and easy to repurpose

Potential downside:

• Less “prestige” than CSS-Tricks in the frontend community
• Technical depth may need to be lighter or more explanation-driven to fit the tone

Quick recommendation

• Choose CSS-Tricks if your content is deep frontend expertise, performance, CSS architecture, advanced JS, UI engineering, etc.
• Choose In Plain English if your content is accessible tutorials, broader frontend education, or you want simpler distribution.

If your goal is...

• Brand authority in frontend: CSS-Tricks
• Ease of reading and broad reach: In Plain English
• Advanced technical credibility: CSS-Tricks
• Beginner/intermediate tutorials: In Plain English

If you want, I can also compare them on:

1. audience quality,
2. SEO/value for backlinks, or
3. best content formats for each platform.