{"id":187280,"date":"2014-10-29T09:06:07","date_gmt":"2014-10-29T16:06:07","guid":{"rendered":"http:\/\/css-tricks.com\/?page_id=187280"},"modified":"2024-06-28T10:19:01","modified_gmt":"2024-06-28T17:19:01","slug":"guest-writing-for-css-tricks","status":"publish","type":"page","link":"https:\/\/css-tricks.com\/guest-writing-for-css-tricks\/","title":{"rendered":"Write for CSS-Tricks!"},"content":{"rendered":"\n
We’re in the process of accepting new article proposals after a long hiatus. There’s still work to do and we will drop an application at the bottom of this page when we open the doors.<\/p>\n\n\n\n
Interested in guest writing for CSS-Tricks? We love guest writers<\/a> around here! It’s always a win-win-win.<\/p>\n\n\n\n In other words:<\/strong> Would you<\/em> be happy to land on this article from a web search? Are you speaking to the reader, developer-to-developer, based on your personal and professional experience?<\/p>\n\n\n We’re looking for technical<\/strong>, referential<\/strong>, and instructional<\/strong> content and veer away from editorial think pieces<\/a>. You might start with “How to X” by default, where “X” is somewhere in the realm of building websites. We also skew toward front-end topics (e.g. HTML, CSS, and JavaScript).<\/p>\n\n\n\n We prefer if you are motivated because you have something you very much want to share. <\/strong>You have a deep knowledge<\/em> on this topic. You are excited<\/em> about it. You’re ready<\/em> to tell people about it on CSS-Tricks. That’s what makes for good guest writing on CSS-Tricks.<\/p>\n\n\n CSS-Tricks readers are mostly front-end web designers and developers at all different points in their professional career. We’re not going to tell you to write for “beginners” or “experts” \u2014 strive for clarity<\/em> instead. Everyone appreciates an article that makes technology approachable and understandable.<\/p>\n\n\n\n That said, you can generally assume that readers have at least basic knowledge of HTML, CSS, and JavaScript, except when covering those basics adds to the clarity of your article.<\/p>\n\n\n Voice and tone are related<\/em>, but different<\/em> concepts. Your voice rarely changes, but your tone does depending on the situation.<\/p>\n\n\n\n As far as voice goes, CSS-Tricks is far from what you’d call an academic source of content. Sure, articles are educational in nature but we approach them in clear terms<\/strong> that are devoid of technical jargon<\/strong>. In most cases, we like to think that the voice of any given article is like a conversation<\/strong> between two front-enders talking shop.<\/p>\n\n\n\n The tone you use to make your points may change throughout the content. If you’re excited, write with excitement<\/em>. If you’re frustrated, it’s okay to vent<\/em> a little. Your tone is what makes your article personable to readers.<\/p>\n\n\n\n In general, however, your tone will be:<\/p>\n\n\n\n The loose goal is 600 words<\/strong>. An article can be shorter if it’s extremely useful and clear. Or an article might need between 1,000-2,000 words to properly cover a more complex topic. If you find yourself at around 1,500 words, that’s a good point to pause and look for opportunities for brevity.<\/p>\n\n\n\n We do consider longer articles but those are typically reserved for super comprehensive topics formatted as guides<\/a>.<\/p>\n\n\n\n Always good to include:<\/strong><\/p>\n\n\n\n\n
Table of Contents<\/h3>\n
\n
Guiding principles<\/h3>\n\n\n
\n
The types of content we accept<\/h3>\n\n\n
\n
What you should write about<\/h3>\n\n\n
Who you’re writing for<\/h3>\n\n\n
Voice and tone<\/h3>\n\n\n
\n
\n Examples <\/summary>\n \n\n
\n
Length<\/h3>\n\n\n
\n
\n
alt<\/code> text and a caption. Just make sure the images support the content; we wanna avoid memes.<\/li>\n\n\n\n
\n