-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Description
Pointing out how "simple", "obvious", or "easy" something is can have the opposite-of-intended effect. If a person doesn't understand the 'simple' code, the project can seem inaccessible. "I don't understand this easy thing. I guess I just don't get it like other people do." A good resource on words to avoid is https://css-tricks.com/words-avoid-educational-writing/. Some that appear often in the Gatsby documentation are "simply", "easily", and "just (do x)".
For example, in the Plugins documentation:
Plugins are just Node.js packages meaning you install them like anything else in node using NPM.
Then in your site’s gatsby-config.js you simply add gatsby-transformer-json to the plugins array like:
If I wasn't familiar with node modules, or if I had any trouble or experienced a bug when adding something to the plugins array I might feel especially stupid for not "getting" an easy thing. IMO it's better to show something is easy than to say it is!
These could be rewritten to be more direct, not assume ease, but still be friendly:
Plugins are Node.js packages. You can install them with NPM.
Then, in your site’s gatsby-config.js add gatsby-transformer-json to the plugins array:
I removed this type of language from the Vue documentation, but don't currently have time to try the same here. Would you consider cleaning up some of the language that assumes ease?