Stackify’s website and blog attract more than 60,000 monthly visits. We aim to provide high quality content that is valuable to the developer community. We’re always looking for contributors to share relevant information to our users. If you have technical writing skills and knowledge of the software development industry, we’d love to hear from you.
Please take some time to review our guidelines. It will give you a better understanding of the type of content, tone, and format that we want to publish.
Content Guidelines, Topics, and Process
We look for content that provides solutions and value to our users. Our focus is on .NET and Java developers around these types of topics:
- Cloud computing best practices – Azure, AWS, GCE, etc
- Application performance tips & best practices
- Developer culture & industry trends
- Developer tools
It’s important the articles help solve a problem or teach users something. We’re also interested in publishing any topic that developers care about, which includes things like hiring, team development, job skills, etc.
We also look for the following:
- Unique concepts, compelling arguments, and high-quality writing. We will not republish anything that’s been published elsewhere.
- Article reflects the writing style/tone of Stackify’s Blog. We aim to be casual and entertaining, yet informative and professional.
- Proper references and quotations included
Ideal Post Types & Formats
We love these types of posts:
- List style articles of tips, best practices
- “How to” topics
- Developer tools reviews or tutorials
- Product comparisons
We are open to additional posts, but these types are given top priority.
- Long-Form: These posts give readers in-depth tactical takeaways that are supported by relevant, recent examples, original quotes, original graphics, and current data. These articles are typically 1,500 words and above. When readers finish this type of post, they should be able to immediately execute on the given topic and have very few questions left on how to do it.
- Shorter Blog Posts: Usually, these feature a few paragraphs of introduction, original graphics, and helpful tips. These articles should be comprehensive and easy to read, have a compelling narrative, contain plenty of white space, and feature timely information. These articles should be 750 words and above.
- Lists: Everyone loves lists. These posts focus on providing a list of tips or tools.
Writing Style Tips
Readers love easy to consume content, but most readers are likely to skim through. The usage of headings, images, and lists are key to making it easy to read. Articles should provide examples, references, screenshots, and data to back up your claims and tell a story.
Here are some critical tips we recommend:
- Avoid large “walls” of text – nobody wants to read a novel!
- Try to limit paragraphs to 4 sentences – feel free to make 1-2 sentence paragraphs
- Break the content up into multiple sections with headings and subheadings
- Utilize images, screenshots, and code samples where possible
What We Won’t Accept
- Anything that’s been covered on our blog before
- Poor content created only for link-building
- Anything that’s too promotional for your company or organization
How to Submit Your Post
Please email [email protected] with the following:
- Your completed post as a Word document or link to a Google document
- Image files (with attribution) embedded in the doc or separately
- Short author bio including a maximum of one anchor text link to your own website
- We cannot allow you to republish your guest post to your own blog, LinkedIn, Medium, or Inbound.org afterward. Why? Because duplicate content isn’t a good practice and we try to keep Google happy.
- Feel free to share links to any of our content by email and social media.
- Feel free to reference or quote up to 75 words of any of our text content (facts, figures, quotes, etc.) in your own blog articles, presentations, documents, etc.
- Our marketing team reserves the right to edit and adapt your guest blog content as we see fit, and update it in the future. Stackify reserves the right to include calls-to-action to Stackify content, including but not limited to email newsletters, ebooks, and other downloadable content.
- Please attribute Stackify as the source and link to the original Stackify source you’re referencing.
What’s In It For You (besides great exposure)?
- Your article could be chosen as one of our focus posts. These posts get special treatment in the form of email, social and paid promotion. This includes emailing tens of thousands of people on our newsletter list.
- You can promote your Pluralsight content, consulting company, etc
- Stackify will try to retweet, share, and/or like your post through our social media channels. Please just let us know when you’re posting.
- You may be asked to contribute content on a regular basis on our blog, but also on our BuildBetter eMag publication.
- You get the opportunity to build highly relevant and high quality backlinks to your site
If your article meets editorial standards and aligns with our content strategy, we will respond to let you know your article will be published, or not, as fast as possible. Getting the content live may take up to 2 weeks.
Thank you! We look forward to working with you!