NCAR / NCAR/MechanismConfiguration
Standardize our doc style
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1
- Forks
- 3
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 4
Description
Replicate the same doc layout and style as micm
Contributor guide
No contributing guide indexed for this repository
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 by reviewing the repository's current documentation and the linked micm documentation to compare their layout and style. Identify which documentation sections would need standardization; done means the project's documentation follows the same agreed layout and style as micm.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100