HubSpot Developer Blog Contributor Guidelines

Last updated:

Are you looking to contribute to the HubSpot Developer Blog? Read our guidelines below to find out who our blog’s target audience is, what kind of content we publish (and don’t publish), where you can submit to become a contributor, and how HubSpot will help amplify your content.

The goal of our blog and our target audience

The goal of the HubSpot developer blog is to inspire and educate developers with relevant, impactful, and quality content pertaining to web development on the HubSpot platform. Our blog is tailored toward a technical audience at any level in their developer journey. These individuals are typically identified by the following roles/titles in an organization:

  • Web Developers including Front-End (FE) or Back-End (BE) developers
  • Technical Leaders
  • Solution Architects
  • Revenue Operations (RevOps)

What kind of content do we publish?

The HubSpot Developer Blog covers various types of content including (but not limited to):

  • Tutorials/How-to’s: This category of content includes any resource article that walks users through the creation process for a project. These posts perform best when code and screenshots are included.
  • Use Cases: This category of content includes resources highlighting the various ways to use the HubSpot platform. These posts perform best when the use case incorporates projected and actual business value of the project with the technical implementation.
  • Best Practices & Thought Leadership: This category of content includes resources that are rooted in an opinion accompanied by relevant research, best practices, and/or procedures.
  • Guides: These are longer articles with detailed information and research that is presented to educate individuals on a topic, theme, feature, or functionality.

What content will we not publish?

We value working with individual contributors from the HubSpot developer community. But, we must first make sure the content is relevant to our audience. We do not accept any of the following:

  • Content submitted on behalf of another person: The content submitted for contribution must be created by the individual who submitted it (you).
  • Re-Syndication of content: If the content is already published on HubSpot or another website or platform such as (but not limited to) Medium, Dev.to, LinkedIn, etc., we will not re-publish this content.
  • Promotional pieces: Content that is purely for marketing or promotional purposes of a product or service that is not related to HubSpot.
  • Product walkthroughs, reviews, or demonstrations: Content that simply walks through using a product/application or reviews a product/application.
  • Tool Comparisons: Unless specifically related to HubSpot functionality, such as deprecations, we will not publish content that compares two tools.
  • Roundups: Content containing “Top 15 plugins” or other content that is a collection of apps, assets, or services only.

What does HubSpot do to help promote submitted content?

Once a contributor’s content is submitted, approved, and ready to publish, we will amplify that content on HubSpot developer channels:

  • Social Media channels:
    • HubSpot’s Developer Twitter Account
    • HubSpot’s Developer Slack Workspace
  • HubSpot Developer Newsletter

While we do our best to share content we cannot guarantee when and where your content will be shared.

What is the process for contributing content to the HubSpot Developer Blog?

Below outlines our process for contributing content to the HubSpot Developer Blog.

Step 1: Apply to contribute content

Fill out our form below and provide us with the required information. Upon review of your submission, which can take up to 10 business days, a member of our team will reach out to notify you if you have been approved as a contributor to the blog.

Step 2: Topic assignment and selection

We value working with our contributors in a guided approach. We will work with you and review the submitted topic ideas along with providing additional topics for possible content where applicable. The contributor will then choose one topic to create content on.

Step 3: Content creation

Once the topic has been approved, our team will provide the contributor with a shared document template. This template will provide an example of the typical flow of content for our blog posts and all content for the post will then be entered into this document. Our team will check in from time to time throughout the content creation process and will be available as a resource to the contributor during the content creation process. We ask that contributors create their content no later than 15 business days from the topic assignment.

Step 4: Review Process

During content creation and also upon completion of the content, our team will review your post for:

  • Technical accuracy
  • Content flow
  • Spelling and Grammar

Our team will provide feedback and direction through the use of comments within the provided document.

Step 5: Scheduling and Publication of content

Once content has been finalized and is scheduled for publication, our team will provide you with the following information:

  • Date of content publication
  • Final URL of published content

Terms and Conditions - aka the fine print

As a guest contributor, by submitting your interest in contributing you agree to the following terms and conditions:

  • Your content cannot be copied or plagiarized from any other source. So please apply proper attribution of public data, quotations, and outside content referenced in the article.
  • You will not disclose any confidential or sensitive HubSpot information that is not public (e.g. roadmaps, non-released features) without reaching out to us first.
  • Your content will not contain anything that's offensive or inaccurate.
  • Your content will not be overly critical or disparaging of individuals or companies (e.g. competitors or HubSpot integrators) — this is not a place to air grievances.
  • HubSpot reserves the right to reject any content at its discretion during any point of the contribution process.
  • In rare cases, contributed posts may be removed from the blog and we may recycle the URL.
  • Hubspot reserves the right to edit and adapt your content as needed for clarity, SEO, accuracy, and comprehensiveness on the topic. If the meaning of the content is in question we will let you know prior to edits.
  • HubSpot reserves the right to include calls-to-action to HubSpot content, including but not limited to email, newsletters, ebooks, white papers, and other downloadable content.
  • HubSpot reserves the right to use your likeness across our content as we see fit, including but not limited to HubSpot’s social media channels.

Apply to contribute content

We’re excited to have you contribute to our Developer Blog! Check out our recommended topics below or suggest your own while you apply to contribute in our form below.

Below is a list of recommended topics, if you are interested in any of these, please indicate it on the form below.

Application Form