shift-org / shift-org/shift-docs
clean up 404 page
Open
Nobody has claimed this yet.
enhancement
frontend
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 25
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
We can see that the build process currently does some "wizardry" around the 404 page:
https://github.com/shift-org/shift-docs/blob/main/netlify.toml#L19-L33
...where we copy the 404.html into public/. I suspect we could do this better/easier/automatically these days.
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 with netlify.toml lines 19-33 and inspect how 404.html is currently copied into public/ during the build. Determine whether the copy step can be removed or simplified, then verify that the built site still serves 404.html correctly without the current workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100