Commit 9a35b264 authored by sajolida's avatar sajolida
Browse files

Improve blueprint on Mac compatibility list

- Make it a subsection of the router (instead of h1)
- Improve English
- Rewrap very long lines
- Call Apple computers as "Mac" consistently
parent f8fbf068
......@@ -115,69 +115,79 @@ Third iteration
- Mention virtual machines as a minor option on OS page or destination media page.
- Consider improving navigation.
List of compatibility with Mac
------------------------------
Seeing that:
## For the router's Apple page : maintain a Tails compatibility list
- A lot of current and potential users are Mac users.
- Tails is running more or less on this devices.
- There are a limited number of different models.
Seeing that :
- a lot of current and potential users are Apple users
- Tails is running more or less on this devices
- There are a limite number of different models
We suggest to maintain a list with the state of the tails compatibility on this hardware. So in the web assistant router a potential user could know if Tails works on his computer and wich way (dvd/usb...) before he tries to install it (and maybe wich computer to buy).
We suggest to maintain a list of the state of Tails compatibility on
these computers. In the router of the web assistant, a potential user
could know if Tails works on her computer and on which media (DVD or
USB) before she tries to install it.
### Data type
The data could be stored in a yaml file, in the git repo.
The data could be stored in a YAML file, in the git repo.
### Data content
Something like :
Something like:
model / part of the serial number
tails version | working ? | boot on usb ? | boot on dvd ? | comments
* In we way to keep history off compatibilty (with olders Tails versions) in this file, maybe we will have to show to the user the last relevant informations. We have the "Tails version" to :
- know globaly how evolves the support for Apple computers
- aware the user or the support teams where compatibilty has broken
* "comment" are raw informations on wifi support, retina..
Tails version | working? | boot on USB? | boot on DVD? | comments
* In we want to keep history of compatibility (with older Tails
versions) in this file, maybe we will have to show to the user only
the last relevant informations.
* "Tails version" can be useful to:
- Have a better view of how the support Mac evolves.
- Let the user or frontdesk know when the compatibility got broken.
* "Comments" is raw information on Wi-Fi support, graphic support, etc.
### Who maintain ?
- call to heavily test sometimes
- ask to people doing Tails trainings
- report to frontdesk
- mayby something editable by users
### How to feed the list
### In the router
In the Apple page of the router, we could implement it in two steps, or in two ways.
- Call to heavily test sometimes
- Ask to people doing Tails trainings
- Update from frontdesk
- Maybe something editable by users
#### all information (without form)
### Implementation
- data is transformed server-side (with https://ikiwiki.info/plugins/contrib/ymlfront/ ?) in html in a table, with links to the working scenarios for each models.
- everything is one the html
- some information is displayed to know easily what kind of mac is working (simplifing https://fr.ifixit.com/Info/ID-your-Mac ?)
- the user can toggle to display content (a list by computer type : iMac, Macbook Air...)
- toggle is in JS, as a fallback : display all information (no toggle)
In the Mac page of the router, we could implement this in two ways, that
could be two iterations.
#### relevant information (with form)
#### All information (without form)
- some information is displayed to know easily what kind of mac is working
- the user type in a form the serial number or click in a dedicades tiny wizard like https://fr.ifixit.com/Info/ID-your-Mac
- some server-side (ruby) or client-side(JS) get the revelant model and display the links. so the user see information for his computer
- if it's in JS, as a non-js fallback :
- the "without form" version
- or no fallback, just the default instructions
- Raw data is transformed server-side into an HTML table with links to
the available scenarios for each model (maybe using
<https://ikiwiki.info/plugins/contrib/ymlfront/>).
- The full list is included in the HTML page sent to the user by hidden
in toggle by default.
- Some information is displayed to help the user identify his type of
Mac (maybe simplifying <https://fr.ifixit.com/Info/ID-your-Mac>).
- The user can toggle to display the sublist corresponding to her type
of Mac (iMac, Macbook, MacBook Air, etc.)
- If JavaScript is disabled, the full list is displayed.
#### Only relevant information (with form)
- Some information is displayed to know easily what kind of mac is
working
- The user types in a form the serial number of her Mac or clicks in a
dedicated tiny wizard like <https://fr.ifixit.com/Info/ID-your-Mac>.
- Some server-side code (Ruby?) or client-side code (JavaScript) gets
the relevant model and displays the possible scenarios.
- If implemented in JavaScript, it would fallback on the "without form"
version described earlier.
### Redmine
### Redmine
This tickets wants to fix the same problem : [[!tails_ticket 9150]]
<a id="overview"></a>
Overview
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment