Closed Greggless closed 6 years ago
Some comments from on 404 in #397
- "404: Page not found" is confusing. This page has useful content.
- "Snap 'azure-iot-edge' (snap id)". Snap is redundant and grammatically odd as the first word. The snap ID is meaningless to anyone but the developer of this application. I don't think it should be shown on this page.
- "… has no published revisions in the given context." This is unnecessarily technical. Do we think end users will know what a "published revision" is? What context is "this context"? How about dropping the 404 and instead saying:
azure-iot-edge is not available in the stable channel, but may be available in the candidate, beta, or edge channels. Run
snap info azure-iot-edge
on a snap enabled system to review the installation options.
Puns are MVP
Ah, snap!
Perhaps “Aw, snap!” would better express the disappointment. (To me, “Ah, snap!” seems delighted.)
Try searching for the snap
For any given 404, often it will be an end user trying to visit a snap’s directory page. But not always, for example:
/account
So, probably we shouldn’t assume you are looking for the end-user page for “the snap”. Perhaps pose it as a question: “Looking for a snap? Try searching:”
Roger roger, I concur will all of the above.
To summarise:
Aw, snap! We couldn't find that page.
Looking for a snap? Try searching: | ____ | Search | Or browse the Snapcraft Forum or Docmentation
If we take a look at some other 404's from around the world wide web we can see that they have been actually designed. We should follow suit and help our users who end up at a dead end.
404's
Github
A search? Hell yeh (maybe)!
Heroku
Useful links? Hoorah!
Digital ocean
Digital ocean
Short page to expose an extensive footer? đź‘Ł Great!
Docker
I just like the whale.