Hey, glad you’re here! If you’re interested in writing an article to publish on CSS-Tricks, you’re in the right spot. We put this little page together to give you everything you need to get started.<\/p>\n\n\n
sensation of lived experience and professional acumen<\/q>. (Frank Chimero<\/a>)\u00a0<\/li>\n<\/ol>\n\n\n\nWould you<\/em> be happy to land on this article from a search? Are you speaking to me, developer-to-developer, from experience?<\/p>\n\n\n
What you should write about<\/h3>\n\n\n
The best advice is something Chris Coyier wrote<\/a> a while back:<\/p>\n\n\n\n
\nWrite the article you wish you found when you googled something.<\/p>\n<\/blockquote>\n\n\n\n
There\u2019s a Frank Chimero quote that\u2019s equally relevant:<\/p>\n\n\n\n
\nMost design content has become poor quality, surface-level content marketing that does more damage than good, because it offers over-simplified, misinformed perspectives dressed up as guidance. One hardly gets the sensation of lived experience and professional acumen in the words.<\/p>\n<\/blockquote>\n\n\n\n
So, the bottom line is that we\u2019re looking for something that is referential and instructional, but also based on real-life experiences that connect with readers. It can\u2019t be documentation that the reader can get somewhere else, nor can it be a tutorial using the same example \u2014 modal, to-do list, meme generator, etc. \u2014 that is already well-covered in other tutorials. It\u2019s a specific situation of a learning discovery you made that resonates with readers personally and gives them something new to bookmark and use later.<\/p>\n\n\n
Audience, tone, and length<\/h3>\n\n\n
It probably goes without saying that front-end web designers and developers are our main audience. What might be less obvious is that they are coming from different points in their careers. Some are seasoned veterans from the table layout era, others may be getting into HTML & CSS for the first, while the rest are somewhere in between.<\/p>\n\n\n
Audience<\/h4>\n\n\n
The other thing to note is that “web design” and “web development” mean so many different things. One of the funny things we laugh about around here is that we’re called CSS-Tricks but tend to write about the larger field of front-end development. And that field is long and wide with many, many specializations<\/a>. We cater to all of them, whether we’re talking about code, design systems, accessibility, performance, typography, copywriting, semantics… and so on.<\/p>\n\n\n
Tone<\/h4>\n\n\n
We’re all friends around here! We like to keep the tone of our articles pretty chill. Some will be more technical than others. Some will be a little more opinionated than others. The best articles are those that explore ideas from multiple angles with an open mind that there’s usually more than one way to do something and the “best” way could depend on who is reading and what they’re working on.<\/p>\n\n\n\n
You can generally assume readers have basic knowledge of HTML, CSS, and JavaScript, except when covering those basics adds to the clarity of your article.<\/p>\n\n\n\n
The tone should be:<\/p>\n\n\n\n
\n
- Comprehensive and written for all experience levels<\/li>\n\n\n\n
- Technically detailed and correct<\/li>\n\n\n\n
- Practical, useful, and self-contained<\/li>\n\n\n\n
- Friendly but formal<\/li>\n<\/ul>\n\n\n\n
So, the best advice is to be yourself and write like we’re all gathered around a campfire talking shop.<\/p>\n\n\n
Length<\/h4>\n\n\n
We’re all about substance over quantity! The sweet spot for any article is somewhere in the range of 600-1,500 words<\/strong>. Articles can be short and sweet if they’re clear and useful. Similarly, articles can be longer if we’re dealing with a nitty-gritty topic with nuance and technical details.<\/p>\n\n\n\n
But again, clarity is the goal<\/em>.<\/p>\n\n\n\n
Speaking of which, the following things are great to help improve the clarity of your article:<\/p>\n\n\n\n
\n
- Relevant images and videos.<\/strong> Visual aides are strongly encouraged. Be sure that images have proper
alt<\/code> text and captions (if needed). No memes, please.<\/li>\n\n\n\n- Blocks of code.<\/strong> They help demonstrate concepts. But focus on just the most relevant parts of the code rather than plopping an entire file on the page.<\/li>\n\n\n\n
- Demos.<\/strong> CodePen<\/a>, if possible; other interactive code embeds, if needed. Demos are perfect for demonstrating a proof of concept or finished work.<\/li>\n<\/ol>\n\n\n
Payments<\/h3>\n\n\n
We do indeed pay you for any of your work that we publish. You put in the work, after all!<\/p>\n\n\n\n
We pay $250 USD<\/strong> for the vast majority of articles, which is paid either via PayPal or in the form of DigitalOcean credit. Please be sure that PayPal is supported in your country, otherwise we’ll go the DigitalOcean credit route.<\/p>\n\n\n
Guest writing application<\/h3>\n\n\n
We ask everyone to fill out this form to guest post on CSS-Tricks, whether you have written for us before or are a new writer. We will never share your private information without your express permission.<\/p>\n\n\n\n
You’ll be asked to attach a rough draft of your idea to give us a sense of your writing style and professional experience. It doesn’t have to be perfect. There will be<\/em> an editing process to clean things up. And if you don’t have the time to write a draft, you’re welcome to submit a brief outline of the key points instead \u2014 but you will write a draft at some point in the process if your application is accepted. 😉<\/p>\n\n\n\n
One final note: We review applications weekly and we get a lot of them<\/em>. Every application is looked at and, even though we try our best to follow up on all of them, we prioritize responding to accepted applications.<\/p>\n\n\n\n
Open Application<\/summary>\n
<\/p>\n\n\n