Yes, you must follow these article guidelines. Articles that do not follow our guidelines will not be published on Strapi.

Every writer should fill out the vendor form once. Please submit this form before getting started on articles to ensure we can pay promptly.

You get paid for articles published on the Strapi Blog, and the article will be published under your name, along with a profile picture and a link to your Twitter profile.

We follow these criteria to compensate our writers.

Note: we are currently not accepting new articles until January 1st, 2023, since we have enough articles in the cue. Please note the new pricing will go into effect starting January 2023.

For article or series of tutorials updates, check this page. You can also get paid with Open Collective gift cards or Amazon gift cards.

All WFC members must fill out this form before submitting a draft/outline to allow us to process payments.

Beginner: A beginner tutorial or article shares with users what are the fundamentals of Strapi, best practices of native features, the basics of Strapi combined with other technologies, general use cases, and guides explaining the basics of the ecosystem (e.g., “What is JavaScript?”). This type of blog post answers questions like “what is” and “how-to’s” that include one or two technologies diving into getting started with Strapi with other frameworks.

Intermediate: An intermediate tutorial or article that dives into Strapi’s customization capabilities, implementation best practices, and development using Strapi with other technologies. This type of blog post answers questions like “how-to’s” that include diving into a more complex development of Strapi back-end customization and deployment.

Advanced: An advanced tutorial or article that dives into more extensive expertise on Strapi’s customization, building blocks/primitives. This type of blog post introduces users to complex concepts and provides different solutions to uncommon scenarios.

Note: The Strapi team will assign a tag during the outline process and confirm on the article draft submission that it is still in line with the label given.

• Strapi customization Front/Backend
• Intermediate examples of Dynamic Zones and Components
• Deployment options and strategies
• Extensions / adding features
• Plugins and custom fields development
• Strapi testing
• Intermediate/Advanced GraphQl usage
• Cashing
• Structuring your content types/database
• Intermediate to Advanced topics covering
  • Routes
  • Middlewares
  • Policies
  • Controllers
  • Services
  • EntityService
  • DB Queiring with strapi.db.query
  • using knex with strapi.db.connection
  • Topics around population and filtering

Once your blog post is published on our blog, please follow the below guidelines to submit your invoice:

• Fill out the "Vendor Form". This form should be filled only after writing your first blog post.
• The invoice should use this template and must include the URL of your blog post. Please duplicate it before editing the template content.
• Invoice sent should be in PDF format.
• Invoice file name should follow this format "firstname lastname month blog post title".
• Payments are issued twice a month (1st and 3rd week every month) and require 10 working days. Your bank account should be able to cash in USD.
• Submit your invoice by filling the following form

Unfortunately, content published on our blog is currently in English only.

No, we only publish original content to our blog. Submitted content must pass a plagiarism checker.

Strapi claims the blog post piece as our own after it is published and you have been compensated. You can however publish it on your Dev.to & Hashnode account as part of Strapi organization using a canonical link pointing to the Strapi post.

If you'd like to ask a question that isn't covered here, please reach out on Discord (Paul) or send an email to paul.bratslavsky@strapi.io or dessire-ugarte.amaya@strapi.io.