solid / solid/solidproject.org
Review the way the "redirects" are used
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 183
- Forks
- 152
- PR merge metrics
- No merged PRs in 30d
Description
In a nutshell: none of these presumably redirected resources are actually available a different URI. For example, the identity of the resource "newsletter" can't be found on the resource identified for "homepage", and the list goes on
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
No file, test, or entry point is named. Start by locating the site's redirect definitions and checking the referenced resource URIs, including “newsletter” and “homepage”; done means every redirect either identifies the same resource at another URI or is corrected or removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100