Description of implications for end users
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
A short description at the start of the Solid specification explaining the desired implications for end users.
There was the beginning of something along these lines on solid spec although could be good to get more specific in a revisit.
Solid in a Nutshell is another attempt that could be a helpful reference for this work.
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 overview of the Solid specification and compare the existing text with the linked Solid in a Nutshell reference. Draft a short, specific explanation of the intended implications for end users at the beginning of the specification, then verify that it fits the surrounding document and addresses the requested user perspective.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100