Add documentation on the documentation repo structure and some basic things (e.g. editing rules of markdownlint)
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 71
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 11
Description
The README has some info on this, but would be good to have it in the docs website itself?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the README sections describing the documentation repository structure and markdownlint editing rules, then locate where equivalent material belongs on the documentation website. Done means the website explains the repository layout and the basic Markdown editing rules currently covered by the README.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100