feat: Add dark mode (fix #2)

[hugoattal]

Fix #2

Description

I added dark mode in a header using vue-use:

Additional context

It's the first time I use tailwind, and as someone who love doing frontend stuff, I can't emphasize enough how much I hated it. IMO, this enforces all the bad practice on frontend development without any benefit (other that not using CSS? I mean, I love CSS, so it's not a benefit to me).

• The templates classes are unreadable
• I must search the documentation every time I want to use a CSS property
• No class name makes sense, especially when using flex
• No fine-tuning at all
• I hoped that making a dark theme will be as easy as adding a class in the HTML, but no, we must update ALL the component to add a dark: class instead of leveraging the use of CSS vars.
• The result isn't even that good

I know you guys are used to it, so I'd just want to know if its usage is still subject to discussion or if it's definitive.
I'd totally get it if you want to stick with it, but I must say I won't do much frontend using it.

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

[netlify]

❌ Deploy Preview for histoirejs failed.

🔨 Explore the source changes: 4af1c55

🔍 Inspect the deploy log: https://app.netlify.com/sites/histoirejs/deploys/61fd64ee4520920007983391

[Akryum]

The package is @vueuse/core and is already installed

[hugoattal]

Aaaah, nice spot! I'll update this!

[hugoattal]

Fixed here: 4af1c55