GitHub Marketplace blog post guidelines
As the home for developers large and small, GitHub is committed to ensuring that partners have a voice on our platform. In order to provide an open and transparent process, all guest and partner posts must be submitted through the request for proposal (RFP) process.
Request for proposal (RFP) process
We are continuously accepting proposals for GitHub Marketplace blog posts. Please submit complete, well-defined topic ideas with outlines so we can accept your submission and move it forward in the blog post process.
Graphics in guest and partner posts must be approved during the writing process. If you need help creating simple graphics (graphs, charts, or headers), we may be able to provide assistance depending on timing. However, preference will be given to posts that already include visuals.
- Blog posts should be submitted to firstname.lastname@example.org by April 10 for consideration in the current review session.
- You must not republish your guest post elsewhere, such as to your own blog, LinkedIn, or Medium.
- We reserve the right to edit, adapt, and update your blog post content for accuracy and comprehensiveness.
Writing a successful post
Partner posts must be:
- Actionable, useful, and relevant. The blog audience includes the entire GitHub community, as well as individual developers, open source aficionados, enterprise customers, and more.
- In the context of a GitHub workflow. Posts must clearly demonstrate how a product can improve your GitHub workflow. For example, users should be able to easily understand the inherent value of an integration without connecting any dots.
- Technical, inspirational, or informational. Posts must not be ads or snippets.
- More educational than promotional. It's more important for posts to show our audience how to do something, rather than promote an app or integration.
- Appropriately introduced and attributed. Posts must be framed as partner posts with front and end matter introducing the partner. Proper attribution of data, quotations, and outside content must be referenced in the article.
- Generally positive. Posts should not highlight any deficiencies of GitHub as a platform.
Additionally, we look for:
- Original concepts, compelling arguments, and high-quality writing. We will not re-publish anything that's been published elsewhere.
- Style and tone of the GitHub Blog. We aim to be casual, yet helpful (typically, we avoid buzzwords and jargon).
- Minimal sponsored links. No more than one link to your company's website in the body of the post.
Examples of effective posts
- Migrating to GitHub Apps: Code Climate shares their story
- Keep your dependencies secure and up-to-date with GitHub and Dependabot
Submit blog posts to email@example.com for consideration.