Merge branch 'upd_description' of git.selfprivacy.org:SelfPrivacy/selfprivacy.org.app into upd_description

2024-11-16 21:53:17 +00:00 · 2023-10-12 01:30:45 +04:00 · 2023-10-12 01:30:45 +04:00 · ec06d831e0
parent d4bbdade0f b3643b3c45
commit ec06d831e0
553 changed files with 76069 additions and 11046 deletions
--- a/.drone.yml
+++ b/.drone.yml
@ -0,0 +1,205 @@
+kind: pipeline
+type: exec
+name: Nightly
+
+steps:
+  - name: Prepare
+    commands:
+      - ln -s /var/lib/drone-runner-exec/.local $HOME/.local
+      - ln -s /var/lib/drone-runner-exec/fdroid $HOME/fdroid
+
+  - name: Run Tests
+    commands:
+      - ./ci.py --ci-run-tests
+      - sonar-scanner -Dsonar.projectKey=SelfPrivacy-Flutter-App -Dsonar.sources=. -Dsonar.host.url=http://analyzer.lan:9000 -Dsonar.login="$SONARQUBE_TOKEN"
+    environment:
+      SONARQUBE_TOKEN:
+        from_secret: SONARQUBE_TOKEN
+
+  - name: Build Nightly Linux Release Artifact (Binary)
+    commands:
+      - ./ci.py --ci-build-linux
+
+  - name: Build Nightly Release Artifact (.APK)
+    commands:
+      - ./ci.py --ci-build-apk
+
+  - name: Sign and Commit Nightly Android Release Artifact (.APK) for F-Droid Repository
+    commands:
+      - rm -rf $HOME/fdroid/build/org.selfprivacy.app.nightly && mkdir $HOME/fdroid/build/org.selfprivacy.app.nightly
+      - git archive --format=tar HEAD | tar x -C $HOME/fdroid/build/org.selfprivacy.app.nightly
+      - ./ci.py --sign-apk-fdroid-nightly
+    environment:
+      STANDALONE_KEYSTORE_PASS:
+        from_secret: STANDALONE_KEYSTORE_PASS
+      FDROID_KEYSTORE_PASS:
+        from_secret: FDROID_KEYSTORE_PASS
+      GOOGLE_KEYSTORE_PASS:
+        from_secret: GOOGLE_KEYSTORE_PASS
+
+  - name: Deploy F-Droid Repository
+    commands:
+      - ./ci.py --deploy-fdroid-repo
+    environment:
+      SSH_PRIVATE_KEY:
+        from_secret: SSH_PRIVATE_KEY
+
+trigger:
+  event:
+    - push
+  branch:
+    - master
+
+node:
+  server: builder
+
+---
+
+kind: pipeline
+type: exec
+name: Release
+
+steps:
+  - name: Prepare
+    commands:
+      - ln -s /var/lib/drone-runner-exec/.local $HOME/.local
+      - ln -s /var/lib/drone-runner-exec/fdroid $HOME/fdroid
+      - if podman volume exists release; then podman volume rm -f release; podman volume create release; else podman volume create release; fi
+      - git config user.email "builder@selfprivacy.org"
+      - git config user.name "Builder"
+
+  - name: Create an Empty Gitea Release
+    commands:
+      - ./ci.py --gitea-create-release
+    environment:
+      GITEA_RELEASE_TOKEN:
+        from_secret: GITEA_RELEASE_TOKEN
+
+  - name: Build Intermediate Linux Release Artifact (Binary)
+    commands:
+      - ./ci.py --build-linux
+    environment:
+      STANDALONE_KEYSTORE_PASS:
+        from_secret: STANDALONE_KEYSTORE_PASS
+      FDROID_KEYSTORE_PASS:
+        from_secret: FDROID_KEYSTORE_PASS
+      GOOGLE_KEYSTORE_PASS:
+        from_secret: GOOGLE_KEYSTORE_PASS
+
+  - name: Build Intermediate Android Release Artifact (.APK)
+    commands:
+      - ./ci.py --build-apk
+    environment:
+      STANDALONE_KEYSTORE_PASS:
+        from_secret: STANDALONE_KEYSTORE_PASS
+      FDROID_KEYSTORE_PASS:
+        from_secret: FDROID_KEYSTORE_PASS
+      GOOGLE_KEYSTORE_PASS:
+        from_secret: GOOGLE_KEYSTORE_PASS
+
+  - name: Build Intermediate Android Release Artifact (Bundle)
+    commands:
+      - ./ci.py --build-bundle
+    environment:
+      STANDALONE_KEYSTORE_PASS:
+        from_secret: STANDALONE_KEYSTORE_PASS
+      FDROID_KEYSTORE_PASS:
+        from_secret: FDROID_KEYSTORE_PASS
+      GOOGLE_KEYSTORE_PASS:
+        from_secret: GOOGLE_KEYSTORE_PASS
+
+  - name: Sign Android Release Artifact (.APK) for Standalone Use
+    commands:
+      - ./ci.py --sign-apk-standalone
+    environment:
+      STANDALONE_KEYSTORE_PASS:
+        from_secret: STANDALONE_KEYSTORE_PASS
+      FDROID_KEYSTORE_PASS:
+        from_secret: FDROID_KEYSTORE_PASS
+      GOOGLE_KEYSTORE_PASS:
+        from_secret: GOOGLE_KEYSTORE_PASS
+
+  - name: Sign and Commit Android Release Artifact (.APK) for F-Droid Repository
+    commands:
+      - rm -rf $HOME/fdroid/build/org.selfprivacy.app && mkdir $HOME/fdroid/build/org.selfprivacy.app
+      - git archive --format=tar HEAD | tar x -C $HOME/fdroid/build/org.selfprivacy.app
+      - ./ci.py --sign-apk-fdroid
+    environment:
+      STANDALONE_KEYSTORE_PASS:
+        from_secret: STANDALONE_KEYSTORE_PASS
+      FDROID_KEYSTORE_PASS:
+        from_secret: FDROID_KEYSTORE_PASS
+      GOOGLE_KEYSTORE_PASS:
+        from_secret: GOOGLE_KEYSTORE_PASS
+
+  - name: Sign Android Release Artifact (Bundle) for Google Play
+    commands:
+      - ./ci.py --sign-bundle
+    environment:
+      STANDALONE_KEYSTORE_PASS:
+        from_secret: STANDALONE_KEYSTORE_PASS
+      FDROID_KEYSTORE_PASS:
+        from_secret: FDROID_KEYSTORE_PASS
+      GOOGLE_KEYSTORE_PASS:
+        from_secret: GOOGLE_KEYSTORE_PASS
+
+  - name: Package Linux AppImage Artifact
+    commands:
+      - ./ci.py --package-linux-appimage
+
+  - name: Package Linux Flatpak Artifact
+    commands:
+      - ./ci.py --package-linux-flatpak
+
+  - name: Package Linux Archive Artifact
+    commands:
+      - ./ci.py --package-linux-archive
+
+  - name: Push Artifacts to the Release Volume
+    commands:
+      - git add -v *.AppImage *.AppImage.zsync *.flatpak *.apk *.apk.idsig *.aab *.tar.zstd
+      - git commit -m Release
+      - git archive --format=tar HEAD | podman volume import release -
+
+trigger:
+  event:
+    - tag
+
+node:
+  server: builder
+
+---
+
+kind: pipeline
+type: exec
+name: Deploy
+
+steps:
+  - name: Prepare
+    commands:
+      - ln -s /var/lib/drone-runner-exec/.local $HOME/.local
+      - podman unshare podman volume mount release
+
+  - name: Deploy Artifacts to Gitea
+    commands:
+      - ./ci.py --deploy-gitea-release
+    environment:
+      GITEA_RELEASE_TOKEN:
+        from_secret: GITEA_RELEASE_TOKEN
+
+  - name: Deploy F-Droid Repository
+    commands:
+      - ./ci.py --deploy-fdroid-repo
+    environment:
+      SSH_PRIVATE_KEY:
+        from_secret: SSH_PRIVATE_KEY
+
+trigger:
+  event:
+    - tag
+
+node:
+  server: builder
+
+depends_on:
+  - Release
--- a/.editorconfig
+++ b/.editorconfig
@ -14,3 +14,6 @@ max_line_length = 150

 [*.md]
 trim_trailing_whitespace = false
