fix(docs): reorder toc

Reviewed-on: SelfPrivacy/selfprivacy.org#115
Reviewed-by: Inex Code <inex.code@selfprivacy.org>
Co-authored-by: dettlaff <dettlaff@riseup.net>
Co-committed-by: dettlaff <dettlaff@riseup.net>

content/en/blog/releases/0.11.0.md

@@ -0,0 +1,80 @@
+---
+title: "Version 0.11.0 Release"
+linkTitle: "0.11.0"
+date: 2024-03-14
+description: >
+  New About screen, reworked jobs management
+---
+
+## Changelog
+
+### Features
+
+- Enabled the following languages:
+  - Arabic
+  - Estonian
+  - Kazakh
+  - Chinese (Simplified)
+
+- **Server management**: Add ssh settings ([#477](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/477))
+- **UI**: Server settings is now a separate screen ([#477](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/477))
+- **UI**: The new About page now contains links to our support channels ([#464](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/464), resolves [#339](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/339) and [#170](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/170))
+- **Jobs**: Now you can track the result of jobs, and the progress of the server rebuilds and upgrades ([#440](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/440), resolves [#254](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/254))
+- **UI**: On iOS, use the Curpentino bottom navbar ([#483](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/483))
+- **UI**: Use Curpentino widgets where possible on iOS ([#483](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/483))
+- **Jobs**: Block starting client-side jobs when the server is rebuilding or moving a service ([#477](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/477))
+- **UI**: On the bottom bar, show all labels, not only the selected one ([#458](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/458), resolves [#454](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/454))
+- **UI**: Move provider card titles to the top row ([#449](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/449), resolves [#448](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/448))
+- Unified management of API connection to the server: the app should be now more reactive to changes ([#440](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/440))
+- **UI**: Onboarding page now looks better on big screens ([#444](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/444))
+
+### Bug Fixes
+
+- **UI**: Card titles no longer overflow on small screens ([#483](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/483), resolves [#476](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/476))
+- **DNS**: Detect the situation when we have faulty link-local IPv6 records ([#473](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/473))
+- **DNS**: Do not include faulty link-local DNS records in the list of found records ([#475](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/475))
+- **UI**: Fix the empty server confirmation screen during recovery ([#474](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/474))
+- **UI**: Fix the misleading value of "Do not verify TLS" ([#468](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/468))
+- **Jobs**: When you return the server settings value back, the job to change the setting is deleted ([#440](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/440), resolves [#166](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/166))
+- **Jobs**: When removing all completed jobs, optimistically delete them in UI first ([#440](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/440), resolves [#277](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/277))
+
+
+### Other
+
+- Binds migration screen is now in Developer settings, as it is no longer needed on API 3.0, but might still be helpful for stuck servers.
+- Remove the server deletion function ([#484](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/484))
+
+### Translation contributions
+
+- Kazakh
+  - TabithiS (133)
+
+- Chinese (Simplified)
+  - Nil (545)
+
+- Polish
+  - TabithiS (52)
+
+- Russian
+  - Inex Code (43)
+
+- Hebrew
+  - Yaron (17)
+
+- Estonian
+  - Dmitri B. (536)
+
+- Thai
+  - Inex Code (2)
+
+- German
+  - Inex Code (14)
+    - Based on anonymous suggestions
+
+- Ukrainian
+  - Nagibator Nagibuchiy (18)
+  - TabithiS (26)
+  - Meko (93)
+
+- Arabic
+  - Deem Alosili (656)

content/en/docs/About us/_index.md

@@ -1,7 +1,7 @@
 ---
 title: "About us"
 linkTitle: "About us"
-weight: 4
+weight: 6
 date: 2022-01-09
 description: >
   Who we are, our motivation and policies.

content/en/docs/About us/policy.md

@@ -1,7 +1,7 @@
 ---
 title: "Privacy Policy"
 date: 2023-05-15
-weight: 4
+weight: 5
 description: >
   Our policies and politics.
 ---

content/en/docs/About us/roadmap.md

@@ -1,7 +1,7 @@
 ---
 title: "Roadmap"
 linkTitle: "Roadmap"
-weight: 5
+weight: 3
 date: 2023-10-05
 description: >
   What we are going to do next

content/en/docs/About us/team.md

@@ -1,7 +1,7 @@
 ---
 title: "Team"
 date: 2017-01-05T
-weight: 3
+weight: 1
 description: >
   Our team, contributors and like-minded people.
 ---

content/en/docs/Backups/_index.md

@@ -2,7 +2,7 @@
 title: "Backups"
 linkTitle: "Backups"
 date: 2023-07-31T
-weight: 2
+weight: 4
 description: >
     Backing up your services so that they are not lost
 ---

content/en/docs/Contributing/_index.md

@@ -2,7 +2,7 @@
 title: "How to contribute"
 linkTitle: "Contributing"
 date: 2023-03-13T
-weight: 2
+weight: 7
 description: >
     You can help with translations and programming 
 ---

content/en/docs/FAQ/_index.md

@@ -2,7 +2,7 @@
 title: "Frequency Asked Questions"
 linkTitle: "FAQ"
 date: 2023-03-13T
-weight: 2
+weight: 8
 description: >
     Frequently asked questions about our project.
 ---

content/en/docs/Getting started/_index.md

@@ -1,7 +1,7 @@
 ---
 title: "Getting Started"
 linkTitle: "Getting Started"
-weight: 1
+weight: 2
 description: >
   How do you deploy and set up SelfPrivacy server?
 aliases:

content/en/docs/How To Guides/_index.md

@@ -1,6 +1,6 @@
 ---
 title: "How-to guides"
-weight: 2
+weight: 5
 date: 2023-03-14
 description: >
     These are the guides on how to perform common tasks.

content/en/docs/Overview/_index.md

@@ -1,39 +0,0 @@
----
-title: "Overview"
-linkTitle: "Overview"
-weight: 2
-draft: true
-description: >
-  Here's where your user finds out if your project is for them.
----
-
-{{% pageinfo %}}
-This is a placeholder page that shows you how to use this template site.
-{{% /pageinfo %}}
-
-
-The Overview is where your users find out about your project. Depending on the size of your docset, you can have a separate overview page (like this one) or put your overview contents in the Documentation landing page (like in the Docsy User Guide). 
-
-Try answering these questions for your user in this page:
-
-## What is it?
-
-Introduce your project, including what it does or lets you do, why you would use it, and its primary goal (and how it achieves it). This should be similar to your README description, though you can go into a little more detail here if you want.
-
-## Why do I want it?
-
-Help your user know if your project will help them. Useful information can include: 
-
-* **What is it good for?**: What types of problems does your project solve? What are the benefits of using it?
-
-* **What is it not good for?**: For example, point out situations that might intuitively seem suited for your project, but aren't for some reason. Also mention known limitations, scaling issues, or anything else that might let your users know if the project is not for them.
-
-* **What is it *not yet* good for?**: Highlight any useful features that are coming soon.
-
-## Where should I go next?
-
-Give your users next steps from the Overview. For example:
-
-* [Getting Started](/docs/getting-started/): Get started with $project
-* [Examples](/docs/examples/): Check out some example code!
-

content/en/docs/Services/bitwarden.md

@@ -1,6 +1,7 @@
 ---
 title: "Bitwarden"
 date: 2023-01-11T18:09:37+03:00
+weight: 7
 description: >
   Your password manager 
 ---

content/en/docs/Services/delta-chat.md

@@ -1,6 +1,7 @@
 ---
 title: "Delta.Chat"
 date: 2023-01-11T17:15:31+03:00
+weight: 4
 description: >
   E-mail-based messenger with end-to-end encryption
 ---

content/en/docs/Services/email/_index.md

@@ -1,6 +1,7 @@
 ---
 title: "E-mail"
 date: 2023-01-11T17:10:29+03:00
+weight: 1
 description: >
   Self-hosted e-mail service
 ---

content/en/docs/Services/gitea.md

@@ -1,6 +1,7 @@
 ---
 title: "Gitea"
 date: 2023-01-11T18:09:12+03:00
+weight: 3
 description: >
   Gitea is a self-hosted Git service
 ---

content/en/docs/Services/jitsi.md

@@ -1,6 +1,7 @@
 ---
 title: "Jitsi"
 date: 2023-01-11T17:15:31+03:00
+weight: 6
 description: >
   Video conference
 ---

content/en/docs/Services/nextcloud.md

@@ -1,6 +1,7 @@
 ---
 title: "Nextcloud"
 date: 2023-01-11T17:08:23+03:00
+weight: 2
 description: >
   Swiss knife in the business of working together
 ---

content/en/docs/Services/pleroma.md

@@ -1,6 +1,7 @@
 ---
 title: "Pleroma"
 date: 2023-01-11T17:17:40+03:00
+weight: 5
 description: >
   Decentralized Social Network Server
 ---

content/en/docs/Theory/_index.md

@@ -1,7 +1,7 @@
 ---
 title: "Theory"
 linkTitle: "Theory"
-weight: 5
+weight: 1
 date: 2023-05-09
 description: >
     Discussion of various aspects of the project 

content/en/docs/Theory/architecture.md

@@ -9,13 +9,11 @@ description: >
 
 Yes, you could use kubernetes. But why when immutability is ensured by NixOS?
 
-## Mobile app ##
-[Flutter](https://flutter.dev/)/[Dart](https://dart.dev/) was chosen because of the speed and smoothness of the UI and cross-platform.
+**User app:** [Flutter](https://flutter.dev/)/[Dart](https://dart.dev/) was chosen because of the speed and smoothness of the UI and cross-platform.
 
-## Backend
-[NixOS](https://nixos.org/) + [Python](https://www.python.org/). NixOS was chosen because of its reproducibility, python because of its versatility and popularity.
+**Server side (backend):** [NixOS](https://nixos.org/) + [Python](https://www.python.org/). NixOS was chosen because of its reproducibility, python because of its versatility and popularity.
 
-## Service providers
+# Service providers
 **We do not get paid by any service providers!** We are not affiliated with them in any way. We chose them purely for professional reasons. But we do not exclude partnership in the future.
 
 ### Hosting
@@ -23,8 +21,6 @@ SelfPrivacy supports two hosting providers: [Hetzer](https://www.hetzner.com/) a
 
 Both were chosen because of low price and acceptable level of service, quality REST API.
 
-Hetzer has not been seen to have any privacy or data collection problems.
-
 Candidates:
 - Own personal iron server. **Our main priority right now**;
 - A service provider that will provide an API to deploy an iron server. Outside [FVEY](https://en.wikipedia.org/wiki/Five_Eyes);
@@ -34,7 +30,15 @@ Candidates:
 There's also free [Oracle Cloud](https://docs.oracle.com/en-us/iaas/Content/FreeTier/freetier_topic-Always_Free_Resources.htm), but where you don't pay, you're usually a commodity.
 
 ### DNS
-[Cloudlare](https://cloudflare.com) reliable, free. Probably collects data, otherwise it's hard to explain why proxy other people's traffic for free. In our case we use it only as a DNS-server and do not proxy anything. In the future we will replace it with self-hosted DNS, as soon as we solve the reliability problem.
+There's a choice between [Cloudflare](https://cloudflare.com), [deSEC](https://desec.io/), or [DigitalOcean DNS](https://www.digitalocean.com/).
+
+[deSEC](https://desec.io/) is a more private option and is recommended by default.
+
+[Cloudflare](https://cloudflare.com) likely collects data in proxy traffic mode, otherwise it's hard to explain why they would offer such services for free. **In our case, we don't proxy anything and use it only as a DNS server.**
 
 ### Backup repository
-[Backblaze](https://www.backblaze.com/) is free or times cheaper than AWS. Not seen in data collection. [Publishes](https://www.backblaze.com/blog/open-source-data-storage-server/) in open source the hardware it runs on. And also [shares](https://www.backblaze.com/b2/hard-drive-test-data.html) very useful statistics about disk failures, on the basis of which you can choose the most reliable and tested one. In the future, perhaps, we will replace it with a self-hosted or p2p solution. Now it is not the main priority, because the data is encrypted, and the service provider sees only the ip of your server, but not the home one.
+We use [Backblaze](https://www.backblaze.com/).
+
+The first 20GB are free and significantly cheaper than AWS. [Backblaze](https://www.backblaze.com/) publishes its hardware developments in open source. They also [shares](https://www.backblaze.com/b2/hard-drive-test-data.html) very useful statistics on disk failures, based on which one can choose the most reliable and tested option.
+
+In the future, we might replace them with a self-hosted solution or a peer-to-peer one. **Currently, this is not a top priority since the data is encrypted, and the service provider only sees the IP address of your server, not the device with the application.**