Improve documentation
See original GitHub issueI’ve been thinking about this for a while. I just want to show my plan here and maybe get some advice/suggestions before making any change.
- Add feature descriptions (e.g. scopes and how to add more)
- List supported formats (by default)
- Explain “hidden” behaviors (e.g. using
prettier
from project dependencies) - Review contributing guidelines
- Add table of contents and links to navigate back to top
- Add links to other documents (contributing guidelines, code of conduct)
- List ESLint rules that match Prettier options (for config tweaks)
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Strategies for Improving Documentation
EHRs increase healthcare providers' responsibility and accountability with respect to reviewing, comprehending and documenting personal health information.
Read more >10 Tips to Improve Technical Documentation Skills
Technical writing requires knowledge of the subject and creative writing skills. Find out how to improve your technical documentation skills ...
Read more >How to Improve Documentation In Healthcare - Ditto Transcripts
What is effective healthcare documentation? · Provide factual, consistent, and accurate input · Update the information after any recordable event ...
Read more >Five ways to improve clinical documentation and bridge the ...
Five strategies for improving clinical documentation compliance · 1. Do the pre-work before launching a CDI program · 2. Find a physician champion...
Read more >Tips for Great Nursing Documentation - Rivier Academics
Improving Your Nursing Skills. Nursing documentation is critical to effective communication within a patient care team. Develop the communication skills you ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh also, it might be useful to list a mapping of the eslint rules to their prettier rules, so people know what rules to set in their eslint config
I think we definitely should go into greater detail of how the different options interact with each other. We’ve had a lot of issues in the past where people didn’t properly understand how various settings were getting chosen, especially regarding the eslint integration and which version of prettier gets used. At first, we didn’t have this because it was simpler, but lots of people requested it, so we put it in, and now people are confused by it. I think it’s nice to have, but you’re right, it needs to be made more clear what is going on.
We just need to make sure that people who want a really quick rundown of how to use the plugin aren’t overwhelmed by the amount of information, so if we could somehow put the really quick rundown of what the plugin does and how to use it first, and then link to a different section for those wanting a deep dive, that would be great.
Also, “Add anchors for navigation” should automatically be done by GitHub’s markdown parser if I’m not mistaken.
Contributing guidelines and code of conduct and all of that probably needs updating as .you say, I think a lot of that I just copied over from prettier-eslint and didn’t really update it.
As far as feature descriptions, I almost feel that we should stick to modifying the config-schema.json descrptions so that it’s DRY and so that people don’t have to leave Atom to figure out how things work?