cerrado @ f4ea96c52928eedd11b3f809cd9a481eda214482

docs: Update goals

Makes clear what is needed for 1.0, also pushs mail based PR for the
feature.
 1diff --git a/README.md b/README.md
 2index 20492e76f333232ec9196a843dab558284b6f8a1..0954b92a678b4348e4f1d3c1ba2feb099cde9b9d 100644
 3--- a/README.md
 4+++ b/README.md
 5@@ -1,6 +1,6 @@
 6 ### Cerrado
 7 
 8-Self host single user mail based forge.
 9+Self host single user forge.
10 
11 You can find a running instance here:
12 
13@@ -21,9 +21,9 @@
14 The deployment process should be easy to wrap the head around and
15 straightforward to set up. To achieve that it uses a simple file format[^1] to
16 configure everything. Also to reduce the moving parts the whole application,
17-including its statics file, is bundled into a single binary.
18+including its statics files, is bundled into a single binary.
19 
20-To run the project you just need to do a make run.
21+To run the project you just need to `make run`.
22 
23 ### Installations
24 
25@@ -61,18 +61,21 @@ mail@gabrielgio.me
26 
27 ### Missing for 1.0
28 
29-- Git clone support
30-- Some rework on summary page.
31+- Git clone support: that is very important feature for a git forge.
32+- Dark mode support: in the same way as mobile support this should be supported
33+  from the get go. I have slacked on this one but it should be done before 1.0.
34+- Some rework on summary page: it is feels a bit crude as it is.
35 
36 ### Ideas
37-- Mail patch / mailing list
38 - Code snippet support
39 - Setup manual (man feature perhaps?)
40-- Add authentication
41-    - Enforce public property
42 - Add metrics
43 - Add reference based cache system. Cerrado should be able to cache the whole
44-  page based on its reference hash.
45+  page based on its reference hash
46+
47+### Future
48+- Mail patch / mailing list. This is very complex endeavour. In a distant
49+  future I might do it, but for now I will focus on the features listed above.
50 
51 [^1]: https://git.sr.ht/~emersion/scfg
52 [^2]: https://apkdoc.gabrielgio.me/