solid / solid/solidproject.org

Add a short history of Solid

Open
#840 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
183
Forks
152
PR merge metrics
No merged PRs in 30d

Description

Search terms you've used

history
Is your feature request related to a problem? Please describe.

There has been a lack of understanding of the basic history of th Solid Protocol in for example W3C discussions.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Add a link to history in the about for example,
and include the content of
https://www.w3.org/DesignIssues/history/AShortHistoryoftheSolidProtocol.html
as a new page.

In a place where it is github controlled to others an suggest additions or corrections.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context

I have suggested content for the moment parked here but wan't sure where to put inn the site and thought it should go in
after the refactor.

https://www.w3.org/DesignIssues/history/AShortHistoryoftheSolidProtocol.html

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the current About section and the site's post-refactor structure; no specific files or tests are named. Use the linked W3C page as the proposed history content and determine where a GitHub-controlled page and About link belong. Done means the history is published and additions or corrections can be proposed through the repository.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.