Introduction
============

So you heard about this operating system called Qubes OS.
Maybe you've dabbled in Linux and want to take the next step. Maybe someone sent you this link and
you already have strong opinions about Qubes or Linux — which is fine, I won’t hold that against you.

This documentation is written primarily for people in that first group: curious, motivated,
but unsure where to start.
That said, if you are in that second group I mentioned, you may be find yourself intrigued with some
of the concepts and want to apply to your own workflow.
This documentation can be used in many ways as I will cover not just Qubes OS, but also other tools
such as i3wm which I also recommend.

Why I Wrote This
----------------

If you're trying to install Qubes OS, you've probably browsed the official website and skimmed
through the introductions.
They’re full of excellent information — but it can also be overwhelming when all you really want is:

**“How do I get this thing working?”**

That was me when I started. I came from Arch Linux, so I was already
used to:

- nothing working out of the box,
- breaking a huge problem into tiny pieces,
- and eventually getting something functional.

But Qubes OS adds a new layer of complexity on top of that. You might love it or hate it, but the
reality is: **it’s getting easier**, the documentation keeps improving, and despite what the
internet says, Qubes is not just for people “hiding from governments.”

Understanding Use Cases
-----------------------

One of the Qubes OS introduction pages talks about
`use cases <https://doc.qubes-os.org/en/latest/user/how-to-guides/how-to-organize-your-qubes.html>`_
for organizing qubes. When I first read it, it went over my head. I didn’t care about use cases —
I wanted *results*.

Now I get it.

Their point was simple:

**“When you understand how to mold Qubes to your lifestyle, it works beautifully — with the bonus of
reasonable security.”**

There is no one-size-fits-all solution. Everyone uses technology differently, and Qubes gives you
the tools to shape your environment to your needs.

What This Documentation Covers
------------------------------

This entire project documents **my** approach to Qubes OS:

- my workflows,
- my architecture choices,
- my templates,
- my policies,
- my mistakes,
- my improvements over time.

While I won’t explain **every** little detail — for obvious reasons — I will show the majority of
what I do so you can:

- understand the reasoning,
- replicate it **manually**,
- and avoid the trap of mindlessly copying dotfiles or configs without
  learning anything.

(Because let's be honest, we have all either seen people clone rices, try to use them, and quit or 
we were those people.)

If you have the time, patience, and the desire to take control of your technical life, you can
absolutely learn this. It might feel daunting at first, but with effort you *will* understand what
you're doing.

Documentation is a Skill
------------------------

If you don’t understand something, look it up.  
Man pages, StackOverflow, Qubes Forum, and official docs exist for a reason.

Reading documentation — really reading it — is a skill.  
And you’re practicing it right now.

.. admonition:: Disclaimer

    I am not a tech guru who knows everything. I might know more than you (for now), but there are 
    people far smarter than me who know more about every topic I discuss.
    So take everything here with a grain of salt.  
    Verify things.  
    Cross-check sources.  
    Qubes itself teaches you that—starting with verifying its ISO ;)