Feature #11495
JavaScript to provide links to all previous steps in installation assistant
0%
Description
As suggested in https://labs.riseup.net/code/issues/11269#note-11:
In the installation assistant itself consider adding a “Timeline” on top, with clickable items so that we can jump to the last step directly if we want to, because for example, we already know that installation will take x hours and don’t care reading this twice.
My proposal is to add this on all pages: https://tails.boum.org/install/win/index.en.html, https://tails.boum.org/install/mac/index.en.html and https://tails.boum.org/install/debian/index.en.html
Something like step 1 - step 2 - step 3. Where the currently active step is visually distinguishable from the others.
Subtasks
Related issues
|
Related to Tails - |
Resolved | 2016-03-21 |
History
#1 Updated by Anonymous 2016-05-27 10:32:00
- related to
Bug #11269: Consider linking to /install/download from /install added
#2 Updated by sajolida 2016-05-27 16:37:16
- Category set to Installation
- Status changed from New to Confirmed
- Priority changed from Normal to Low
- Type of work changed from Discuss to Website
Again, I’m seeing this after answering on Bug #11269 so pasting my answer here:
I agree that this would be an improvement. Still, I don’t
consider it as an important bug enough to fix as part of our contract
with Hivos, so I won’t add it to my plate but will be very excited about
reviewing patches. This sounds like something to be written in
JavaScript, no?
#3 Updated by sajolida 2016-05-27 16:38:47
- Description updated
#4 Updated by sajolida 2016-05-27 16:39:05
- Description updated
#5 Updated by sajolida 2016-05-27 16:47:08
- Description updated
- Status changed from Confirmed to New
- Assignee deleted (
None) - Priority changed from Low to Normal
- QA Check set to Info Needed
Hmm… While trying to edit the description of this ticket I realize that I didn’t understand the proposal correctly. You’re actually talking here about the “router” part of the assistant (/install/debian, /install/win, /install/mac). I thought you were talking about the “steps” (/install/win/usb, /install/clone).
Since you’re talking about the “router” I’m not sure what do you refer as “Step 1”, “Step 2”… If you are talking about the installation steps (the 7 steps from /install/win/usb for example), then each page of the router links to different installation scenario (two in general: “Clone” and “USB”, four for /install/mac) so to which steps of which scenario would you link to?
Maybe you could do a wireframe mockup so I understand better the proposal?
#6 Updated by Anonymous 2016-05-29 21:03:16
sajolida wrote:
> Again, I’m seeing this after answering on Bug #11269 so pasting my answer here:
>
> I agree that this would be an improvement. Still, I don’t
> consider it as an important bug enough to fix as part of our contract
> with Hivos,
ack.
> so I won’t add it to my plate but will be very excited about
> reviewing patches. This sounds like something to be written in
> JavaScript, no?
Not necessarily, no.
#7 Updated by Anonymous 2016-05-29 21:09:44
sajolida wrote:
> Maybe you could do a wireframe mockup so I understand better the proposal?
Hm, that’s a pity that it is not understandable. I dont really have the time to work on a wireframe, sorry. Let me try again.
For example, consider the Windows installation process. First click i end up here:
https://tails.boum.org/install/win/index.en.html. That’s step 1.
Second click, as an example, I end up here: https://tails.boum.org/install/win/usb/overview/index.en.html
That’s step 2. No i need to scroll down.
Third click I end up here: https://tails.boum.org/install/win/usb/index.en.html That’s step 3, which itself contains 7 steps to accomplish.
So my idea is simply to add Step 1 - Step 2 - Step 3 on top of each of these 3 pages. This should be clickable so that I can jump back and forth. It’s completely doable in HTML. The current step should have a darker color or other visual feedback to tell the user: ok, you’ve clicked that many times, and now there is nothing else ahead, here you are. You are welcome, our installation process is transparent.
#8 Updated by sajolida 2016-05-31 21:02:12
Ok, now I got it! So you’re talking about quick links between:
- 1. The OS page
- 2. The overview
- 3. The steps
Let’s analyze all the combinations to see what we have already and what
is missing.
Links forward:
- OS → overview: This is already provided by the regular buttons and we
can’t provide a single option forward as people have to choose which
scenario they want to follow. - OS → steps: Same here: it’s not possible to give a shortcut because we
can’t know in advance which scenario people are going to choose. - overview → steps: This is provided by the “Let’s go!” button. I agree
with you that having to scroll is not nice and I dislike this as well.
I’ve been lobbying tchou, in vain so far, to make this screen more
compact and allow displaying the “Let’s go” button without scrolling.
I’d be happy if you helped me.
So I think there’s not much worth being done regarding links forward,
except making the overview more compact.
Links backward:
- overview → OS: This is already provided by the “Back” button.
- steps → overview: I’m realizing now that we don’t have a “Back” button
on the steps. This should be possible to add in most cases but wouldn’t
work for DVD (which is linked from all the different OS pages). I think
that’s why we didn’t put any but I’m not against adding one when it’s
possible. - steps → OS: Same as before. This would be possible with ikiwiki
techniques only in most cases (/install/win/usb for example) but not
always (/install/clone) unless we create different pages for
/install/clone according to the base OS. In my opinion, it’s not worth
it. Maybe this can be done more efficiently with JS but I don’t know.
So, regarding links backwards there is room for improvement. We could
provide, using ikiwiki techniques when possible, direct links to all the
previous steps. Still, note that this won’t be possible on all pages and
will introduce inconsistency. For example we won’t be able to do this on
/install/clone/overview or /install/dvd without creating a duplicate of
this page for each OS. You’d have to tell me whether this is possible
and worth it using JS.
#9 Updated by Anonymous 2016-09-06 03:50:13
- Assignee set to sajolida
Thanks for going into detail here.
So, indeed, we would not want any inconsistency.
JS could do the job - by setting a cookie which tells us from which page I arrived yes. But do we want that?
#10 Updated by sajolida 2016-09-10 09:55:44
- Subject changed from Consider adding a timeline for the Installation Assistant to JavaScript to provide links to all previous steps in installation assistant
- Status changed from New to Confirmed
- Assignee deleted (
sajolida) - Priority changed from Normal to Low
- QA Check deleted (
Info Needed) - Type of work changed from Website to Code
I’m personally fine with having JavaScript on our website to improve UX, as long as the website is also working good without it. See https://tails.boum.org/blueprint/bootstrapping/assistant#index7h1
The result quite often is that, once we found a solution that is good enough for people without JavaScript, we’re lazy to implement the fancy improvements for JavaScript.
The sure thing is that I’m not going to be the one to write this JavaScript because I don’t know how to do that, so I can’t evaluate the cost. I would say that the benefits are low. On the other hand, we might be interested in reusing such JavaScript on other parts of the website in the future (I can’t think of anything in particular right now).
So I’m updating this ticket accordingly.
#11 Updated by Anonymous 2017-06-29 12:50:27
- Status changed from Confirmed to Rejected
I agree that benefits for this are simply too low. Closing.