Hello community, I’d like to get a feedback of what you think:
With V1.0 I’d enjoy to have an /e/ introduction manual for new users: A comprehensive and compact document that is printable (PDF) and written in an accessible language (length 5-10 pages).
I am aware that there’s an online manual/wifi in preparation. But I do not see this as a concurrence product rather as a kind of (additional) starter document for less tech-affine future /e/ users.
The document should include (what I have in mind for now):
What is /e/ / Who’s behind / What does it mean Android without Google / Intro to data security privacy in the Internet
Guidance through the initial installation process (including how to get an e-email address)
Very brief explanation of the system and its different preinstalled apps with a special focus on the ones that are particular for /e/ - such as Trust
Explanation of the security features of /e/ as well as the webbased side of /e/.
Explanation of things to keep in mind when using /e/
– Traffic with /e/ services - if you are on a data connection this implies that photos are uploaded
– Naming folders that are synced with the /e/ services and how to switch off specific ones.
– How to (re)connect a device with /e/ services when it is not done in the initial setup process
Further references to the /e/ wiki (direct reference links to specific topics) to user forum and other sources for getting support (in what languages).
A summary that explains
– …especially what /e/ provides and what it doesn’t (/e/ is not and cannot be a fully secure tool for phone and internet use).
If this document is becoming a first reference document for new users, it can contain other stuff that is of particular importance for the /e/ team…
This manual could serve for instance as a perfect self-advertisement for /e/ - as a honest and transparent product. Furthermore it could be a great place to stress how /e/ is financed and that (satisfied) users are invited to support/donate (ideally on a regular basis) or to buy a subscription.
It could be a good place as well to underline the community driven aspect of /e/ and that respectful communication is key. The latter point is something I really enjoy in all interactions with the community so far but it will probably take some efforts to maintain that once /e/ will go public.
That’s all for now, please feedback.