projectwallace / projectwallace/projectwallace.com
📚 rewrite docs
Open
Nobody has claimed this yet.
page: docs
- Dominant language
- Svelte
- Stars
- 3
- Forks
- 0
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 11
Description
- group current docs, like vendor prefixed values, into a single doc
- setup redirects
- refer to docs from analysis and code quality
- link to tons of blog posts for examples and other stuff: manuel matozovic, stefan judis, polypane/kilian valkhof, etc
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 locating the current documentation and the analysis and code-quality pages mentioned in the checklist. Group the existing material, identify where redirects belong, and review the listed authors' blog posts for suitable examples. Done means the docs are consolidated, redirects are set up, related pages link to them, and example posts are referenced.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100