Skip to content

Tip 41 - if you please

Docs writing often addresses the reader to avoid clunky sentences or passive voice. When writing instructions, letting your reader know what ā€œyou will seeā€ can be helpful and reassuring as they work through your guides. Docs is, though, a one-way broadcast.

Writing your docs to your readers doesnā€™t mean you have to follow conversational conventions. You can respect your readers without being ā€œpolite.ā€

One PR suggestion I will make is to remove formalities and pleasantries when Iā€™m not soliciting or recognizing particular action. We typically donā€™t ā€œthankā€ our readers at the end for completing our guide. (Though, we may thank visitors for expressing an interest in contributing when they land on our Contributing guide!) Itā€™s just as out of place to preface instructions or explain features with ā€œplease.ā€

  • āœ… Adding the official Astro MDX integration allows you to write standard Markdown with JSX variables, expressions and components.
  • šŸ˜ Please install the official @astrojs/mdx integration to use JSX variables, expressions and components.

No, Iā€™m also not a fan of ā€œPlease see the view transitions guide for more information.ā€ I am not asking them to go there. I am informing them that there is more information available. ā€œPleaseā€ implies a request. Or, it is overly formal/flowery language that doesnā€™t belong in our docs anyway.

I try to make Astro docs as full-service as possible. If Iā€™m doing it right, I shouldnā€™t need to ā€œaskā€ you to do anything. Just sit back and enjoy the docs!

Toggle Comments

Ā© 2021 - 2024 Sarah Rainsberger. Except where otherwise noted, and/or quoting external sources, the content of this site is licensed under CC BY-NC-SA 4.0