<aside>
💡 Subject: Editorial Guidelines
DRI: @Victor Coisne @Dessire Ugarte Amaya
Last update: October 2022
</aside>
Welcome to the Strapi Editorial Guide. Writing is the most common way we communicate with the Strapi community, clients, partners, and companies. How we write shapes the way the community perceives us as an organization. Hence, it's important to write using the Strapi voice, even if the tone may vary depending on the situation.
Writing Goals
With every piece of content we publish, we aim to:
- Empower the community. We help the community understand Strapi by using a level of language accessible that informs them and encourages them to use Strapi for their projects.
- Support. We treat readers with consideration and empathy by giving them the necessary information and direction to learn more. We always assume good faith and don't forget that we are more knowledgeable about our solution and that users are not necessarily as experienced as we are.
- Speak truthfully. We avoid jargon, metaphors, and exaggeration and focus on clarity and real proven data-driven claims.
- Respect. Above all, the Strapi voice demonstrates our deep respect for the Strapi community of clients and users. Ultimately, Strapi exists because of them, so it’s important to keep their needs at the forefront of everything we do.
To do so, we make sure our content is:
- Informative. We always know well the topic we are writing about. We use clear, simple and informative words and sentences.
- Useful. With every piece of content, we start by asking ourselves: why our users should care? Who is going to read this? How do we solve a problem for them?
- Friendly. We are humans and write like humans. We use spoken language when writing, just like in a face-to-face conversation, and adapt to who we write for and about.
Strapi's readers
When you write for Strapi, remember who your audience is and who will be reading your writing. Strapi's audience is diverse, but we mainly communicate with a technical audience and want to show Strapi as a helper in the Engineering, Marketing, and Operations departments.