Add documentation
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 4
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Information about class names are necessary and there are a bunch of mixins that should be documented as well.
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
The issue requests documentation for class names and mixins, but names no files, entry points, or tests. Start by locating the CSS stylesheets and mixin definitions, then inventory the relevant items; done means the requested class names and mixins have clear documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- documentation, frontend
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100