This is a very common story and is one of the big reasons you should invest in writing good documentation for your product. The documentation is the relationship manager between your product and the developers. Good documentation makes the life of developers easy by explaining the features of your product, whereas bad documentation can frustrate and drive away the developers, even if your product is superb and does a fantastic job! Good documentation also lifts the burden from your support team because if developers can get answers to their questions from the documentation, they won’t need to bother the support team with their issues. Believe me, no developer likes filling out a form and waiting multiple days for an answer from the support team when they can get their answers from the documentation.
The other article explained what makes documentation good. In this article, you’ll see some real-life examples of good documentation. You can take inspiration from these amazing documentation examples and apply the learnings the next time you create documentation.
Before you jump into the list, let’s take a moment to understand the parameters these entries have been judged on:
Now, without further ado, let’s get to the list.
Note: This is not an exhaustive list by any means. This list is purely opinion-based, and you might find a tool that you feel has better documentation than any tool in this list. Remember that the goal of this article is to inspire you, not to judge tools based on their documentation.
Stripe is revered by developers as having one of the best documentation. The documentation home page is designed neatly with tabs at the top that link to the documentation for each product, such as Payments, Developer tools, and No-code. The home page also shows some example snippets that give an idea of some of the important functions of the tool at a glance:
The documentation provides great starting points in the form of quick starts and clonable sample apps. The documentation covers a wide range of ways to use their products, including APIs and SDKs.
The documentation is accompanied by adequate examples. Each example is in-depth and complete. And the best part is that you can choose the language and framework of the examples. You can also mix and match frameworks; for example, Android SDK, Kotlin frontend, and PHP backend. If you’re logged in, the examples will fetch the API keys from your account and populate the appropriate fields in the examples, which makes it easy for you to copy-paste the examples as is:
The examples also have optional sections that provide more ways to customize your experience:
Stripe boasts a superior search functionality that can show results from all over the docs and example code snippets. It also supports fuzzy searching:
Finally, you have the option to contact support or sales from any page:
Overall, Stripe provides remarkable documentation, with its amazing UI/UX, interactive examples, and depth of documentation, which sets the bar high for any developer tool.
Kubernetes is one of the most popular container orchestration tools that is part and parcel of the DevOps world. Being this popular, it’s no surprise that Kubernetes boasts amazing documentation. The documentation home page is entirely made up of links to different sections, including a glossary and the process of how to contribute to Kubernetes. Each page of the documentation allows you to submit an edit to the documentation repository hosted on GitHub:
Kubernetes documentation is also one of the few documentation provided in multiple languages. You can choose over ten different languages to read the documentation in, which means language is no barrier, and developers from anywhere can make full use of the documentation:
The documentation website has an easy-to-understand layout. The Getting started guide provides a nice starting point, and each concept has its own section. You can also find complete tutorials of different use cases and scenarios in the Tutorials section:
Each concept is supplemented by adequate examples of necessary YAML files and kubectl
commands:
Each section also has a What’s Next? section to guide you in exploring related features. The search features support fuzzy searching, but it doesn’t support autocomplete or autosuggestions. However, the search is still powerful enough to find what you need in most cases.
Overall, Kubernetes delivers solid multilingual documentation with enough examples and resources to make sure that you’re not left empty-handed.
Docker is undoubtedly a household name for developers all around the world. And you don’t become as popular as Docker without having superb documentation. The documentation is well-thought-out and structured in an easy-to-navigate manner. It is subdivided into guides, manuals, references, samples, and FAQ. The home page links to the installation guide so that someone who doesn’t have Docker yet can get started immediately:
You can also access different sections right from the home page:
Docker also takes advantage of its huge open source community by linking to community resources such as the forum and Slack channel:
Docker incorporates Algolia as the search engine, which offers a powerful search feature along with fuzzy searching and a keyboard-navigable search widget. You can use CTRL + K to activate the search and arrow keys to navigate:
When it comes to depth, it’s hard to beat the Docker documentation. A simple example is the installation guide for Docker Engine. Not only does Docker provide guides for different operating systems and platforms, but it also provides you with useful tips like post-installation steps and troubleshooting guides:
Docker provides thorough examples and explanations for all its features, including related environment variables, configuration files, and experimental features. The Reference documentation section is a goldmine for discovering every single property of the Docker CLI, Dockerfile, Compose file, and API. Finally, the FAQ section saves developers much time as it already answers common questions.
In conclusion, the Docker documentation is an example of an all-around solid documentation. A clean UI/UX, complete examples, and a nice FAQ section shine as its plus points.
Twilio is a popular service that provides communication tools for making and receiving phone calls, texts, emails, and much more. The Twilio documentation clearly shows the amount of effort put into the tool to make it accessible to every developer. The documentation boasts a clear and modern design, with the home page showcasing different products. The documentation is offered in three languages: English, German, and Spanish:
Just like Docker, Twilio also uses Algolia to implement the search functionality. So you can rest assured you will find what you are looking for!
Each product provides an overview to give you a bird’s-eye view of what you can expect. You can find detailed examples and explanations in the left sidebar:
The API references are all accompanied by sample code in multiple languages and frameworks, such as Node.js, Python, and Java, along with sample responses and a detailed description:
The Tutorials section provides complete guides on different scenarios and use cases of the Twilio API, with the option to choose your favorite language:
Overall, the Twilio documentation does a good job of hitting it out of the park with complete examples, multiple languages and frameworks, and solid search functionality.
Vue is a JavaScript library for creating reactive and highly performant frontend UIs. The Vue documentation boasts a variety of contents, such as guides, tutorials, examples, quick starts, glossaries, and many more:
For the guides, you have the option to choose between the Options API or the Composition API:
The accompanying code samples are complete, and all of them are followed by links to the Vue Playground, where you can experiment with the code interactively:
If you choose to go the Tutorial route, you’ll be presented with a step-by-step interactive tutorial where you can learn the ins and outs of Vue interactively:
The Vue documentation also uses Algolia to implement searching. Needless to say, it provides a solid site-wide searching experience with autosuggestions and fuzzy searching.
Overall, the Vue documentation does a good job of covering all the grounds and showing you the full power of Vue through an interactive playground.
Next.js is a React framework for building full-stack web applications. Next.js has seen a boom in popularity, and there’s no surprise that it boasts great documentation. The Next.js documentation has a sleek, modern UI that greets you with a nice introduction that sets the stage for what to expect:
The docs provide a thorough tour of the features of Next.js, including routing, rendering, caching, components, and functions. You can choose whether you want to use the Pages Router or App Router:
A fast and snappy search widget is provided, which can also be activated by pressing CTRL + K. You get a documentation-wide search with the option to switch between the Pages Router or the App Router:
The code examples are complete and in-depth, with the option to choose between JavaScript and TypeScript:
Finally, if you click on the Learn button at the top, you’ll get access to a Next.js course that’s designed to take you from beginner to expert. Next.js also has guides on the Vercel site that explores many different scenarios where Next.js can be used.
The Next.js documentation is a solid work of art that blends a modern design with thorough resources and helps any developer learn the tool quickly and easily.
Let’s face it, Google Cloud is a behemoth. With a product of that size, you’d expect the documents to be complicated. But Google has done a commendable job of keeping it organized. The home page immediately points toward the quick-start guides, tutorials, and code samples for those who are just testing the waters with Google Cloud:
For seasoned veterans, scrolling down reveals the list of documentation of every single one of the hundreds of products available in Google Cloud:
Each product showcases a collection of training materials and tutorials, use cases, code samples, and even videos:
The tutorials are clear, are in-depth, and link to appropriate pages in the console. With one press of a button, you are taken to where you need to be to follow along with the tutorial:
For codes and commands, you get the option to edit variables inline, which then replaces all occurrences of the variable in the rest of the tutorial, making it easy for you to copy-paste the code:
When it comes to search, it’s a no-brainer that Google dominates that field. This documentation is also no different. Google’s powerful search engine can fetch you hundreds of results in milliseconds:
However, Google takes its documentation one step further by incorporating role-based learning, a training hub, and certifications. This means that if you want to learn Google Cloud, their documentation is literally the best place for that.
The Google Cloud Services stand out from the rest by incorporating training programs and guides. It’s pretty hard to beat Google Cloud Services in terms of the resources provided.
Just like Google Cloud, Amazon Web Services (AWS) is a giant in the cloud computing landscape. And just like Google Cloud, AWS also hosts hundreds of products, so you can expect the documentation to also be gigantic. Unfortunately, the AWS documentation is organized very confusingly, especially if someone has never used AWS before. If you go to the AWS home page and click on the Documentation tab, you’ll be taken to a page that seems daunting because it just has links to all the products and nothing else:
If you click on any of the links, you’ll realize that it’s not the full documentation but rather just an overview of that product:
That’s because the Documentation page is just a collection of overviews of different products. To find the actual documentation of a product, you need to find it from the Products menu and click on it to go to the product’s home page:
From there, you can click on Resources and then on Documentation to find the documentation:
However, where AWS lacks in user experience, it makes up for in terms of depth and usefulness. After all the work you did to find the documentation for a product, you’ll be rewarded because it’ll be all you need. Each product page has easy-to-understand overviews with diagrams, getting-started guides, use cases, and often, introductory videos.
The documentation is thorough, covering all possible ground, starting from setup and prerequisites, all the way up to advanced features, best practices, tutorials, and code examples:
The code examples provide options to choose your favorite language or framework, and you also get a mega repository of all code examples used in the documentation:
As for search capabilities, AWS offers a super powerful search engine that returns results from the documentation across all their products, blogs, and resources, as long as you search from the Overview page:
If you search from within an individual product’s documentation, by default, it’ll be scoped to that product only, but you can simply remove the filter to trigger a full documentation search:
AWS offers the ability to download each product’s documentation as a PDF so that you can store an offline copy or read it from your own devices.
Overall, AWS loses a few points on the UI/UX front but scores solid points for the volume and depth of the guides.
Heroku is a cloud platform as a service that offers hosting applications written in a wide range of languages, such as Ruby, Node.js, Scala, and Go. The Heroku documentation home page starts with a prompt to select your programming language, along with links to some important language-agnostic features, such as the Heroku CLI, Heroku CI, and logging:
For each language, they offer a quick-start guide that starts from the setup and takes you to the full-fledged app deployment on Heroku:
Each quick-start guide has an accompanying sample application that you can clone from GitHub:
You can log into Heroku and save your progress in the quick start. This means you don’t need to finish the quick start in one go, and you can learn at your own pace.
Apart from quick-start guides, Heroku has in-depth documentation on other features, such as the CLI tool, continuous integration, continuous delivery (CI/CD), database, monitoring, add-ons, and security and billing.
The search feature of the Heroku documentation is very good. It doesn’t have autocomplete or autosuggestion, but it can search through the documentation, marketplace, blog, and the whole of the Heroku website:
For non-English-speaking developers, Heroku docs are also available in Japanese.
The Heroku documentation shows how you can create good documentation with a minimal and clean UI while still delivering enough content. Although it doesn’t have an interactive playground like Vue, it is in no way less resourceful.
If you were impressed by the Next.js documentation, wait till you see the Vercel documentation. Since Vercel is the company behind Next.js, it’s no surprise their documentation feels very similar to the Next.js documentation in terms of UI and aesthetics. At first glance, they both use a similar design and UI elements, like cards, buttons, and a sidebar:
Vercel provides a Get started with Vercel guide that gives you an overview of the process that you need to follow to deploy your app on Vercel. Vercel provides framework-specific documentation, such as Next.js, SvelteKit, and Remix. You can deploy an app straight from the documentation by clicking on the Deploy buttons, or you can choose a template:
The code snippets show an option to switch between JavaScript and TypeScript. The code snippets also have line highlighting, which makes it easy to draw attention to particular lines of code. Each snippet is accompanied by a file name, line numbers, and a Copy button to make your life easier:
Each page also has a More Resources section so that you can follow up on what you learned by using it in a real-life scenario:
Finally, searching in the Vercel documentation is similar to Next.js, except you get an option to search within the Vercel docs, the Next.js docs, the Turborepo docs, or through everything:
The Vercel documentation, just like Next.js, has a great combination of good UI and content that delivers immense value to the developer.
While on the topic of cloud platform-as-a-service providers, don’t ignore Netlify. Netlify is used by big companies, such as Google, Twilio, and Peloton, to deploy their web infrastructure. The Netlify documentation greets you with a minimal and sleek modern design, with links to Netlify products and a sidebar menu:
The docs cover a wide range of topics, starting from a quick-start guide to advanced features, such as the Netlify CLI. The guides are accompanied by code snippets and video tutorials wherever possible:
The guides do a great job of explaining the topics in detail, and if you still feel like you’re stuck, you can send them feedback about the docs directly from the page:
The search widget of the Netlify documentation does a great job of finding the relevant information quickly and accurately. The search bar supports autosuggestion and fuzzy searching:
However, one area where Netlify excels is the Ask Netlify feature. It’s an integrated AI chatbot that you can ask questions, and it’ll find you the answers based on the product documentation, support forums, blogs, CLI documentation, and API documentation.
Netlify goes one step further by incorporating an AI chatbot into the documentation. With the advent of AI, incorporating it is a big step toward an excellent user experience. However, even without the AI chatbot, Netlify documentation holds great value for any developer with its tutorials, guides, and examples.
Tailscale is a VPN service that lets you access your devices and services from anywhere in the world. Tailscale boasts simple but thorough documentation. It doesn’t have the super modern design that some of the other entries in this list have, but it makes up for that with the content:
The Tailscale documentation covers a wide range of topics and explains all its bells and whistles. The guides are super thorough, with lucid explanations, along with screenshots and internal links:
Where needed, code snippets are provided. The snippets lack line numbers, but they have syntax highlighting, and comments are used to explain different parts:
The search widget supports autosuggestion, and it can show you results quickly. However, it doesn’t support fuzzy searching:
Tailscale does a fantastic job of packing a punch within a clean and minimal UI. The documentation is solid, explains all features, and goes into in-depth explanations.
Documentation can make or break your product. Good documentation is the key to retaining developers and onboarding new ones. In this article, you looked at twelve of the best documentation out there. You learned what makes them great and, hopefully, got some ideas for improving your existing documentation or creating new ones.
]]>Last month, we tackled this challenge in our webinar, “Cultivating a Thriving Developer Community.” Joined by community champions like Rebecca Marshburn (Head of Community at Common Room), Ron Northcutt (Head of Developer Relations at Appsmith), and Tessa Kriesel (DevRel Leader & Coach), we explored the main ingredients for fostering a developer community that drives business success.
This blog post distills the webinar’s key insights and strategies for starting, building, and measuring your developer community’s success.
At its core, a developer community is a group of developers who share a common interest. This interest could be a specific programming language, a particular technology stack, or even just a general passion for software development. Engaged developers who find value in the community are more likely to become paying users of your product.
Ron Northcutt offered a broader perspective on developer communities. With a background in open-source, he sees a developer community as encompassing a wide range of audiences, including those who have simply heard about the product, those who use it occasionally, and those who are deeply engaged members. External channels like Reddit can be valuable tools for attracting developers to a more focused community platform.
Now that we understand the core concept, let’s explore the various forms developer communities can take:
These communities exist within a single company and cater to two distinct audiences:
External developer communities are open to everyone and can be centered around a specific product, technology, or simply a shared interest in software development. It’s important to distinguish these communities from audiences on platforms like Reddit. As Tessa Kriesel pointed out, these platforms are more like channels for information sharing and discussion, not true communities that foster a sense of belonging and deeper connections.
While the above categories provide a foundational understanding, developer communities can also be classified based on their focus:
Many communities blend these approaches. This allows them to attract developers interested in the broader practice while also catering to those who use their specific product, which can be particularly beneficial as members can learn about the field and discover a valuable tool to enhance their work.
Imagine a developer on a quest to find the perfect tool for their project. Their journey likely starts with a broad search, then narrows down as they explore options and deepen their understanding. Your developer community can be a powerful destination on this journey, offering valuable resources, support, and connections.
But how do developers actually find their way to your community? To understand this, let’s explore the concept of community growth types and how they align with the developer journey.
First, we can think of two growth options: organic and intentional.
Then, we can map our growth method together with the developer or community stages, guiding developers through a series of steps within your community and offering targeted resources and experiences based on their current stage and needs.
Tessa Kriesel emphasized that during the discovery phase, external communities like Reddit might be a good fit. As developers progress through the stages, they can be nurtured towards your more focused community platform.
💡Read the book How to Build and Grow a Successful Developer Program to learn more about the developer journey map.
Rebecca Marshburn offered a model with three community stages:
Both perspectives emphasize the importance of understanding the stages developers go through and strategically guiding them toward your community at the most relevant points. Understanding the developer journey and strategically guiding them through the different stages can help you build a thriving community that benefits both developers and your business.
Before you start considering building a developer community, there are two important foundation steps to consider:
As Rebecca emphasized, the cornerstone of any successful community is a deep understanding of your target audience. Regardless of the size of your initial community, take the time to truly understand their needs, motivations, and pain points.
Some of the key questions to consider are:
These evaluative questions will help you to:
Before embarking on community building, it’s essential to align with your internal stakeholders, as Tessa mentioned. Take a step back and consider the bigger picture: what are the overall business goals for your developer community?
Measuring the success of a developer community is probably the hardest aspect of any developer relations department. As Ron Northcutt highlighted, it’s challenging because DevRel efforts serve various stages of the developer lifecycle. You might create a blog post that a developer uses to solve a problem for free, or you might nurture a student who becomes a brand advocate years later. Both interactions contribute to the community’s value, but tracking their impact on the business can be difficult.
Here are some key tactics that can help you start measuring success:
Rebecca offered a helpful framework for navigating this challenge by considering both short-term and long-term goals.
Imagine being a chef who can’t taste their own food. That’s what it can be like without data in DevRel. Tessa Kriesel highlighted the importance of data in gauging the effectiveness of your DevRel programs, but she also acknowledged the challenges of accessing the right data or using tools that collect and analyze relevant metrics effectively.
The key metrics in building and growing a developer community that you should track are:
Building a successful developer community hinges on three key pillars: a deep understanding of your audience, tailoring your approach to the developer journey stages, and continuously measuring impact.
As Ron Northcutt pointed out, the tech sales landscape has shifted. Contrary to the past decades, prospects now often conduct extensive research before even reaching out to ask a question. This means that capturing data during the early research phase is crucial for understanding what resonates with developers and identifying areas where your community content or resources might be lacking.
Prioritizing genuine value over marketing tactics remains the key takeaway in community building as well as developer marketing in general. This translates into more than just brand loyalty and fosters a powerful ecosystem that generates valuable leads for your business.
Ready to dive into more DevRel and Developer Marketing insights? Join our upcoming webinars for expert insights and live sessions packed with knowledge from industry leaders.
]]>Technical documentation refers to comprehensive written guides and materials that explain the design, development, and usage of a system, software, or product, facilitating understanding, troubleshooting, and maintenance for users, developers, and other stakeholders.
Why is this important? Whether you’re someone who knows your way around technology, a homeowner figuring things out, or someone who is just trying to keep up with the digital world, clear technical documentation is crucial for your success. It gives you the tools to understand new technologies, solve issues with confidence, and make the most out of the products and processes you encounter.
In this article, you will explore the various types of technical documentation, delve into their diverse applications, and learn some essential tips for crafting your own clear and user-friendly technical guides.
Technical documentation serves as the bridge between complex systems and the people who interact with them. It’s a vast umbrella term that covers any written material that explains the functionality, use, and inner workings of a product, service, or process. Technical documentation is written by technical writers in collaboration with subject matter experts (SMEs), and it comes in various forms:
The quality of technical documentation can greatly affect the user experience and productivity, irrespective of whether these users are your external customers or internal employees. Here are a few other reasons why you should focus on creating good technical documentation:
Now that you understand what technical documentation is and why it’s important, it is time to learn some of the ways in which you can improve the quality of your technical documentation. This section will not go into the basics of how to write technical documentation but rather focus on some key tips you can use to improve the quality of your technical documentation.
The first thing any reader would notice when they come across your technical documentation is its structure. It is usually not possible for a reader to go through the entire documentation for a product or service to find what they are looking for, so having a structure that is easy to navigate and allows convenient searching of commonly used concepts or pages becomes very vital.
There are other benefits of keeping a simple, easily navigable structure for your technical documentation:
Some changes you can make to your document’s structure to improve it include the following:
The Firebase documentation is a great example of a good structure that makes it possible to navigate through a huge knowledge base easily. The entire documentation for all products is first categorized based on the purpose of the services (ie app development, release and monitor, or engagement):
Then as you go into each category, you find detailed docs arranged based on the individual services and the platforms that they work on:
Without such a hierarchy, it is very difficult to find what you’re looking for when you’re working with one of the many Firebase services.
Technical documentation usually consists of information that is entirely new to its target audience. In such a case, it becomes all the more important to present the information in a way that allows readers to understand it easily. Excessive use of technical jargon and complex language can make it difficult for new readers to quickly read and grasp the concepts. Simple language can also assist experienced users in quickly finding information, and your team members have to answer fewer questions from the users.
Here are a few key points you can keep in mind to make your technical documentation simpler:
Imagine explaining intricate financial strategies to someone unfamiliar with finance—it can be overwhelming. Similarly, in technical documentation, understanding your audience is essential. Customizing your content to your audience’s specific needs and knowledge level is crucial for creating clear and impactful documents. This approach enhances the quality and effectiveness of your writing, ensuring it resonates with the audience and serves its purpose effectively.
Tailoring the writing style and depth to your audience’s understanding prevents confusion and frustration. Beginners require more explanation and context, while experts appreciate conciseness and technical details. Providing the right level of detail saves users time and effort, allowing them to quickly find and apply relevant information.
To do this, you need to first know your audience. Start by defining user personas and creating profiles representing different user types. Then conduct surveys, interviews, or usability tests to understand their needs, expectations, and technical knowledge. You could also look at user support tickets, forum discussions, and app analytics for insights into the user challenges and information needs.
Once you have a clear idea of who your audience is, customize your technical documentation to their technical understanding. Here’s a quick list of tips to help you get started:
In some cases, it might be hard to put your audience in just one of these categories. The Twilio documentation is a great example of this case. Twilio’s users encompass all technical levels, so Twilio provides a detailed glossary of concepts while offering interactive tutorials and guides to help everyone get started at their preferred pace:
The key is to know your users.
Technical documentation can often feel like a text-heavy slog, stranding readers in a sea of words. That’s where visuals, examples, and interactive elements become crucial. They aren’t just there for decoration; they’re powerful tools that can turn your documentation from boring to interesting, making it easier for readers to understand and remember the information.
Visuals and interactivity in technical documentation can help in catering to different lifestyles. As not everyone learns best by reading, visuals, like diagrams, screenshots, and videos, can explain complex concepts more intuitively, appealing to visual learners. More often than not, a wall of text can be intimidating.
Integrating visuals creates interesting breaks, making the document more scannable and engaging. Interactive elements like quizzes, simulations, and clickable tutorials allow readers to experiment and learn by doing, solidifying their understanding. Therefore, you should consider using visuals, examples, and interactive elements in your technical documents.
However, you must also remember not to overdo it. Always make sure that your visuals and interactive elements directly relate to the content and enhance understanding. Invest in high-resolution images and clear diagrams. Blurry or poorly designed visuals can hinder comprehension. When working with visuals, ensure all of them have alt text for screen readers and consider color contrast for visual impairments. Remember, interactive elements should engage, not overwhelm. Always balance their complexity with the target audience’s skills.
The Stripe documentation is one of the best examples of using interactive and visual elements to the fullest while not overdoing it. For instance, their Quickstart page on Stripe-hosted payments features a follow-along tutorial with interactive code blocks and preview windows to help you visualize what your integration’s final result will look like right on the documentation page itself:
Building such documentation requires great effort, but it pays as well. The key is to understand how your document can benefit from visual and interactive elements and make use of them effectively.
Creating technical documentation isn’t a write-it-once-and-forget-it task. The technology landscape, processes, and user expectations change quickly. To keep your documentation valuable and effective, it requires regular updates.
Outdated information in technical documents leads to confusion, frustration, and wasted time for users. Updating ensures that users have the right instructions and procedures at their fingertips. Additionally, new features, bug fixes, and changes in workflows need to be reflected in the documentation for users to stay on top of things. Also, regular updates demonstrate your commitment to maintaining high-quality resources and building trust and credibility with users.
To make sure you’re updating your technical documentation effectively, here are a few tips you can follow:
Clear technical documentation gives your users the tools to understand your technology, solve issues with confidence, and make the most out of the products and processes they encounter.
This article covered what technical documentation is, its various types, and its practical use cases. You also learned handy tips on how to create effective technical documentation.
If you want to dive deeper into this topic, check out websites like the Society for Technical Communication (STC) and the Microsoft Writing Style Guide for detailed guidelines and best practices around technical documentation and communication. Books such as The Art of Technical Documentation by Katherine Haramundanis l and Read Me First! A Style Guide for the Computer Industry by Sun Technical Publications offer more in-depth insights. These resources can help you continue to refine your skills in creating user-friendly and effective technical documentation.
]]>There are more than 66,000 heads of marketing currently employed in the United States. They were once considered a ‘luxury role,’ but have since become a core hire for both startups and enterprise brands.
A head of marketing is even more integral in the finance and tech industries. If you’re scaling a SaaS or a fintech platform, hiring a head of marketing could be a no-brainer.
Hiring a head of marketing also demonstrates your understanding of direction and leadership. Not only is your head of marketing a driving force for ROI, but they can also maintain the cohesiveness of your communications.
Let’s take a closer look.
There are many moving parts in a growth marketing team, which means there are many opportunities for something to break down. If your business manages technical writers, product marketing specialists, and social media experts, you’ll need a driving force to keep everyone on the same page.
This is where your head of marketing comes into play.
By balancing timelines, deadlines, and creative briefs, your head of marketing can keep everything running smoothly. They can also drive campaigns with a growth mentality, facilitating purpose-driven content for leads.
The key responsibilities of a head of marketing include:
But how do you find a head of marketing, and when should you start looking for the right person?
It mostly depends on what your company needs.
First, let’s define what a head of marketing actually does.
A head of marketing is a senior staff member charged with managing a business’s marketing activities. They may report directly to the Chief Marketing Officer (CMO), or in some cases actually be the CMO.
Since the head of marketing is an eclectic role, the work they do can take a variety of forms.
This may include:
The overall goal is to help your business succeed by focusing on lead generation and building your marketing funnel.
But most heads of marketing don’t do this alone. In fact, they typically rely on a growth marketing team to maximize their results and proof test new ideas.
Grow marketing teams are a subset of marketers focused on growing your marketing funnel. Their overall goal is to test new ideas and identify hiccups in your lead generation strategies.
Heads of marketing typically lead growth marketers, which is one of the reasons they’re sometimes called ‘chief growth officers.’ Growth marketers report directly to the CGO, who then reports their findings to senior management.
You should know you’re not required to separate your growth marketing team from the rest of your staff. Most startups ask existing marketers to experiment with growth strategies alongside other their duties.
And keep in mind growth managers are not the same as heads of marketing. We wrote a comprehensive guide to help you tell the difference.
💡 Related: What is a Head of Growth?
While your head of marketing may work on some creative output, their primary task will be to establish KPIs. This requires a firm understanding of your business objectives, as well as strong familiarity with common BI platforms.
First, your head of marketing collects information about campaign spend, ROI, and KPIs. Then, they report their findings to senior management so they can develop an action plan.
This process looks different in every business depending on its hierarchy or management structure.
There are three different approaches your company might take:
You should choose the reporting or accountability framework that makes the most sense for your business.
💡 Related: Developer Content Strategies That Work (and Scale)
Timing is critical for hiring a head of marketing.
If your business hasn’t yet turned a profit, you may want to rely on an internal role.
If your company has already found its footing, it may be time to hire a full-time marketing head.
But before you start writing a job description, you should answer these questions with members of your C-suite:
If your business has a small or concise marketing team, you can hire a head of marketing at any time. This employee may act more as a CMO and work alongside senior management to keep the department’s work in line with goals.
If your marketing team is already well established, adding a new senior leader may not be a bad idea. If your marketing team doesn’t exist at all, it would be good to hire a head of marketing as the first member of the team.
The best way to answer this is by looking at data — namely, understanding which departments drive the most conversions. Do your cold calls have a greater impact than your organic inbound traffic? Your answer will sculpt your growth marketing plan going forward
If you don’t already have a marketing or sales team, it might be beneficial to hold off hiring any full-time personnel. Instead, you should rely on freelance work or hire an agency until your company is ready to expand.
Here’s a list of other marketing roles and titles you might want to consider before making a decision.
The right time to hire a head of marketing is before your company needs one. It’s best to set yourself up for success and avoid putting new employees in difficult starting positions.
You may be ready to hire a head of marketing if:
If you don’t meet any of the above criteria, your company may not be ready to hire a full-time head of marketing.
You should avoid hiring a head of marketing if:
Does this latter category describe your business? You may want to consider some alternatives to a head of growth.
Agencies like Draft.dev vet applicants to find the most qualified freelance writers. By focusing on quality rather than quantity, we help technical businesses craft holistic approaches to scaling developer content.
If you’re going to spend money on a marketing head, you’ll want to make sure they’re a good fit for your team. Since this is the leader in charge of your KPIs, they should be skilled in their field and familiar with your industry.
Start by asking friends, coworkers, and networks about qualified marketers who may be interested in your role.
Note that referred hires can be five times more effective than non-organic hires. They also cost less to hire, stay longer at their companies, and are more satisfied in their roles.
You could also post job applications through LinkedIn, Monster, or Indeed. Just keep in mind this could be extremely time-consuming. Every publicly posted job averages more than 250 applications, taking hours to screen, interview, and reject.
You could instead rely on DevRel Careers, a dedicated platform for developer marketing jobs. You can post jobs for free to a select group of talent who have years of experience in technical niches.
It’s best to schedule face-to-face interviews whether you’re planning to host in-person or online. This makes it easy to ask hard-hitting questions and engage with the candidate on a personal level.
In a similar vein, look for candidates with hands-on experience working in your industry. This doesn’t have to be a perfect match, but five years or more is typically the starting line.
If candidates have adjunct industry experience, don’t cross them off the list just yet. Unique industry knowledge could provide a unique perspective, encouraging your company to try things your competitors can’t, don’t, or won’t.
Regardless of your candidate’s background or experience, they should feel confident about seamlessly transitioning into your role. As you interview, be open and transparent about your expectations. What will the role entail? What sort of expectations should they have? What are your expectations for their success?
Being open and up-front will help you identify a well-suited candidate.
Strong marketing teams require strong leaders. For thousands of technical brands, this includes a head of marketing.
But with so much at stake for making the wrong hire, finding the right professional matters more than ever.
If you think hiring a head of growth is the next step for you, you should start planning for change right away. Make sure the timing is right, and always choose the right candidate, even if it means prolonging the hiring process.
Not looking to hire a full-time head of marketing? We’d love to talk with you. Learn more about Draft.dev and our growth marketing process by booking a discovery call.
]]>Since I started building Draft.dev a few years ago, I have worked with more than 100 developer tools companies and seen them try various marketing tactics, and come to appreciate the unique challenges and complexities of this field.
So in this post, I want to share my learnings from the past 5-6 years to empower your devtools marketing journey, whether you’re starting fresh or fine-tuning your strategy.
Many outside the industry might not realize that developers rely on a vast arsenal of tools, often called “devtools,” to get their job done. A devtool (short for developer tool) is a software application specifically designed to aid in the development process.
These tools go beyond the typical software most people are familiar with. Imagine the testing tools, automation software, and infrastructure tools that companies like Microsoft, AWS, and Azure provide. These are all examples of devtools.
However, the sheer diversity of devtools presents a unique marketing challenge. Many valuable tools operate “behind the scenes,” so to speak, remaining invisible to typical marketing folks. This presents the first challenge in devtools marketing: you must understand what your tool does for developers.
My advice for anyone starting in the field is:
The devtools market is a thriving ecosystem bursting with diversity. This variety is exciting, but it also presents a unique challenge for marketers: there’s no single magic formula that works for everyone. So, how do you find your devtools marketing strategy in a market overflowing with diversity?
Understand Your Strengths:
Having collaborated with over 100 devtools companies, I’ve learned that successful marketing strategies are custom-built, not one-size-fits-all.
Large enterprises with big budgets can afford complex, resource-intensive campaigns. But replicating that approach for a smaller startup? Recipe for disaster.
Instead, embrace your nimbleness. As a startup, you have the freedom to experiment and test freely, unburdened by bureaucratic hurdles. Leverage this agility to discover unique value propositions and perspectives that larger companies cannot replicate.
Specify Your Target Audience:
The devtools market encompasses a vast spectrum, from hosting providers like DigitalOcean to IDE developers like JetBrains. Each segment caters to a distinct developer profile and sales cycle. Are you targeting CTOs, entry-level developers, or somewhere in between? Understanding your target audience is vital in shaping your marketing strategy.
Consider Your Devtool’s Adoption Model:
Finally, consider the adoption model of your tool. Is it a top-down solution requiring team-wide implementation and CTO approval, or is it a bottom-up tool where individual developers can sign up and start using it immediately?
Top-down solutions involve longer sales cycles and potentially higher investments, while bottom-up tools offer faster adoption but potentially lower initial revenue streams. Aligning your marketing strategy with your product’s adoption model is crucial for maximizing its effectiveness.
By acknowledging the inherent diversity of the devtools market and tailoring your approach to your unique strengths and product characteristics, you can pave the path to a successful marketing strategy.
Let’s face it, developers are a savvy bunch. They have got ad blockers on lockdown and cold emails find their way straight to the trash bin. So, how do you reach these valuable users in the devtools space? The answer is simple, yet often overlooked: build trust.
First of all, content is king. Developers are bombarded with information on a daily basis. They don’t have time for fluff. That’s why content marketing is your secret weapon. Whether it’s technical blog posts, video tutorials, developer-specific events, community-building or even contributing to open-source projects, the goal is the same: connect with developers on their terms, in a way that is friendly and helpful for them.
Secondly, concentrate on the users, not your product. By creating valuable, informative content that troubleshoots real-world developer challenges, you’re not just pushing a product, you’re offering genuine help. This user-centric approach sets you apart from companies focused solely on features and flashy marketing campaigns. It shows developers that you understand their needs and are committed to being a valuable resource, not just another vendor.
Lastly, consider open-sourcing your tool or parts of it. This allows developers to see your work firsthand and fosters a sense of trust and collaboration. Building a strong reputation, having a great team, and actively participating in developer relations (DevRel) activities all contribute to this trust-building equation.
Remember, content isn’t just a marketing tactic, it’s the foundation of building lasting relationships with developers. When you prioritize trust and focus on user needs, you’re laying the groundwork for long-term success in devtools marketing.
Twitter is full of folks bragging about their latest “growth hack” to skyrocket their SaaS startup or grab a thousand users overnight. While these might occasionally bear fruit, the truth is that consistent, long-term strategies are the true foundation of devtools marketing success. Think of it this way: would you rather chase the latest hot stock hoping to get lucky, or invest in a diversified, well-established index fund like the S&P 500? The S&P might not make headlines with overnight gains, but its consistent, long-term growth is what truly builds wealth.
So how do we create good content consistently and repeatedly?
One thing you shouldn’t do is overburning yourself by investing in only one channel. Spreading yourself too thin can lead to burnout and hinder results. Instead, choose a few channels that align with your audience and resources, and consistently deliver valuable content and engagement through those channels.
However, achieving this consistency can be especially challenging for early-stage startups with venture capital. The pressure to deliver quick results is real, leading to a search for silver bullets and shortcuts.
So, for early-stage startups with limited timeframes, the best strategy is leveraging personal relationships and founder credibility. Founders can be powerful advocates, actively engaging with the community through events, podcasts, webinars, and social media. Involving the founders in early-stage marketing demonstrates commitment and fosters trust with potential users.
For companies with a long-term horizon, the focus should shift towards building valuable, enduring assets that build value over time. This includes content, sample projects, open-source contributions, and exceptional documentation. All those are forms of developer marketing that can help build up this annuity they can be interlinked together and repurposed. A well-written blog post can be transformed into a video and then adapted into a compelling conference talk. This approach allows you to leverage a single piece of content across multiple channels, maximizing its reach and impact.
In the devtools space, success often shines on the latest technological advancements. While these are crucial, another important factor often gets overlooked: the significant contributions of marketing.
Marketing plays a vital role in building brand awareness, generating leads, and nurturing developer communities. It’s the engine that drives adoption and propels a devtool from launch to widespread success. However, marketing often operates in a thankless environment.
One significant challenge for marketing teams is often inheriting a raw product lacking features and documentation.
This creates two main difficulties:
The result? Content that generates traffic without driving conversions, potentially leading to unfair blame directed toward the marketing team.
When things go well, other departments may take credit for the success, while marketing becomes the first target if things fall short. This phenomenon isn’t unique to early-stage startups. Even Series B companies can resort to drastic measures, with entire marketing departments facing the brunt of the blame when things go south.
This “blame game” has led to a growing pool of talented devtools marketing professionals seeking new opportunities compared to just a couple of years ago. If you’re looking for new opportunities in the devtools marketing space or a company seeking to fill a role, visit DevRel Careers to find or post jobs.
Now that we’ve tackled the complexities and realities of devtools marketing, and hopefully learned a thing or two about building trust and being consistent, let’s explore the essential tactics that form the foundation of success. These strategies, while seemingly universal, require careful tailoring to resonate with your specific audience and product.
Live events might have faced a temporary setback, but their importance in devtools marketing hasn’t wavered. Being a part of these events is crucial for building relationships and establishing your brand. Conferences like Kubecon and AWS re:Invent offer prime opportunities to connect with your target audience and showcase your product. Use events to engage in thought-provoking sessions, facilitate workshops, and actively foster connections with attendees.
Content marketing is the cornerstone of devtools marketing and for good reason. By providing valuable knowledge and solutions to existing developer problems, you establish yourself as a trusted resource. Content can take two key forms:
Blog posts, tutorials, case studies, or even comprehensive documentation are powerful tools for building trust. Remember, the goal here is not just to sell your product, but to educate, inform, and solve problems for developers over time. An agency like Draft.dev can be particularly helpful in getting your written content out there.
Video content offers an engaging and accessible format for reaching a wider developer audience. Video is increasingly popular with younger generations and companies can utilize diverse video formats like product demos, explainer animations, or even interview-style content to cater to different learning styles and preferences.
Community-driven marketing is a powerful, yet long-term play. The goal is to foster an organic, developer-led community around your product. This can involve building forums, online communities, or even internal user groups. Building a thriving community takes time and dedication, but the rewards are significant: increased user engagement, valuable product feedback, and an amplified brand voice through organic word-of-mouth.
Social media platforms like LinkedIn and Twitter are popular among developers, but they are wary of intrusive advertising. Instead of solely promoting your product on social media, use these platforms to actively listen to developer conversations, understand their needs and challenges, and engage in meaningful discussions. This authentic approach can help you build brand awareness and foster positive sentiment towards your product.
The world of developer marketing is complex and ever-evolving. While building trust with developers remains the cornerstone of success, the methods for achieving it are constantly evolving. Video content is rapidly gaining popularity, offering an engaging and accessible format to reach developers.
Through a strategic blend of valuable content, genuine community engagement, thoughtful use of social media, and a presence at key industry events, you can position your devtool for enduring success.
Remember, consistency is key. While the lure of quick wins and flashy tactics is strong, it’s the steadfast commitment to providing value to developers that will truly pay off in the long run.
Finally, if you’d like to start investing in authentic devtools marketing content, book a call with us to learn more. We specialize in both technical written content and engaging video tutorials, specifically tailored to reach software developers.
]]>This article shares some best practices for creating and publishing developer-oriented documentation. These pointers will ensure your guides, tutorials, API references, and other resources all create a positive experience for devs using your tool.
Developers use software documentation in two main ways: first, to evaluate the high-level capabilities of your tool and, second, to learn the technical details of how it’s used and integrated. Even the best tools are useless if developers don’t know what the tool does or how it achieves its purpose, so it’s vital to invest in authoring quality documentation that makes dev life easier.
The effects of bad documentation—whether missing, outdated, or hard to find—shouldn’t be underestimated. Documentation issues create developer roadblocks that cause frustration and can lead to tools abandonment. Poor docs also drain your internal resources as support teams field more inquiries from uncertain devs seeking answers.
Creating effective documentation starts with following standard best practices for communicating information:
Beyond these principles of documentation, here are four key features to focus on when you’re writing for developers.
Your documentation should be a comprehensive, one-stop place to find any answers that developers require. It’s important to provide in-depth details about all the features provided by your tool in addition to the ways in which they can be used.
Beyond a description of the what and how of your tool, your docs should also clearly explain the why. Detailing your target use cases with the ways in which your tool achieves them and the reasons behind any opinionated behavior enables devs and buyers to easily understand the problems you’re trying to solve.
The exact content to cover depends on the type of tool you’re creating. APIs need a breakdown of every endpoint, the parameters they accept, and the responses they issue, for example, while CLI apps should include a reference for each supported command with its options and how they can be combined.
Such detailed reference material ensures developers can easily discover available functions and learn how to use them. The npm documentation provides clear instructions for every command, for example, offering a clear technical synopsis, a description of the command’s use case, and a list of supported configuration parameters:
Technical depth mustn’t replace high-level guides and overviews, however. Introductory tutorials that are relatively light on detail but walk users through common workflows in simple steps should also be provided. In particular, create concise installation or setup guides for all supported platforms and environments to ensure that first encounters with your tool are frictionless.
This kind of content lowers the learning curve for first-time users who aren’t yet ready to head deep into your reference material. The GitHub REST API showcases how both these content types can be presented—the top of the sidebar is dedicated to quick-start guides and explanations of key concepts, while the bottom section provides a feature-by-feature index of each API capability:
Who doesn’t love a good example? Examples can make concepts and features much easier for devs to understand, especially around areas that are unique to your tool. Even comparatively simple functions should include examples as this provides extra clarity to developers and prevents uncomfortable doubts from arising.
Examples should be easy to find, ready to run, and approachable for those who’ve never experienced your tool before. Incomplete examples can create more confusion than they solve as developers might not yet have enough background knowledge to be able to fill in the gaps.
You should include examples in line with your quick-start guides and technical reference information to help contextualize what you’re describing. It’s also useful to prepare a cheat sheet of examples for your tool’s most commonly used operations. Command line HTTP client HTTPie does a good job of succinctly illustrating how to achieve key use cases, for instance:
Where possible, try to favor the use of interactive examples that are embedded into your content. These allow devs to observe features in action without leaving the docs, creating a more intuitive and satisfying experience. The web platform documentation on MDN illustrates this pattern: examples are clearly signposted in the content, including interactive Play buttons that open the code in a live playground environment:
The way in which docs are presented is almost as important as their content. Select a clean UI that’s easy to use and well optimized for readability so developers can easily find and digest your material. Setting up a dedicated docs site provides a more sophisticated experience than relying on wikis and plaintext files while creating an opportunity to showcase your brand style and design expertise.
A specialist docs interface also facilitates the use of more powerful capabilities that produce a more convenient developer experience. For example, you could link your docs site to your developer accounts system, then customize your code samples so they include real account values after developers log in.
The Stripe API documentation uses this technique to good effect. Once you’re logged in, the API keys and other configurable values shown in the docs are fetched from your account. You can copy and run the examples without having to manually alter any options:
It’s also good practice to let developers persistently select the client library, programming language, or integration type they’re using. This allows irrelevant information to be filtered out, making it easier for developers to focus on the steps that apply to them.
In whatever way the documentation is published, it needs to be supported by a clear navigation structure that makes it obvious how to jump between different content types and topics. Establish a logical pathway for users to follow, from the guide to getting started through to the in-depth reference material, but ensure it’s always possible to skip to specific areas when developers already know what they’re looking for.
Use links—both internal and external—to tie topics together. This lets devs effortlessly discover more information that’s related to the topic they’re reading. Similarly, adding a table of contents at the start of each topic and section aids readers in quickly gauging whether they’ve reached their intended destination.
Discoverability is key to the success of documentation, so it’s crucial to integrate search functionality extensively throughout your docs system. Search needs to be fast, accurate, and capable of surfacing material from all your content sections as users are likely to rely on it to reach the topics they’re looking for. A powerful example is Docker, which lets you open their search panel from anywhere using a keyboard shortcut and then neatly groups all the matching pages based on content type:
Furthermore, optimizing content for search engine visibility provides more paths into relevant content, including when developers are still evaluating different tools within the marketplace. SEO for docs is similar to other evergreen content types: add correct HTML meta tags to your pages, use descriptive URLs and headers, and avoid indexing any autogenerated reference material that might trigger a search engine’s spam or AI detection algorithms.
Shareability is another navigation aspect to consider. Making headers into anchors that act as link targets allows devs to more conveniently reference specific parts of your documentation in chat messages, work specifications, and comments on issues and pull requests. This reduces time spent hunting for information, leading to a more satisfying and productive developer experience.
Focusing on documentation quality ensures devs have the simplest possible experience as they use your tools. Properly formatted, easily navigable docs that provide an exhaustive reference for available capabilities—alongside accessible getting-started guides—keep devs productive, improve retention, and reduce the volume of support tickets you receive.
Creating good documentation takes time, but the benefits more than offset any investment you make. As you’ve seen in this article, many of the most successful developer-oriented tools and platforms have prioritized their docs, ensuring newcomers can quickly find accurate answers to their questions while more experienced users have a clear route to the precise technical info they need. In a crowded marketplace, documentation quality can sell your tool over a competitor’s, so implementing the tips shared here will help improve your business outcomes.
]]>This is where the concept of the marketing funnel was born — a foundation marketers would follow for more than 100 years.
But the marketing funnel isn’t so cut and dry for B2B businesses. Since decision makers and internal experts are the ultimate targets of B2B marketing, treating all visitors like the same type of user could negatively impact your brand.
To make matters worse, most B2B companies completely overlook the importance of the marketing funnel. Nearly three in four businesses (or 68%) have never tried to identify one or implement the stages into their marketing processes.
The good news is, repositioning your marketing funnel doesn’t have to be complicated. By equipping your B2B with a few general guidelines, you can easily scale your marketing efforts to address top, middle, and bottom funnel customers.
The concept of a marketing funnel is simple at first glance – it’s about putting labels on customer relationships and understanding how they change.
Just think about how real-life funnels work – in weather, cooking, or mathematics. These tubes are wider at the top and smaller at the bottom to direct a large amount of something into a smaller place.
Funnels also root out qualified B2B leads and encourage them to move through each stage of awareness. The closer they get to the bottom of the funnel, the closer they get to making a purchase.
When used correctly:
So what does the B2C funnel look like?
There are typically four funnel stages:
Most visitors begin at the Awareness stage — they’re just beginning their relationship with your brand. This is followed by prospects or visitors who are genuinely interested in the products you provide (the Interest stage). If they engage with your brand on social media platforms, they may be at the Desire stage. This could be followed by a purchase decision in the Action stage (so long as everything goes well).
Keep in mind this is a B2C model — the B2B model is much more complicated than this.
With this foundation now in place, let’s take a closer look.
B2B marketing funnels must adapt the B2C approach to technical decision makers and C-suite executives. They usually operate under specific use cases and take much longer to close a deal (up to 84 days on average).
There are typically six B2B funnel stages:
Quick side note: there are many (many) opinions about what to call each stage of the B2B sales funnel. For the purposes of this guide, we’re focusing on their purpose, not their jargon.
Now, let’s break down each stage of the B2B funnel:
B2B clients are typically aware of their pain points well before discovering your company. During the Interest stage, they may investigate your brand and its offerings from a bird’s eye view.
They’re usually interested in content related to your product, what it does, and how it can solve problems.
Users who believe your brand may be a good fit for them have entered the Consideration stage. They may take more time to pursue your middle funnel content, including case studies, technical tutorials, and blogs and articles. More on this later.
In the Intent stage, the user is expressly considering you as a future business partner. This is where your bottom funnel content becomes even more relevant, including use cases, product comparisons, and video courses.
The evaluation stage is the final step before the purchase decision. Depending on the size or scope of your business, it may also be the longest as well.
Here, customers discuss your brand with their internal stakeholders, teams, and leadership groups. They may request additional information or demos from your team.
Exactly as it sounds, the Purchase stage is where customers buy into your product. This is also the stage where onboarding becomes important, especially if you’re a SaaS or service-oriented brand.
Customers who are happy and satisfied with your products may enter the Ambassador stage. Not only are they more likely to purchase additional products in the future, but their outspoken loyalty makes your brand more attractive to new B2B leads.
Keep in mind the Ambassador stage holds the fewest of all customers. However, this small-but-mighty group is instrumental in creating a renewable sales cycle.
Great customers become great referrers, which builds your reputation both on and offline. This turns the marketing funnel into a self-sufficient flywheel using ambassador momentum to reach new clients, customers, and leads.
There are three major differences between B2B and B2C funnels.
First, B2C funnels are typically much wider than B2Bs. There are more people in the world interested in buying coffee makers than SaaS platforms, for example.
Second, B2B funnels require extremely accurate targeting. The B2B marketer must know their target audience inside and out, while the B2C marketer can get away with non-specificity.
Finally, B2B funnels are much slower to complete. The B2C customer can make a purchase decision in minutes, but B2B clients with a wide chain of command can take weeks, months, or sometimes years to move forward.
B2B marketing funnels and B2B content marketing funnels are similar, but not the same.
Marketing funnels focus on active leads who may be interested in purchasing your product or service. Content marketing funnels may capture audience members who don’t even know what your product is.
The latter is necessary to create awareness, growth, and impact around your goods and services. But cutting through the advertising clutter isn’t easy. In order to remain competitive, you need to pivot your content and messaging into an organized marketing strategy.
There are three major stages in the B2B content marketing funnel:
ToFU content includes any topics or subjects designed for the widest reaches of your audience. They may or may not be familiar with your company, but they’re probably familiar with (or at least exploring) the solutions you’re offering.
As a B2B company, this may include:
Remember: this is content for audience members who know little if anything about your brand. The goal is to guide them through the pain points you solve and provide a general overview of your overall market.
This is for audiences who are familiar with your market and know at least a little about your brand. They’re not necessarily ready to buy your product, but they’re much more comfortable with the jargon or technicalities of your industry.
A few examples of MoFU content include:
Anything encompassing your offer (and convincing customers why it’s the best one) can draw your leads to the final stage of conversion.
Conversion content, otherwise known as BoFU content, is strictly for audiences that are ready to buy. Users may be willing to purchase a product or switch from one solution to the other.
Common BoFU content types include:
Some B2Bs combine their BoFU content with RoFU content, which is retention-focused content marketing for customers who have converted. However, RoFU content is much more effective when separated from BoFU. Try writing guides, publishing product updates, or discussing industry news.
As you can see, B2B content marketing funnels are a sustainable mechanism of value able to cut through the chaos of online marketing clutter. Building enough content for every stage of the funnel creates a sustainable system that runs while you sleep.
Using the marketing funnel correctly within your B2B is more than just a nebulous ‘good practice.’ Instead, properly constructing marketing content that reflects different marketing stages can dramatically boost customer traffic, product interest, and of course, your profit margin.
Let’s look at some practical applications:
P.S., working with a marketing agency can help you achieve all these benefits at once.
The B2B marketing funnel can impact all areas of your business. With it, content teams create more efficient value, head marketers nurture more targeted campaigns, and B2B customers at all levels of engagement are encouraged to interact with your brand.
But understanding the B2B buyer’s journey is just the first step in refining your marketing process. If you’re an early-stage startup or scaling business, starting off on the right foot is paramount to your success.
Curious to learn more about other elements of B2B marketing? Check out our most recent marketing resources here.
]]>So, should your company host a hackathon? And if so, how do you make it a success?
Recently, we kicked off our new monthly webinar series at Draft.dev with a focus on hackathons.
Our CEO, Karl Hughes, and Brandon Kessler, CEO of Devpost, dived deep into what makes hackathons tick, their benefits, and key strategies for organizing one. This blog post takes you through the essential questions you might have, like what hackathons are good for, how to plan them right, and more.
For developer marketing professionals with no technical background, organizing a hackathon might sound like a confusing, expensive event that feels more like a game than a serious business strategy. But the benefits go far beyond that surface.
Regardless of the multiple benefits and reasons why both participants, as well as organizers, can benefit from hackathons, there are situations where organizing them might just not be right for your company.
If your sole goal is acquiring a finished product on the cheap, don’t frame it as a hackathon. Brandon Kessler aptly calls it “cheap procurement,” undermining the collaborative spirit and devaluing participants’ contributions.
Can early-stage start-ups host hackathons? Sure! But it’s important to manage expectations because you might not attract big companies to partner up with, or established developers just yet. Instead, focus on building community and engagement instead of immediate product solutions.
Think beyond a single event and don’t view hackathons as a standalone marketing campaign. Integrate them into your ongoing developer outreach strategy. Use them to complement technical content, inspire your community, and foster long-term connections.
Hackathons are powerful, but they’re not your entire developer marketing strategy. Think of them as an umbrella providing shade alongside other channels like tutorials, forums, and community events. Use them to drive engagement and support broader initiatives.
In essence, hackathons are catalysts for innovation, community building, and learning. By acknowledging their limitations and integrating them strategically, you can create win-win situations for both you and your developer community.
So, hackathons seem like a promising addition to your developer marketing strategy. Now, how do you build a truly successful one? Here are the four fundamental pillars Brandon pointed out:
This might seem obvious, but if developers don’t know about your event, it’s doomed to be a ghost town. While we’ll dig deeper into specific tactics in the below “Promoting Your Hackathon” section, promotion is a must-have ingredient for an impactful hackathon.
The competition itself is the heart of the hackathon, so make sure it has the “wow” factor.
Choose a challenge that leverages your product’s strengths and offers genuine value to participants. Consider real-world problems or opportunities to innovate with your tools.
Imagine developers hitting a technical problem - frustration rising, motivation dwindling. To prevent this, ensure readily available, knowledgeable tech support. This could be internal developers, volunteers, or partners familiar with your tools.
Cash prizes are considered the standard, but it’s also a good idea to explore creative additions to cash prices which we’ll go more into detail in the “Incentives for Developers” section.
While your product might seem like a “one-trick pony” at first glance, remember that creativity knows no bounds. Brandon mentioned the success they had with one of their clients Okta which can serve as an example:
Check out Okta’s past hackathons and their case study on DevPost for inspiration. See how they broadened their authentication-focused challenges to encourage creative solutions.
Private hackathons with key accounts can also be a powerful tool for fostering engagement and showcasing your product’s potential. Your customers might have questions about your product’s suitability for specific scenarios. A hackathon allows them to experiment and discover new possibilities firsthand.
Also, consider real-time collaboration: Imagine showcasing how your database tool works for e-commerce through a live hackathon demonstration. This interactive experience can be far more impactful than traditional presentations.
One of the easiest ways to promote your hackathon is to work with a company like Devpost to take the burden as they already have an existing community of developers which makes it easier to attract developers with matching skills to attend your hackathon. But if you have been assigned to promote your webinar on your own, here are some main tips for achieving success with your hackathon promotional plan. In short, Brandon recommends doing “Everything!” when it comes to the promotion.
While cash is a traditional prize, developers may find it more attractive if you can offer something they may usually not have access to. Here are some additional incentives you could consider:
Tailoring prizes to your audience can also be a good idea. For example, consider the type of developers you’re trying to attract and their motivations. While junior developers might appreciate career development incentives, senior developers may find recognition and their personal brand awareness more important.
Also, transparency is key, so communicate prize details and eligibility criteria clearly, and don’t forget to research local regulations for any specific prize restrictions or guidelines in the country of your organized hackathon.
Attendance figures offer an overview of participation, but to understand your hackathon’s success you have to dig deeper. Success can also mean many things, so make sure you define what are your goals for the event. Is it amplifying brand awareness, gathering feedback, inspiring innovation, or perhaps even attracting talent?
Let’s take a look at some key metrics:
So, are hackathons right for your company? While they offer exciting possibilities for innovation, community building, and learning, it’s crucial to approach them strategically and acknowledge their limitations. Hackathons are not about acquiring cheap solutions or short-term marketing gains but instead, a chance to build genuine value for participants.
Remember, successful hackathons go beyond caffeine-fueled coding sprints, building a vibrant community, and fostering genuine connections with developers. When planning a hackathon, it might be worth seeking help from platforms like Devpost which offer various packages to help you organize one. These packages can include essential features like project management, an online platform, and even marketing and promotion assistance.
Looking towards the future, advancements in AI are poised to streamline the entire experience, from logistics and team formation to project management and innovation cycles. As Brandon Kessler mentioned, “Every dev tool has now AI implemented, and AI is also helping to save much time, improving team building and project management side.” This means smoother operations, better collaboration, and ultimately, faster innovation.
Ready to dive into more DevRel and Developer Marketing insights? Join our upcoming webinars for expert insights and live sessions packed with knowledge from industry leaders.
]]>This is why technical marketing managers matter more than ever.
Technical marketing managers aren’t your average marketing lead. Instead, they’re a powerhouse of multiple disciplines and highly trained in their technical field(s). They have a working knowledge of your product and industry, as well as a deep knowledge of your target audience — which typically includes developers, devops, and software engineers.
The average technical marketing manager juggles a wide variety of tasks:
Demand for technical marketing managers is steadily on the rise. Digital marketing as a field is set to grow 13.1% between 2024 and 2032. Combined with the growing number of tech startups in the US (with more than 13,000 new brands per year), the need for experienced technical marketing managers is here to stay.
Whether you’re trying to hire or become a technical marketing manager, we wrote this guide to help you build a plan. First, we explain what they are, what they do, and the tools they need to succeed. Then, we describe some hiring triggers and reasons why you may want to wait.
Looking for a place to get your first gig? Or looking to post a job opening? We also explain how DevRel Careers can help you get started for free.
The technical marketing manager is responsible for creating and managing content that educates and persuades technical audiences. This includes tasks such as developing technical content strategies, creating white papers, writing product documentation, and managing social media channels.
There are a few ‘bare necessities’ required for technical marketing managers:
How does a technical marketing manager’s role differ from a digital marketing manager? For one thing, their level of experience is different. Most technical marketing managers have hands-on experience in your industry. Some digital marketing managers, however, have never worked outside the marketing industry.
Plus, many technical marketing managers focus heavily on content creation. Content might be a focus of the digital marketing manager, but they may have more experience working with PPC, SEO, and earned media.
Perhaps the biggest differentiator of all is the marketer’s approach to your target audience. Traditional marketing strategies rarely (if ever work) for technical audiences. The technical marketing manager knows this all too well — they’re not going to waste time on tactics that don’t work.
To summarize: the technical marketing manager uses developer marketing tactics, not just traditional marketing approaches. This usually means writing great technical content, but also includes open-source development, building a network, and focusing on developer content strategies that scale.
Most technical marketing managers didn’t start in marketing. Many of them began as software developers or engineers, then moved into the role as their skills developed.
For this reason, you’d be hard-pressed to find two marketing managers with the same skill set, experiences, or backgrounds. There are, however, a few key characteristics shared by top talent in the industry.
This includes:
If you want to become a technical marketing manager, you should start with the experience side of the equation. First, you can try your hand at technical writing or look for opportunities within your current position. Then, you can join a community of technical marketers willing to share experience in developer relations.
Do you love the thought of writing, but feel uncomfortable about navigating the technical side? A career in content marketing management may be what you’re looking for.
There’s some overlap between the platforms used by digital marketing experts and the tools required by technical marketing managers. There are several, however, that are completely unique, and require a working knowledge to successfully complete a campaign.
That’s why most technical marketing managers are familiar with these five integral platforms:
If you’re not familiar with any of the above, you’re not disqualified from becoming a technical marketing manager. Most of these platforms are simple to learn, and there are hundreds of training videos online.
You may be ready to hire a technical marketing manager:
On the other hand, you may not be ready to hire a technical marketing manager if:
Not sure where to start with hiring a technical marketing agency? We wrote this guide to help you vet your options.
The technical marketing manager can be an ace-in-the-hole for technical startups and established brands. Not only can they get more eyes on your product, but they can also nurture customers into passionate brand ambassadors.
Plus, the future is bright for those pursuing a role in technical marketing management. Demand is increasing, the salary is competitive, and the opportunity for career development is virtually endless.
No matter where you fall on the spectrum, DevRel Careers can help. On this platform, companies can post their marketing positions to hundreds of qualified applicants all over the world. Applicants can easily create a profile online then upload their resumes for review.
Ready to get started? You can submit your resume or post a job for free at any time.
]]>In developer marketing, newsletters play a unique part in your arsenal of marketing tools. Software development is constantly evolving. Breaking changes, new tools, and updated best practices are added every day, so keeping up in the tech industry can be incredibly hard.
Curated newsletters help developers keep up because a set of experts have already sorted through the content and picked the best stuff. Developers don’t have to worry about being overrun with information while keeping tabs on everything that’s changing in the tech industry.
Unlike traditional advertising, developer newsletters are typically trusted sources of information, as readers actively opt in to receive them. This willingness to provide their email addresses signals their interest, engagement, and trust. In a community known for its skepticism of hard-sell tactics, this trust factor can make a world of difference in generating leads.
So, in this piece, I wanted to compile a roundup of a diverse selection of developer newsletters, spanning from tech leadership and web development to specific coding languages. I’ve included each newsletter’s category, sponsorship rates, and contact information in case you want to pitch them stories or sponsor them.
As we find new developer newsletters, this list will continue to grow, so check back periodically or email us if you know of another one we should include.
Stay informed. Receive weekly insight from industry insiders—plus exclusive content, offers, and more on the topic of software development.
Number of subscribers: 594,000+
Sponsorship rates: https://cdn.oreillystatic.com/pdf/OReilly_Marketing_Sponsorship_Opportunities.pdf
Contact email/info: https://www.oreilly.com/content-marketing-solutions.html
TLDR newsletter is a daily newsletter with links and TLDRs of the most interesting stories in tech, science, and coding!
Number of subscribers: 1,250,000+
Sponsorship rates: https://advertise.tldr.tech/
Contact email/info: partnerships@tldr.tech
Programming Digest is a weekly newsletter with the five most interesting stories in programming, data, and technology.
Number of subscribers: 14,202+
Sponsorship rates: https://bonobopress.com/media-kit/
Contact email/info: jakub@bonobopress.com
A weekly newsletter with five interesting stories about building teams, leadership, and engineering culture.
Number of subscribers: 22,720
Sponsorship rates: https://bonobopress.com/media-kit/
Contact email/info: jakub@bonobopress.com
A weekly email for busy people who care about people, culture, and leadership.
Number of subscribers: 31,020+
Sponsorship rates: $2,749 for a 6-week product add
Contact email/info: https://orenellenbogen.gumroad.com/l/swlw-6w-product-ad?recommended_by=mc
Curated technology leadership and management articles from around the web.
Number of subscribers: undeclared
Sponsorship rates: varies
Contact email/info: partners@ctocraft.com
An email update for web developers. Keep up with the latest releases of tools, frameworks and services. Know what’s happening in the world of web development, cloud infrastructure and serverless. Get curated links to the latest videos and repos that can make you a better developer.
Number of subscribers: undeclared
Sponsorship rates: https://cfe.dev/docs/prospectus.pdf
Contact email/info: brian@cfe.dev
FreeCodeCam’s newsletter provides updates on learning how to code, building new projects, and earning certifications.
Number of subscribers: undeclared
Sponsorship rates: undeclared
Contact email/info: support@freecodecamp.org
Newsletter about software development, tech industry, and anything else interesting.
Number of subscribers: undeclared
Sponsorship rates: undeclared
Contact email/info: assaf@labnotes.org
A newsletter of JavaScript articles, news, and cool projects
Number of subscribers: 180,162
Sponsorship rates: https://cooperpress.com/files/cooperpress-media-kit-q1-2024.pdf
Contact email/info: https://cooperpress.com/advertise
A weekly overview of the most popular JavaScript news, articles, and projects
Number of subscribers: 21,722
Sponsorship rates: https://js.libhunt.com/advertise
Contact email/info: stan@libhunt.com
Web Tools Weekly is a front-end development and web design newsletter with a focus on tools.
Number of subscribers: 13,096
Sponsorship rates: https://webtoolsweekly.com/sponsor
Contact email/info: https://webtoolsweekly.com/contact
The latest in JavaScript and cross-platform tools
Number of subscribers: 16,000
Sponsorship rates:
https://ecmascript.news/advertising.html
Every Tuesday we send out an editorial email newsletter with useful tips and techniques on front-end and UX.
Number of subscribers: 200,000+
Sponsorship rates: $2,500 per post
Contact email/info: advertising@smashingmagazine.com
Get the best weekly JavaScript articles hand-picked by experienced developers
Number of subscribers: undeclared
Sponsorship rates: https://javascriptkicks.com/sponsor
Contact email/info: support@javascriptkicks.com
Your weekly dose of Javascript. Staying informed on the JavaScript ecosystem has never been so entertaining. Delivered every Monday, for free.
Number of subscribers: 216,286
Contact email/info: https://bytes.dev/advertise
A weekly roundup of the latest React and React Native links and tutorials.
Number of subscribers: 55,614
Sponsorship rates: https://cooperpress.com/files/cooperpress-media-kit-q1-2024.pdf
Contact email/info: https://cooperpress.com/advertise and sales@cooperpress.com
Stay up to date on the latest React news, tutorials, resources, and more. Delivered every Tuesday, for free.
Number of subscribers: 18,650
Sponsorship rates: undeclared
Contact email/info: hi@ui.dev
With our weekly newsletter, you will get 5 top stories hand-picked into your inbox every Monday with topics ranging from React and React Native, and many other supporting libraries, tools, and tutorials.
Number of subscribers: 18,953
Sponsorship rates: https://bonobopress.com/media-kit/
Contact email/info: https://bonobopress.com/advertise/
A weekly overview of the most popular React news, articles and projects.
Number of subscribers: 21,745
Sponsorship rates: https://react.libhunt.com/advertise
Contact email/info: stan@libhunt.com
A weekly newsletter of the latest news in React.
Number of subscribers: 33,406
Sponsorship rates: https://thisweekinreact.com/sponsor
Contact email/info: sponsor@thisweekinreact.com
Weekly email roundup of CSS articles, tutorials, experiments, and tools curated by Zoran Jambor.
Number of subscribers: 37,000
Sponsorship rates: https://css-weekly.com/advertise/
Contact email/info: https://css-weekly.com/contact/
Be the first to know about the latest Web Design and Front-end trends.
Number of subscribers: 20,000+
Sponsorship rates: Undeclared
Contact email/info: https://web-design-weekly.com/advertise/
Five design-centric posts each day.
Number of subscribers: Undeclared
Sponsorship rates: ($950) https://sidebar.io/sponsor
Contact email/info: sponsor@sidebar.io
Curated stories for designers.
Number of subscribers: 100,000+
Sponsorship rates: https://webdesignernews.com/advertising/
Contact email/info: https://webdesignernews.com/contact/
The latest articles about interface usability, website design, and UX research from the Nielsen Norman Group.
Number of subscribers: Undeclared
Sponsorship rates: Undeclared
Contact email/info: https://www.nngroup.com/about/contact/
An easy-to-follow design course for people who do amazing things. Learn at your own pace, and apply it to your real-life work.
Number of subscribers: 400,000+
Sponsorship rates: Undeclared
Contact email/info: contact@hackdesign.org
Latest web news and articles from industry experts.
Number of subscribers: 95,600+
Sponsorship rates: https://ewebdesign.com/advertise/
Contact email/info: https://ewebdesign.com/contact/
Design inspiration and great design-related content sourced from the best subreddits.
Number of subscribers: 1,400
Sponsorship rates: Undeclared
Contact email/info: hello@unread.it
Figmalion is a curated collection of the most valuable Figma resources.
Number of subscribers: Undeclared
Sponsorship rates: Undeclared
Contact email/info: hello@efedorenko.com
A weekly overview of the most popular iOS news, articles, and projects
Number of subscribers: 21,744
Sponsorship rates: https://ios.libhunt.com/advertise
Contact email/info: stan@libhunt.com
C# Digest is a weekly newsletter with the five most interesting stories in .NET and C#.
Number of subscribers: 22,512
Sponsorship rates: https://bonobopress.com/media-kit/ Contact email/info: jakub@bonobopress.com
A weekly overview of the most popular .NET news, articles, and projects
Number of subscribers: 21,744
Sponsorship rates: https://dotnet.libhunt.com/advertise
Contact email/info: stan@libhunt.com
A weekly overview of the most popular Node.js news, articles, and packages.
Number of subscribers: 21,744
Sponsorship rates: https://nodejs.libhunt.com/advertise
Contact email/info: stan@libhunt.com
Subscribe to a hand-picked round-up of the best iOS development links every week. Curated by Dave Verwer and published every Friday.
Number of subscribers: 46,121
Sponsorship rates: https://iosdevweekly.com/sponsorship
Contact email/info: https://iosdevweekly.com/sponsorship-inquiry?q=2
A weekly overview of the most popular Swift news, articles, and projects
Number of subscribers: 21,744
Sponsorship rates: https://swift.libhunt.com/advertise
Contact email/info: stan@libhunt.com
A weekly newsletter about the Go programming language
Number of subscribers: 36,248
Sponsorship rates: https://cooperpress.com/files/cooperpress-media-kit-q1-2024.pdf
Contact email/info: https://cooperpress.com/advertise/
A weekly overview of the most popular Go news, articles, and projects
Number of subscribers: 21,744
Sponsorship rates: https://go.libhunt.com/advertise
Contact email/info: stan@libhunt.com
A free, once-weekly e-mail round-up of Ruby news and articles.
Number of subscribers: 39,159
Sponsorship rates: https://cooperpress.com/files/cooperpress-media-kit-q1-2024.pdf
Contact email/info: https://cooperpress.com/advertise
Written by thoughtbot, experienced designers and developers who turn your idea into the right product
Number of subscribers: Undeclared
Sponsorship rates: https://github.com/sponsors/thoughtbot
Contact email/info: https://github.com/sponsors/thoughtbot
A collection of awesome Ruby gems, tools, frameworks, and software.
Number of subscribers: 21,744
Sponsorship rates: https://ruby.libhunt.com/advertise
Contact email/info: stan@libhunt.com
A free once-a-week newsletter, featuring some great articles, news, and blog posts.
Number of subscribers: 18,604
Sponsorship rates: Undeclared
Contact email/info: articles@phpweekly.com
A free once-a-week newsletter, featuring some great articles, news, and blog posts.
Number of subscribers: 38,000+
Sponsorship rates: https://laravel-news.com/advertising
Contact email/info: https://laravel-news.com/contact
A weekly overview of the most popular PHP news, articles, and projects
Number of subscribers: 21,744
Sponsorship rates: https://php.libhunt.com/advertise
Contact email/info: stan@libhunt.com
A bi-weekly newsletter on modern PHP and Laravel.
Number of subscribers: Undeclared
Sponsorship rates: https://freek.dev/advertising
Contact email/info: freek@spatie.be.
A free weekly newsletter featuring the best hand-curated news, articles, new releases, tools and libraries, events, etc related to Python.
Number of subscribers: Undeclared
Sponsorship rates: Undeclared
Contact email/info: https://twitter.com/rahulgchaudhary
A free, weekly email newsletter for those interested in Python development and various topics around Python and the community
Number of subscribers: 111,426
Sponsorship rates: Undeclared
Contact email/info: https://pycoders.com/advertise
A weekly overview of the most popular Python news, articles, and projects
Number of subscribers: 21,744
Sponsorship rates: https://python.libhunt.com/advertise
Contact email/info: stan@libhunt.com
A daily Python and data science snippet.
Number of subscribers: 4,100
Sponsorship rates: Undeclared
Contact email/info: https://mathdatasimplified.com/about-2/
A free, once-a-week e-mail round-up of hand-picked news and articles about Perl.
Number of subscribers: 4,523
Sponsorship rates: https://perlweekly.com/sponsors.html
Contact email/info: gabor@szabgab.com
A weekly overview of the most popular Elixir news, articles, and projects
Number of subscribers: 21,747
Sponsorship rates: https://elixir.libhunt.com/advertise
Contact email/info: stan@libhunt.com
The Haskell Weekly Newsletter covers the Haskell programming language. Each issue features several hand-picked links to interesting content about Haskell from around the web.
Number of subscribers: Undeclared
Sponsorship rates: https://haskellweekly.news/advertising.html
Contact email/info: info@haskellweekly.news
The wonderful world of the Elm programming language, in your inbox.
Number of subscribers: 2000+
Sponsorship rates: Undeclared
Contact email/info: https://twitter.com/elmweekly
A weekly overview of the most popular Rust news, articles, and projects
Number of subscribers: 21,747
Sponsorship rates: https://rust.libhunt.com/advertise
Contact email/info: stan@libhunt.com
A weekly overview of the most popular C++ news, articles, and projects
Number of subscribers: 21,747
Sponsorship rates: https://cpp.libhunt.com/advertise
Contact email/info: stan@libhunt.com
A weekly overview of the most popular Scala news, articles, and projects
Number of subscribers: 17,798
Sponsorship rates: https://scala.libhunt.com/advertise
Contact email/info: stan@libhunt.com
A curated list of awesome Java frameworks, libraries, and software.
Number of subscribers: 21,747
Sponsorship rates: https://java.libhunt.com/advertise
Contact email/info: stan@libhunt.com
Keep up-to-date with the main developments in the Java world through this weekly guide.
Number of subscribers: 135,000+
Sponsorship rates: https://www.baeldung.com/advertise
Contact email/info: https://www.baeldung.com/contact
A weekly overview of the most popular Kotlin news, articles, and libraries.
Number of subscribers: 21,747
Sponsorship rates: https://kotlin.libhunt.com/advertise
Contact email/info: stan@libhunt.com
The weekly newsletter for Kotlin developers, with articles, libraries, videos, and podcasts from the Kotlin environment.
Number of subscribers: Undeclared
Sponsorship rates: https://kotlin-weekly.web.app/#sponsor
Contact email/info: https://kotlin-weekly.web.app/#social
Get the Most From Your Mac With the Free Weekly Email Newsletter From MacMost
Number of subscribers: 35,491
Sponsorship rates: Undeclared
Contact email/info: Undeclared
A weekly email roundup of Postgres news and articles
Number of subscribers: 16,165
Sponsorship rates: https://cooperpress.com/files/cooperpress-media-kit-q1-2024.pdf
Contact email/info: https://cooperpress.com/advertise
Whether you’re trying to reach game developers, web developers, or to tap into the thriving Android development community, this extensive list of developer newsletters will help you connect with the right audience and establish credibility among tech professionals.
If you enjoyed this list, you may also find our ultimate list of developer podcasts valuable.
Do you have others you would like to suggest for our list, or would you like to add commentary to our choices? Let us hear about them on Twitter or Linkedin.
]]>