+
+[*.json]
+indent_size = 4
--- a/.gitea/ISSUE_TEMPLATE/bug.yaml
+++ b/.gitea/ISSUE_TEMPLATE/bug.yaml
@ -0,0 +1,68 @@
+name: Bug report
+about: File a bug report
+labels:
+  - Bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report! Please provide a short but a descriptive title for your issue.
+  - type: textarea
+    id: expected-behaviour
+    attributes:
+      label: Expected Behavior
+      description: What did you expect to happen?
+    validations:
+      required: true
+  - type: textarea
+    id: actual-behaviour
+    attributes:
+      label: Actual Behavior
+      description: What actually happened?
+    validations:
+      required: true
+  - type: textarea
+    id: steps-to-reproduce
+    attributes:
+      label: Steps to Reproduce
+      description: What steps can we follow to reproduce this issue?
+      placeholder: |
+        1. First step
+        2. Second step
+        3. and so on...
+    validations:
+      required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: Context and notes
+      description: Additional information about environment or what were you trying to do. If you have an idea how to fix this issue, please describe it here too.
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output, if you have any. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+  - type: input
+    id: app-version
+    attributes:
+      label: App Version
+      description: What version of SelfPrivacy app are you running? You can find it in the "About" section of the app.
+    validations:
+      required: true
+  - type: input
+    id: api-version
+    attributes:
+      label: Server API Version
+      description: What version of SelfPrivacy API are you running? You can find it in the "About" section of the app. Leave it empty if your app is not connected to the server yet.
+  - type: dropdown
+    id: os
+    attributes:
+      label: Operating System
+      description: What operating system are you using?
+      options:
+        - Android
+        - iOS
+        - Linux
+        - macOS
+        - Windows
--- a/.gitea/ISSUE_TEMPLATE/feature.yaml
+++ b/.gitea/ISSUE_TEMPLATE/feature.yaml
@ -0,0 +1,23 @@
+name: Feature request
+about: Suggest an idea for this project
+label:
+  - Feature request
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this feature request! Please provide a short but a descriptive title for your issue.
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Describe the feature you'd like to see.
+      placeholder: |
+        As a user, I want to be able to...
+    validations:
+      required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: Context and notes
+      description: Additional information about environment and what were you trying to do. If you have an idea how to implement this feature, please describe it here too.
--- a/.gitea/ISSUE_TEMPLATE/translation.yaml
+++ b/.gitea/ISSUE_TEMPLATE/translation.yaml
@ -0,0 +1,29 @@
+name: Translation issue
+about: File a translation (localization) issue
+labels:
+  - Translations
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Translations can be modified and discussed on [Weblate](https://weblate.selfprivacy.org/projects/selfprivacy/). You can fix the mistranslation issue yourself there. Using the search, you can also find the string ID of the mistranslated string. If your issue is more complex, please file it here
+
+        If you are a member of SelfPrivacy core team, you **must** fix the issue yourself on Weblate.
+  - type: input
+    id: language
+    attributes:
+      label: Language
+      description: What language is affected?
+      placeholder: |
+        English
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Describe the issue in detail. If you have an idea how to fix this issue, please describe it here too. Include the string ID of the mistranslated string, if possible.
+      placeholder: |
+        The string `string.id` is translated as "foo", but it should be "bar".
+    validations:
+      required: true
--- a/.github/workflows/windows.yml
+++ b/.github/workflows/windows.yml
@ -0,0 +1,29 @@
+name: Windows Builder
+
+on: tag
+
+jobs:
+  build-windows:
+    runs-on: windows-latest
+    steps:
+      - uses: actions/checkout@v3
+
+      # Install Python dependencies
+      - run: pip install requests pyyaml
+
+      # Install Flutter
+      - uses: subosito/flutter-action@v2
+        with:
+          flutter-version: '3.3.10'
+          channel: 'stable'
+
+      # Build Windows artifact
+      - run: flutter build windows
+
+      # Archive the build
+      - run: python ci.py --package-windows-archive
+
+      # Upload the build
+      - run: python ci.py --deploy-windows-archive
+        env:
+          GITEA_RELEASE_TOKEN: ${{ secrets.GITEA_RELEASE_TOKEN }}
--- a/58
+++ b/58
@ -0,0 +1,58 @@
+FROM ubuntu:22.04
+
+ARG PACKAGES="build-essential openjdk-11-jdk-headless clang cmake curl git jq libblkid1 \
+              libblkid-dev libc6 libc6-dev libc-bin libcrypt1 libdbus-1-3 libexpat1 libffi7 \
+              libgcc-s1 libgcrypt20 libgcrypt20-dev libglib2.0-0 libglib2.0-dev libglu1-mesa \
+              libgpg-error0 libgtk-3-0 libgtk-3-dev liblz4-1 liblz4-dev liblzma5 liblzma-dev \
+              libmount1 libpcre3 libselinux1 libsepol2 libstdc++-10-dev libstdc++6 libuuid1 \
+              ninja-build pkg-config rsync unzip xz-utils zlib1g unzip libsecret-1-dev libsecret-tools \
+              libsecret-1-0 libjsoncpp-dev fuse flatpak-builder binutils coreutils desktop-file-utils \
+              fakeroot fuse libgdk-pixbuf2.0-dev patchelf python3-pip python3-setuptools squashfs-tools \
+              strace util-linux zsync"
+ARG ANDROID_SDK_TOOLS_VERSION="8512546"
+ARG ANDROID_SDK_TOOLS_URL="https://dl.google.com/android/repository/commandlinetools-linux-${ANDROID_SDK_TOOLS_VERSION}_latest.zip"
+ARG FLUTTER_VERSION="3.3.1"
+ARG FLUTTER_URL="https://storage.googleapis.com/flutter_infra_release/releases/stable/linux/flutter_linux_${FLUTTER_VERSION}-stable.tar.xz"
+ARG FREEDESKTOP_SDK_VERSION="22.08"
+
+# Update packages
+RUN apt-get update && apt-get upgrade -y && apt-get install -y $PACKAGES
+
+WORKDIR /opt
+
+# Install Android SDK
+ADD $ANDROID_SDK_TOOLS_URL .
+RUN mkdir -p android-sdk/cmdline-tools && unzip commandlinetools-linux-${ANDROID_SDK_TOOLS_VERSION}_latest.zip \
+    && rm commandlinetools-linux-${ANDROID_SDK_TOOLS_VERSION}_latest.zip && mv cmdline-tools android-sdk/cmdline-tools/latest
+
+# Install Flutter
+ENV FLUTTER_HOME "/opt/flutter"
+ADD $FLUTTER_URL .
+RUN tar -vxf flutter_linux_${FLUTTER_VERSION}-stable.tar.xz && \
+    rm flutter_linux_${FLUTTER_VERSION}-stable.tar.xz
+# Flutter doesn't work without write permissions, so fuck it, fuck
+RUN chmod -R 777 $FLUTTER_HOME
+RUN git config --system --add safe.directory $FLUTTER_HOME
+
+ENV ANDROID_HOME "/opt/android-sdk"
+ENV ANDROID_SDK_ROOT "${ANDROID_HOME}"
+ENV PATH "$PATH:$ANDROID_SDK_ROOT/cmdline-tools/latest/bin:$ANDROID_SDK_ROOT/build-tools/30.0.3:/opt/flutter/bin"
+
+# Install needed Android SDK packages
+RUN yes | sdkmanager 'build-tools;30.0.3' 'platforms;android-29' 'platforms;android-30' 'platforms;android-31'
+
+WORKDIR /tmp
+
+# Prepare dependencies for offline build
+ENV PUB_CACHE "/tmp/flutter_pub_cache"
+ENV GRADLE_USER_HOME "/tmp/gradle"
+RUN git clone --depth=1 --single-branch https://git.selfprivacy.org/kherel/selfprivacy.org.app.git deps
+WORKDIR /tmp/deps
+RUN flutter build linux
+RUN flutter build apk --flavor production
+WORKDIR /tmp
+RUN rm -rf deps
+RUN find $GRADLE_USER_HOME/daemon -exec chmod 777 {} \;
+
+# Install AppImage Builder and F-Droid Server
+RUN pip3 install appimage-builder fdroidserver
--- a/README.md
+++ b/README.md
@ -1,17 +1,57 @@
 # SelfPrivacy App

- [Official site](https://selfprivacy.org)
- [SelfPrivacy App (F-Droid)](https://f-droid.org/en/packages/pro.kherel.selfprivacy/)
+SelfPrivacy — is a platform on your cloud hosting, that allows to deploy your own private services and control them using mobile application.

-## Getting Started
+To use this application, you'll be required to create accounts of different service providers. Please reffer to this manual: https://selfprivacy.org/docs/getting-started/

-This project is a starting point for a Flutter application.
+Application will do the following things for you:

-A few resources to get you started if this is your first Flutter project:
+1. Create your personal server
+2. Setup NixOS
+3. Bring all services to the ready-to-use state. Services include:

- [Lab: Write your first Flutter app](https://flutter.dev/docs/get-started/codelab)
- [Cookbook: Useful Flutter samples](https://flutter.dev/docs/cookbook)
+* E-mail, ready to use with DeltaChat
+* NextCloud - your personal cloud storage
+* Bitwarden — secure and private password manager
+* Pleroma — your private fediverse space for blogging
+* Jitsi — awesome Zoom alternative
+* Gitea — your own Git server
+* OpenConnect — Personal VPN server

-For help getting started with Flutter, view our
-[online documentation](https://flutter.dev/docs), which offers tutorials,
-samples, guidance on mobile development, and a full API reference.
+**Project is currently in open beta state**. Feel free to try it. It would be much appreciated if you would provide us with some feedback. 
+
+## Building
+
+Supported platforms are Android, Linux, and Windows. We are looking forward to support iOS and macOS builds.
+
+For Linux builds, make sure you have these packages installed:
+|Arch-based|Debian-based|
+|----------|------------|
+|pacman -S ninja xdg-user-dirs gnome-keyring unzip xz-utils zip|apt install ninja-build xdg-user-dirs gnome-keyring unzip xz-utils zip|
+
+Install [Flutter](https://docs.flutter.dev/get-started/install/linux) and [Android SDK tools](https://developer.android.com/studio/command-line/sdkmanager), then try your setup:
+
+```
+flutter pub get
+
+# Build .APK for Android
+flutter build --flavor production apk
+# Build AAB bundle for Google Play
+flutter build --flavor production aab
+# Build Linux binaries
+flutter build linux
+# Build Windows binaries
+flutter build windows
+
+# Package AppImage
+appimage-builder --recipe appimage.yml
+# Package Flatpak
+flatpak-builder --force-clean --repo=flatpak-repo flatpak-build flatpak.yml
+flatpak build-bundle flatpak-repo org.selfprivacy.app.flatpak org.selfprivacy.app
+```
+
+## Translations
+
+[![Translation status](http://weblate.selfprivacy.org/widgets/selfprivacy/-/selfprivacy-app/multi-auto.svg)](http://weblate.selfprivacy.org/engage/selfprivacy/)
+
+Translations are stored in `assets/translations/*.json` and can be edited on <https://weblate.selfprivacy.org/projects/selfprivacy/selfprivacy-app/>.
--- a/analysis_options.yaml
+++ b/analysis_options.yaml
@ -13,6 +13,7 @@ analyzer:
  exclude:
    - lib/generated_plugin_registrant.dart
    - lib/**.g.dart
+    - lib/**.graphql.dart

 linter:
  # The lint rules applied to this project can be customized in the
@ -28,17 +29,16 @@ linter:
  # producing the lint.
  rules:
    avoid_print: false  # Uncomment to disable the `avoid_print` rule
-    prefer_single_quotes: true  # Uncomment to enable the `prefer_single_quotes` rule
-    always_use_package_imports: true
-    invariant_booleans: true
-    no_adjacent_strings_in_list: true
-    unnecessary_statements: true
    always_declare_return_types: true
-    always_put_required_named_parameters_first: true
    always_put_control_body_on_new_line: true
+    always_put_required_named_parameters_first: true
+    always_use_package_imports: true
    avoid_escaping_inner_quotes: true
    avoid_setters_without_getters: true
+    collection_methods_unrelated_type: true
+    combinators_ordering: true
    eol_at_end_of_file: true
+    no_adjacent_strings_in_list: true
    prefer_constructors_over_static_methods: true
    prefer_expression_function_bodies: true
    prefer_final_in_for_each: true
@ -48,12 +48,18 @@ linter:
    prefer_if_elements_to_conditional_expressions: true
    prefer_mixin: true
    prefer_null_aware_method_calls: true
+    prefer_single_quotes: true
    require_trailing_commas: true
    sized_box_shrink_expand: true
    sort_constructors_first: true
+    unawaited_futures: true
    unnecessary_await_in_return: true
+    unnecessary_null_aware_operator_on_extension_on_nullable: true
    unnecessary_null_checks: true
    unnecessary_parenthesis: true
+    unnecessary_statements: true
+    unnecessary_to_list_in_spreads: true
+    unreachable_from_main: true
    use_enums: true
    use_if_null_to_convert_nulls_to_bools: true
    use_is_even_rather_than_modulo: true
@ -61,6 +67,7 @@ linter:
    use_named_constants: true
    use_setters_to_change_properties: true
    use_string_buffers: true
+    use_string_in_part_of_directives: true
    use_super_parameters: true
    use_to_and_as_if_applicable: true

--- a/android/app/build.gradle
+++ b/android/app/build.gradle
@ -26,7 +26,9 @@ apply plugin: 'kotlin-android'
 apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"

 android {
-    compileSdkVersion flutter.compileSdkVersion
+  namespace 'org.selfprivacy.app'
+
+  compileSdkVersion flutter.compileSdkVersion
    ndkVersion flutter.ndkVersion

    sourceSets {
@ -48,18 +50,41 @@ android {

    defaultConfig {
        // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
-        applicationId "pro.kherel.selfprivacy"
+        applicationId "org.selfprivacy.app"
        minSdkVersion 21
-        targetSdkVersion 31
+        targetSdkVersion 33
+        compileSdkVersion 33
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
    }

-    buildTypes {
-        release {
-            // TODO: Add your own signing config for the release build.
-            // Signing with the debug keys for now, so `flutter run --release` works.
-            signingConfig signingConfigs.debug
+    flavorDimensions "default"
+    productFlavors {
+        fdroid {
+            applicationId "pro.kherel.selfprivacy"
+        }
+        production {
+            applicationIdSuffix ""
+        }
+        nightly {
+            applicationIdSuffix ".nightly"
+            versionCode project.getVersionCode()
+            versionName "nightly-" + project.getVersionCode()
+        }
+    }
+
+    flavorDimensions "default"
+    productFlavors {
+        fdroid {
+            applicationId "pro.kherel.selfprivacy"
+        }
+        production {
+            applicationIdSuffix ""
+        }
+        nightly {
+            applicationIdSuffix ".nightly"
+            versionCode project.getVersionCode()
+            versionName "nightly-" + project.getVersionCode()
        }
    }
 }
--- a/android/app/src/debug/AndroidManifest.xml
+++ b/android/app/src/debug/AndroidManifest.xml
@ -1,5 +1,5 @@
 <manifest xmlns:android="http://schemas.android.com/apk/res/android"
-    package="pro.kherel.selfprivacy">
+    package="org.selfprivacy.app">
    <!-- Flutter needs it to communicate with the running application
         to allow setting breakpoints, to provide hot reload, etc.
    -->
--- a/android/app/src/main/AndroidManifest.xml
+++ b/android/app/src/main/AndroidManifest.xml
@ -1,5 +1,5 @@
 <manifest xmlns:android="http://schemas.android.com/apk/res/android"
-    package="pro.kherel.selfprivacy">
+    package="org.selfprivacy.app">
    <uses-permission android:name="android.permission.INTERNET" />
    <!-- io.flutter.app.FlutterApplication is an android.app.Application that
         calls FlutterMain.startInitialization(this); in its onCreate method.
--- a/android/app/src/main/kotlin/pro/kherel/selfprivacy/MainActivity.kt
+++ b/android/app/src/main/kotlin/pro/kherel/selfprivacy/MainActivity.kt
@ -1,4 +1,4 @@
-package pro.kherel.selfprivacy
+package org.selfprivacy.app

 import io.flutter.embedding.android.FlutterActivity

--- a/android/app/src/nightly/AndroidManifest.xml
+++ b/android/app/src/nightly/AndroidManifest.xml
@ -0,0 +1,8 @@
+<manifest xmlns:android="http://schemas.android.com/apk/res/android"
+    xmlns:tools="http://schemas.android.com/tools"
+    package="org.selfprivacy.app">
+    <application
+        tools:replace="android:label"
+        android:label="SelfPrivacy (Nightly)">
+    </application>
+</manifest>
--- a/android/app/src/nightly/res/mipmap-hdpi/ic_launcher.png
+++ b/android/app/src/nightly/res/mipmap-hdpi/ic_launcher.png
--- a/android/app/src/nightly/res/mipmap-hdpi/launcher_icon.png
+++ b/android/app/src/nightly/res/mipmap-hdpi/launcher_icon.png
--- a/android/app/src/nightly/res/mipmap-mdpi/ic_launcher.png
+++ b/android/app/src/nightly/res/mipmap-mdpi/ic_launcher.png
--- a/android/app/src/nightly/res/mipmap-mdpi/launcher_icon.png
+++ b/android/app/src/nightly/res/mipmap-mdpi/launcher_icon.png
--- a/android/app/src/nightly/res/mipmap-xhdpi/ic_launcher.png
+++ b/android/app/src/nightly/res/mipmap-xhdpi/ic_launcher.png
--- a/android/app/src/nightly/res/mipmap-xhdpi/launcher_icon.png
+++ b/android/app/src/nightly/res/mipmap-xhdpi/launcher_icon.png
--- a/android/app/src/nightly/res/mipmap-xxhdpi/ic_launcher.png
+++ b/android/app/src/nightly/res/mipmap-xxhdpi/ic_launcher.png
--- a/android/app/src/nightly/res/mipmap-xxhdpi/launcher_icon.png
+++ b/android/app/src/nightly/res/mipmap-xxhdpi/launcher_icon.png
--- a/android/app/src/nightly/res/mipmap-xxxhdpi/ic_launcher.png
+++ b/android/app/src/nightly/res/mipmap-xxxhdpi/ic_launcher.png
--- a/android/app/src/nightly/res/mipmap-xxxhdpi/launcher_icon.png
+++ b/android/app/src/nightly/res/mipmap-xxxhdpi/launcher_icon.png
--- a/android/app/src/profile/AndroidManifest.xml
+++ b/android/app/src/profile/AndroidManifest.xml
@ -1,5 +1,5 @@
 <manifest xmlns:android="http://schemas.android.com/apk/res/android"
-    package="pro.kherel.selfprivacy">
+    package="org.selfprivacy.app">
    <!-- Flutter needs it to communicate with the running application
         to allow setting breakpoints, to provide hot reload, etc.
    -->
--- a/android/build.gradle
+++ b/android/build.gradle
@ -1,5 +1,18 @@
 buildscript {
    ext.kotlin_version = '1.6.10'
+    ext.getVersionCode = { ->
+      try {
+        def stdout = new ByteArrayOutputStream()
+        exec {
+          commandLine 'git', 'rev-list', '--first-parent', '--count', 'HEAD'
+          standardOutput = stdout
+        }
+        return Integer.parseInt(stdout.toString().trim())
+      }
+      catch (ignored) {
+        return -1
+      }
+    }
    repositories {
        google()
        jcenter()
@ -26,6 +39,6 @@ subprojects {
    project.evaluationDependsOn(':app')
 }

-task clean(type: Delete) {
+tasks.register("clean", Delete) {
    delete rootProject.buildDir
 }
--- a/android/gradle.properties
+++ b/android/gradle.properties
@ -1,4 +1,4 @@
 org.gradle.jvmargs=-Xmx1536M
 android.useAndroidX=true
 android.enableJetifier=true
-android.enableR8=true
+android.bundle.enableUncompressedNativeLibs=false
--- a/android/gradle/wrapper/gradle-wrapper.properties
+++ b/android/gradle/wrapper/gradle-wrapper.properties
@ -3,4 +3,4 @@ distributionBase=GRADLE_USER_HOME
 distributionPath=wrapper/dists
 zipStoreBase=GRADLE_USER_HOME
 zipStorePath=wrapper/dists
-distributionUrl=https\://services.gradle.org/distributions/gradle-7.4-all.zip
+distributionUrl=https\://services.gradle.org/distributions/gradle-7.6-all.zip
--- a/appimage.yml
+++ b/appimage.yml
@ -0,0 +1,53 @@
+# appimage-builder recipe see https://appimage-builder.readthedocs.io for details
+version: 1
+script:
+  - rm -rf AppDir || true
+  - cp -r build/linux/x64/release/bundle AppDir
+  - install -Dm644 assets/images/icon/logo.svg AppDir/usr/share/icons/hicolor/scalable/apps/org.selfprivacy.app.svg
+AppDir:
+  path: AppDir
+  app_info:
+    id: org.selfprivacy.app
+    name: SelfPrivacy
+    icon: org.selfprivacy.app
+    version: 0.9.1
+    exec: selfprivacy
+    exec_args: $@
+  apt:
+    arch:
+      - amd64
+    allow_unauthenticated: true
+    sources:
+      - sourceline: deb http://archive.ubuntu.com/ubuntu/ jammy main restricted
+      - sourceline: deb http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted
+      - sourceline: deb http://archive.ubuntu.com/ubuntu/ jammy universe
+      - sourceline: deb http://archive.ubuntu.com/ubuntu/ jammy-updates universe
+      - sourceline: deb http://archive.ubuntu.com/ubuntu/ jammy multiverse
+      - sourceline: deb http://archive.ubuntu.com/ubuntu/ jammy-updates multiverse
+      - sourceline: deb http://archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse
+      - sourceline: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted
+      - sourceline: deb http://security.ubuntu.com/ubuntu/ jammy-security universe
+      - sourceline: deb http://security.ubuntu.com/ubuntu/ jammy-security multiverse
+    include:
+      - libjsoncpp-dev
+      - libsecret-1-0
+      - xdg-desktop-portal
+  test:
+    fedora-30:
+      image: appimagecrafters/tests-env:fedora-30
+      command: ./AppRun
+    debian-stable:
+      image: appimagecrafters/tests-env:debian-stable
+      command: ./AppRun
+    archlinux-latest:
+      image: appimagecrafters/tests-env:archlinux-latest
+      command: ./AppRun
+    centos-7:
+      image: appimagecrafters/tests-env:centos-7
+      command: ./AppRun
+    ubuntu-xenial:
+      image: appimagecrafters/tests-env:ubuntu-xenial
+      command: ./AppRun
+AppImage:
+  arch: x86_64
+  update-information: guess
--- a/assets/images/icon/logo.svg
+++ b/assets/images/icon/logo.svg
@ -0,0 +1,9 @@
+<svg width="186" height="186" viewBox="0 0 186 186" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M181.85 0H179.81C180.898 0 181.782 0.882482 181.782 1.96861V180.23C181.782 181.316 180.898 182.199 179.81 182.199H14.7574C13.6692 182.199 12.7852 181.316 12.7852 180.23V181.859C12.7852 184.167 14.6893 186 16.9336 186H181.85C184.162 186 185.998 184.167 185.998 181.859V4.14088C186.066 1.83285 184.162 0 181.85 0Z" fill="#EFCD29"/>
+<path d="M87.0484 106.577C87.1164 106.577 87.1164 106.645 87.1164 106.645L81.1999 131.287H105.478L99.5617 106.645C99.5617 106.577 99.5617 106.577 99.6297 106.577C105.138 104.133 109.015 98.6347 109.015 92.2537C109.015 80.9172 96.9774 72.4318 84.9402 78.8129C82.832 79.9669 80.9958 81.7318 79.9077 83.8362C74.7392 93.4756 79.2277 103.183 87.0484 106.577Z" fill="#FFDD00"/>
+<path d="M87.0484 106.577C87.1164 106.577 87.1164 106.645 87.1164 106.645L81.1999 131.287H105.478L99.5617 106.645C99.5617 106.577 99.5617 106.577 99.6297 106.577C105.138 104.133 109.015 98.6347 109.015 92.2537C109.015 80.9172 96.9774 72.4318 84.9402 78.8129C82.832 79.9669 80.9958 81.7318 79.9077 83.8362C74.7392 93.4756 79.2277 103.183 87.0484 106.577Z" fill="#FFDD00"/>
+<path d="M14.7574 182.199H179.81C180.898 182.199 181.782 181.316 181.782 180.23V1.96861C181.782 0.882482 180.898 0 179.81 0H17.0016H14.8254C13.7372 0 12.8532 0.882482 12.8532 1.96861V4.14088V46.3642H95.2092L125.336 82.4102L127.444 84.9898V148.257H12.7852V160.612V180.23C12.7852 181.316 13.6692 182.199 14.7574 182.199Z" fill="#FFDD00"/>
+<path d="M14.7574 182.199H179.81C180.898 182.199 181.782 181.316 181.782 180.23V1.96861C181.782 0.882482 180.898 0 179.81 0H17.0016H14.8254C13.7372 0 12.8532 0.882482 12.8532 1.96861V4.14088V46.3642H95.2092L125.336 82.4102L127.444 84.9898V148.257H12.7852V160.612V180.23C12.7852 181.316 13.6692 182.199 14.7574 182.199Z" fill="#FFDD00"/>
+<path d="M125.336 145.677V82.4102L95.2093 46.3643H12.7853H0V145.677H125.336ZM79.9078 83.9037C81.0639 81.7993 82.8321 80.0343 84.9403 78.8803C96.9095 72.4993 109.015 80.9847 109.015 92.3212C109.015 98.7022 105.138 104.201 99.6298 106.645C99.5618 106.645 99.5618 106.712 99.5618 106.712L105.478 131.354H81.2L87.1165 106.712C87.1165 106.645 87.1165 106.645 87.0485 106.645C79.2278 103.182 74.7393 93.4752 79.9078 83.9037Z" fill="#404548"/>
+<path d="M127.444 148.257V84.9902L125.336 82.4785V145.678H0L12.7853 160.68V148.257H127.444Z" fill="#333638"/>
+</svg>
--- a/assets/images/logos/cloudflare.svg
+++ b/assets/images/logos/cloudflare.svg
@ -0,0 +1 @@
+<svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 209.51 94.74"><defs><style>.cls-1{fill:#fff;}</style></defs><path class="cls-1" d="M143.05,93.42l1.07-3.71c1.27-4.41.8-8.48-1.34-11.48-2-2.76-5.26-4.38-9.25-4.57L58,72.7a1.47,1.47,0,0,1-1.35-2,2,2,0,0,1,1.75-1.34l76.26-1c9-.41,18.84-7.75,22.27-16.71l4.34-11.36a2.68,2.68,0,0,0,.18-1,3.31,3.31,0,0,0-.06-.54,49.67,49.67,0,0,0-95.49-5.14,22.35,22.35,0,0,0-35,23.42A31.73,31.73,0,0,0,.34,93.45a1.47,1.47,0,0,0,1.45,1.27l139.49,0h0A1.83,1.83,0,0,0,143.05,93.42Z"/><path class="cls-1" d="M168.22,41.15q-1,0-2.1.06a.88.88,0,0,0-.32.07,1.17,1.17,0,0,0-.76.8l-3,10.26c-1.28,4.41-.81,8.48,1.34,11.48a11.65,11.65,0,0,0,9.24,4.57l16.11,1a1.44,1.44,0,0,1,1.14.62,1.5,1.5,0,0,1,.17,1.37,2,2,0,0,1-1.75,1.34l-16.73,1c-9.09.42-18.88,7.75-22.31,16.7l-1.21,3.16a.9.9,0,0,0,.79,1.22h57.63A1.55,1.55,0,0,0,208,93.63a41.34,41.34,0,0,0-39.76-52.48Z"/></svg>
--- a/assets/images/logos/desec.svg
+++ b/assets/images/logos/desec.svg
@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+   xmlns:dc="http://purl.org/dc/elements/1.1/"
+   xmlns:cc="http://creativecommons.org/ns#"
+   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+   xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+   width="7.4053912mm"
+   height="7.5173831mm"
+   viewBox="0 0 7.4053913 7.5173831"
+   version="1.1"
+   id="svg1262"
+   sodipodi:docname="logo.notext.svg"
+   inkscape:version="0.92.4 (5da689c313, 2019-01-14)">
+  <defs
+     id="defs1256" />
+  <sodipodi:namedview
+     id="base"
+     pagecolor="#ffffff"
+     bordercolor="#666666"
+     borderopacity="1.0"
+     inkscape:pageopacity="0.0"
+     inkscape:pageshadow="2"
+     inkscape:zoom="5.6"
+     inkscape:cx="101.86078"
+     inkscape:cy="8.9271745"
+     inkscape:document-units="mm"
+     inkscape:current-layer="g3885"
+     showgrid="false"
+     fit-margin-top="0"
+     fit-margin-left="0"
+     fit-margin-right="0"
+     fit-margin-bottom="0"
+     inkscape:window-width="2560"
+     inkscape:window-height="1365"
+     inkscape:window-x="0"
+     inkscape:window-y="38"
+     inkscape:window-maximized="1" />
+  <metadata
+     id="metadata1259">
+    <rdf:RDF>
+      <cc:Work
+         rdf:about="">
+        <dc:format>image/svg+xml</dc:format>
+        <dc:type
+           rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+        <dc:title></dc:title>
+      </cc:Work>
+    </rdf:RDF>
+  </metadata>
+  <g
+     inkscape:label="Layer 1"
+     inkscape:groupmode="layer"
+     id="layer1"
+     transform="translate(-254.94057,-266.78298)">
+    <g
+       id="g3885"
+       transform="matrix(0.26519825,0,0,0.26519825,228.89366,215.69135)"
+       style="fill:#000000">
+      <g
+         style="fill:#000000;stroke:#ffffff;stroke-opacity:1"
+         id="layer1-9"
+         transform="matrix(0.22901929,0,0,0.22901929,26.296508,84.906304)"
+         inkscape:export-filename="/home/nils/git/desec-stack/webapp/src/assets/logo.png"
+         inkscape:export-xdpi="567.52002"
+         inkscape:export-ydpi="567.52002">
+        <g
+           style="fill:#000000;stroke:#ffffff;stroke-opacity:1"
+           transform="translate(-194.13584,150.8067)"
+           id="g3933">
+          <path
+             inkscape:connector-curvature="0"
+             d="m 509.13584,366.2239 c 8.87906,-33.13708 42.93987,-52.8021 76.07695,-43.92304 21.43594,5.74374 38.17931,22.48711 43.92305,43.92304 0,0 -6.09923,-6.07815 -10,-6.07815 -3.90077,0 -10,6.07815 -10,6.07815 0,0 -6.09923,-6.07815 -10,-6.07815 -3.90077,0 -10,6.07815 -10,6.07815 0,0 -6.09923,-6.07815 -10,-6.07815 -3.90077,0 -10,6.07815 -10,6.07815 0,0 -6.09923,-6.07815 -10,-6.07815 -3.90077,0 -10,6.07815 -10,6.07815 0,0 -6.09923,-6.07815 -10,-6.07815 -3.90077,0 -10,6.07815 -10,6.07815 0,0 -6.09923,-6.07815 -10,-6.07815 -3.90077,0 -10,6.07815 -10,6.07815 z"
+             id="path2985-6-3"
+             style="color:#000000;display:inline;overflow:visible;visibility:visible;fill:#000000;fill-opacity:1;stroke:#ffffff;stroke-width:0.99999994;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker:none;enable-background:accumulate" />
+          <path
+             inkscape:connector-curvature="0"
+             d="m 567.42674,364.89583 v 61.87321 c 0,9.34738 5.48085,16.17306 12.23879,16.17306 6.75795,0 12.23635,-6.83606 12.23635,-16.18344 0,0 -1.07806,-1.02674 -1.75904,-1.03964 -0.64261,-0.0122 -1.69589,0.91753 -1.69589,0.91753 0,6.70817 -3.93157,13.01592 -8.78142,13.01592 -4.84984,0 -8.78142,-6.30775 -8.78142,-13.01592 l -7.6e-4,-61.74072 z"
+             id="path3775-7-4-6"
+             style="color:#000000;display:inline;overflow:visible;visibility:visible;fill:#000000;fill-opacity:1;stroke:#ffffff;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:117.14173126;stroke-opacity:1;marker:none;enable-background:accumulate" />
+        </g>
+      </g>
+    </g>
+  </g>
+</svg>
--- a/assets/images/logos/digital_ocean.png
+++ b/assets/images/logos/digital_ocean.png
--- a/assets/images/logos/digital_ocean.svg
+++ b/assets/images/logos/digital_ocean.svg
@ -0,0 +1,6 @@
+<svg width="24" height="25" viewBox="0 0 24 25" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M12.0013 24.0128V19.3592C16.927 19.3592 20.7505 14.4743 18.8591 9.2901C18.1652 7.37152 16.6276 5.83395 14.709 5.14C9.52482 3.26224 4.63995 7.07217 4.63995 11.9979H0C0 4.14669 7.59264 -1.97641 15.8248 0.595295C19.417 1.72467 22.2881 4.58211 23.4038 8.17433C25.9755 16.4201 19.8661 24.0128 12.0013 24.0128Z" fill="white"/>
+<path d="M12.0149 19.3729H7.38855V14.7466H12.0149V19.3729Z" fill="white"/>
+<path d="M7.38861 22.9376H3.82361V19.3726H7.38861V22.9376Z" fill="white"/>
+<path d="M3.82354 19.373H0.843628V16.3931H3.82354V19.373Z" fill="white"/>
+</svg>
--- a/assets/images/logos/hetzner.svg
+++ b/assets/images/logos/hetzner.svg
@ -0,0 +1,10 @@
+<svg width="24" height="23" viewBox="0 0 24 23" fill="none" xmlns="http://www.w3.org/2000/svg">
+<g clip-path="url(#clip0_51804_9018)">
+<path d="M22.5704 0H19.3252C18.5948 0 18.2817 0.302609 18.2817 1.04348V9.25565H5.35304V1.04348C5.35304 0.313043 5.05044 0 4.30957 0H1.04348C0.302609 0 0 0.302609 0 1.04348V22.1739C0 22.9148 0.302609 23.2174 1.04348 23.2174H4.30957C5.04 23.2174 5.35304 22.9252 5.35304 22.1739V13.8261H18.2922V22.1739C18.2922 22.9043 18.5948 23.2174 19.3357 23.2174H22.5809C23.3113 23.2174 23.6243 22.9148 23.6243 22.1739V1.04348C23.6035 0.333913 23.3009 0 22.5704 0Z" fill="white"/>
+</g>
+<defs>
+<clipPath id="clip0_51804_9018">
+<rect width="24" height="22.9565" fill="white"/>
+</clipPath>
+</defs>
+</svg>
--- a/assets/markdown/about-be.md
+++ b/assets/markdown/about-be.md
@ -0,0 +1,12 @@
+### Пра нас
+
+Усё больш арганізацый жадаюць валодаць нашымі дадзенымі
+Праект дазваляе толькі Вам у поўнай меры распараджацца ўласнымі **дадзенымі** на сваім сэрвэры.
+
+### Наша місія
+
+Лічбавая незалежнасць і прыватнасць, даступныя кожнаму
+
+### Мэта
+
+Распрацаваць праграму, якая дазволіць кожнаму разгарнуць свае прыватныя паслугі для сябе і сваіх суседзяў.
--- a/assets/markdown/about-cs.md
+++ b/assets/markdown/about-cs.md
@ -0,0 +1,12 @@
+### O nás
+
+More and more corporations want to control our data.
+We want to have full control of our **data** on our own.
+
+### Naše poslání
+
+Digitální nezávislost a soukromí dostupné všem
+
+### Cíl
+
+Rozvíjet program, který umožní každému nasadit své soukromé služby pro sebe a své sousedy.
--- a/assets/markdown/about-de.md
+++ b/assets/markdown/about-de.md
@ -0,0 +1,12 @@
+### Über uns
+
+Immer mehr Unternehmen wollen unsere Daten kontrollieren.
+Wir wollen selbst die volle Kontrolle über unsere **data** haben.
+
+### Unsere Mission
+
+Digitale Unabhängigkeit und Privatsphäre für alle verfügbar
+
+### Ziel
+
+Das Programm entwickeln, das es jedem ermöglicht, seine privaten Dienste für sich und seine Nachbarn einzusetzen.
--- a/assets/markdown/about-es.md
+++ b/assets/markdown/about-es.md
@ -0,0 +1,12 @@
+### About us
+
+More and more corporations want to control our data.
+We want to have full control of our **data** on our own.
+
+### Our mission
+
+Digital independence and privacy, available to everyone
+
+### Target
+
+Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours.
--- a/assets/markdown/about-fr.md
+++ b/assets/markdown/about-fr.md
@ -0,0 +1,12 @@
+### About us
+
+More and more corporations want to control our data.
+We want to have full control of our **data** on our own.
+
+### Our mission
+
+Digital independence and privacy, available to everyone
+
+### Target
+
+Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours.
--- a/assets/markdown/about-it.md
+++ b/assets/markdown/about-it.md
@ -0,0 +1,12 @@
+### About us
+
+More and more corporations want to control our data.
+We want to have full control of our **data** on our own.
+
+### Our mission
+
+Digital independence and privacy, available to everyone
+
+### Target
+
+Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours.
--- a/assets/markdown/about-ja.md
+++ b/assets/markdown/about-ja.md
@ -0,0 +1,12 @@
+### About us
+
+More and more corporations want to control our data.
+We want to have full control of our **data** on our own.
+
+### Our mission
+
+Digital independence and privacy, available to everyone
+
+### Target
+
+Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours.
--- a/assets/markdown/about-ka.md
+++ b/assets/markdown/about-ka.md
@ -0,0 +1,12 @@
+### About us
+
+More and more corporations want to control our data.
+We want to have full control of our **data** on our own.
+
+### Our mission
+
+Digital independence and privacy, available to everyone
+
+### Target
+
+Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours.
--- a/assets/markdown/about-nl.md
+++ b/assets/markdown/about-nl.md
@ -0,0 +1,12 @@
+### About us
+
+More and more corporations want to control our data.
+We want to have full control of our **data** on our own.
+
+### Our mission
+
+Digital independence and privacy, available to everyone
+
+### Target
+
+Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours.
--- a/assets/markdown/about-pl.md
+++ b/assets/markdown/about-pl.md
@ -0,0 +1,12 @@
+### About us
+
+More and more corporations want to control our data.
+We want to have full control of our **data** on our own.
+
+### Misja projektu
+
+Niezależność i prywatność cyfrowa dostępna dla wszystkich
+
+### Cel
+
+Opracuj program, dzięki któremu każdy będzie mógł stworzyć prywatne usługi dla siebie i swoich bliskich.
--- a/assets/markdown/about-ru.md
+++ b/assets/markdown/about-ru.md
@ -5,7 +5,7 @@

 ### Миссия проекта

-Цифровая независимость и приватность доступная каждому.
+Цифровая независимость и приватность, доступная каждому

 ### Цель

--- a/assets/markdown/about-sk.md
+++ b/assets/markdown/about-sk.md
@ -0,0 +1,12 @@
+### O nás
+
+More and more corporations want to control our data.
+We want to have full control of our **data** on our own.
+
+### Naše poslanie
+
+Digitálna nezávislosť a súkromie dostupné pre každého
+
+### Cieľ
+
+Vytvorte program, ktorý umožní každému vytvoriť súkromné služby pre seba a svojich blízkych.
--- a/assets/markdown/about-th.md
+++ b/assets/markdown/about-th.md
@ -0,0 +1,12 @@
+### About us
+
+More and more corporations want to control our data.
+We want to have full control of our **data** on our own.
+
+### Our mission
+
+Digital independence and privacy, available to everyone
+
+### Target
+
+Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours.
--- a/assets/markdown/about-uk.md
+++ b/assets/markdown/about-uk.md
@ -0,0 +1,12 @@
+### Про нас
+
+Все більше корпорацій хочуть контролювати свої дані. 
+Ми хочемо мати повний контроль над нашими.
+
+### Наша місія
+
+Цифрова незалежність і конфіденційність доступні кожному
+
+### Ціль
+
+Розробити програму, яка дозволить кожному розгорнути свої приватні послуги для себе та їх сусідів.
--- a/assets/markdown/how_backblaze-be.md
+++ b/assets/markdown/how_backblaze-be.md
@ -0,0 +1,8 @@
+### Як атрымаць Backblaze API Token
+1. Перайдзіце па спасылцы https://secure.backblaze.com/user_signin.htm і аўтарызуйцеся
+2. У левай частцы інтэрфейсу абярыце **App Keys** y **B2 Cloud Storage** падкатэгорыі.
+3. Націсніце на сінюю кнопку **Generate New Master Application Key**.
+4. Пацвердзіце стварэнне ва ўсплываючым акне.
+5. Схавайце _keyID_ і _applicationKey_ у бяспечным месце. Напрыклад, у мэнеджэры пароляў.
+
+![Атрыманіе токена Backblaze](resource:assets/images/gifs/Backblaze.gif)
--- a/assets/markdown/how_backblaze-cs.md
+++ b/assets/markdown/how_backblaze-cs.md
@ -0,0 +1,8 @@
+### Jak získat Backblaze API Token
+1. Navštivte následující odkaz a autorizujte se: https://secure.backblaze.com/user_signin.htm
+2. V levé části rozhraní vyberte položku **App Keys** v podkategorii **B2 Cloud Storage**.
+3. Klikněte na modré tlačítko **Generate New Master Application Key** (Vygenerovat nový hlavní aplikační klíč**).
+4. V zobrazeném vyskakovacím okně potvrďte vygenerování.
+5. Save _keyID_ and _applicationKey_ in the safe place.. Například ve správci hesel.
+
+![Nastavení tokenu Backblaze](resource:assets/images/gifs/Backblaze.gif)
--- a/assets/markdown/how_backblaze-de.md
+++ b/assets/markdown/how_backblaze-de.md
@ -0,0 +1,8 @@
+### So erhalten Sie das Backblaze-API-Token
+1. Besuchen Sie den folgenden Link und melden Sie sich an: https://secure.backblaze.com/user_signin.htm
+2. Wählen Sie auf der linken Seite der Benutzeroberfläche **App Keys** in der Unterkategorie **B2 Cloud Storage** aus.
+3. Klicken Sie auf die blaue Schaltfläche **Generate New Master Application Key**.
+4. Bestätigen Sie im erscheinenden Popup-Fenster die Generierung.
+5. Speichern Sie _keyID_ und _applicationKey_ an einem sicheren Ort. Zum Beispiel im Passwort-Manager.
+
+![Backblaze token Einrichtung](resource:assets/images/gifs/Backblaze.gif)
--- a/assets/markdown/how_backblaze-es.md
+++ b/assets/markdown/how_backblaze-es.md
@ -0,0 +1,8 @@
+### How to get Backblaze API Token
+1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
+2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
+3. Click on the blue **Generate New Master Application Key** button.
+4. In the appeared pop-up window confirm the generation.
+5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
+
+![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif)
--- a/assets/markdown/how_backblaze-fr.md
+++ b/assets/markdown/how_backblaze-fr.md
@ -0,0 +1,8 @@
+### How to get Backblaze API Token
+1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
+2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
+3. Click on the blue **Generate New Master Application Key** button.
+4. In the appeared pop-up window confirm the generation.
+5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
+
+![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif)
--- a/assets/markdown/how_backblaze-it.md
+++ b/assets/markdown/how_backblaze-it.md
@ -0,0 +1,8 @@
+### How to get Backblaze API Token
+1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
+2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
+3. Click on the blue **Generate New Master Application Key** button.
+4. In the appeared pop-up window confirm the generation.
+5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
+
+![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif)
--- a/assets/markdown/how_backblaze-ja.md
+++ b/assets/markdown/how_backblaze-ja.md
@ -0,0 +1,8 @@
+### How to get Backblaze API Token
+1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
+2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
+3. Click on the blue **Generate New Master Application Key** button.
+4. In the appeared pop-up window confirm the generation.
+5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
+
+![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif)
--- a/assets/markdown/how_backblaze-ka.md
+++ b/assets/markdown/how_backblaze-ka.md
@ -0,0 +1,8 @@
+### How to get Backblaze API Token
+1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
+2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
+3. Click on the blue **Generate New Master Application Key** button.
+4. In the appeared pop-up window confirm the generation.
+5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
+
+![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif)
--- a/assets/markdown/how_backblaze-nl.md
+++ b/assets/markdown/how_backblaze-nl.md
@ -0,0 +1,8 @@
+### How to get Backblaze API Token
+1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
+2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
+3. Click on the blue **Generate New Master Application Key** button.
+4. In the appeared pop-up window confirm the generation.
+5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
+
+![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif)
--- a/assets/markdown/how_backblaze-pl.md
+++ b/assets/markdown/how_backblaze-pl.md
@ -0,0 +1,8 @@
+### Jak otrzymać Backblaze API Token
+1. Odwiedź poniższy link i autoryzuj: https://secure.backblaze.com/user_signin.htm
+2. Po lewej stronie wybierz **App Keys** w podkategorіі **B2 Cloud Storage**.
+3. Naciśnij **Generate New Master Application Key**.
+4. W wyświetlonym oknie podręcznym potwierdź generację.
+5. Zapisz _keyID_ i _applicationKey_ w bezpiecznym miejscu. Na przykład w menedżerze haseł.
+
+![Otrzymanie tokena Backblaze](resource:assets/images/gifs/Backblaze.gif)
--- a/assets/markdown/how_backblaze-ru.md
+++ b/assets/markdown/how_backblaze-ru.md
@ -5,4 +5,4 @@
 4. Во всплывающем окне подтверждаем генерацию.
 5. Сохраняем _keyID_ и _applicationKey_ в надёжном месте. Например в менеджере паролей.

-![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif)
+![Получение токена Backblaze](resource:assets/images/gifs/Backblaze.gif)
--- a/assets/markdown/how_backblaze-sk.md
+++ b/assets/markdown/how_backblaze-sk.md
@ -0,0 +1,8 @@
+### Ako získať token API spoločnosti Backblaze
+1. Navštívte nasledujúci odkaz a autorizujte sa: https://secure.backblaze.com/user_signin.htm
+2. Na ľavej strane rozhrania vyberte položku **App Keys** v podkategórii **B2 Cloud Storage** podkategória.
+3. Kliknite na modré tlačidlo **Generate New Master Application Key**.
+4. V zobrazenom pop-up okne potvrďte generovanie.
+5. Uložte _keyID_ and _applicationKey_ in bezpečné miesto. Napríklad v správcovi hesiel.
+
+![Prijatie tokenu Backblaze](resource:assets/images/gifs/Backblaze.gif)
--- a/assets/markdown/how_backblaze-th.md
+++ b/assets/markdown/how_backblaze-th.md
@ -0,0 +1,8 @@
+### How to get Backblaze API Token
+1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
+2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
+3. Click on the blue **Generate New Master Application Key** button.
+4. In the appeared pop-up window confirm the generation.
+5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
+
+![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif)
--- a/assets/markdown/how_backblaze-uk.md
+++ b/assets/markdown/how_backblaze-uk.md
@ -0,0 +1,8 @@
+## Як отримати Backblaze API токен
+1. Перейдіть за посиланням і авторизуйте: https://secure.backblaze.com/user_signin.htm
+2. У лівій частині інтерфейсу виберіть **App Keys** у підкатегорії **B2 Cloud Storage**.
+3. Натисніть кнопку синій **Створити новий майстер-ключ програми**.
+4. У з'явилось спливаюче вікно підтверджують покоління.
+5. Save _KeyID_ and _applicationKey_ in the safe place. Наприклад, в менеджері паролів.
+
+![Backblaze токен налаштування](resource:assets/images/gifs/Backblaze.gif)
--- a/assets/markdown/how_cloudflare-be.md
+++ b/assets/markdown/how_cloudflare-be.md
@ -0,0 +1,17 @@
+### Як атрымаць токен Cloudflare API
+1. Перайдзіце па наступнай спасылцы: https://dash.cloudflare.com/
+2. У правым куце націсніце на значок профілю (чалавек у крузе). Для мабільнай версіі сайта ў левым верхнім куце націсніце кнопку **Menu** (тры гарызантальныя палоскі), у выпадальным меню націсніце **My Profile**.
+3. Ёсць чатыры катэгорыі канфігурацыі на выбар: *Communication*, *Authentication*, **API Tokens**, *Session*. Выберыце **API Tokens**.
+4. Націсніце на кнопку **Create Token**.
+5. Спусціцеся ўніз і паглядзіце поле **Create Custom Token** і націсніце кнопку **Get Started** справа.
+6. У полі **Token Name** дайце назву токену.
+7. Далей у нас налады. У крайнім левым полі абярыце **Zone**. У самым доўгім полі па цэнтры абярыце **DNS**. У крайнім правым полі абярыце **Edit**. 
+8. Далей прама пад гэтым радком націсніце «Дадаць яшчэ». З'явіцца аналагічнае поле.
+9. У самым левым полі новага радка выберыце аналагічна папярэдняму радку — **Zone**. У цэнтры — крыху іншае. Тут абярыце тое ж, што і злева — **Zone**. У крайнім правым полі абярыце **Read**.
+10. Далей паглядзіце на **Resources Zone**. Пад гэтым надпісам радок з двума палямі. Злева павінна быць **Include**, а справа павінна быць **Specific Zone**. Пасля таго як вы выберыце канкрэтную зону, справа з'явіцца іншае поле. Выберыце ў ім свой дамен.
+11. Прагартайце ўніз і націсніце сінюю кнопку **Continue to Summary**.
+12. Правер, ці ўсё ў цябе правільна. Аналагічны радок павінен прысутнічаць: *Domain — DNS:Edit, Zone:Read*.
+13. Націсніце на **Create Token**.
+14. Створаны токен капіюем і захоўваем у надзейным месцы (пажадана ў мэнэджару пароляў).
+
+![Настройка токену Cloudfire](resource:assets/images/gifs/CloudFlare.gif)
--- a/assets/markdown/how_cloudflare-cs.md
+++ b/assets/markdown/how_cloudflare-cs.md
@ -0,0 +1,17 @@
+### Jak získat token API Cloudflare
+1. Přejděte na následující odkaz: https://dash.cloudflare.com/.
+2. V pravém rohu klikněte na ikonu profilu (mužík v kruhu). V případě mobilní verze webu klikněte v levém horním rohu na **Menu** (tři vodorovné pruhy), v rozbalovací nabídce klikněte na **My profile**.
+Na výběr jsou čtyři kategorie nastavení: *Communication*, *Authentication*, **API Tokens**, *Session*. Vyberte možnost **API Tokens**.
+4. Klikněte na tlačítko **Create Token**.
+5. Přejděte dolů, zobrazte pole **Create Custom Token** a klikněte na tlačítko **Get Started** vpravo.
+6. V poli **Token Name** pojmenujte svůj token.
+7. Dále máme přístupová práva. V poli zcela vlevo vyberte možnost **Zone**. V nejdelším poli uprostřed vyberte položku **DNS**. V pravém krajním poli vyberte možnost **Edit**.
+8. Poté hned pod tímto řádkem klepněte na tlačítko Přidat další. Zobrazí se podobné pole.
+9. Na zcela levé straně nového řádku vyberte totéž co u předchozího řádku - **Zone**. Prostřední pole se mírně liší. Zde vyberte totéž co na levém okraji - **Zone**. Na pravém okraji zcela vpravo vyberte možnost **Read**.
+10. Dále se podívejte na položku **Zone Resources**. Pod ním se nachází řádek se dvěma poli. V levém z nich by mělo být uvedeno **Include** a v pravém **Specific Zone**. Jakmile vyberete možnost Specifická zóna, objeví se vpravo další pole. V něm vyberte svou doménu.
+11. Přejděte úplně dolů a klikněte na modré tlačítko **Continue to Summary**.
+12. Zkontrolujte, zda jste vše provedli správně. Měl by se objevit podobný řádek: *Domain - DNS:Edit, Zone:Read*.
+13. Klepněte na tlačítko **Create Token**.
+14. Zkopírujte vytvořený token a uložte jej na bezpečné místo (nejlépe do správce hesel).
+
+![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif)
--- a/assets/markdown/how_cloudflare-de.md
+++ b/assets/markdown/how_cloudflare-de.md
@ -0,0 +1,17 @@
+### Wie man Cloudflare API Token bekommt
+1. Besuchen Sie den folgenden link: https://dash.cloudflare.com/
+2. Klicken Sie in der rechten Ecke auf das Profilsymbol (ein Mann in einem Kreis). Bei der mobilen Version der Website klicken Sie in der oberen linken Ecke auf die Schaltfläche **Menu** (drei horizontale Balken), im Dropdown-Menü klicken Sie auf **My Profile**
+3. Es gibt vier Konfigurationskategorien, aus denen Sie wählen können: *Communication*, *Authentication*, **API Tokens**, *Session*. Wählen Sie **API Tokens**.
+4. Klicken Sie auf die Schaltfläche **Create Token**.
+5. Gehen Sie nach unten und sehen Sie das Feld **Create Custom Token** und klicken Sie auf der rechten Seite auf die Schaltfläche **Get Started**.
+6. Geben Sie in das Feld **Token Name** einen Namen für Ihr Token ein.
+7. Als nächstes folgen die Berechtigungen. Wählen Sie im Feld ganz links **Zone**. Wählen Sie im längsten Feld in der Mitte **DNS**. Wählen Sie im Feld ganz rechts **Edit**. 
+8. Klicken Sie anschließend direkt unter dieser Zeile auf Add More. Ein ähnliches Feld wird angezeigt.
+9. Wählen Sie im ganz linken Feld der neuen Zeile, ähnlich wie in der letzten Zeile, **Zone**. In der Mitte - ein wenig anders. Wählen Sie hier dasselbe wie in der linken Zeile - **Zone**. Im Feld ganz rechts wählen Sie **Read**.
+10. Als nächstes sehen Sie sich **Zone Resources** an. Unter dieser Aufschrift befindet sich eine Zeile mit zwei Feldern. Auf der linken Seite muss **Include** und auf der rechten Seite **Specific Zone** stehen. Sobald Sie Spezifische Zone auswählen, erscheint rechts ein weiteres Feld. Wählen Sie dort Ihre Domain aus.
+11. Streichen Sie nach unten und drücken Sie die blaue Schaltfläche **Continue to Summary**.
+12. Überprüfen Sie, ob Sie alles richtig gemacht haben. Eine ähnliche Zeichenfolge muss vorhanden sein: *Domain — DNS:Edit, Zone:Read*.
+13. Klicken Sie auf **Create Token**.
+14. Kopieren Sie das erstellte Token und speichern Sie es an einem zuverlässigen Ort (vorzugsweise im Passwort-Manager).
+
+![Cloudflare token Einrichtung](resource:assets/images/gifs/CloudFlare.gif)
--- a/assets/markdown/how_cloudflare-es.md
+++ b/assets/markdown/how_cloudflare-es.md
@ -0,0 +1,17 @@
+### How to get Cloudflare API Token
+1. Visit the following link: https://dash.cloudflare.com/
+2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
+3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
+4. Click on **Create Token** button.
+5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
+6. In the **Token Name** field, give your token a name.
+7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. 
+8. Next, right under this line, click Add More. Similar field will appear.
+9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
+10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
+11. Flick to the bottom and press the blue **Continue to Summary** button.
+12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
+13. Click on **Create Token**.
+14. We copy the created token, and save it in a reliable place (preferably in the password manager).
+
+![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif)
--- a/assets/markdown/how_cloudflare-fr.md
+++ b/assets/markdown/how_cloudflare-fr.md
@ -0,0 +1,17 @@
+### How to get Cloudflare API Token
+1. Visit the following link: https://dash.cloudflare.com/
+2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
+3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
+4. Click on **Create Token** button.
+5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
+6. In the **Token Name** field, give your token a name.
+7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. 
+8. Next, right under this line, click Add More. Similar field will appear.
+9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
+10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
+11. Flick to the bottom and press the blue **Continue to Summary** button.
+12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
+13. Click on **Create Token**.
+14. We copy the created token, and save it in a reliable place (preferably in the password manager).
+
+![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif)
--- a/assets/markdown/how_cloudflare-it.md
+++ b/assets/markdown/how_cloudflare-it.md
@ -0,0 +1,17 @@
+### How to get Cloudflare API Token
+1. Visit the following link: https://dash.cloudflare.com/
+2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
+3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
+4. Click on **Create Token** button.
+5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
+6. In the **Token Name** field, give your token a name.
+7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. 
+8. Next, right under this line, click Add More. Similar field will appear.
+9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
+10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
+11. Flick to the bottom and press the blue **Continue to Summary** button.
+12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
+13. Click on **Create Token**.
+14. We copy the created token, and save it in a reliable place (preferably in the password manager).
+
+![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif)
--- a/assets/markdown/how_cloudflare-ja.md
+++ b/assets/markdown/how_cloudflare-ja.md
@ -0,0 +1,17 @@
+### How to get Cloudflare API Token
+1. Visit the following link: https://dash.cloudflare.com/
+2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
+3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
+4. Click on **Create Token** button.
+5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
+6. In the **Token Name** field, give your token a name.
+7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. 
+8. Next, right under this line, click Add More. Similar field will appear.
+9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
+10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
+11. Flick to the bottom and press the blue **Continue to Summary** button.
+12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
+13. Click on **Create Token**.
+14. We copy the created token, and save it in a reliable place (preferably in the password manager).
+
+![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif)
--- a/assets/markdown/how_cloudflare-ka.md
+++ b/assets/markdown/how_cloudflare-ka.md
@ -0,0 +1,17 @@
+### How to get Cloudflare API Token
+1. Visit the following link: https://dash.cloudflare.com/
+2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
+3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
+4. Click on **Create Token** button.
+5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
+6. In the **Token Name** field, give your token a name.
+7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. 
+8. Next, right under this line, click Add More. Similar field will appear.
+9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
+10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
+11. Flick to the bottom and press the blue **Continue to Summary** button.
+12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
+13. Click on **Create Token**.
+14. We copy the created token, and save it in a reliable place (preferably in the password manager).
+
+![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif)
--- a/assets/markdown/how_cloudflare-nl.md
+++ b/assets/markdown/how_cloudflare-nl.md
@ -0,0 +1,17 @@
+### How to get Cloudflare API Token
+1. Visit the following link: https://dash.cloudflare.com/
+2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
+3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
+4. Click on **Create Token** button.
+5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
+6. In the **Token Name** field, give your token a name.
+7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. 
+8. Next, right under this line, click Add More. Similar field will appear.
+9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
+10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
+11. Flick to the bottom and press the blue **Continue to Summary** button.
+12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
+13. Click on **Create Token**.
+14. We copy the created token, and save it in a reliable place (preferably in the password manager).
+
+![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif)
--- a/assets/markdown/how_cloudflare-pl.md
+++ b/assets/markdown/how_cloudflare-pl.md
@ -0,0 +1,17 @@
+### Jak uzyskać token API Cloudflare'a
+1. Przejdź pod następujący link: https://dash.cloudflare.com/.
+2. W prawym rogu kliknij ikonę profilu (człowiek w kółku). W przypadku wersji mobilnej strony, w lewym górnym rogu kliknij **Menu** (trzy poziome paski), w rozwijanym menu kliknij **My Profile**.
+Do wyboru są cztery kategorie ustawień: *Communication*, *Authentication*, **API Tokens**, *Session*. Należy wybrać **API Tokens**.
+4. Kliknij przycisk **Create token**.
+5. Zjedź na dół, zobacz pole **Create Custom Token** i kliknij przycisk **Get Started** po prawej stronie.
+6. W polu **Token Name** nadaj nazwę swojemu tokenowi.
+7. Następnie mamy prawa dostępu. W skrajnie lewym polu wybierz **Zone**. W najdłuższym polu, środkowym, wybierz **DNS**. W skrajnie prawym polu wybierz **Edit**.
+8. Następnie, tuż pod tym wierszem, kliknij Add more. Pojawi się podobne pole.
+9. W skrajnie lewej części nowej linii wybierz to samo, co w poprzedniej linii - **Zone**. Środkowe pole jest nieco inne. Tutaj wybierz to samo, co na lewym marginesie - **Zone**. W skrajnie prawym marginesie wybierz **Read**.
+10. Następnie spójrz na **Strefę zasobów**. Poniżej tego znajduje się linia z dwoma polami. W lewym powinno być **Include**, a w prawym **Specific Zone**. Gdy wybierzesz Specific Zone, po prawej stronie pojawi się kolejne pole. Wybierz w nim swoją domenę.
+11. Przejdź na sam dół i kliknij niebieski przycisk **Continue to Summary**.
+12. Sprawdź, czy wszystko zrobiłeś poprawnie. Powinna pojawić się podobna linia: *Domain - DNS:Edit, Zone:Read*.
+13. Kliknij na **Create Token**.
+14. Skopiuj utworzony token i zapisz go w bezpiecznym miejscu (najlepiej w menedżerze haseł).
+
+![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif)
--- a/assets/markdown/how_cloudflare-ru.md
+++ b/assets/markdown/how_cloudflare-ru.md
@ -1,18 +1,17 @@
-### Как получить Cloudflare API Token
-1. Переходим по [ссылке](https://dash.cloudflare.com/) и авторизуемся в ранее созданном аккаунте. https://dash.cloudflare.com/
-2. В правом верхнем углу кликаем на иконку профиля (для мобильной версии сайта: в верхнем левом углу нажимаем кнопку **Меню** с тремя горизонтальными полосками). В выпавшем меню кликаем на пункт **My Profile**.
-![My profile](resource:assets/images/pics/myprofile.png)
-3. Нам предлагается на выбор, четыре категории настройки: **Preferences**, **Authentication**, **API Tokens**, **Sessions**. Выбираем **API Tokens**.
-4. Самым первым пунктом видим кнопку **Create Token**. С полной уверенностью в себе и желанием обрести приватность, нажимаем на неё.
-5. Спускаемся в самый низ и видим поле **Create Custom Token** и кнопку **Get Started** с правой стороны. Нажимаем.
-6. В поле **Token Name** даём своему токену имя. Можете покреативить и отнестись к этому как к наименованию домашнего зверька :)
-7. Далее, у нас **Permissions**. В первом поле выбираем **Zone**. Во втором поле, по центру, выбираем **DNS**. В последнем поле выбираем **Edit**.
-8. Нажимаем на синюю надпись снизу **+ Add more** (сразу же под левым полем которое мы заполняли ранее). Вуаля, у нас появились новые поля. Заполняем по аналогии с предыдущим пунктом, в первом поле выбираем **Zone**, во-втором тоже **Zone**. А уже в третьем нажимаем на **Read**. Давайте сверим с тем, что у вас получилось:
-![Permissions](resource:assets/images/pics/permissions.png)
-8. Далее смотрим на **Zone Resources**. Под этой надписью есть строка с двумя полями. В первом должно быть **Include**, а во втором — **Specific Zone**. Как только Вы выберите **Specific Zone**, справа появится ещё одно поле. В нём выбираем наш домен.
-9. Листаем в самый низ и нажимаем на синюю кнопку **Continue to Summary**.
-10. Проверяем, всё ли мы правильно выбрали. Должна присутствовать подобная строка: ваш.домен — **DNS:Edit, Zone:Read**.
-11. Нажимаем **Create Token**.
-12. Копируем созданный токен, и сохраняем его в надёжном месте (желательно — в менеджере паролей).
+### Как получить токен API Cloudflare
+1. Перейдите по следующей ссылке: https://dash.cloudflare.com/.
+2. В правом углу нажмите на значок профиля (человечек в круге). Для мобильной версии сайта: в левом верхнем углу нажмите на кнопку **Menu** (три горизонтальные полоски), в выпадающем меню нажмите на **My Profile**.
+3. На выбор предлагаются четыре категории настроек: *Communication*, *Authentication*, **API Tokens**, *Session*. Выберите **API Tokens**.
+4. Нажмите на кнопку **Create token**.
+5. Спуститесь в самый низ, увидите поле **Create Custom Token** и нажмите кнопку **Get Started** справа.
+6. В поле **Token Name** дайте имя вашему токену.
+7. Далее у нас есть права доступа. В крайнем левом поле выберите **Zone**. В самом длинном поле, по центру, выберите **DNS**. В крайнем правом поле выберите **Edit**.
+8. Далее, прямо под этой строкой, нажмите **Добавить еще**. Появится аналогичное поле.
+9. В крайнем левом поле новой строки выберите, аналогично предыдущей строке - **Zone**. В центральном - немного иначе. Здесь выберите то же, что и в левом - **Zone**. В крайнем правом поле выберите **Read**.
+10. Далее посмотрите на **Resources Zone**. Под этой надписью находится строка с двумя полями. В левом должно быть **Include**, а в правом - **Specific Zone**. Как только вы выберете Specific Zone, справа появится еще одно поле. Выберите в нем свой домен.
+11. Перейдите в самый низ и нажмите синюю кнопку **Continue to Summary**.
+12. Проверьте, все ли вы сделали правильно. Должна присутствовать аналогичная строка: *Domain - DNS:Edit, Zone:Read*.
+13. Нажмите на **Create Token**.
+14. Копируем созданный токен и сохраняем его в надежном месте (желательно в менеджере паролей).

 ![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif)
--- a/assets/markdown/how_cloudflare-sk.md
+++ b/assets/markdown/how_cloudflare-sk.md
@ -0,0 +1,17 @@
+### Ako získať token API Cloudflare
+1. Navštívte nasledujúce prepojenie: https://dash.cloudflare.com/
+2. V pravom rohu kliknite na ikonu profilu (muž v kruhu). V prípade mobilnej verzie stránky kliknite v ľavom hornom rohu na tlačidlo **Menu** (tri vodorovné pruhy), v rozbaľovacej ponuke kliknite na **My profile**
+3. Na výber sú štyri kategórie konfigurácie: *Communication*, *Authentication*, **Toky API**, *Session*. Vyberte **API Tokens**.
+4. Kliknite na tlačidlo **Create Token**.
+5. Prejdite na spodnú časť a zobrazte pole **Create Custom Token** a stlačte tlačidlo **Get Started** na pravej strane.
+6. V poli **Token Name** zadajte svoj token.
+7. Ďalej tu máme položku Permissions. V ľavom krajnom poli vyberte položku **Zone**. V najdlhšom poli uprostred vyberte položku **DNS**. V krajnom pravom poli vyberte položku **Edit**. 
+8. Ďalej priamo pod týmto riadkom kliknite na položku **Pridať ďalšie**. Zobrazí sa podobné pole.
+9. V krajnom ľavom poli nového riadku vyberte podobne ako v predchádzajúcom riadku - **Zone**. V strede - trochu inak. Tu vyberte rovnako ako v ľavom poli - **Zone**. V krajnom pravom poli vyberte položku **Read**.
+10. Ďalej sa pozrite na položku **Zone Resources**. Pod týmto nápisom sa nachádza riadok s dvoma poľami. V ľavom musí byť uvedené **Include** a v pravom **Specific Zone**. Keď vyberiete položku **Špecifická zóna**, vpravo sa objaví ďalšie pole. V ňom vyberte svoju doménu.
+11. Prejdite na spodnú časť a stlačte modré tlačidlo **Continue to Summary**.
+12. Skontrolujte, či máte všetko správne. Musí sa vyskytovať podobný reťazec: *Domain — DNS:Edit, Zone:Read*.
+13. Kliknite na **Create Token**.
+14. Vytvorený token skopírujeme a uložíme ho na spoľahlivé miesto (najlepšie do správcu hesiel).
+
+![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif)
--- a/assets/markdown/how_cloudflare-th.md
+++ b/assets/markdown/how_cloudflare-th.md
@ -0,0 +1,17 @@
+### How to get Cloudflare API Token
+1. Visit the following link: https://dash.cloudflare.com/
+2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
+3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
+4. Click on **Create Token** button.
+5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
+6. In the **Token Name** field, give your token a name.
+7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. 
+8. Next, right under this line, click Add More. Similar field will appear.
+9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
+10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
+11. Flick to the bottom and press the blue **Continue to Summary** button.
+12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
+13. Click on **Create Token**.
+14. We copy the created token, and save it in a reliable place (preferably in the password manager).
+
+![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif)
--- a/assets/markdown/how_cloudflare-uk.md
+++ b/assets/markdown/how_cloudflare-uk.md
@ -0,0 +1,17 @@
+### Як отримати токен Cloudflare API
+1. Перейдіть за цим посиланням: https://dash.cloudflare.com/
+2. В правому куті натисніть на іконку профілю (людина в колі). Для мобільної версії сайту, у верхньому лівому кутку натисніть кнопку **Menu** (три горизонтальні смужки), у випадаючому меню натисніть **My profile**
+3. Є чотири категорії конфігурації на вибір: *Communication*, *Authentication*, **API Tokens**, *Session*. Виберіть **API Tokens**.
+4. Натисніть кнопку **Create Token**.
+5. Спустіться вниз і перегляньте поле **Create Custom Token** і натисніть кнопку **Get Started** праворуч.
+6. У полі **Назва токена** введіть назву токена.
+7. Далі у нас є Дозволи. У крайньому лівому полі виберіть **Zone**. У найдовшому полі по центру виберіть **DNS**. У крайньому правому полі виберіть **Edit**.
+8. Далі прямо під цим рядком натисніть «Add more». З'явиться аналогічне поле.
+9. У крайньому лівому полі нового рядка виберіть, як і в останньому рядку, — **Zone**. У центрі — трохи інше. Тут вибираємо те саме, що й зліва — **Zone**. У крайньому правому полі виберіть **Read**.
+10. Далі подивіться на **Zone Resources**. Під цим написом — рядок із двома полями. Ліворуч має бути **Include**, а праворуч має бути **Specific Zone**. Після вибору «Specific Zone» праворуч з’явиться ще одне поле. Виберіть у ньому свій домен.
+11. Прокрутіть униз і натисніть синю кнопку **Continue to Summary**.
+12. Перевірте, чи все ви зробили правильно. Подібний рядок має бути присутнім: *Domain — DNS:Edit, Zone:Read*.
+13. Натисніть **Create Token**.
+14. Копіюємо створений токен і зберігаємо в надійному місці (бажано в менеджері паролів).
+
+![Cloudflare налаштування токена](resource:assets/images/gifs/CloudFlare.gif)
--- a/assets/markdown/how_desec-en.md
+++ b/assets/markdown/how_desec-en.md
@ -0,0 +1,9 @@
+### How to get deSEC API Token
+1. Log in at: https://desec.io/login
+2. Go to **Domains** page at: https://desec.io/domains
+3. Go to **Token management** tab.
+4. Click on the round "plus" button in the upper right corner.
+5. **"Generate New Token"** dialogue must be displayed. Enter any **Token name** you wish. *Advanced settings* are not required, so do not touch anything there.
+6. Click on **Save**.
+7. Make sure you save the token's "**secret value**" as it will only be displayed once.
+8. Now you can safely **close** the dialogue.
--- a/assets/markdown/how_desec-ru.md
+++ b/assets/markdown/how_desec-ru.md
@ -0,0 +1,9 @@
+### Как получить deSEC API Токен
+1. Авторизуемся в deSEC: https://desec.io/login
+2. Переходим на страницу **Domains** по ссылке: https://desec.io/domains
+3. Переходим на вкладку **Token management**.
+4. Нажимаем на большую кнопку с плюсом в правом верхнем углу страницы.
+5. Должен был появиться **"Generate New Token"** диалог. Вводим любое имя токена в **Token name**. *Advanced settings* необязательны, так что ничего там не трогаем.
+6. Кликаем **Save**.
+7. Обязательно сохраняем "**secret value**" ключ токена, потому что он отображается исключительно один раз.
+8. Теперь спокойно закрываем диалог, нажав **close**.
--- a/assets/markdown/how_digital_ocean-be.md
+++ b/assets/markdown/how_digital_ocean-be.md
@ -0,0 +1,12 @@
+### Як атрымаць токен Digital Ocean API
+1. Перайдзіце па наступнай [link](https://cloud.digitalocean.com/) і падпішыцеся
+     у толькі што створаны ўліковы запіс.
+2. Увайдзіце ў раней створаны праект. Калі вы яго не стварылі,
+     тады, калі ласка, працягвайце.
+3. Перайдзіце па спасылцы "API" на панэлі злева.
+4. Націсніце на кнопку "Generation New Token".
+5. Увядзіце любую назву токена.
+6. Усталюйце час заканчэння тэрміну дзеяння на "No Expiry".
+7. Усталюйце сцяжок "Write (optional)".
+8. Цяпер націсніце на кнопку "Generate Token".
+9. Пасля гэтага будзе паказаны токен. Захоўвайце яго ў любым надзейным месцы, пажадана ў менеджэры пароляў.
--- a/assets/markdown/how_digital_ocean-cs.md
+++ b/assets/markdown/how_digital_ocean-cs.md
@ -0,0 +1,12 @@
+### Jak získat token API Digital Ocean
+1.  Navštivte následující [link](https://cloud.digitalocean.com/) a podepište se.
+    k nově vytvořenému účtu.
+2.  Vstupte do dříve vytvořeného projektu. Pokud jste žádný nevytvořili,
+    pak prosím pokračujte.
+3.  Přejděte na odkaz "API" na levé liště.
+4.  Klikněte na tlačítko "Generate New Token" (Vygenerovat nový token).
+5.  Zadejte libovolný název tokenu.
+6.  Nastavte dobu platnosti na "No expiry".
+7.  Zaškrtněte políčko "Write (optional)".
+8.  Nyní klikněte na tlačítko "Generate Token".
+9.  Poté se zobrazí token. Uložte jej na libovolné spolehlivé místo, nejlépe do správce hesel.
--- a/assets/markdown/how_digital_ocean-de.md
+++ b/assets/markdown/how_digital_ocean-de.md
@ -0,0 +1,12 @@
+### So erhalten Sie das Digital Ocean API-Token
+1. Besuchen Sie den folgenden [link](https://cloud.digitalocean.com/) und melden Sie sich
+     in das neu erstellte Konto an.
+2. Gehen Sie in ein zuvor erstelltes Projekt. Wenn Sie noch keine erstellt haben,
+     dann bitte fortfahren.
+3. Gehen Sie zum Link "API" in der linken Leiste.
+4. Klicken Sie auf "Generate New Token".
+5. Geben Sie einen beliebigen Namen für das Token ein.
+6. Setzen Sie die Ablaufzeit auf "No expiry".
+7. Aktivieren Sie das Kontrollkästchen "Write (optional)".
+8. Klicken Sie nun auf die Schaltfläche "Generate Token".
+9. Danach wird der Token angezeigt. Bewahren Sie es an einem zuverlässigen Ort auf, vorzugsweise in einem Passwort-Manager.
--- a/assets/markdown/how_digital_ocean-en.md
+++ b/assets/markdown/how_digital_ocean-en.md
@ -0,0 +1,12 @@
+### How to get Digital Ocean API Token
+1.  Visit the following [link](https://cloud.digitalocean.com/) and sign
+    into newly created account.
+2.  Enter into previously created project. If you haven't created one,
+    then please proceed.
+3.  Go to the "API" link on the left bar.
+4.  Click on the "Generate New Token".
+5.  Enter any name for the token.
+6.  Put expiration time to "No expiry".
+7.  Check the "Write (optional)" checkbox.
+8.  Now click on the "Generate Token" button. 
+9.  After that, the token will be shown. Store it in any reliable place, preferably a password manager.
--- a/assets/markdown/how_digital_ocean-es.md
+++ b/assets/markdown/how_digital_ocean-es.md
@ -0,0 +1,12 @@
+### How to get Digital Ocean API Token
+1.  Visit the following [link](https://cloud.digitalocean.com/) and sign
+    into newly created account.
+2.  Enter into previously created project. If you haven't created one,
+    then please proceed.
+3.  Go to the "API" link on the left bar.
+4.  Click on the "Generate New Token".
+5.  Enter any name for the token.
+6.  Put expiration time to "No expiry".
+7.  Check the "Write (optional)" checkbox.
+8.  Now click on the "Generate Token" button. 
+9.  After that, the token will be shown. Store it in any reliable place, preferably a password manager.
--- a/assets/markdown/how_digital_ocean-fr.md
+++ b/assets/markdown/how_digital_ocean-fr.md
@ -0,0 +1,12 @@
+### How to get Digital Ocean API Token
+1.  Visit the following [link](https://cloud.digitalocean.com/) and sign
+    into newly created account.
+2.  Enter into previously created project. If you haven't created one,
+    then please proceed.
+3.  Go to the "API" link on the left bar.
+4.  Click on the "Generate New Token".
+5.  Enter any name for the token.
+6.  Put expiration time to "No expiry".
+7.  Check the "Write (optional)" checkbox.
+8.  Now click on the "Generate Token" button. 
+9.  After that, the token will be shown. Store it in any reliable place, preferably a password manager.
--- a/assets/markdown/how_digital_ocean-it.md
+++ b/assets/markdown/how_digital_ocean-it.md
@ -0,0 +1,12 @@
+### How to get Digital Ocean API Token
+1.  Visit the following [link](https://cloud.digitalocean.com/) and sign
+    into newly created account.
+2.  Enter into previously created project. If you haven't created one,
+    then please proceed.
+3.  Go to the "API" link on the left bar.
+4.  Click on the "Generate New Token".
+5.  Enter any name for the token.
+6.  Put expiration time to "No expiry".
+7.  Check the "Write (optional)" checkbox.
+8.  Now click on the "Generate Token" button. 
+9.  After that, the token will be shown. Store it in any reliable place, preferably a password manager.
--- a/assets/markdown/how_digital_ocean-ja.md
+++ b/assets/markdown/how_digital_ocean-ja.md
@ -0,0 +1,12 @@
+### How to get Digital Ocean API Token
+1.  Visit the following [link](https://cloud.digitalocean.com/) and sign
+    into newly created account.
+2.  Enter into previously created project. If you haven't created one,
+    then please proceed.
+3.  Go to the "API" link on the left bar.
+4.  Click on the "Generate New Token".
+5.  Enter any name for the token.
+6.  Put expiration time to "No expiry".
+7.  Check the "Write (optional)" checkbox.
+8.  Now click on the "Generate Token" button. 
+9.  After that, the token will be shown. Store it in any reliable place, preferably a password manager.
--- a/assets/markdown/how_digital_ocean-ka.md
+++ b/assets/markdown/how_digital_ocean-ka.md
@ -0,0 +1,12 @@
+### How to get Digital Ocean API Token
+1.  Visit the following [link](https://cloud.digitalocean.com/) and sign
+    into newly created account.
+2.  Enter into previously created project. If you haven't created one,
+    then please proceed.
+3.  Go to the "API" link on the left bar.
+4.  Click on the "Generate New Token".
+5.  Enter any name for the token.
+6.  Put expiration time to "No expiry".
+7.  Check the "Write (optional)" checkbox.
+8.  Now click on the "Generate Token" button. 
+9.  After that, the token will be shown. Store it in any reliable place, preferably a password manager.
--- a/assets/markdown/how_digital_ocean-nl.md
+++ b/assets/markdown/how_digital_ocean-nl.md
@ -0,0 +1,12 @@
+### How to get Digital Ocean API Token
+1.  Visit the following [link](https://cloud.digitalocean.com/) and sign
+    into newly created account.
+2.  Enter into previously created project. If you haven't created one,
+    then please proceed.
+3.  Go to the "API" link on the left bar.
+4.  Click on the "Generate New Token".
+5.  Enter any name for the token.
+6.  Put expiration time to "No expiry".
+7.  Check the "Write (optional)" checkbox.
+8.  Now click on the "Generate Token" button. 
+9.  After that, the token will be shown. Store it in any reliable place, preferably a password manager.
--- a/assets/markdown/how_digital_ocean-pl.md
+++ b/assets/markdown/how_digital_ocean-pl.md
@ -0,0 +1,12 @@
+### Jak uzyskać token API Digital Ocean
+1.  Wejdź na stronę [link](https://cloud.digitalocean.com/) i zaloguj się
+    na konto, które właśnie utworzyłeś.
+2.  Zaloguj się do wcześniej utworzonego projektu. Jeśli jeszcze nie utworzyłeś projektu,
+    to przejdź dalej.
+3.  Kliknij na link "API" w lewym panelu.
+4.  Kliknij na przycisk "Generate New Token".
+5.  Wprowadź dowolną nazwę dla tokena.
+6.  Ustaw datę wygaśnięcia na "No expiry".
+7.  Zaznacz pole wyboru "Write (optional)".
+8.  Teraz kliknij przycisk "Generate Token".
+9.  Na ekranie pojawi się wówczas token. Przechowuj go w dowolnym bezpiecznym miejscu, najlepiej w menedżerze haseł.
--- a/assets/markdown/how_digital_ocean-ru.md
+++ b/assets/markdown/how_digital_ocean-ru.md
@ -0,0 +1,12 @@
+### Как получить API-токен Digital Ocean
+1.  Перейдите по следующей [link](https://cloud.digitalocean.com/) и войдите
+    в только что созданную учетную запись.
+2.  Войдите в ранее созданный проект. Если вы еще не создали проект,
+    тогда приступайте.
+3.  Перейдите по ссылке "API" на левой панели.
+4.  Нажмите на кнопку "Generate New Token".
+5.  Введите любое имя для токена.
+6.  Установите срок действия на "No expiry".
+7.  Установите флажок "Write (optional)".
+8.  Теперь нажмите на кнопку "Generate Token".
+9.  После этого на экране появится токен. Сохраните его в любом надежном месте, лучше всего в менеджере паролей.
--- a/assets/markdown/how_digital_ocean-sk.md
+++ b/assets/markdown/how_digital_ocean-sk.md
@ -0,0 +1,12 @@
+### Ako získať token API Digital Ocean
+1.  Navštívte nasledujúci [link](https://cloud.digitalocean.com/) a prihláste sa
+    do novo vytvoreného účtu.
+2.  Vstúpte do predtým vytvoreného projektu. Ak ste ho ešte nevytvorili,
+    potom pokračujte ďalej.
+3.  Prejdite na odkaz "API" na ľavej lište.
+4.  Kliknite na tlačidlo "Generate New Token".
+5.  Zadajte ľubovoľný názov tokenu.
+6.  Nastavte čas vypršania platnosti na "No expiry".
+7.  Začiarknite políčko "Write (optional)" zaškrtávacie políčko.
+8.  Teraz kliknite na tlačidlo "Generate Token" tlačidlo.
+9.  Potom sa zobrazí token. Uložte ho na akékoľvek spoľahlivé miesto, najlepšie do správcu hesiel.
--- a/assets/markdown/how_digital_ocean-th.md
+++ b/assets/markdown/how_digital_ocean-th.md
@ -0,0 +1,12 @@
+### How to get Digital Ocean API Token
+1.  Visit the following [link](https://cloud.digitalocean.com/) and sign
+    into newly created account.
+2.  Enter into previously created project. If you haven't created one,
+    then please proceed.
+3.  Go to the "API" link on the left bar.
+4.  Click on the "Generate New Token".
+5.  Enter any name for the token.
+6.  Put expiration time to "No expiry".
+7.  Check the "Write (optional)" checkbox.
+8.  Now click on the "Generate Token" button. 
+9.  After that, the token will be shown. Store it in any reliable place, preferably a password manager.
--- a/assets/markdown/how_digital_ocean-uk.md
+++ b/assets/markdown/how_digital_ocean-uk.md
@ -0,0 +1,12 @@
+### How to get Digital Ocean API Token
+1.  Visit the following [link](https://cloud.digitalocean.com/) and sign
+    into newly created account.
+2.  Enter into previously created project. If you haven't created one,
+    then please proceed.
+3.  Go to the "API" link on the left bar.
+4.  Click on the "Generate New Token".
+5.  Enter any name for the token.
+6.  Put expiration time to "No expiry".
+7.  Check the "Write (optional)" checkbox.
+8.  Now click on the "Generate Token" button. 
+9.  After that, the token will be shown. Store it in any reliable place, preferably a password manager.
--- a/assets/markdown/how_fallback_old-be.md
+++ b/assets/markdown/how_fallback_old-be.md
@ -0,0 +1,3 @@
+У наступным акне увядзіце токен, атрыманы з кансолі папярэдняй версіі прыкладання.
+
+Увядзіце яго без слова *Bearer*.
--- a/assets/markdown/how_fallback_old-cs.md
+++ b/assets/markdown/how_fallback_old-cs.md
@ -0,0 +1,3 @@
+V dalším okně zadejte token získaný z konzoly předchozí verze aplikace.
+
+Zadejte ji bez slova *Bearer*.
--- a/assets/markdown/how_fallback_old-de.md
+++ b/assets/markdown/how_fallback_old-de.md
@ -0,0 +1,3 @@
+Geben Sie im nächsten Fenster das Token ein, das Sie von der Konsole der vorherigen Version der Anwendung erhalten haben.
+
+Geben Sie es ohne das Wort *Bearer* ein.
--- a/assets/markdown/how_fallback_old-es.md
+++ b/assets/markdown/how_fallback_old-es.md
@ -0,0 +1,3 @@
+In the next window, enter the token obtained from the console of the previous version of the application.
+
+Enter it without the word *Bearer*.
--- a/assets/markdown/how_fallback_old-fr.md
+++ b/assets/markdown/how_fallback_old-fr.md
@ -0,0 +1,3 @@
+In the next window, enter the token obtained from the console of the previous version of the application.
+
+Enter it without the word *Bearer*.
--- a/assets/markdown/how_fallback_old-it.md
+++ b/assets/markdown/how_fallback_old-it.md
@ -0,0 +1,3 @@
+In the next window, enter the token obtained from the console of the previous version of the application.
+
+Enter it without the word *Bearer*.
--- a/Show more
+++ b/Show more
				`@ -0,0 +1 @@`
				<svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 209.51 94.74"><defs><style>.cls-1{fill:#fff;}</style></defs><path class="cls-1" d="M143.05,93.42l1.07-3.71c1.27-4.41.8-8.48-1.34-11.48-2-2.76-5.26-4.38-9.25-4.57L58,72.7a1.47,1.47,0,0,1-1.35-2,2,2,0,0,1,1.75-1.34l76.26-1c9-.41,18.84-7.75,22.27-16.71l4.34-11.36a2.68,2.68,0,0,0,.18-1,3.31,3.31,0,0,0-.06-.54,49.67,49.67,0,0,0-95.49-5.14,22.35,22.35,0,0,0-35,23.42A31.73,31.73,0,0,0,.34,93.45a1.47,1.47,0,0,0,1.45,1.27l139.49,0h0A1.83,1.83,0,0,0,143.05,93.42Z"/><path class="cls-1" d="M168.22,41.15q-1,0-2.1.06a.88.88,0,0,0-.32.07,1.17,1.17,0,0,0-.76.8l-3,10.26c-1.28,4.41-.81,8.48,1.34,11.48a11.65,11.65,0,0,0,9.24,4.57l16.11,1a1.44,1.44,0,0,1,1.14.62,1.5,1.5,0,0,1,.17,1.37,2,2,0,0,1-1.75,1.34l-16.73,1c-9.09.42-18.88,7.75-22.31,16.7l-1.21,3.16a.9.9,0,0,0,.79,1.22h57.63A1.55,1.55,0,0,0,208,93.63a41.34,41.34,0,0,0-39.76-52.48Z"/></svg>