Restructure the installation pages

Terminology

The router is the set of pages that help the user choose their installation scenario, for example:
- https://tails.boum.org/install/
- https://tails.boum.org/install/win/
The overview appears after the router to summarize the process, for example:
- https://tails.boum.org/install/win/usb-overview/
The download page appears after the overview, for example:
- https://tails.boum.org/install/win/usb-download/
The steps are the installation steps themselves, for example:
- https://tails.boum.org/install/win/usb/

Current problems

In #18074 (closed), several participants had a hard time finding the link to the steps from the download page, not verifying their download didn't help. After that, they went free style without installing and run into big troubles.

These people went frequently back-and-forth between router, overview, download, and steps.

For example, they went back to the overview when they were lost without knowing what to do with the USB image because they missed the link to the steps from the download page.

The fact that the download page is not linear didn't help: the warnings are at the bottom of the page and the link to the steps is before the warnings.

Should we merge the overview, download, and steps to have all the process on a single page?

Would merging overview and download make more people skip the overview and still get lost in the process?
In #18074 (closed), only 1 person verified their download.

On top of improving the verification instructions (#18776 (closed)) and mentioning the verification in the overview (#18774 (closed)), should we make it more visible or get people to pause more at this step?

How might the structure of the page make it so that more people verify their download?
In #18074 (closed), nobody commented on the warnings.

Maybe it's not a big deal given the test participants didn't feel personally at risk.

How might we get more at-risk users pay attention to the warnings?
Hardware warnings are not consistently integrated (#17441 (closed))
- https://tails.boum.org/doc/about/requirements/
- https://tails.boum.org/support/known_issues/
- https://tails.boum.org/install/mac/
- https://tails.boum.org/install/mac/usb/#back (right before the anchor)
How much should we bother people about hardware requirements and when is the best time to do so?
The installation pages are not very exciting visually.

In #18074 (closed), nobody commented on the intro of the router.

Now that we have @anhdres, we could add visual to support better this long process emotionally.

Since the process became simpler, how do we want the beginning of the process to feel to users?

What are the best opportunities to support the process with visuals? How should they feel?
SEO is tricky with the current multiple pages

Currently we index the overview and have noindex in the download page and the steps to prevent people from ending on the steps without downloading. This means that the content of the steps is not searchable. For example, searching for "install etcher" leads to pretty poor results on DuckDuckGo.
The router is more complicated than it should.

We created the router in 2015 because Mac users had complicated options to choose from and because we wanted to put forward that installing from another Tails was always much easier. It's not the case anymore since we distribute USB images.

How might we improve the structure of the router?

Open questions and ideas

Move "Download" after "Install Etcher"?
- Makes it clear that people can't free style after the download
- Makes it clear that it can't be done from a phone
Move "Warnings"
- Before "Verification" to encourage people to read them while download?
- Just before running Tails to remove clutter from the download and verification steps?
How many stops do we want for users as they move forward in the process?
- 1 stop for each step
- Only strategic stops, even if they don't match the big steps
- No strong stop but scroll snapping
How many steps?
- Are all the steps on the page are mapped to a step in the overview or in-page navigation?

TODO

Edited Feb 28, 2022 by sajolida

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information