Writing in style 2.0
3 years ago we implemented a style guide on the Umbraco Documentation. The purpose of this style guide was to help contributors write not only good documentation but excellent documentation.
Along with the style guide, we also added a style linter to the GitHub repository where the documentation lives. This allowed us to set up some automation to check every incoming Pull Request against our defined guidelines.
If you want to learn more about how this all works, read Sofie's Docs Diary Vol. 16: Writing in style 😎 from 2019.
Over the past few months, we’ve picked up the style guide once more, revised what was there, and added a bunch of new guidelines to improve the readability of the Umbraco documentation even further.
The following guidelines have been added or revamped:
- Write shorter sentences
We now encourage you to keep your sentences below 25 words. Not always an easy task, I can tell you! But breaking tech-heavy and often complex information into smaller chunks helps to improve readability and the ability to understand the written.
- Define acronyms on first use - NEW ✨
Working in the software industry we might take the definition of a lot of acronyms like common knowledge. OK, maybe ‘HTML’ and ‘CSS’ don’t need an introduction, but ‘CDN’, ‘CLI’, and ‘SSMS’ do! 🙈 We have implemented a guideline that will prompt you to define the acronym the first time it’s used in an article.
- Spell Umbraco and Document Type correctly - NEW ✨
We want to ensure consistency between the Umbraco Documentation and the Umbraco products. This is why it’s important that features, product names, and other Umbraco-specific concepts are spelled correctly and use consistent casing. Is it ‘Doc Type’, ‘document-type’, or ‘Document Type’? In our guideline, we recommend using the latter 💪🏻
- Get the names, terms, and brands right
Some of these existed already, but we now have several guidelines to ensure that certain brand names and names of markup languages are written correctly. This includes writing ‘HTML’ instead of ‘html’ and remembering to capitalize the ‘T’ in ‘YouTube’. These might seem like small things, but in the big picture, they make a big difference to the overall perception of the Umbraco docs.
For Hacktoberfest we’ve asked for help with updating the Umbraco Documentation against all these new guidelines, and it has been a great success! Once we’ve had a minute to get an overview of all the things, we’ll make sure to share it with all of you ⭐