Tails

#2 Updated by esperal 2014-05-15 15:04:46

I’m up for doing that since I was the one moaning about it ;)

#4 Updated by sajolida 2014-05-17 02:40:40

redmine@labs.riseup.net:
> Issue Feature #7214 has been updated by esperal.
>
>
> I’m up for doing that since I was the one moaning about it ;)

Cool. I created a couple of subtasks to Feature #7214. I guess you could start
working in parallel on:

Feature Feature #7255: Identify which entries to put in a more complete sidebar
Feature Feature #7257: Write the code to have submenus on the sidebar

Regarding the first, I think this will need to go through tails-dev,
either you can do a proposal first and then ask for comments, or you
could start a brainstorming there, gather input, and then make a proposal.

#5 Updated by esperal 2014-07-01 23:35:26

DEMO: http://35p3ral.webuda.com/index.html
INSTRUCTIONS: http://tny.cz/3ce1ab6a

I added few new elements to the sidebar that should be visible at all times… IMO of course. I also wanted to reduce the number of clicks to those places. I think that FAQ, Press & Media, Contact Us are the things that the new Tails users will look for and find them useful.

New users will definately have some questions so FAQ should be visible at all times.

Same goes for the contact details. It’s kind of a normal, expected thing to be in a website menu.

Next, ‘Press & Media’ … we should be proud what others say about Tails :)

‘Quick Links’ dropdown item. It will be a time saver, less clicks, better user experience and no more problems with way too long sidebar. I did try to include stuff that users, devs and press people might look for. The elements I decided to include are:

• Tails Roadmap
• Design Document
• Known issues
• Report an issue
• Request a feature
• Next release changes
• Q&A (external website)
• Git repositories
• Mailing list
• License

This dropdown can have much more items, so please write your proposals.

I was a bit confused about links to Mailing List, List of known issues and the FAQ.

Should the Mailing List link to:
https://mailman.boum.org/listinfo/amnesia-news or https://tails.boum.org/support/tails-support/index.en.html ?

Should the List of known issues link to:
https://labs.riseup.net/code/projects/tails/issues or https://tails.boum.org/support/known_issues/index.en.html ?

And lastly the FAQ link:
https://tails.boum.org/support/faq/index.en.html and the external Tor Stack Exchange, tagged with ‘tails’ https://tor.stackexchange.com/questions/tagged/tails I did include both anyway… but it might be confusing.
If it is the first one, the one one Tails website, it would be good to add a paragraph on top, just above the questions, something like “If you didn’t find the answer to your question in our FAQ, please send us an email to example@example.com with a subject line ‘FAQ’. To achieve end-to-end encryption, encrypt such email with our OpenPGP key.” We should give them a change to ask a new question.

But if this FAQ is no longer maintained then tell users to ask questions on tor stack exchange, tagging it with a ‘tails’ tag?

If you are OK with this sidebar please follow these instructions http://tny.cz/3ce1ab6a

#6 Updated by intrigeri 2014-07-02 00:36:14

> DEMO: http://35p3ral.webuda.com/index.html

Would it be possible (please :) to have it somewhere that doesn’t block Tor exit nodes? (Or is it just my current one?)

#7 Updated by sajolida 2014-07-02 09:37:30

> Would it be possible (please :) to have it somewhere that doesn’t block Tor exit nodes? (Or is it just my current one?)

Same here :(

#10 Updated by esperal 2014-07-20 10:04:16

intrigeri wrote:
> I think this was worked on during the Tails HackFest and/or summit. Could the output be made available somewhere, e.g. as a blueprint, or finer-grained sub-tickets?

Yeah that would be great

#11 Updated by Anonymous 2014-07-20 16:00:23

Actually, we have not worked on this during the HackFest, as there was no time left for this question.

However, we have decided to pause the work on the sidebar for the moment, in order to concentrate first on the restructuring of the website. This will undoubtedly influence the sidebar issue.
One idea which had been raised but not agreed upon entirely was to have a sidebar according to the “category” of pages one navigates in at the moment. For example: if i would be in the developer section of the website i’d have development related entries in the sidebar and a main menu to get back to main points.

Esperal, I apologize that nobody has updated you on this yet, i think we have all been quite busy. We shall try to improve communication a bit here.