Nice! It looks like it reduces your steps to: - Encounter a status code in some code - Go to https://statuses.now.sh/ https://statuses.now.sh/ - Type in the

Nice! It looks like it reduces your steps to: - Encounter a status code in some code - Go to https://statuses.now.sh/ https://statuses.now.sh/ - Type in the status code - Read the explanation That's 66% of the steps. It's harder to remember that URL than wikipedia though. You could remove a step if you could easily put the number in the url without having to remember the "code" query param. Just go directly to https://statuses.now.sh/418 https://statuses.now.sh/418. I live in the terminal. If I'm investigating a status code then I have a terminal open. That's not true for everyone, but it'd be super cool if I could `curl https://statuses.now.sh/418` https://statuses.now.sh/418` and get plaintext information about the status right from my terminal! You could implement that by checking the user agent to see if it's curl/postman/etc.. or requiring a .json or .txt extension at the end. Either way, it'd cut my workflow down to three steps: - Encounter a status code in some code - `curl https://statuses.now.sh/418` https://statuses.now.sh/418` - Read the explanation. It also allows me to set an alias/function in my bashrc so that I don't have to remember the url. As for the svelte part, I haven't used it and don't really do frontend dev very often...but I bet you'd get more specific feedback on the code itself if you listed a git repo people could use to check things out.