On this page
Day 20 - Tutorials by product: Cloud and Mail, step by step
We reorganized the tutorials by product and added simple KM0 Mail guides: create an account, sign in, and use your own domain.
With mail now mature (day 19), the documentation had to catch up. We reordered the tutorials and wrote new guides aimed at anyone, with no jargon.
Organized by product
The tutorials used to be a flat list focused on Cloud. Now they are grouped by product:
- KM0 Cloud: how to access from the browser, Android, iOS, and macOS.
- KM0 Mail: the new email guides.
That way, someone looking for help finds their product at a glance, without mixing contexts.
New KM0 Mail guides
Three short tutorials that cover the full journey of a new user:
- Create a KM0 Mail account: base plan €7.99/month (mail and cloud); pick a username and password and get your
@km0digital.comaddress. - Sign in: reach webmail with your address and password.
- Use your own domain: end to end, add the domain, publish DNS, verify it, create addresses, and sign in with them.
Each guide gets to the point: numbered steps, one problem per block, and a common-issues section at the end.
With screenshots where they help
Where an image saves explanation (the registration form, the sign-in screen, the domains panel), we left room for screenshots. They illustrate the step, not decorate the page.
In four languages
Everything is available in Spanish, Catalan, English, and German, with the same structure, so language is not a barrier.
Closing
The goal is for someone with no technical background to go from “I have no email” to “I write from my own domain” by following a guide. See them in tutorials, and if you get stuck, come to the next meetup.
More from the blog
- Day 29 - One KM0 login: Keycloak for Cloud web, desktop, and mobile Cloud in the browser, the OpenCloud desktop client, and the mobile apps now share the same KM0 sign-in. Why we moved, what to do, and links to the new tutorials.
- Day 28 - A cleaner front door for public HTTPS We put a reverse proxy in front of the public edge so TLS and routing sit in one place, with a maintenance path ready, while Cloud URLs stayed the same.