Feature #9308

What do we do for people coming from search engines inside the assistant

Added by tchou 2015-04-30 12:12:36 . Updated 2018-04-24 14:26:55 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Installation
Target version:
Start date:
2015-04-30
Due date:
% Done:

100%

Feature Branch:
feature/9308-dont-index-installation-instructions
Type of work:
Discuss
Blueprint:

Starter:
Affected tool:
Installation Assistant
Deliverable for:

Description

If we do nothing special, people could crash on random pages in the Tails Installer Assistant. At some point it could be problematic, for example someone using firefox on a tablet comes in the “Linux/Install Tails Downloader” extension. A user starting at the begining of the assistant would have been routed to a specific path (no scenario for you, sorry).

We could :

- unindex all the internal pages of the assistant. We don’t have this probleme anymore, but we have an other problem : maybe we could like to have some of this pages indexed to get have some traffic.
or
- have some warning or reminders in some pages. In wich page ?


Subtasks


Related issues

Blocks Tails - Feature #15392: Core work 2018Q2 → 2018Q3: User experience Resolved 2018-03-09

History

#1 Updated by BitingBird 2015-04-30 20:05:01

  • Subject changed from what do we don't for people comming from search engines inside the assistant to what do we don't for people coming from search engines inside the assistant
  • Category set to Installation

#2 Updated by BitingBird 2015-04-30 20:05:21

  • Subject changed from what do we don't for people coming from search engines inside the assistant to What do we do for people coming from search engines inside the assistant

#3 Updated by sajolida 2015-05-01 08:15:28

  • Status changed from New to Confirmed
  • Assignee set to tchou
  • QA Check set to Info Needed

I think that:

  • The pages from inside the route shouldn’t be indexed by search engines (and if they are it’s probably no big deal).
  • The overviews and steps can be indexed with no problem as they are supposed to make it clear what we are doing and where we are.
  • The overview should make it clear which scenario has been selected.
  • The steps should have a reminder of the scenario.

#4 Updated by BitingBird 2015-05-13 04:58:01

  • Affected tool set to ISO Verification Extension

#5 Updated by sajolida 2015-05-13 11:01:28

  • Affected tool deleted (ISO Verification Extension)

The web assistant is different from the ISO verification extension. We probably miss an “affected tool” for it. I’ll ask tails-sysadmins.

#6 Updated by BitingBird 2015-05-13 16:24:42

oops sorry

#7 Updated by sajolida 2015-05-19 19:23:23

  • Affected tool set to Installation Assistant

#8 Updated by sajolida 2015-08-15 08:25:46

  • Priority changed from Normal to Low

#9 Updated by sajolida 2015-11-23 08:57:07

  • Priority changed from Low to Normal
  • Target version set to 246

#10 Updated by sajolida 2015-11-23 08:57:14

#11 Updated by sajolida 2015-11-24 02:51:22

#12 Updated by sajolida 2015-11-27 04:44:28

  • Target version changed from 246 to Tails_2.0

#13 Updated by sajolida 2016-01-16 16:26:38

  • Target version deleted (Tails_2.0)
  • Parent task deleted (Feature #8592)

Let’s say this is a bonus and not a blocker for the first release.

#14 Updated by intrigeri 2018-03-01 09:09:01

  • Assignee deleted (tchou)
  • QA Check deleted (Info Needed)

#15 Updated by sajolida 2018-03-01 11:05:45

  • Assignee set to sajolida
  • Target version set to Tails_3.7

#16 Updated by sajolida 2018-04-16 11:07:06

  • blocks Feature #15392: Core work 2018Q2 → 2018Q3: User experience added

#17 Updated by sajolida 2018-04-17 14:28:14

  • Assignee deleted (sajolida)
  • QA Check set to Ready for QA
  • Feature Branch set to feature/9308-dont-index-installation-instructions

Here is a branch!

feature/9308-dont-index-installation-instructions

Ulrike: Same as Feature #15114#note-3. I think this is core UX.

#18 Updated by sajolida 2018-04-19 17:55:34

  • Status changed from Confirmed to In Progress

Applied in changeset commit:be7f91b823a6207f3038b13625a3105e98cb8288.

#19 Updated by Anonymous 2018-04-24 14:26:55

  • Status changed from In Progress to Resolved
  • Assignee deleted ()
  • % Done changed from 0 to 100
  • QA Check deleted (Ready for QA)

LGTM. Merged into master.