Find time to redesign RedwoodJS's 404 Not Found page

The 404 Not Found error is one of those things you never want your users seeing – but when and if they do, it should be informative and also friendly.

As legend has it, the origin of the error message has a very interesting story dating all the way back to the 1980s when a group of scientists at CERN (Switzerland) started working on what would become the World Wide Web.

In order to achieve this goal, the scientists worked to create a database infrastructure that offered open access to data in various formats.

The World Wide Web’s central database was located in the office on the fourth floor of a building — room 404 to be exact.

Many companies have given their 404 pages some character and style:

But currently, RedwoodJS’s is:

I like minimalism, but perhaps this is too “spartan”

image

Want to make this page better?

You can find the page code here:

Some general considerations:

  • All markup and styles need to be within the component
  • Shouldn’t rely on TailwindCss
  • Supports Safari, Chrome, Firefox, etc.
  • Quick to load, so relatively lightweight
  • Friendly, engaging, exciting
  • Reflects mission and sentiment from Docs - Introduction : RedwoodJS Docs

Open to new animation, mascot/characters, helpful links to resources … be creative!

And – practically every RedwoodJS dev will get to see your work at some point. How cool is that?

Reply here if you are interested and will be posting either a repo to contribute to or some other way to showcase your work so people can see and maybe vote for the page that becomes part of v1!

Also something that would be really useful in dev mode:

Listing all available routes on the 404 page. We certainly don’t want it in production, but would be a really nice experience to have in dev (just in case you have typos in your Routes.js)

Ooo I’m interested :open_mouth:
Here is my quick attempt, The file size is lower too by the looks of it.

https://neosh11.github.io/RedwoodJSErrorPages/

1 Like

Hi @neosh11 and thanks for submitting this.

I started a repo here: GitHub - redwoodjs/redwood-page-redesign: Help RedwoodJS redesign some framework pages and have your work seen by millions! to take submissions and began writing up the contributing process.

It isn’t complete, but I needed someone to try it out … and could use your help and comments to see if it makes sense:

Fork this repo
Copy the example directory in submissions
Rename this example directory to contain your github username (or some other way to identify you)
Within this directory is where you can contribute screenshots and components for each page to review.
Use the README.md to tell us more about your redesign concept and thoughts.
Submit a PR with a short message and introduction
We will review, comment and merge in after a basic check (just in the event there are inappropriate submissions)
Once merged the RedwoodJS community can review and decide which pages get to be part of the framework for v1.0! (Date TBD)

The idea is to let people create their own directory, then submit screenshots and code per each page.

Could you give it a try and let me know if it’s too cumbersome, etc?

Thanks!

1 Like

Yeah it makes sense @dthyresson ! Tried it out and submitted a PR.
I haven’t yet made proper designs yet though :stuck_out_tongue:

I’ll do that when I get some time!

1 Like