diff --git a/af/locale/af_ZA/content/codebase/_meta.yml b/af/locale/af_ZA/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/af/locale/af_ZA/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/af/locale/af_ZA/content/contributing/_meta.yml b/af/locale/af_ZA/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/af/locale/af_ZA/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/af/locale/af_ZA/content/running_bookwyrm/_meta.yml b/af/locale/af_ZA/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/af/locale/af_ZA/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/af/locale/af_ZA/content/using_bookwyrm/_meta.yml b/af/locale/af_ZA/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/af/locale/af_ZA/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/ar/locale/ar_SA/content/codebase/_meta.yml b/ar/locale/ar_SA/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/ar/locale/ar_SA/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/ar/locale/ar_SA/content/contributing/_meta.yml b/ar/locale/ar_SA/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/ar/locale/ar_SA/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/ar/locale/ar_SA/content/running_bookwyrm/_meta.yml b/ar/locale/ar_SA/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/ar/locale/ar_SA/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/ar/locale/ar_SA/content/using_bookwyrm/_meta.yml b/ar/locale/ar_SA/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/ar/locale/ar_SA/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/ba/locale/ba_RU/content/codebase/_meta.yml b/ba/locale/ba_RU/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/ba/locale/ba_RU/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/ba/locale/ba_RU/content/contributing/_meta.yml b/ba/locale/ba_RU/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/ba/locale/ba_RU/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/ba/locale/ba_RU/content/running_bookwyrm/_meta.yml b/ba/locale/ba_RU/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/ba/locale/ba_RU/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/ba/locale/ba_RU/content/using_bookwyrm/_meta.yml b/ba/locale/ba_RU/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/ba/locale/ba_RU/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/bn-IN/locale/bn_IN/content/codebase/_meta.yml b/bn-IN/locale/bn_IN/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/bn-IN/locale/bn_IN/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/bn-IN/locale/bn_IN/content/contributing/_meta.yml b/bn-IN/locale/bn_IN/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/bn-IN/locale/bn_IN/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/bn-IN/locale/bn_IN/content/running_bookwyrm/_meta.yml b/bn-IN/locale/bn_IN/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/bn-IN/locale/bn_IN/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/bn-IN/locale/bn_IN/content/using_bookwyrm/_meta.yml b/bn-IN/locale/bn_IN/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/bn-IN/locale/bn_IN/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/bn/locale/bn_BD/content/codebase/_meta.yml b/bn/locale/bn_BD/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/bn/locale/bn_BD/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/bn/locale/bn_BD/content/contributing/_meta.yml b/bn/locale/bn_BD/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/bn/locale/bn_BD/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/bn/locale/bn_BD/content/running_bookwyrm/_meta.yml b/bn/locale/bn_BD/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/bn/locale/bn_BD/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/bn/locale/bn_BD/content/using_bookwyrm/_meta.yml b/bn/locale/bn_BD/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/bn/locale/bn_BD/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/ca/locale/ca_ES/content/codebase/_meta.yml b/ca/locale/ca_ES/content/codebase/_meta.yml
new file mode 100644
index 00000000..69a00451
--- /dev/null
+++ b/ca/locale/ca_ES/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codibase
+order: 4
diff --git a/ca/locale/ca_ES/content/contributing/_meta.yml b/ca/locale/ca_ES/content/contributing/_meta.yml
new file mode 100644
index 00000000..e9156b59
--- /dev/null
+++ b/ca/locale/ca_ES/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Col·laborar
+order: 3
diff --git a/ca/locale/ca_ES/content/running_bookwyrm/_meta.yml b/ca/locale/ca_ES/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..4fbb4e40
--- /dev/null
+++ b/ca/locale/ca_ES/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Executant BookWyrm
+order: 2
diff --git a/ca/locale/ca_ES/content/using_bookwyrm/_meta.yml b/ca/locale/ca_ES/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..6857c896
--- /dev/null
+++ b/ca/locale/ca_ES/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Utilitzant BookWyrm
+order: 1
diff --git a/cdo/locale/cdo/content/codebase/_meta.yml b/cdo/locale/cdo/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/cdo/locale/cdo/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/cdo/locale/cdo/content/contributing/_meta.yml b/cdo/locale/cdo/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/cdo/locale/cdo/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/cdo/locale/cdo/content/running_bookwyrm/_meta.yml b/cdo/locale/cdo/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/cdo/locale/cdo/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/cdo/locale/cdo/content/using_bookwyrm/_meta.yml b/cdo/locale/cdo/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/cdo/locale/cdo/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/cs/locale/cs_CZ/content/codebase/_meta.yml b/cs/locale/cs_CZ/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/cs/locale/cs_CZ/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/cs/locale/cs_CZ/content/contributing/_meta.yml b/cs/locale/cs_CZ/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/cs/locale/cs_CZ/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/cs/locale/cs_CZ/content/running_bookwyrm/_meta.yml b/cs/locale/cs_CZ/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/cs/locale/cs_CZ/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/cs/locale/cs_CZ/content/using_bookwyrm/_meta.yml b/cs/locale/cs_CZ/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/cs/locale/cs_CZ/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/cy/locale/cy_GB/content/codebase/_meta.yml b/cy/locale/cy_GB/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/cy/locale/cy_GB/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/cy/locale/cy_GB/content/contributing/_meta.yml b/cy/locale/cy_GB/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/cy/locale/cy_GB/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/cy/locale/cy_GB/content/running_bookwyrm/_meta.yml b/cy/locale/cy_GB/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/cy/locale/cy_GB/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/cy/locale/cy_GB/content/using_bookwyrm/_meta.yml b/cy/locale/cy_GB/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/cy/locale/cy_GB/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/da/locale/da_DK/content/codebase/_meta.yml b/da/locale/da_DK/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/da/locale/da_DK/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/da/locale/da_DK/content/contributing/_meta.yml b/da/locale/da_DK/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/da/locale/da_DK/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/da/locale/da_DK/content/running_bookwyrm/_meta.yml b/da/locale/da_DK/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/da/locale/da_DK/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/da/locale/da_DK/content/using_bookwyrm/_meta.yml b/da/locale/da_DK/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/da/locale/da_DK/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/de/locale/de_DE/content/codebase/_meta.yml b/de/locale/de_DE/content/codebase/_meta.yml
new file mode 100644
index 00000000..57af2bb4
--- /dev/null
+++ b/de/locale/de_DE/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebasis
+order: 4
diff --git a/de/locale/de_DE/content/contributing/_meta.yml b/de/locale/de_DE/content/contributing/_meta.yml
new file mode 100644
index 00000000..da3bf8a9
--- /dev/null
+++ b/de/locale/de_DE/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Beitragen
+order: 3
diff --git a/de/locale/de_DE/content/running_bookwyrm/_meta.yml b/de/locale/de_DE/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..28fc3c8b
--- /dev/null
+++ b/de/locale/de_DE/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: BookWyrm betreiben
+order: 2
diff --git a/de/locale/de_DE/content/using_bookwyrm/_meta.yml b/de/locale/de_DE/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..9a58b051
--- /dev/null
+++ b/de/locale/de_DE/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: BookWyrm benutzen
+order: 1
diff --git a/el/locale/el_GR/content/codebase/_meta.yml b/el/locale/el_GR/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/el/locale/el_GR/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/el/locale/el_GR/content/contributing/_meta.yml b/el/locale/el_GR/content/contributing/_meta.yml
new file mode 100644
index 00000000..a46b3743
--- /dev/null
+++ b/el/locale/el_GR/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Συνεισφορά
+order: 3
diff --git a/el/locale/el_GR/content/running_bookwyrm/_meta.yml b/el/locale/el_GR/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..d6134d88
--- /dev/null
+++ b/el/locale/el_GR/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Εκτέλεση BookWyrm
+order: 2
diff --git a/el/locale/el_GR/content/using_bookwyrm/_meta.yml b/el/locale/el_GR/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..eb991ce5
--- /dev/null
+++ b/el/locale/el_GR/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Χρήση BookWyrm
+order: 1
diff --git a/es-ES/locale/es_ES/content/codebase/_meta.yml b/es-ES/locale/es_ES/content/codebase/_meta.yml
new file mode 100644
index 00000000..554b4668
--- /dev/null
+++ b/es-ES/locale/es_ES/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Código base
+order: 4
diff --git a/es-ES/locale/es_ES/content/contributing/_meta.yml b/es-ES/locale/es_ES/content/contributing/_meta.yml
new file mode 100644
index 00000000..34c6bf04
--- /dev/null
+++ b/es-ES/locale/es_ES/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contribuyendo
+order: 3
diff --git a/es-ES/locale/es_ES/content/running_bookwyrm/_meta.yml b/es-ES/locale/es_ES/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..6dac9329
--- /dev/null
+++ b/es-ES/locale/es_ES/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Ejecutando BookWyrm
+order: 2
diff --git a/es-ES/locale/es_ES/content/using_bookwyrm/_meta.yml b/es-ES/locale/es_ES/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..043219ae
--- /dev/null
+++ b/es-ES/locale/es_ES/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Usando BookWyrm
+order: 1
diff --git a/eu/locale/eu_ES/content/codebase/_meta.yml b/eu/locale/eu_ES/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/eu/locale/eu_ES/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/eu/locale/eu_ES/content/contributing/_meta.yml b/eu/locale/eu_ES/content/contributing/_meta.yml
new file mode 100644
index 00000000..681fcd20
--- /dev/null
+++ b/eu/locale/eu_ES/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Lagundu
+order: 3
diff --git a/eu/locale/eu_ES/content/running_bookwyrm/_meta.yml b/eu/locale/eu_ES/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..50dd5ba6
--- /dev/null
+++ b/eu/locale/eu_ES/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: BookWyrm exekutatzen
+order: 2
diff --git a/eu/locale/eu_ES/content/using_bookwyrm/_meta.yml b/eu/locale/eu_ES/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..9dde030e
--- /dev/null
+++ b/eu/locale/eu_ES/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Erabili BookWyrm
+order: 1
diff --git a/fi/locale/fi_FI/content/codebase/_meta.yml b/fi/locale/fi_FI/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/fi/locale/fi_FI/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/fi/locale/fi_FI/content/contributing/_meta.yml b/fi/locale/fi_FI/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/fi/locale/fi_FI/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/fi/locale/fi_FI/content/running_bookwyrm/_meta.yml b/fi/locale/fi_FI/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/fi/locale/fi_FI/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/fi/locale/fi_FI/content/using_bookwyrm/_meta.yml b/fi/locale/fi_FI/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/fi/locale/fi_FI/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/fr/locale/fr_FR/content/codebase/_meta.yml b/fr/locale/fr_FR/content/codebase/_meta.yml
new file mode 100644
index 00000000..c5c5e743
--- /dev/null
+++ b/fr/locale/fr_FR/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Code source
+order: 4
diff --git a/fr/locale/fr_FR/content/contributing/_meta.yml b/fr/locale/fr_FR/content/contributing/_meta.yml
new file mode 100644
index 00000000..81fe7d65
--- /dev/null
+++ b/fr/locale/fr_FR/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contribuer
+order: 3
diff --git a/fr/locale/fr_FR/content/running_bookwyrm/_meta.yml b/fr/locale/fr_FR/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..d7ea7fcb
--- /dev/null
+++ b/fr/locale/fr_FR/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Exécuter BookWyrm
+order: 2
diff --git a/fr/locale/fr_FR/content/using_bookwyrm/_meta.yml b/fr/locale/fr_FR/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..cf0217d2
--- /dev/null
+++ b/fr/locale/fr_FR/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Utiliser BookWyrm
+order: 1
diff --git a/gl/locale/gl_ES/content/codebase/_meta.yml b/gl/locale/gl_ES/content/codebase/_meta.yml
new file mode 100644
index 00000000..f59f2c7f
--- /dev/null
+++ b/gl/locale/gl_ES/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Código
+order: 4
diff --git a/gl/locale/gl_ES/content/contributing/_meta.yml b/gl/locale/gl_ES/content/contributing/_meta.yml
new file mode 100644
index 00000000..6b4f862b
--- /dev/null
+++ b/gl/locale/gl_ES/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contribuír
+order: 3
diff --git a/gl/locale/gl_ES/content/running_bookwyrm/_meta.yml b/gl/locale/gl_ES/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..21b596fa
--- /dev/null
+++ b/gl/locale/gl_ES/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Xestionar BookWyrm
+order: 2
diff --git a/gl/locale/gl_ES/content/using_bookwyrm/_meta.yml b/gl/locale/gl_ES/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..139e1e8b
--- /dev/null
+++ b/gl/locale/gl_ES/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Usar BookWyrm
+order: 1
diff --git a/he/locale/he_IL/content/codebase/_meta.yml b/he/locale/he_IL/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/he/locale/he_IL/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/he/locale/he_IL/content/contributing/_meta.yml b/he/locale/he_IL/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/he/locale/he_IL/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/he/locale/he_IL/content/running_bookwyrm/_meta.yml b/he/locale/he_IL/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/he/locale/he_IL/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/he/locale/he_IL/content/using_bookwyrm/_meta.yml b/he/locale/he_IL/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/he/locale/he_IL/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/hu/locale/hu_HU/content/codebase/_meta.yml b/hu/locale/hu_HU/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/hu/locale/hu_HU/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/hu/locale/hu_HU/content/contributing/_meta.yml b/hu/locale/hu_HU/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/hu/locale/hu_HU/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/hu/locale/hu_HU/content/running_bookwyrm/_meta.yml b/hu/locale/hu_HU/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/hu/locale/hu_HU/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/hu/locale/hu_HU/content/using_bookwyrm/_meta.yml b/hu/locale/hu_HU/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/hu/locale/hu_HU/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/it/locale/it_IT/content/codebase/_meta.yml b/it/locale/it_IT/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/it/locale/it_IT/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/it/locale/it_IT/content/contributing/_meta.yml b/it/locale/it_IT/content/contributing/_meta.yml
new file mode 100644
index 00000000..151cd3eb
--- /dev/null
+++ b/it/locale/it_IT/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contribuire
+order: 3
diff --git a/it/locale/it_IT/content/running_bookwyrm/_meta.yml b/it/locale/it_IT/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..c6e3221f
--- /dev/null
+++ b/it/locale/it_IT/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: BookWyrm In Esecuzione
+order: 2
diff --git a/it/locale/it_IT/content/using_bookwyrm/_meta.yml b/it/locale/it_IT/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..20ae18ae
--- /dev/null
+++ b/it/locale/it_IT/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Usare BookWyrm
+order: 1
diff --git a/ja/locale/ja_JP/content/codebase/_meta.yml b/ja/locale/ja_JP/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/ja/locale/ja_JP/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/ja/locale/ja_JP/content/contributing/_meta.yml b/ja/locale/ja_JP/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/ja/locale/ja_JP/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/ja/locale/ja_JP/content/running_bookwyrm/_meta.yml b/ja/locale/ja_JP/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/ja/locale/ja_JP/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/ja/locale/ja_JP/content/using_bookwyrm/_meta.yml b/ja/locale/ja_JP/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/ja/locale/ja_JP/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/ko/locale/ko_KR/content/codebase/_meta.yml b/ko/locale/ko_KR/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/ko/locale/ko_KR/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/ko/locale/ko_KR/content/contributing/_meta.yml b/ko/locale/ko_KR/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/ko/locale/ko_KR/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/ko/locale/ko_KR/content/running_bookwyrm/_meta.yml b/ko/locale/ko_KR/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/ko/locale/ko_KR/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/ko/locale/ko_KR/content/using_bookwyrm/_meta.yml b/ko/locale/ko_KR/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/ko/locale/ko_KR/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/locale/af_ZA/LC_MESSAGES/messages.po b/locale/af_ZA/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..caa8b549
--- /dev/null
+++ b/locale/af_ZA/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Afrikaans\n"
+"Language: af_ZA\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: af\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/af_ZA/content/codebase/activitypub.md b/locale/af_ZA/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/af_ZA/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/af_ZA/content/codebase/permissions.md b/locale/af_ZA/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/af_ZA/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/af_ZA/content/contributing/contributing.md b/locale/af_ZA/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/af_ZA/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/af_ZA/content/contributing/debug_toolbar.md b/locale/af_ZA/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/af_ZA/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/af_ZA/content/contributing/install-dev.md b/locale/af_ZA/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/af_ZA/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/af_ZA/content/contributing/style_guide.md b/locale/af_ZA/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/af_ZA/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/af_ZA/content/contributing/translation.md b/locale/af_ZA/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/af_ZA/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/af_ZA/content/index.md b/locale/af_ZA/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/af_ZA/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/af_ZA/content/pages/index.md b/locale/af_ZA/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/af_ZA/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/af_ZA/content/running_bookwyrm/cli.md b/locale/af_ZA/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/af_ZA/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/af_ZA/content/running_bookwyrm/external-storage.md b/locale/af_ZA/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/af_ZA/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/af_ZA/content/running_bookwyrm/install-prod-dockerless.md b/locale/af_ZA/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/af_ZA/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/af_ZA/content/running_bookwyrm/install-prod.md b/locale/af_ZA/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/af_ZA/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/af_ZA/content/running_bookwyrm/moderation.md b/locale/af_ZA/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/af_ZA/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/af_ZA/content/running_bookwyrm/monitoring-queue.md b/locale/af_ZA/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/af_ZA/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/af_ZA/content/running_bookwyrm/optional_features.md b/locale/af_ZA/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/af_ZA/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/af_ZA/content/running_bookwyrm/reverse-proxy.md b/locale/af_ZA/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/af_ZA/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/af_ZA/content/running_bookwyrm/updating.md b/locale/af_ZA/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/af_ZA/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/af_ZA/content/using_bookwyrm/adding-books.md b/locale/af_ZA/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/af_ZA/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/af_ZA/content/using_bookwyrm/posting-statuses.md b/locale/af_ZA/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/af_ZA/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/ar_SA/LC_MESSAGES/messages.po b/locale/ar_SA/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..8240c8b6
--- /dev/null
+++ b/locale/ar_SA/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Arabic\n"
+"Language: ar_SA\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=6; plural=(n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 : n%100>=11 && n%100<=99 ? 4 : 5);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: ar\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/ar_SA/content/codebase/activitypub.md b/locale/ar_SA/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/ar_SA/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/ar_SA/content/codebase/permissions.md b/locale/ar_SA/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/ar_SA/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/ar_SA/content/contributing/contributing.md b/locale/ar_SA/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/ar_SA/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/ar_SA/content/contributing/debug_toolbar.md b/locale/ar_SA/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/ar_SA/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/ar_SA/content/contributing/install-dev.md b/locale/ar_SA/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/ar_SA/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/ar_SA/content/contributing/style_guide.md b/locale/ar_SA/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/ar_SA/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/ar_SA/content/contributing/translation.md b/locale/ar_SA/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/ar_SA/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/ar_SA/content/index.md b/locale/ar_SA/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/ar_SA/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/ar_SA/content/pages/index.md b/locale/ar_SA/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/ar_SA/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/ar_SA/content/running_bookwyrm/cli.md b/locale/ar_SA/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/ar_SA/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/ar_SA/content/running_bookwyrm/external-storage.md b/locale/ar_SA/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/ar_SA/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/ar_SA/content/running_bookwyrm/install-prod-dockerless.md b/locale/ar_SA/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/ar_SA/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/ar_SA/content/running_bookwyrm/install-prod.md b/locale/ar_SA/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/ar_SA/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/ar_SA/content/running_bookwyrm/moderation.md b/locale/ar_SA/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/ar_SA/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/ar_SA/content/running_bookwyrm/monitoring-queue.md b/locale/ar_SA/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/ar_SA/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/ar_SA/content/running_bookwyrm/optional_features.md b/locale/ar_SA/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/ar_SA/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/ar_SA/content/running_bookwyrm/reverse-proxy.md b/locale/ar_SA/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/ar_SA/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/ar_SA/content/running_bookwyrm/updating.md b/locale/ar_SA/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/ar_SA/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/ar_SA/content/using_bookwyrm/adding-books.md b/locale/ar_SA/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/ar_SA/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/ar_SA/content/using_bookwyrm/posting-statuses.md b/locale/ar_SA/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/ar_SA/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/ba_RU/LC_MESSAGES/messages.po b/locale/ba_RU/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..49ef9e17
--- /dev/null
+++ b/locale/ba_RU/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-12-15 14:51\n"
+"Last-Translator: \n"
+"Language-Team: Bashkir\n"
+"Language: ba_RU\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: ba\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/ba_RU/content/codebase/activitypub.md b/locale/ba_RU/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/ba_RU/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/ba_RU/content/codebase/permissions.md b/locale/ba_RU/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/ba_RU/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/ba_RU/content/contributing/contributing.md b/locale/ba_RU/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/ba_RU/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/ba_RU/content/contributing/debug_toolbar.md b/locale/ba_RU/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/ba_RU/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/ba_RU/content/contributing/install-dev.md b/locale/ba_RU/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/ba_RU/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/ba_RU/content/contributing/style_guide.md b/locale/ba_RU/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/ba_RU/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/ba_RU/content/contributing/translation.md b/locale/ba_RU/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/ba_RU/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/ba_RU/content/index.md b/locale/ba_RU/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/ba_RU/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/ba_RU/content/running_bookwyrm/cli.md b/locale/ba_RU/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/ba_RU/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/ba_RU/content/running_bookwyrm/external-storage.md b/locale/ba_RU/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/ba_RU/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/ba_RU/content/running_bookwyrm/install-prod-dockerless.md b/locale/ba_RU/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/ba_RU/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/ba_RU/content/running_bookwyrm/install-prod.md b/locale/ba_RU/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/ba_RU/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/ba_RU/content/running_bookwyrm/moderation.md b/locale/ba_RU/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/ba_RU/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/ba_RU/content/running_bookwyrm/monitoring-queue.md b/locale/ba_RU/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/ba_RU/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/ba_RU/content/running_bookwyrm/optional_features.md b/locale/ba_RU/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/ba_RU/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/ba_RU/content/running_bookwyrm/reverse-proxy.md b/locale/ba_RU/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/ba_RU/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/ba_RU/content/running_bookwyrm/updating.md b/locale/ba_RU/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/ba_RU/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/ba_RU/content/using_bookwyrm/adding-books.md b/locale/ba_RU/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/ba_RU/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/ba_RU/content/using_bookwyrm/posting-statuses.md b/locale/ba_RU/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/ba_RU/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/bn_BD/LC_MESSAGES/messages.po b/locale/bn_BD/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..26b6cbd6
--- /dev/null
+++ b/locale/bn_BD/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2023-01-01 19:22\n"
+"Last-Translator: \n"
+"Language-Team: Bengali\n"
+"Language: bn_BD\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: bn\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/bn_BD/content/codebase/activitypub.md b/locale/bn_BD/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/bn_BD/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/bn_BD/content/codebase/permissions.md b/locale/bn_BD/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/bn_BD/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/bn_BD/content/contributing/contributing.md b/locale/bn_BD/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/bn_BD/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/bn_BD/content/contributing/debug_toolbar.md b/locale/bn_BD/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/bn_BD/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/bn_BD/content/contributing/install-dev.md b/locale/bn_BD/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/bn_BD/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/bn_BD/content/contributing/style_guide.md b/locale/bn_BD/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/bn_BD/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/bn_BD/content/contributing/translation.md b/locale/bn_BD/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/bn_BD/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/bn_BD/content/index.md b/locale/bn_BD/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/bn_BD/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/bn_BD/content/running_bookwyrm/cli.md b/locale/bn_BD/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/bn_BD/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/bn_BD/content/running_bookwyrm/external-storage.md b/locale/bn_BD/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/bn_BD/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/bn_BD/content/running_bookwyrm/install-prod-dockerless.md b/locale/bn_BD/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/bn_BD/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/bn_BD/content/running_bookwyrm/install-prod.md b/locale/bn_BD/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/bn_BD/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/bn_BD/content/running_bookwyrm/moderation.md b/locale/bn_BD/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/bn_BD/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/bn_BD/content/running_bookwyrm/monitoring-queue.md b/locale/bn_BD/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/bn_BD/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/bn_BD/content/running_bookwyrm/optional_features.md b/locale/bn_BD/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/bn_BD/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/bn_BD/content/running_bookwyrm/reverse-proxy.md b/locale/bn_BD/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/bn_BD/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/bn_BD/content/running_bookwyrm/updating.md b/locale/bn_BD/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/bn_BD/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/bn_BD/content/using_bookwyrm/adding-books.md b/locale/bn_BD/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/bn_BD/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/bn_BD/content/using_bookwyrm/posting-statuses.md b/locale/bn_BD/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/bn_BD/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/bn_IN/LC_MESSAGES/messages.po b/locale/bn_IN/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..58a302e5
--- /dev/null
+++ b/locale/bn_IN/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2023-01-01 19:23\n"
+"Last-Translator: \n"
+"Language-Team: Bengali, India\n"
+"Language: bn_IN\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: bn-IN\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/bn_IN/content/codebase/activitypub.md b/locale/bn_IN/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/bn_IN/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/bn_IN/content/codebase/permissions.md b/locale/bn_IN/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/bn_IN/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/bn_IN/content/contributing/contributing.md b/locale/bn_IN/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/bn_IN/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/bn_IN/content/contributing/debug_toolbar.md b/locale/bn_IN/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/bn_IN/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/bn_IN/content/contributing/install-dev.md b/locale/bn_IN/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/bn_IN/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/bn_IN/content/contributing/style_guide.md b/locale/bn_IN/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/bn_IN/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/bn_IN/content/contributing/translation.md b/locale/bn_IN/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/bn_IN/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/bn_IN/content/index.md b/locale/bn_IN/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/bn_IN/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/bn_IN/content/running_bookwyrm/cli.md b/locale/bn_IN/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/bn_IN/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/bn_IN/content/running_bookwyrm/external-storage.md b/locale/bn_IN/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/bn_IN/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/bn_IN/content/running_bookwyrm/install-prod-dockerless.md b/locale/bn_IN/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/bn_IN/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/bn_IN/content/running_bookwyrm/install-prod.md b/locale/bn_IN/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/bn_IN/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/bn_IN/content/running_bookwyrm/moderation.md b/locale/bn_IN/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/bn_IN/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/bn_IN/content/running_bookwyrm/monitoring-queue.md b/locale/bn_IN/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/bn_IN/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/bn_IN/content/running_bookwyrm/optional_features.md b/locale/bn_IN/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/bn_IN/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/bn_IN/content/running_bookwyrm/reverse-proxy.md b/locale/bn_IN/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/bn_IN/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/bn_IN/content/running_bookwyrm/updating.md b/locale/bn_IN/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/bn_IN/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/bn_IN/content/using_bookwyrm/adding-books.md b/locale/bn_IN/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/bn_IN/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/bn_IN/content/using_bookwyrm/posting-statuses.md b/locale/bn_IN/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/bn_IN/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/ca_ES/LC_MESSAGES/messages.po b/locale/ca_ES/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..061f0d96
--- /dev/null
+++ b/locale/ca_ES/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2023-01-11 09:51\n"
+"Last-Translator: \n"
+"Language-Team: Catalan\n"
+"Language: ca_ES\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: ca\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr "Documentació de BookWyrm"
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr "La teva guia per a utilitzar i contribuir a BookWyrm"
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr "Com Utilitzar i Contribuir"
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr "BookWyrm: Lectura Social i Ressenyes"
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "Uneix-te"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr "Col·laboreu-hi"
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "Assistència"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr "Codi"
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr "Documentació"
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr "<strong>BookWyrm</strong> és un programari col·laboratiu i anticorporatiu mantingut per <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr "Dona suport a BookWyrm mitjançant <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr "Col·laboreu-hi"
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr "BookWyrm a GitHub"
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr "Contribueix a aquesta pàgina"
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr "Més informació"
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr "Contacta amb l'administrador"
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr "Llicència"
+
diff --git a/locale/ca_ES/content/codebase/activitypub.md b/locale/ca_ES/content/codebase/activitypub.md
new file mode 100644
index 00000000..b81b85c1
--- /dev/null
+++ b/locale/ca_ES/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm utiltza el protocol [ActivityPub](http://activitypub.rocks/) per enviar i rebre activitat d'usuari entre diferents instàncies de BookWyrm i altres serveis que implementen ActivityPub, com [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Tipus d'objecte
+
+- `Nota`: En serveis com Mastodon, les `Notes` són el tipus principal d'estat. Contenen un cos del missatge, adjunts, poden fer menció a usuaris i, ser respostes altres tipus d'estat. Dins de BookWyrm, les `Notes` només poden ser creades com a missatges directes o com a respostes a altres estats.
+- `Ressenya`: Una ressenya és un estat en resposta a un llibre (indicat pel camp `inReplyToBook`), el qual conté títol, cos i, una valoració numèrica entre 0 (no valorat) i 5.
+- `Comentari`: Un comentari en un llibre fa referència a un llibre i té un cos del missatge.
+- `Cita`: Una cita té un cos del missatge, un extracte d'un llibre i, menciona un llibre.
+
+
+#### Activitats
+
+- `Crear`: guarda un nou estat a la base de dades.
+
+   **Nota**: BookWyrm nomès accepta activitats de `Crear` si són:
+
+   - Missatges directes (per exemple `Notes` amb el nivell de privacitat `directe`, el qual menciona a un usuari local),
+   - Relacionat amb un llibre (amb un estat personalitzat que inclogui el camp `inReplyToBook`),
+   - Respostes a estats ja existents guardats a la base de dades
+- `Eliminar`: Elimina un estat
+- `M'agrada`: Crea un favorit a l'estat
+- `Anunci`: Destaca l'estat a la línia de temps de l'actor
+- `Desfer`: Desfà un `M'agrada` o un `Anunci`
+
+### Col·leccions
+Els llibres i llistats de l'usuari son representats per [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objectes
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activitats
+
+- `Create`: Afegeix un prestatge o llista a la base de dades.
+- `Delete`: Elimina un prestatge o llista.
+- `Add`: Afegeix un llibre al prestatge o llista.
+- `Remove`: Elimina un llibre del prestatge o llista.
+
+
+## Serialitzacions alternatives
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/ca_ES/content/codebase/permissions.md b/locale/ca_ES/content/codebase/permissions.md
new file mode 100644
index 00000000..8aff2ab2
--- /dev/null
+++ b/locale/ca_ES/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Títol: Permisos Data: 2021-04-18 Ordre: 2
+- - -
+
+L'accés de l'usuari a les diferents funcionalitats és controlat mitjançant el [sistema d'autenticació](https://docs.djangoproject.com/en/3.2/topics/auth/default/) de Django. Quan es crea una instància, l'script `initdb` crea una sèrie de permisos, els quals són assignats a grups. Per defecte, tots els usuaris nous són assignats al grup `editor` , el qual els hi permet editar les metadades dels llibres.
+
+La instància d'administrador ha de disposar de l'estat `superusuari` , el qual li dona accés a l'administració de Django (`/admin`) i li otorga tots els permisos a l'usuari.
+
+## Permisos i grups
+Aquesta taula mostra els quatre grups (administrador, moderador, editor i usuari) i quins permisos tenen els usuaris en aquell grup:
+
+|                                        | administrador | moderador | editor | usuari |
+| -------------------------------------- | ------------- | --------- | ------ | ------ |
+| editar la configuració de la instància | ✔️            | -         | -      | -      |
+| modificar el nivell de l'usuari        | ✔️            | -         | -      | -      |
+| gestionar federació                    | ✔️            | ✔️        | -      | -      |
+| convidar                               | ✔️            | ✔️        | -      | -      |
+| desactivar usuaris                     | ✔️            | ✔️        | -      | -      |
+| eliminar publicacions                  | ✔️            | ✔️        | -      | -      |
+| editar llibres                         | ✔️            | ✔️        | ✔️     | -      |
+ pujar portades            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/ca_ES/content/contributing/contributing.md b/locale/ca_ES/content/contributing/contributing.md
new file mode 100644
index 00000000..3d9e738d
--- /dev/null
+++ b/locale/ca_ES/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Títol: Com col·laborar Data: 2021-04-12 Ordre: 1
+- - -
+
+Hi ha moltes formes de col·laborar en el projecte, independentment dels teus coneixements tècnics o experiència.
+
+## Suggeriments i petició de funcionalitats
+Si us plau, sigues lliure de remetre errors, suggeriments, demanar funcionalitats i altre idees sobre com millorar mitjançant [incidències de GitHub](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Contribucions al codi
+Les contribucions al codi són molt benvingudes! Si no saps per on començar, fes un cop d'ull a l''etiqueta ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22). Degut a que BookWyrm és un petit projecte, no hi ha molta estructura formal, però hi ha una gran capacitat de recolzament entre tots, que es pot veure formulant preguntes, programant en equip, fent videotrucades, etcetera, així que sigueu lliures de contactar-nos.
+
+Si teniu preguntes sobre el projecte o com col·laborar-hi, us podeu unir al [xat de matrix de BookWyrm](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Traducció
+Parles alguna altra llengua a més de l'Anglès? BookWyrm necessita traducció! Pots afegir i editar traduccions a [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Suport Financer
+BookWyrm és un projecte sense anuncis i sense voluntat de cercar mecenes de manera activa o finançament mitjançant relacions amb empreses. Si vols ajudar a mantenir el projecte viu, et pots convertir en contribuïdor mitjançant [Patreon](https://www.patreon.com/bookwyrm) o [OpenCollective](https://opencollective.com/bookwyrm), o enviant una ajuda puntual a través de [PayPal](https://paypal.me/oulipo).
diff --git a/locale/ca_ES/content/contributing/debug_toolbar.md b/locale/ca_ES/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..4035f8f9
--- /dev/null
+++ b/locale/ca_ES/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Títol: Barra d'eines de depuració de Django Data: 2022-05-16 Ordre: 5
+- - -
+
+BookWyrm té una branca configurada per executar la [Barra d'Eines de Depuració de Django](https://django-debug-toolbar.readthedocs.io/en/latest/). Aquesta branca no serà mai unida a `main` i té alguns retocs que li permet treballar amb la barra d'eines però, no és segur fer-ne ús en un entorn destinat a producció. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/ca_ES/content/contributing/install-dev.md b/locale/ca_ES/content/contributing/install-dev.md
new file mode 100644
index 00000000..10803716
--- /dev/null
+++ b/locale/ca_ES/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Títol: Entorn de desenvolupament Data: 2021-04-12 Ordre: 3
+- - -
+
+## Requisits previs
+
+Aquestes instruccions assumeixen que estàs desenvolupant BookWyrm mitjançant Docker. Necessitaràs [instal·lar Docker](https://docs.docker.com/engine/install/) i [docker-compose](https://docs.docker.com/compose/install/) per començar.
+
+## Configuració de l'entorn de desenvolupament
+
+- Aconsegueix una còpia del [codi base de BookWyrm a GitHub](https://github.com/bookwyrm-social/bookwyrm). Pots [crear una derivació](https://docs.github.com/en/get-started/quickstart/fork-a-repo) del repositori i, llavors [utilitzar `git clone` per descarregar el codi](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) a l'ordinador.
+- Ves al directori que conté el codi al teu ordinador, treballaràs des d'aquí d'ara en endavant.
+- Configura el teu fitxer de variables d'entorn de desenvolupament copiant el fitxer d'entorn d'exemple (`.env.example`) a un nou fitxer anomenat `.env`. A la línia de comandes, pots fer-ho mitjançant:
+``` { .sh }
+cp .env.example .env
+```
+- A `.env`, modifica `DEBUG` a `true`
+- Opcionalment, pots utilitzar un servei com [ngrok](https://ngrok.com/) per configurar el nom de domini i, establir la variable `DOMAIN` al teu fitxer `.env` al nom de domini generat per ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/ca_ES/content/contributing/style_guide.md b/locale/ca_ES/content/contributing/style_guide.md
new file mode 100644
index 00000000..a7cfd13e
--- /dev/null
+++ b/locale/ca_ES/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Títol: Guia d'estil Data: 2021-10-20 Ordre: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+Fem ús d'[EditorConfig](https://editorconfig.org) per mantenir sagnats i finals de línia consistents.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Plantilles (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Disseny inclusiu
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Formularis
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Botons i enllaços
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/ca_ES/content/contributing/translation.md b/locale/ca_ES/content/contributing/translation.md
new file mode 100644
index 00000000..367736a0
--- /dev/null
+++ b/locale/ca_ES/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Títol: Traduccions Data: 2021-10-20 Ordre: 2
+- - -
+
+## Contribueix a les traduccions
+
+Pots unir-te al projecte de traduccions de BookWyrm a [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Llenguatge de gènere neutre
+
+Sempre que sigui possible, les traduccions de BookWyrm hauran d'utilitzar llenguatge de gènere neutre. Això aplica tant si la llengua té per defecte el gènere masculí com a neutre o si utilitza quelcom similar a "ell/ella". És important per a les traduccions ser clar, concís i comprensible de cara al lector i, alguns cops aquests objectius es troben en conflicte; no hi ha una solució única o perfecta, depèn del mateix idioma.
+
+Com a principi, intenta donar un valor alt al llenguatge inclusiu i de gènere neutre que a formes respectuoses o guies d'estil oficials. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/ca_ES/content/index.md b/locale/ca_ES/content/index.md
new file mode 100644
index 00000000..8912a90f
--- /dev/null
+++ b/locale/ca_ES/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Títol: Acollida Data: 2021-04-13
+- - -
+
+BookWyrm és una xarxa social per monitorar la teva lectura, parlar de llibres, escriure ressenyes i descobrir que llegir a continuació. La federació permet als usuaris de BookWyrm unir-se a comunitats petites i confiables que poden connectar-se entre si i amb altres serveis ActivityPub com Mastodon i Pleroma.
+
+## Funcionalitats
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/ca_ES/content/pages/index.md b/locale/ca_ES/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/ca_ES/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/ca_ES/content/running_bookwyrm/cli.md b/locale/ca_ES/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..225a40dd
--- /dev/null
+++ b/locale/ca_ES/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Títol: Eina de Línia de Comandes Data: 2021-11-11 Ordre: 9
+- - -
+
+Els desenvolupadors i gestors d'instàncies de BookWyrm poden fer ús de l'script `bw-dev` per a tasques habituals. Això pot fer que les teves comandes siguin més curtes, fàcils de recordar i, més difícil cometre erros.
+
+Un cop ja has instal·lat Bookwyrm en un entorn de [producció](installing-in-production.html) o [desenvolupament](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), pots trucar l'script des de la línia de comandes mitjançant `./bw-dev` seguit de la subcomanda que vols executar.
+
+## Dreceres de Docker
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Gestionar la base de dades
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Gestionar una instància de BookWyrm
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/ca_ES/content/running_bookwyrm/external-storage.md b/locale/ca_ES/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..1ad29e2b
--- /dev/null
+++ b/locale/ca_ES/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Títol: Emmagatzematge Extern Data: 2021-06-07 Ordre: 7
+- - -
+
+Per defecte, BookWyrm fa ús d'emmagatzematge local per a elements estàtics (favicon, avatar per defecte, etc.) i mitjans visuals (avatars d'usuaris, portades de llibres, etc.), però pots utilitzar emmagatzematge extern per nodrir aquests arxius. BookWyrm utilitza `django-storages` per gestionar emmagatzematge extern, com serveis compatibles S3, Apache Libcloud o SFTP.
+
+## Serveis compatibles S3
+
+### Configuració
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### Què t'espera?
+
+Si inicies una nova instància BookWyrm, el procés és el següent:
+
+- Configurar el teu servei d'emmagatzematge extern
+- Habilitar l'emmagatzematge extern a BookWyrm
+- Iniciar la teva instància BookWyrm
+- Actualitzar el connector de la instància
+
+Si ja has iniciat la teva instància i, les imatges han sigut carregades a l'emmagatzematge local, el procés és el següent:
+
+- Configurar el teu servei d'emmagatzematge extern
+- Copiar els teus mitjans visuals locals a l'emmagatzematge extern
+- Habilitar l'emmagatzematge extern a BookWyrm
+- Reiniciar la teva instància BookWyrm
+- Actualitzar el connector de la instància
+
+### Paràmetres de BookWyrm
+
+Edita el teu fitxer `.env` no comentant les següents línies:
+
+- `AWS_ACCESS_KEY_ID`: la teva clau ID d'accés
+- `AWS_SECRET_ACCESS_KEY`: la teva clau d'accés secreta
+- `AWS_STORAGE_BUCKET_NAME`: el nom del teu contenidor
+- `AWS_S3_REGION_NAME`: per exemple `"eu-west-1"` per a AWS, `"fr-par"` per a Scaleway o `"nyc3"` per a Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/ca_ES/content/running_bookwyrm/install-prod-dockerless.md b/locale/ca_ES/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..e5fc88e4
--- /dev/null
+++ b/locale/ca_ES/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Instal·lar sense Docker
+Date: 2022-10-02
+Order: 2
+---
+
+Aquest projecte encara és jove i no és, en aquest moment, molt estable, així que aneu amb compte a l'executar-lo en producció. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Configuració del servidor
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/ca_ES/content/running_bookwyrm/install-prod.md b/locale/ca_ES/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/ca_ES/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/ca_ES/content/running_bookwyrm/moderation.md b/locale/ca_ES/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/ca_ES/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/ca_ES/content/running_bookwyrm/monitoring-queue.md b/locale/ca_ES/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..0f5243e1
--- /dev/null
+++ b/locale/ca_ES/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitorant la cua
+Date: 2022-11-23
+Order: 6
+---
+
+Hi pot haver ocasions en què la teva instància es comporti de manera lenta. Una opció pot ser revisar la cua per veure treballs penjats. Llegeix per saber-ne més.
+
+## Celery
+
+BookWyrm fa ús de [Celery](https://docs.celeryq.dev/en/stable/) per gestionar treballs en cua.
+
+## Flower
+
+Per veure els treballs de Celery en temps real, BookWyrm fa ús de [Flower](https://flower.readthedocs.io/en/latest/).
+
+En cas que no hagis retocat [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) pots trobar el servei al [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). Això és: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasques
+
+Pots trobar [`@app.task` ](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) les tasques anotades al codi base.
diff --git a/locale/ca_ES/content/running_bookwyrm/optional_features.md b/locale/ca_ES/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..b04a0525
--- /dev/null
+++ b/locale/ca_ES/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Generació de previsualitzacions d'imatges
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Habilitar previsualització d'imatges
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generant imatges previsualitzades
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Paràmetres opcionals
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Eliminar previsualització d'imatges per a usuaris remots
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/ca_ES/content/running_bookwyrm/reverse-proxy.md b/locale/ca_ES/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..92ce6edd
--- /dev/null
+++ b/locale/ca_ES/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Títol: Utilitzant un Reverse-Proxy Data: 2021-05-11 Ordre: 4
+- - -
+
+## Executant BookWyrm rere un Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/ca_ES/content/running_bookwyrm/updating.md b/locale/ca_ES/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..d946b064
--- /dev/null
+++ b/locale/ca_ES/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Títol: Actualitzant la teva instància Data: 2022-11-17 Ordre: 3
+- - -
+
+Quan hi ha canvis disponibles a la branca de producció, els pots instal·lar i fer funcionar a la teva instància mitjançant la comanda `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/ca_ES/content/using_bookwyrm/adding-books.md b/locale/ca_ES/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..1815ffa5
--- /dev/null
+++ b/locale/ca_ES/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Afegir llibres
+Date: 2022-07-29
+Order: 2
+---
+
+Hi ha diferents vies per tal d'afegir llibres a la teva instància de BookWyrm! Quan no trobis el llibre que estàs cercant, prova aquestes opcions per ordre -- és millor fer una importació que crear un des de zero.
+
+## Carregar llibres d'altres catàlegs
+
+Si el llibre que estàs cercant no es troba disponible a la teva instància, hi ha diferents vies per tal d'afegir-lo. La millor via és important-lo des d'una font externa -- la teva instància pot carregar llibres d'altres instàncies de BookWyrm, com també d'[OpenLibrary](http://openlibrary.org/) i d'[Inventaire](http://inventaire.io/). Si no hi ha resultats per a la teva cerca, aquestes fonts seran automàticament consultades i, se't mostrarà un botó per "**Importar llibre**". Si hi han resultats locals no desitjats, pots pitjar l'enllaç "**Carregar resultats d'altres catàlegs**" per carregar més resultats.
+
+
+## Afegir una altra edició
+
+Si trobes el llibre desitjat, però no l'edició correcta, pots afegir una edició diferent des del llistat d'edicions. Pitja l'enllaç situat sota la descripció on es mostra el número d'edicions que hi ha (per exemple "**4 edicions**"). Al final de la llista d'edicions, hi trobaràs el botó "**Afegir una altra edició**".
+
+## Afegir un llibre completament nou
+
+Un cop has provat de cercar el llibre, importar-lo d'un altre catàleg i, comprovar altres edicions, pots afegir un nou llibre manualment. L'enllaç per a afegir manualment el llibre es troba al final de la pàgina de cerca quan es mostren catàlegs externs. També pots navegar directament a `/create-book` a la teva instància.
diff --git a/locale/ca_ES/content/using_bookwyrm/posting-statuses.md b/locale/ca_ES/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..b5343d7a
--- /dev/null
+++ b/locale/ca_ES/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Tipus d'estats
+
+### Comentari d'usuari
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component                | Review | Comment | Quote | Reply |
+| ------------------------ | ------ | ------- | ----- | ----- |
+| Camp de text             | ✔      | ✔       | ✔     | ✔     |
+| Revela parts de la trama | ✔      | ✔       | ✔     | ✔     |
+| Número de pàgina         |        | ✔       | ✔     |       |
+| Cita                     |        |         | ✔     |       |
+| Valoració                | ✔      |         |       |       |
+| Camp de títol            | ✔      |         |       |       |
+
+
+### Actualitzacions d'estats de lectura
+
+Els estats són generats quan un usuari indica que vol llegir, ha començat a llegir o ha acabat de llegir un llibre.
+
+## Text
+El text pot incloure:
+
+- Mencions (@usuari)
+- URLs (`http(s)://` no es mostra)
+- Algunes [opcions de format](https://www.markdownguide.org/cheat-sheet/)
+  - negreta
+  - cursiva
+  - cometes
+  - llista amb boletes
+  - enllaços
+
diff --git a/locale/cdo/LC_MESSAGES/messages.po b/locale/cdo/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..b2817b7e
--- /dev/null
+++ b/locale/cdo/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Eastern Min\n"
+"Language: cdo\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n > 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: cdo\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/cdo/content/codebase/activitypub.md b/locale/cdo/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/cdo/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/cdo/content/codebase/permissions.md b/locale/cdo/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/cdo/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/cdo/content/contributing/contributing.md b/locale/cdo/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/cdo/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/cdo/content/contributing/debug_toolbar.md b/locale/cdo/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/cdo/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/cdo/content/contributing/install-dev.md b/locale/cdo/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/cdo/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/cdo/content/contributing/style_guide.md b/locale/cdo/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/cdo/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/cdo/content/contributing/translation.md b/locale/cdo/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/cdo/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/cdo/content/index.md b/locale/cdo/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/cdo/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/cdo/content/pages/index.md b/locale/cdo/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/cdo/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/cdo/content/running_bookwyrm/cli.md b/locale/cdo/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/cdo/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/cdo/content/running_bookwyrm/external-storage.md b/locale/cdo/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/cdo/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/cdo/content/running_bookwyrm/install-prod-dockerless.md b/locale/cdo/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/cdo/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/cdo/content/running_bookwyrm/install-prod.md b/locale/cdo/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/cdo/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/cdo/content/running_bookwyrm/moderation.md b/locale/cdo/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/cdo/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/cdo/content/running_bookwyrm/monitoring-queue.md b/locale/cdo/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/cdo/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/cdo/content/running_bookwyrm/optional_features.md b/locale/cdo/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/cdo/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/cdo/content/running_bookwyrm/reverse-proxy.md b/locale/cdo/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/cdo/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/cdo/content/running_bookwyrm/updating.md b/locale/cdo/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/cdo/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/cdo/content/using_bookwyrm/adding-books.md b/locale/cdo/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/cdo/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/cdo/content/using_bookwyrm/posting-statuses.md b/locale/cdo/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/cdo/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/cs_CZ/LC_MESSAGES/messages.po b/locale/cs_CZ/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..c7f9f0d3
--- /dev/null
+++ b/locale/cs_CZ/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Czech\n"
+"Language: cs_CZ\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=4; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 3;\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: cs\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/cs_CZ/content/codebase/activitypub.md b/locale/cs_CZ/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/cs_CZ/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/cs_CZ/content/codebase/permissions.md b/locale/cs_CZ/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/cs_CZ/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/cs_CZ/content/contributing/contributing.md b/locale/cs_CZ/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/cs_CZ/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/cs_CZ/content/contributing/debug_toolbar.md b/locale/cs_CZ/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/cs_CZ/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/cs_CZ/content/contributing/install-dev.md b/locale/cs_CZ/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/cs_CZ/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/cs_CZ/content/contributing/style_guide.md b/locale/cs_CZ/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/cs_CZ/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/cs_CZ/content/contributing/translation.md b/locale/cs_CZ/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/cs_CZ/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/cs_CZ/content/index.md b/locale/cs_CZ/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/cs_CZ/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/cs_CZ/content/pages/index.md b/locale/cs_CZ/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/cs_CZ/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/cs_CZ/content/running_bookwyrm/cli.md b/locale/cs_CZ/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/cs_CZ/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/cs_CZ/content/running_bookwyrm/external-storage.md b/locale/cs_CZ/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/cs_CZ/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/cs_CZ/content/running_bookwyrm/install-prod-dockerless.md b/locale/cs_CZ/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/cs_CZ/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/cs_CZ/content/running_bookwyrm/install-prod.md b/locale/cs_CZ/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/cs_CZ/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/cs_CZ/content/running_bookwyrm/moderation.md b/locale/cs_CZ/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/cs_CZ/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/cs_CZ/content/running_bookwyrm/monitoring-queue.md b/locale/cs_CZ/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/cs_CZ/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/cs_CZ/content/running_bookwyrm/optional_features.md b/locale/cs_CZ/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/cs_CZ/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/cs_CZ/content/running_bookwyrm/reverse-proxy.md b/locale/cs_CZ/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/cs_CZ/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/cs_CZ/content/running_bookwyrm/updating.md b/locale/cs_CZ/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..bae05257
--- /dev/null
+++ b/locale/cs_CZ/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Název: Aktualizace instance Datum: 2022-11-17 Pořadí: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` spouští migrace databáze v Django pomocí nově sestavených Docker obrazů
+- `docker-compose run --rm web python manage.py collectstatic --no-input` načte všechny aktualizované statické soubory (například JavaScript a CSS)
+- `dokové složení; docker-compose -d` restartuje všechny Docker kontejnery a použije nově sestavené obrazy (upozornění: výpadek během restartu)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/cs_CZ/content/using_bookwyrm/adding-books.md b/locale/cs_CZ/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/cs_CZ/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/cs_CZ/content/using_bookwyrm/posting-statuses.md b/locale/cs_CZ/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/cs_CZ/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/cy_GB/LC_MESSAGES/messages.po b/locale/cy_GB/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..d7101afd
--- /dev/null
+++ b/locale/cy_GB/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Welsh\n"
+"Language: cy_GB\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=6; plural=(n == 0) ? 0 : ((n == 1) ? 1 : ((n == 2) ? 2 : ((n == 3) ? 3 : ((n == 6) ? 4 : 5))));\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: cy\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/cy_GB/content/codebase/activitypub.md b/locale/cy_GB/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/cy_GB/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/cy_GB/content/codebase/permissions.md b/locale/cy_GB/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/cy_GB/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/cy_GB/content/contributing/contributing.md b/locale/cy_GB/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/cy_GB/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/cy_GB/content/contributing/debug_toolbar.md b/locale/cy_GB/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/cy_GB/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/cy_GB/content/contributing/install-dev.md b/locale/cy_GB/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/cy_GB/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/cy_GB/content/contributing/style_guide.md b/locale/cy_GB/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/cy_GB/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/cy_GB/content/contributing/translation.md b/locale/cy_GB/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/cy_GB/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/cy_GB/content/index.md b/locale/cy_GB/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/cy_GB/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/cy_GB/content/pages/index.md b/locale/cy_GB/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/cy_GB/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/cy_GB/content/running_bookwyrm/cli.md b/locale/cy_GB/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/cy_GB/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/cy_GB/content/running_bookwyrm/external-storage.md b/locale/cy_GB/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/cy_GB/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/cy_GB/content/running_bookwyrm/install-prod-dockerless.md b/locale/cy_GB/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/cy_GB/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/cy_GB/content/running_bookwyrm/install-prod.md b/locale/cy_GB/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/cy_GB/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/cy_GB/content/running_bookwyrm/moderation.md b/locale/cy_GB/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/cy_GB/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/cy_GB/content/running_bookwyrm/monitoring-queue.md b/locale/cy_GB/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/cy_GB/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/cy_GB/content/running_bookwyrm/optional_features.md b/locale/cy_GB/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/cy_GB/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/cy_GB/content/running_bookwyrm/reverse-proxy.md b/locale/cy_GB/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/cy_GB/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/cy_GB/content/running_bookwyrm/updating.md b/locale/cy_GB/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/cy_GB/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/cy_GB/content/using_bookwyrm/adding-books.md b/locale/cy_GB/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/cy_GB/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/cy_GB/content/using_bookwyrm/posting-statuses.md b/locale/cy_GB/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/cy_GB/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/da_DK/LC_MESSAGES/messages.po b/locale/da_DK/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..08dacb57
--- /dev/null
+++ b/locale/da_DK/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Danish\n"
+"Language: da_DK\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: da\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/da_DK/content/codebase/activitypub.md b/locale/da_DK/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/da_DK/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/da_DK/content/codebase/permissions.md b/locale/da_DK/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/da_DK/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/da_DK/content/contributing/contributing.md b/locale/da_DK/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/da_DK/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/da_DK/content/contributing/debug_toolbar.md b/locale/da_DK/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/da_DK/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/da_DK/content/contributing/install-dev.md b/locale/da_DK/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/da_DK/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/da_DK/content/contributing/style_guide.md b/locale/da_DK/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/da_DK/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/da_DK/content/contributing/translation.md b/locale/da_DK/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/da_DK/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/da_DK/content/index.md b/locale/da_DK/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/da_DK/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/da_DK/content/pages/index.md b/locale/da_DK/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/da_DK/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/da_DK/content/running_bookwyrm/cli.md b/locale/da_DK/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/da_DK/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/da_DK/content/running_bookwyrm/external-storage.md b/locale/da_DK/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/da_DK/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/da_DK/content/running_bookwyrm/install-prod-dockerless.md b/locale/da_DK/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/da_DK/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/da_DK/content/running_bookwyrm/install-prod.md b/locale/da_DK/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/da_DK/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/da_DK/content/running_bookwyrm/moderation.md b/locale/da_DK/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/da_DK/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/da_DK/content/running_bookwyrm/monitoring-queue.md b/locale/da_DK/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/da_DK/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/da_DK/content/running_bookwyrm/optional_features.md b/locale/da_DK/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/da_DK/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/da_DK/content/running_bookwyrm/reverse-proxy.md b/locale/da_DK/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/da_DK/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/da_DK/content/running_bookwyrm/updating.md b/locale/da_DK/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/da_DK/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/da_DK/content/using_bookwyrm/adding-books.md b/locale/da_DK/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/da_DK/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/da_DK/content/using_bookwyrm/posting-statuses.md b/locale/da_DK/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/da_DK/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/de_DE/LC_MESSAGES/messages.po b/locale/de_DE/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..d58fdfa2
--- /dev/null
+++ b/locale/de_DE/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2023-01-02 13:53\n"
+"Last-Translator: \n"
+"Language-Team: German\n"
+"Language: de_DE\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: de\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr "BookWyrm Dokumentation"
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr "Deine Anleitung BookWyrm zu nutzen und dazu beizutragen"
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr "Wie man es nutzt und beiträgt"
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr "BookWyrm: gemeinsames Lesen und Besprechen"
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "Beitreten"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr "Mach mit"
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "Unterstützung"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr "Code"
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr "Dokumentation"
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr "<strong>BookWyrm</strong> ist eine kollaborative, nichtkommerzielle Software, die von <a href='https://www.mousereeve.com/'>Mouse Reeve</a> betrieben wird."
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr "Unterstütze BookWyrm auf <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr "Machen Sie mit"
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr "BookWyrm auf GitHub"
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr "Zu dieser Seite beitragen"
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr "Mehr erfahren"
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr "Betreiber*in kontaktieren"
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr "Lizenz"
+
diff --git a/locale/de_DE/content/codebase/activitypub.md b/locale/de_DE/content/codebase/activitypub.md
new file mode 100644
index 00000000..80a19c8f
--- /dev/null
+++ b/locale/de_DE/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm verwendet das [ActivityPub](http://activitypub.rocks/)-Protokoll, um Benutzeraktivitäten zwischen anderen BookWyrm-Instanzen und anderen Diensten zu senden und zu empfangen, die ActivityPub implementieren, wie [Mastodon](https://joinmastodon.org/). Um Buchdaten zu behandeln, hat BookWyrm eine Handvoll erweiterter Aktivitätstypen, die nicht zum Standard gehören, aber nur für andere BookWyrm-Instanzen lesbar sind.
+
+## Aktivitäten und Objekte
+
+### Benutzer*innen und Beziehungen
+Benutzer*innenbeziehungsinteraktionen folgen der Standard ActivityPub Spezifikation.
+
+- `Folgen`: Bitte, um den Status eine*r Benutzer*in zu erhalten und anzusehen, die die Privatsphäre auf nur Follower haben
+- `Akzeptieren`: genehmigt `Folgen` und erstellt die Beziehung
+- `Ablehnen`: verweigert `Folgen`
+- `Blocken`: verhindert, dass Benutzer*innen einander Status ansehen und verhindert, dass der blockierte Benutzer*innen das Profil des Akteurs ansehen
+- `Update`: Aktualisiert das Profil und die Einstellungen eine*r Benutzer*in
+- `Löschen`: Deaktiviert eine*n Benutzer*in
+- `Rückgängig`: Reversiert `Folgen` oder `Blocken`
+
+### Status
+#### Objekttypen
+
+- `Notiz`: Bei Diensten wie Mastodon, ist `Notiz`en der primäre Typ des Status. Sie enthalten einen Text, Anhänge, können Benutzer erwähnen und Antworten auf Status jeder Art sein. In BookWyrm können `Notiz`en nur als direkte Nachrichten oder als Antworten auf andere Status erstellt werden.
+- `Rezension`: Eine Rezension ist ein Status, der sich auf ein Buch bezieht (angezeigt durch das `inReplyToBook`-Feld), welches einen Titel, Text sowie die numerische Bewertung auf einer Skala von 0 (keine Bewertung) bis 5 enthält.
+- `Kommentar`: Ein Kommentar zu einem Buch erwähnt ein Buch und hat einen Text.
+- `Zitat`: Ein Zitat enthält einen Text, einen Auszug aus dem Buch und erwähnt ein Buch.
+
+
+#### Aktivitäten
+
+- `Erstellen`: Speichert einen neuen Status in der Datenbank.
+
+   **Hinweis**: BookWyrm akzeptiert nur `Erstellen`-Aktivitäten, wenn sie sind:
+
+   - Direktnachrichten (d.h. `Hinweis`e mit der Datenschutzstufe `direkt`, welche einen lokalen Benutzer erwähnen),
+   - Verbunden mit einem Buch (eines benutzerdefinierten Statusstyps, der das Feld `inReplyToBook` enthält),
+   - Antworten auf existierende Status in der Datenbank
+- `Löschen`: Entfernt einen Status
+- `Gefällt`: Erstellt einen Favoriten für den Status
+- `Ankündigung`: Teilt den Status in der Zeitleiste des Akteurs
+- `Rückgängig`: Reversiert `Gefällt` oder `Ankündigung`
+
+### Sammlungen
+Bücher und Listen von Benutzern werden durch [`Sortierte Sammlung`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection) repräsentiert
+
+#### Objekte
+
+- `Regal`: Buchsammlung eines Benutzers. Standardmäßig hat jeder Benutzer ein `zu lesen`, `liest`, und `gelesen` Regal, die verwendet werden, um den Lesefortschritt zu verfolgen.
+- `Liste`: Eine Sammlung von Büchern, die möglicherweise von anderen Benutzern als derjenige, der die Liste erstellt hat, beigetragen haben.
+
+#### Aktivitäten
+
+- `Erstellen`: Fügt der Datenbank ein Regal oder eine Liste hinzu.
+- `Löschen`: Entfernt ein Regal oder eine Liste.
+- `Hinzufügen`: Fügt ein Buch zu einem Regal oder einer Liste hinzu.
+- `Entfernen`: Entfernt ein Buch aus einem Regal oder einer Liste.
+
+
+## Alternative Serialisierung
+Weil BookWyrm eigene Objekttypen (`Rezension`, `Kommentar`, `Zitat`) benutzt, die nicht von ActivityPub unterstützt werden, werden Status in Standardtypen umgewandelt, wenn sie an nicht-BookWyrm-Dienste gesendet oder angezeigt werden. `Rezension`en werden in `Artikel` umgewandelt und `Kommentar`s und `Zitat`s werden in `Notiz`s konvertiert mit einem Link auf das Buch und das Titelbild wird angehängt.
diff --git a/locale/de_DE/content/codebase/permissions.md b/locale/de_DE/content/codebase/permissions.md
new file mode 100644
index 00000000..d1581c3b
--- /dev/null
+++ b/locale/de_DE/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Berechtigungen Date: 2021-04-18 Order: 2
+- - -
+
+Der Benutzerzugriff auf verschiedene Funktionen wird über das [integrierte Authentifizierungssystem von Django](https://docs.djangoproject.com/en/3.2/topics/auth/default/) gesteuert. Wenn eine Instanz erstellt wird, erstellt das `initdb`-Skript eine Reihe von Berechtigungen, die auf Gruppen übertragen werden. Standardmäßig wird allen neuen Benutzern die `-Editor-Gruppe` zugewiesen, die es ihnen erlaubt, Buch-Metadaten zu bearbeiten.
+
+Der Instanzadministrator sollte `Superuser` Status haben, was Zugriff auf Django Admin (`/admin`) gibt und diesem Benutzer alle Berechtigungen überträgt.
+
+## Berechtigungen und Gruppen
+Diese Tabelle zeigt die vier Gruppen (Administrator, Moderator, Editor und Benutzer) und welche Berechtigungen Benutzer in dieser Gruppe haben:
+
+|                                 | Administrator | Moderator | Editor | Benutzer |
+| ------------------------------- | ------------- | --------- | ------ | -------- |
+| Instanzeinstellungen bearbeiten | ✔️            | -         | -      | -        |
+| ändere Benutzerlevel            | ✔️            | -         | -      | -        |
+| verwalte Föderation             | ✔️            | ✔️        | -      | -        |
+| sende Einladungen               | ✔️            | ✔️        | -      | -        |
+| deaktiviere Benutzer            | ✔️            | ✔️        | -      | -        |
+| entferne Beiträge               | ✔️            | ✔️        | -      | -        |
+| bearbeite Bücher                | ✔️            | ✔️        | ✔️     | -        |
+ lade Titelbilder hoch | ✔️ | ✔️ | ✔️ | ✔️
diff --git a/locale/de_DE/content/contributing/contributing.md b/locale/de_DE/content/contributing/contributing.md
new file mode 100644
index 00000000..866146ae
--- /dev/null
+++ b/locale/de_DE/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: Wie mitmachen Date: 2021-04-12 Order: 1
+- - -
+
+Es gibt viele Möglichkeiten, wie du zu diesem Projekt beitragen kannst, unabhängig von deinem technischen Know-how.
+
+## Rückmeldungen oder Funktionswünsche
+Bitte fühle dich willkommen Fehler, Vorschläge, Funktionsanfragen und Ideen, wie die Dinge funktionieren sollten, mittels [GitHub Issues](https://github.com/bookwyrm-social/bookwyrm/issues) zu äußern.
+
+## Codebeiträge
+Codebeiträge sind herzlich willkommen! Wenn du nicht weißt, wo du anfangen sollst, schau dir das ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)-Tag an. Da BookWyrm ein kleines Projekt ist, gibt es nicht viel formale Struktur, aber es gibt eine enorme Kapazität für eins-zu-eins Unterstützung, die aussehen kann wie Fragen zu stellen, Paar-Programmierung, Video-Chats, etc., darum fühle dich frei, dich zu melden.
+
+Wenn du Fragen zum Projekt oder zum Beitragen hast, kannst du dem [BookWyrm Matrix Chat](https://app.element.io/#/room/#bookwyrm:matrix.org) beitreten.
+
+## Übersetzung
+Sprichst du neben Englisch weitere Sprachen? BookWyrm benötigt Übersetzungen! Du kannst Übersetzungen hinzufügen und bearbeiten unter [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Finanzielle Hilfe
+BookWyrm ist ein werbefreies, leidenschaftliches Projekt, das keine Absicht hat, nach Risikokapital oder Unternehmensfinanzierungen zu suchen. Wenn du helfen willst, das Projekt am Laufen zu halten, kannst du ein nachhaltiger Mitwirkender über [Patreon](https://www.patreon.com/bookwyrm) oder [OpenCollective](https://opencollective.com/bookwyrm)werden oder ein einmaliges Geschenk über [PayPal](https://paypal.me/oulipo) machen.
diff --git a/locale/de_DE/content/contributing/debug_toolbar.md b/locale/de_DE/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..78cfa4c7
--- /dev/null
+++ b/locale/de_DE/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug-Symbolleiste Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm hat einen Branch, der konfiguriert ist, um die [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/) auszuführen. Dieser Branch wird niemals in `main` zusammengeführt und hat ein paar Optimierungen, die ihn mit der Symbolleiste funktionieren lassen, aber unsicher ist in allem, was einer Produktionsumgebung ähnelt. Um diesen Branch zu verwenden, musst du einige Schritte durchführen, um ihn zum Laufen zu bringen.
+
+## Einrichtung
+
+- Mit Git den [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar)-Branch auschecken
+- Aktualisiere den Branch relativ zum `main` mit `git merge main`. Der Branch wird periodisch aktualisiert, aber wird wahrscheinlich hinterher sein.
+- Erstelle die Docker-Images mit `docker-compose up --build` neu, um sicherzustellen, dass die Debug-Toolbar-Bibliothek von `requirements.txt` installiert ist
+- Greife direkt auf das Applikations-`web`-Image (anstatt durch `nginx`) mittel des Ports `8000` zu
diff --git a/locale/de_DE/content/contributing/install-dev.md b/locale/de_DE/content/contributing/install-dev.md
new file mode 100644
index 00000000..05ea514b
--- /dev/null
+++ b/locale/de_DE/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Entwicklungsumgebung Date: 2021-04-12 Order: 3
+- - -
+
+## Voraussetzungen
+
+Diese Anweisungen gehen davon aus, dass du BookWyrm mit Docker entwickelst. Du musst [Docker](https://docs.docker.com/engine/install/) und [docker-compose](https://docs.docker.com/compose/install/) installieren, um loszulegen.
+
+## Entwicklungsumgebung einrichten
+
+- Kopiere die [der BookWyrm-Codebasis von GitHub](https://github.com/bookwyrm-social/bookwyrm). Du kannst [einen Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) des Projekts erstellen und [verwende dann `git clone`, um den Code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) auf deinen Computer herunterzuladen.
+- Gehe in das Verzeichnis, das den Code auf Ihrem Computer enthält. Du arbeitest von hier aus.
+- Richte deine Datei für Entwicklungsumgebungsvariablen durch Kopieren der Beispielumgebungsdatei (`.env.example`) in eine neue Datei namens `.env` ein. In der Kommandozeile kannst du das wie folgt tun:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`ändere `DEBUG` zu `true`
+- Optional kannst du einen Dienst wie [ngrok](https://ngrok.com/) verwenden, um eine Domain einzurichten und setze die `DOMAIN`-Variable in Ihrer `.env`-Datei auf den von ngrok-generierten Domainnamen.
+
+- Richte nginx für die Entwicklung ein, indem du die Entwicklerkonfigurationsdatei für nginx (`nginx/development`) in eine neue Datei mit dem Namen `nginx/default.conf` kopierst:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Starte die Applikation. Führe Folgendes über die Kommandozeile aus:
+``` { .sh }
+./bw-dev build            # Baut die Docker-Images
+./bw-dev setup            # Initialisiert die Datenbank und führt die Migrationen aus
+./bw-dev up               # Start die Docker-Container
+```
+- Sobald die Erstellung abgeschlossen ist, kannst du auf die Instanz unter `http://localhost:1333` zugreifen und einen Admin erstellen.
+
+Wenn du neugierig bist: das `./bw-dev` Kommando ist ein simples Shell-Script, das verschiedene Tools ansteuert: darüber hinaus könntest du es überspringen und direk `docker-compose build` oder `docker-compose up` laufen lassen, wenn du magst. `./bw-dev` sammelt sie einfach an einem gemeinsamen Ort zur Bequemlichkeit. Führe es ohne Argumente aus, um eine Liste der verfügbaren Befehle zu erhalten, lese die [Dokumentationsseite](/command-line-tool.html) dafür oder öffne es und schaue dich um, um genau zu sehen, was jeder Befehl tut!
+
+### Modelle editieren oder erstellen
+
+Wenn du ein Modell änderst oder erstellst, wird sich wahrscheinlich die Datenbankstruktur ändern. Damit diese Änderungen wirksam werden, musst du Djangos `makemigrations`-Befehl ausführen, um eine neue [Django Migrationsdatei](https://docs.djangoproject.com/en/3.2/topics/migrations)zu erstellen und dann diese `migrieren`:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Statische Dateien editieren
+Jedes Mal, wenn du CSS oder JavaScript bearbeitest, musst du Djangos `collectstatic`-Befehl erneut ausführen, damit deine Änderungen wirksam werden:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+Wenn du [yarn installierstt](https://yarnpkg.com/getting-started/install) haben, kannst du `yarn watch:static` ausführen, um das vorherige Skript bei jeder Änderung automatisch im Verzeichnis `bookwyrm/static` auszuführen.
diff --git a/locale/de_DE/content/contributing/style_guide.md b/locale/de_DE/content/contributing/style_guide.md
new file mode 100644
index 00000000..6342b4bb
--- /dev/null
+++ b/locale/de_DE/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Stilleitfaden Date: 2021-10-20 Order: 4
+- - -
+
+## Pull Requests
+
+Du möchstest also Code zu BookWyrm hinzufügen: Das ist klasse! Wenn es ein offenes Problem gibt, dass du beheben möchtest, ist es hilfreich, das Problem zu kommentieren, damit die Arbeit nicht dupliziert wird. Versuche den Umfang von Pull Requests kleinzuhalten und konzentriere dich auf ein einzelnes Thema. Auf diese Weise ist es einfacher zu überprüfen und wenn ein Teil Änderungen braucht, wird er die anderen Teile nicht aufhalten.
+
+Wenn du nicht weißt, wie man etwas fixt oder etwas nicht schaffst: Kein Problem. Hinterlasse einen Kommentar im Pull Request und wir versuchen es, herauszufinden 💖.
+
+Pull-Anfragen müssen alle automatisierten Prüfungen bestehen, bevor sie übernommen werden können - dazu gehören Stil-Prüfungen, globale Linter, eine Sicherheitsprüfung und Unit-Tests.
+
+## Linten
+
+### Global
+
+Wir verwenden [EditorConfig](https://editorconfig.org), um konsistente Einrückungen und Zeilenenden zu erhalten.
+
+### Python
+
+BookWyrm verwendet den [Black](https://github.com/psf/black) Code-Formatierer, um die Python Codebasis konsistent zu gestalten. Alle neuen Pull-Requests werden mit GitHub-Aktionen überprüft und Sie können Code-Stilprobleme automatisch beheben, indem du `./bw-dev black` ausführst
+
+Code wird auch mit Pylint mittels GitHub-Aktionen überprüft. Pylint-Warnungen müssen bearbeitet werden, bevor Pull-Anfragen übernommen werden, aber es liegt im Ermessen, ob der Vorschlag verwendet werden oder die Warnung unterdrückt werden sollte. Um eine Warnung zu unterdrücken, füge einen Kommentar am Ende oder über der Zeile mit der Warnung hinzu: `# pylint: disable=Name-der-Warnung`
+
+### Vorlagen (HTML)
+
+Dein Pull-Request wird auch durch den [curlylint](https://www.curlylint.org)-Linter für Django-Templates überprüft.
+
+### CSS
+
+Wir verwenden [stylelint](https://stylelint.io), um alle CSS-Regeln zu überprüfen. Wie bei Pylint [kannst du styelint](https://stylelint.io/user-guide/ignore-code) für eine bestimmte Regel deaktivieren, aber du benötigst dafür eine gute Rechtfertigung.
+
+### JavaScript
+
+[ESLint](https://eslint.org) überprüft alle von Ihnen vorgenommenen JavaScript-Änderungen. Falls ESLint dein funktionierendes JavaScript nicht mag, überprüfe die Linter-Meldung auf das genaue Problem.
+
+## Inklusives Design
+
+Bookwyrm hat zum Ziel, so umfassend und zugänglich wie möglich zu sein.
+
+Überprüfen Sie die [Checkliste für inklusives Web Design](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) bevor du einen Pull-Reuqest erstellst. Für Barrierefreiheit ist [A11Y-101](https://www.a11y-101.com/development) ebenfalls eine nützliche Quelle. Weitere Informationen darüber, wie du deine Seitenvorlagen mehrsprachig erstellst, findest du im [Abschnitt Übersetzungen](/translations.html).
+
+Einige besondere Dinge, die Bookwyrm-Beitragende für nützlich erachtet haben, sind:
+
+### Formulare
+
+* Verwende nur `input[type="checkbox"]` oder `input[type="radio"]` in `<label>`
+* Wenn du die Checkboxen und die Radiobuttons nicht innerhalb des `<label>`platzierst, sollte das `<label>` _nach_ dem Element platziert werden, auf das es sich bezieht
+
+### Buttons und Links
+
+* Verwende ein `<button>` Element für alles, was existiert, um eine JavaScript-Aktion auszulösen (z.B. ein Formular verstecken oder enthüllen) oder eine `POST`-Anfrage senden (z.B. ein Formular übermitteln)
+* Verwende ein `<a>`-Element für alles, was eine `GET`-Anfrage auslöst. Normalerweise sollte ein Ankerelement (`<a>`) nicht als Button (`class="button"`) dargestellt werden, obwohl es einige Ausnahmen gibt, wie z. B. "Abbrechen"-Buttons. Falls Sie Zweifel haben, fragen Sie in Ihrer Pull-Anfrage um Rat
diff --git a/locale/de_DE/content/contributing/translation.md b/locale/de_DE/content/contributing/translation.md
new file mode 100644
index 00000000..7f853e6b
--- /dev/null
+++ b/locale/de_DE/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Übersetzungen Date: 2021-10-20 Order: 2
+- - -
+
+## Zu Übersetzungen beitragen
+
+Du kannst dem BookWyrm Übersetzungsprojekt unter [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/) beitreten.
+
+## Geschlechtsneutrale Sprache
+
+Wo immer möglich, sollten BookWyrm Übersetzungen geschlechtsneutrale Sprache verwenden. Dies gilt auch dann, wenn eine Sprache als neutrales Geschlecht voreingestellt ist oder wenn sie etwas Ähnliches wie "he/she" verwendet. Es ist auch wichtig, dass Übersetzungen klar, präzise und lesbar für einen Screenreader sind und manchmal stehen diese Ziele im Widerspruch zueinander; es gibt nicht die eine perfekte Lösung und diese hängt von der Sprache ab.
+
+Als Leitfaden versuche, einen höheren Wert auf inklusive und geschlechtsneutrale Sprache zu legen als auf formale Korrektheit oder offiziell anerkannte Stilführer. Im Englischen zum Beispiel benötigen viele formale Leitfäden ein einzelnes "she"- oder "he"-Pronomen, um für eine Person verwendet zu werden, aber es wäre besser, in BookWyrm das geschlechtsneutrale singuläre "they" zu verwenden.
+
+Wenn du nicht sicher bist, wie du am besten an ein Übersetzungsproblem herangehen kannst, kommentiere die Übersetzung oder öffne ein [-Diskussionsthema](https://translate.joinbookwyrm.com/project/bookwyrm/discussions), um weitergehende Fragen zu stellen.
+
+## Vorlagen übersetzbar machen
+
+Bookwyrm nutzt die Django-Übersetzungsfunktionalität, um den Seiteninhalt je nach der von den Benutzer*innen gewählten Anzeigesprache ändern zu können. Die Django-Dokumentation [bietet hilfreiche Erklärungen](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) wie das funktioniert, aber hier ist eine Kurzversion:
+
+* alle Template-Texte sollten Übersetzungstexte enthalten
+* füge `{% load i18n %}` oben an deiner Vorlage hinzu, um Übersetzungen zu aktivieren
+* Wenn der Textblock wörtlicher Text ist, kannst du das Template-Tag `{% trans %}` verwenden
+* Wenn der Textblock Variablen enthält, solltest du das Template-Tag-Paar `{% blocktrans %}` und `{% endblocktrans %}` verwenden. Wenn du Leerzeichen oder Zeilenumbrüche einbaust, nutze `gekürzt`, um es automatisch zu entfernen, wenn die Sprachdatei generiert wird: `{% blocktrans trimmed %}`
+
+### Beispiele
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    hinzugefügt von <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/de_DE/content/index.md b/locale/de_DE/content/index.md
new file mode 100644
index 00000000..12cd638c
--- /dev/null
+++ b/locale/de_DE/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Willkommen Date: 2021-04-13
+- - -
+
+BookWyrm ist ein soziales Netzwerk, um deinen Lesefortschritt zu verfolgen, über Bücher zu sprechen, Rezensionen zu schreiben und Neues zu entdecken. Föderation ermöglicht es BookWyrm-Benutzer*innen, kleinen, vertrauenswürdigen Communities beizutreten, die sich untereinander und mit anderen ActivityPub-Diensten wie Mastodon und Pleroma verbinden können.
+
+## Funktionen
+Da sich das Projekt noch in den Anfangsphasen befindet, wachsen die Funktionen jeden Tag und es gibt viel Raum für Anregungen und Ideen. Öffne ein [Ticket](https://github.com/bookwyrm-social/bookwyrm/issues), um die Unterhaltung in Gang zu bringen!
+
+- Über Bücher schreiben
+    - Rezensionen mit oder ohne Bewertungen erstellen, die in der Buchseite zusammengefasst werden
+    - Verfasse andere Arten von Status zu Büchern, z. B.:
+        - Kommentare zu einem Buch
+        - Zitate oder Auszüge
+    - Auf Status antworten
+    - Gesamte Rezensionen eines Buches über verbundene BookWyrm-Instanzen ansehen
+    - Unterscheide lokale und föderierte Rezensionen und Bewertungen in deinem Aktivitätsfeed
+- Leseaktivität verfolgen
+    - Bücher in die Standardregale "Zu Lesen", "Aktuell Lesend" und "Gelesen" einsortieren
+    - Erstelle eigene Regale
+    - Speichere Lesestart/Leseende Daten sowie Fortschrittsaktualisierungen während des Lesens
+    - Aktualisiere Follower über Leseaktivitäten (optional mit granularen Privatsphäreeinstellungen)
+    - Erstelle Listen von Büchern, die offen für Einreichungen von jedem, zusammengestellt, oder nur vom Ersteller bearbeitet werden können
+- Föderation mit ActivityPub
+    - Übertrage und empfange Status von Nutzer*innen und ihre Aktivität
+    - Teile Buchdaten zwischen Instanzen, um eine vernetzte Datenbank mit Metadaten zu erstellen
+    - Identifiziere freigegebene Bücher über Instanzen hinweg und aggregiere verwandte Inhalte
+    - Folge und interagiere mit Nutzer*innen aus mehreren BookWyrm-Instanzen
+    - Arbeite mit nicht-BookWyrm-ActivityPub-Diensten (derzeit wird Mastodon unterstützt) zusammen
+- Granulare Privatsphäreeinstellungen
+    - Privat, nur Follower und öffentliches Privatsphärelevel für Beiträge, Regale und Listen
+    - Option für die manuelle Genehmigung von Followern
+    - Blockieren und Markieren für Moderation erlauben
diff --git a/locale/de_DE/content/pages/index.md b/locale/de_DE/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/de_DE/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/de_DE/content/running_bookwyrm/cli.md b/locale/de_DE/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..c9330b1c
--- /dev/null
+++ b/locale/de_DE/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Befehlszeilenwerkzeug Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm-Entwickler und Instanz-Manager können das `bw-dev`-Skript für gemeinsame Aufgaben verwenden. Dies macht deine Befehle kürzer, leichter zu merken und schwieriger durcheinander zu bringen.
+
+Sobald du Bookwyrm [in Produktion](installing-in-production.html) oder [in Entwicklung](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment)installiert hast, kannst du das Skript von der Kommandozeile aus mit `./bw-dev` ausführen, gefolgt von dem Unterbefehl, den du ausführen willst.
+
+## Docker Kurzbefehle
+
+### bash
+
+Öffne eine interaktive `bash`-Sitzung im Docker-`Web`-Container.
+
+### build
+
+Äquivalent zu `docker-compose build`.
+
+### dbshell
+
+Öffnen Sie eine interaktive Postgres-Datenbank-Shell. Ich hoffe, du weißst, was du tust.
+
+### runweb args
+
+Führe einen beliebigen Befehl (oben durch `args` repräsentiert) im `web`-Container aus.
+
+Äquivalent zu `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Führe einen beliebigen Befehl im `Web`-Container (oben dargestellt durch `args`) mit exponierten Ports aus. Dies ist nützlich, wenn du `pdb`-Tests ausführen möchtest, da `runweb` nicht die `pdb`-Prompt freigibt.
+
+Äquivalent zu `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Öffne eine interaktive Django-Shell im Docker-`Web`-Container. Du würdest das verwenden, wenn du Django Shell-Befehle direkt ausführen möchtest.
+
+### up [args]
+
+Docker-Container starten oder neustarten, optional inklusive aller Argumente (oben dargestellt durch `args`). Äquivalent zu `docker-compose up --build [args]`
+
+## Datenbank verwalten
+
+### initdb
+
+Eine Datenbank initialisieren.
+
+### makemigrations [appname migration number]
+
+_Dieser Befehl ist nicht verfügbar im `Produktion`szweig_.
+
+Führt Djangos `makemigrations`-Befehl im Docker-Container aus. Wenn du die Datenbankstruktur in einem Entwicklungszweig geändert hast, musst du dies ausführen, damit deine Änderungen wirksam werden. Optional kannst du eine bestimmte Migration angeben, z.B. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Führt Djangos `migrate`-Kommando im Docker-Container aus. Du musst dies immer nach `makemigrations` ausführen.
+
+### resetdb
+
+_Dieser Befehl ist nicht verfügbar im `Produktion`szweig_.
+
+Setzt die Datenbank zurück. **Dieser Befehl löscht deine gesamte Bookwyrm-Datenbank**und initiiert dann eine neue Datenbank und führt alle Migrationen aus. Du solltest alle aktuellen Migrationsdateien löschen, die du nicht ausführen möchtest, _bevor_ das `resetdb` ausgeführt wird.
+
+## Eine Bookwyrm-Instanz verwalten
+
+### compile_themes
+
+Kompiliert alle BookWyrm Themes, die `*.scss` Dateien sind, die in `bookwyrm/static/css/themes aufgelistet sind`.
+
+### collectstatic
+
+Migrier statische Assets in einen Docker-Container oder in einen S3-kompatiblen "Bucket", abhängig vom Kontext.
+
+### generate_preview_images
+
+Erzeugen von Vorschaubildern für Webseiten, Benutzer und Bücher. Es kann eine Weile dauern, wenn du viele Bücher hast. Siehe auch [Optionale Funktionen: Generiere Vorschaubilder](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Entferne für entfernte Benutzer generierte Vorschaubilder. Siehe [Optionale Funktionen: Vorschaubilder für entfernte Accounts entfernen](/optional_features.html)
+
+### generate_thumbnails
+
+Generiert Vorschaubilder für Bücher.
+
+### populate_streams args
+
+Redis-Streams (Benutzer-Feeds) werden wieder aufgebaut. Normalerweise giibt es keinen Grund diesen Befehl auszuführen, außer es gibt einen Fehler, der die Feeds deiner Benutzer*innen aus irgendeinem Grund löscht. Du kannst den entsprechenden Feed mit dem `--stream` Argument angeben.
+
+### populate_list_streams
+
+Redis-Cache der Listen wieder auffüllen. Du musst das normalerweise nicht ausführen, es sei denn, es gibt einen Fehler, der die Listen deiner Benutzer*innen aus irgendeinem Grund löscht.
+
+### populate_suggestions
+
+Empfohlene Benutzer*innen für alle anzeigen. Möglicherweise möchten Sie dies manuell ausführen, um Vorschläge zu aktualisieren.
+
+### restart_celery
+
+Startet den `celery_worker`-Docker-Container neu.
+
+### update
+
+Wenn es Änderungen im `-Produktions`-Zweig gibt, kannst Du Deine Instanz ohne Ausfallzeit aktualisieren.
+
+Dieser Befehl verwendet `git pull` um die neusten Aktualisierungen aus dem `production`-Zweig herunterzuladen, baut Docker-Images falls nötig, führt Django-Migrationen aus, aktualisiert statische Dateien und startet alle Docker-Container neu.
+
+### admin_code
+
+Ruft den geheimen Admin-Code ab, der verwendet wird, um den initalen Admin-Benutzer in einer neuen BookWyrm-Instanz zu registrieren.
+
+## S3 kompatiblen Speicher einrichten
+
+Standardmäßig verwendet BookWyrm lokalen Speicher für statische Assets (Favicon, Standard-Avatar, etc.) und Medien (Benutzer-Avatare, Buchtitelbilder usw.), aber du kannst einen externen Speicherdienst verwenden, um diese Dateien zu bereitzustellen. BookWyrm verwendet django-storages, um externen Speicher wie S3-kompatible Dienste, Apache Libcloud oder SFTP anzubinden.
+
+Siehe [Externer Speicher](/external-storage.html) für weitere Informationen.
+
+### copy_media_to_s3
+
+Migriere alle hochgeladenen Medien von einer bestehenden BookWyrm Installation in einen S3-kompatiblen "Bucket". Verwende dies für den initialen Upload in einen leeren Bucket.
+
+### sync_media_to_s3
+
+Synchronisiere neue oder geänderte Medien von einer existierenden Bookwrym-Installation zu einem S3-kompatiblen "Bucket". Verwende diesen Befehl, um sicherzustellen, dass alle lokalen Dateien in einen existierenden Bucket hochgeladen werden.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Entwicklung und Test
+
+Diese Befehle sind zurzeit noch nicht im `production`-Zweig verfügbar.
+
+### black
+
+BookWyrm verwendet den [Black](https://github.com/psf/black) Code-Formatierer, um die Python Codebasis konsistent zu gestalten. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Äquivalent zu:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Erstellt Nachrichtendateien für alle Übersetzungstexte. After you have run `makemessages` you need to run `compilemessages` to compile the translations. Siehe [Djangos makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/de_DE/content/running_bookwyrm/external-storage.md b/locale/de_DE/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..849a8fc9
--- /dev/null
+++ b/locale/de_DE/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: Externer Speicher Date: 2021-06-07 Order: 7
+- - -
+
+Standardmäßig verwendet BookWyrm lokalen Speicher für statische Assets (Favicon, Standard-Avatar, etc.) und Medien (Benutzer-Avatare, Buchtitelbilder usw.), aber Sie können einen externen Speicherdienst verwenden, um diese Dateien zu bereitzustellen. BookWyrm verwendet `django-storages`, um externen Speicher wie S3-kompatible Dienste, Apache Libcloud oder SFTP anzubinden.
+
+## S3-kompatibler Speicher
+
+### Einrichtung
+
+Erstellen Sie einen Bucket in Ihrem S3-kompatiblen Dienst der Wahl, zusammen mit einer Zugangsschlüssel-ID und einem geheimen Zugriffsschlüssel. Diese können selbst gehostet sein, wie [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) oder [MinIO](https://min.io/) (GNU AGPL v3.0) oder kommerziell ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+Diese Anleitung wurde mit Scaleway Object Storage getestet. Wenn Sie einen anderen Dienst verwenden, teilen Sie bitte Ihre Erfahrungen (insbesondere wenn Sie andere Schritte unternehmen mussten), indem Sie einen Problembericht im [BookWyrm Dokumentations](https://github.com/bookwyrm-social/documentation)-Repository einreichen.
+
+### Was erwartet dich
+
+Wenn du eine neue BookWyrm-Instanz startest, wird der Prozess sein:
+
+- Richte deinen externen Speicherservice ein
+- Aktiviere externen Speicher auf BookWyrm
+- Starte deine BookWyrm-Instanz
+- Instanz Konnektor aktualisieren
+
+Wenn du deine Instanz bereits gestartet hast und Bilder auf den lokalen Speicher hochgeladen wurden, wird der Prozess sein:
+
+- Richte den externen Speicherdienst ein
+- Kopiere die lokalen Medien auf externen Speicher
+- Aktiviere externen Speicher auf BookWyrm
+- Starte die BookWyrm-Instanz neu
+- Instanz-Konnektor aktualisieren
+
+### BookWyrm-Einstellungen
+
+Bearbeite die `.env`-Datei, indem du die folgenden Zeilen auskommentierst:
+
+- `AWS_ACCESS_KEY_ID`: Ihre Zugangsschlüssel-ID
+- `AWS_SECRET_ACCESS_KEY`: Ihr geheimer Zugangsschlüssel
+- `AWS_STORAGE_BUCKET_NAME`: Ihr Bucket Name
+- `AWS_S3_REGION_NAME`: z.B. `"eu-west-1"` für AWS, `"fr-par"` für Scaleway oder `"nyc3"` für Digital Ocean
+
+Wenn dein S3-kompatibler Dienst Amazon AWS ist, solltest du startklar sein. Wenn nicht, musst du folgende Zeilen wieder kommentieren:
+
+- `AWS_S3_CUSTOM_DOMAIN`: die Domain, die die Assets bereitstellen soll, z.B. `"example-bucket-name.s3.fr-par.scw.cloud"` oder `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: der S3-API-Endpunkt, z.B. `"https://s3.fr-par.scw.cloud"` oder `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Kopieren lokaler Medien auf externen Speicher
+
+Wenn die BookWyrm-Instanz bereits läuft und Medien hochgeladen wurden (Benutzer-Avatare, Buchtitelbilder…), musst du hochgeladene Medien in deinen Bucket migrieren.
+
+Diese Aufgabe wird mit dem Befehl erledigt:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Aktivierung des externen Speichers für BookWyrm
+
+Um den S3-kompatiblen externen Speicher zu aktivieren, müssen Sie Ihre `.env`-Datei bearbeiten, indem der Eigenschaftswert für `USE_S3` von `false` zu `true` geändert wird:
+
+```
+USE_S3=true
+```
+
+Wenn der externe Speicher über HTTPS ausgeliefert wird (was die meisten dieser Tage sind), musst du auch sicherstellen, dass `USE_HTTPS` auf `true gesetzt ist`, damit Bilder über HTTPS geladen werden:
+
+```
+USE_HTTPS=true
+```
+
+#### Statische Assets
+
+Danach musst du folgenden Befehl ausführen, um die statischen Assets in deinen S3-Bucket zu kopieren:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS-Einstellungen
+
+Sobald die statischen Assets gesammelt sind, musst du Sie CORS für deinen Bucket einrichten.
+
+Einige Dienste wie Digital Ocean bieten eine Schnittstelle, um es einzurichten, siehe [Digital Ocean doc: Wie man CORS konfiguriert](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+Wenn dein Dienst keine Schnittstelle zur Verfügung stellt, kannst du CORS trotzdem mit der Befehlszeile einrichten.
+
+Erstelle eine Datei namens `cors.json` mit folgendem Inhalt:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Ersetzen Sie `MY_DOMAIN_NAME` durch den/die Domainname(n) Ihrer Instanz.
+
+Führe dann den folgenden Befehl aus:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+Keine Ausgabe bedeutet, dass es gut sein sollte.
+
+Wenn du eine neue BookWyrm-Instanz startest, kannst du sofort zu den Installationsanweisungen zurückkehren. Wenn nicht, lese weiter.
+
+### Starte deine Instanz neu
+
+Sobald die Medienmigration abgeschlossen und die statischen Assets gesammelt wurden, kannst du die neue `.env`-Konfiguration laden und die Instanz neustarten mit:
+
+```bash
+./bw-dev up -d
+```
+
+Wenn alles gut geht, wurde dein Speicher ohne Serverausfall geändert. Wenn einige Schriftarten fehlen (und die Browser-JS-Konsole mit Warnung über CORS aufwartet), schlug etwas [hier](#cors-settings) fehl. In diesem Fall kann es gut sein, die Header einer HTTP-Anfrage auf eine Datei in deinem Bucket zu überprüfen:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Ersetze `MY_DOMAIN_NAME` durch deinen Domain-Namen, `BUCKET_URL` mit der URL für deinen Bucket, du kannst den Dateipfad durch jeden anderen gültigen Pfad in deinem Bucket ersetzen.
+
+Wenn du eine Nachricht siehst, insbesondere eine Nachricht, die mit `<Error><Code>CORSForbidden</Code>` beginnt, funktionierte sie nicht. Wenn du keine Nachricht siehst, funktioniert es.
+
+Für eine aktive Instanz kann es eine Handvoll Dateien geben, die während der Zeit zwischen der Migration der Dateien auf den externen Speicher lokal erstellt wurden und ein Neustarten der App nutzt den externen Speicher. Um sicherzustellen, dass alle noch verbleibenden Dateien nach dem Umschalten auf den externen Speicher hochgeladen werden, kannst du folgenden Befehl verwenden, der nur Dateien hochlädt, die nicht bereits im externen Speicher vorhanden sind:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Instanz-Konnektor aktualisieren
+
+*Hinweis: Du kannst diesen Schritt überspringen, wenn du eine aktualisierte Version von BookWyrm verwendest; im September 2021 wurde der "Selbst-Steckverbinder" in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413) entfernt*
+
+Damit die richtige URL für die Anzeige lokaler Buchsuchergebnisse verwendet wird, müssen wir den Wert für die URL-Basis der Titelbilder ändern.
+
+Konnektor-Daten können über die Django-Admin-Schnittstelle unter der URL `http://MY_DOMAIN_NAME/admin` aufgerufen werden. Der Konnektor für deine eigene Instanz ist der erste Datensatz in der Datenbank, damit du auf den Konnektor mit dieser URL zugreifen kannst: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+Das Feld _Covers url_ ist standardmäßig als `https://MY_DOMAIN_NAME/images`definiert, Sie müssen es auf `https://S3_STORAGE_URL/images` ändern. Klicke auf _Speichern_ und voilà!
+
+Du musst den Wert für die _Covers Url_ jedes Mal aktualisieren, wenn du die URL für deinen Speicher änderst.
diff --git a/locale/de_DE/content/running_bookwyrm/install-prod-dockerless.md b/locale/de_DE/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..23a461cc
--- /dev/null
+++ b/locale/de_DE/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installation ohne Docker
+Date: 2022-10-02
+Order: 2
+---
+
+Dieses Projekt ist noch jung und, im Moment, nicht sehr stabil. Bitte verwende es nur mit Vorsicht in Produktion. Diese Methode der Installation benötigt mehr Können und ist daher für erfahrene Administrator*innen. Docker Installation wird empfohlen Diese Installationsmethode geht davon aus, dass du bereits SSL mit verfügbaren Zertifikaten konfiguriert hast
+
+## Servereinrichtung
+- Hole dir eine Domain und konfiguriere DNS für deinen Server. Du musst die Nameserver Deiner Domain bei Deinem DNS-Provider auf den Server verweisen, auf dem du BookWyrm betreibst. Hier sind Anweisungen für [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Setze Deiner Server mit geeigneter Firewall für den Betrieb einer Web-Anwendung auf (dieser Befehlssatz ist mit Ubuntu 20.04 getestet). Hier ist eine Anleitung für [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Richte einen E-Mail-Dienst (wie [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) und die entsprechenden SMTP/DNS-Einstellungen ein. Benutze die Dokumentation des Dienstes für die Konfiguration deines DNS
+- Abhängigkeiten installieren. Auf Debian könnte das wie `apt install postgresql redis nginx python3-venv libpq-dev` aussehen.
+
+## BookWyrm installieren und konfigurieren
+
+Die `-Produktion` Zweig von BookWyrm enthält eine Reihe von Werkzeugen die nicht auf dem `Haupt-` -Zweig sind, die für den Betrieb in der Produktion geeignet sind zum Beispiel `docker-compose` Änderungen, um die Standardbefehle oder die Konfiguration von Containern zu aktualisieren und individuelle Änderungen an der Container-Konfiguration, um Dinge wie SSL oder regelmäßige Sicherungen zu aktivieren. Nicht alle diese Änderungen wirken sich auf die Installation ohne Docker aus, aber der `-production`-Zweig wird immer noch empfohlen
+
+Anleitung für das Ausführen von BookWyrm in Produktion ohne Docker:
+
+- Erstelle und betrete das Verzeichnis, in das Du  BookWyrm installieren willst. Für das Beispiel: `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Hole den Quelltext: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Wechsel in den `production`-zweig: `git checkout production`
+- Erstelle deine Umgebungsvariablendatei `cp .env.example .env` und aktualisiere Folgendes:
+    - `SECRET_KEY` | Eine schwer zu erratende geheime Zeichenfolge
+    - `DOMAIN` | Deine Web-Domain
+    - `POSTGRES_PASSWORD` | Setze ein sicheres Passwort für die Datenbank
+    - `POSTGRES_HOST` | Auf `localhost` (setzen die Maschine auf der Deine Datenbank läuft)
+    - `POSTGRES_USER` | Auf `bookwyrm` setzen (empfohlen) oder etwas Eigenes. (später konfiguriert)
+    - `POSTGRES_DB` | Auf `Bookwyrm` setzen
+    - `REDIS_ACTIVITY_PASSWORD` | Auf nichts setzen (auf einem lokalen Rechner mit einer Firewall)
+    - `REDIS_ACTIVITY_HOST` | Auf  `localhost` setzen (die Maschine, auf der  redis läuft)
+    - `REDIS_BROKER_PASSWORD` | Auf nichts setzen (auf einem lokalen Rechner mit einer Firewall)
+    - `REDIS_BROKER_HOST` | Auf  `localhost` setzen (die Maschine, auf der  redis läuft)
+    - `EMAIL_HOST_USER` | Die "von"-Adresse, die deine App beim Senden von E-Mails verwendet
+    - `EMAIL_HOST_PASSWORD` | Das Passwort von deinem E-Mail-Dienst
+- Nginx konfigurieren
+    - Kopiere die server_config nach nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Erstelle eine Kopie der Konfiguration der Produktionsvorlage und setze sie für die Verwendung in nginx `cp nginx/production nginx/bookwyrm.conf`
+    - Aktualisiere nginx `bookwyrm.conf`:
+        - Ersetze `your-domain.com` mit deinem Domainnamen überall in der Datei (inklusive der aktuell auskommentierten Zeilen)
+        - Ersetze in der Datei überall (inklusive der auskommentierten Zeilen) `/app/` mit deinem Installationsverzeichnis `/opt/bookwyrm/`
+        - Zeilen 18 bis 67 auskommentieren, um die Weiterleitung zu HTTPS zu ermöglichen. Du solltest zwei `Server`-Blöcke aktiviert haben
+        - Ändere die `ssl_certificate` und `ssl_certificate_key` Pfade an Ihre volle Kette und Privkey Positionen
+        - Ändere die Zeile 4 zu folgendem Inhalt: `server localhost:8000`. Du kannst hier einen anderen Port wählen, wenn du magst
+        - Wenn du einen anderen Webserver auf deinem Host-Rechner betreibst, musst du den [Reverse-Proxy-Anweisungen](/reverse-proxy.html) folgen
+    - Aktiviere die nginx-Konfigurationsdatei mit folgendem Befehl: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Lade Nginx neu: `systemctl reload nginx`
+- Einrichtung der virtuellen Python-Umgebung
+    - Erstelle den Python venv-Ordner in deinem Installationsverzeichnis: `mkdir venv` `python3 -m venv ./venv`
+    - Installiere die Python-Abhängigkeiten für Bookwyrm via pip mit folgendem Befehl: `./venv/bin/pip3 install -r requirements.txt`
+- Erstelle die Bookwyrm postgresql Datenbank. Ändere das Passwort zu dem, welches du in der `.env` Konfiguration gesetzt hast:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migriere das Datenbankschema, indem du `venv/bin/python3 manage.py migrate`
+- Initialisiere die Datenbank, indem du folgenden Befehl ausführst `venv/bin/python3 manage.py initdb`
+- Erstelle die Statische durch Ausführen von `venv/bin/python3 manage.py collectstatic --no-input`
+- Wenn du einen externen Speicher für statische Assets und Mediendateien verwenden möchtest (z. B. einen S3-kompatiblen Dienst), [befolge die Anweisungen](/external-storage.html) bis es dir mitteilt, wieder hierherzukommen
+- Erstelle und richte deinen `Bookwyrm` Account ein
+    - Erstelle den System-Bookwyrm-Account: `useradd bookwyrm -r`
+    - Ändere den Eigentümer deines Installationsverzeichnisses auf bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - Du solltest nun die Befehle welche mit Bookwyrm zu tun haben mit dem Bookwyrm-Benutzer ausführen:   `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Erstelle den Admin-Code mit `sudo -u bookwyrm venv/bin/python3 manage. y admin_code`, und kopieren Sie den Admin-Code, der beim Erstellen Ihres Admin-Kontos verwendet werden soll.
+- Du kannst deinen Code jederzeit erhalten, indem du diesen Befehl erneut ausführst. Hier ist eine Beispielausgabe:
+
+``` { .sh }
+*******************************************
+Verwende diesen Code um deinen Administratoraccount zu erstellen:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Erstelle und konfiguriere das Startskript
+    - Erstelle eine Datei mit dem Namen dockerless-run.sh und füge die folgenden Inhalte ein
+
+``` { .sh }
+#!/bin/bash
+
+# Stoppen falls ein Prozess fehlschlägt.
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Ersetze `/opt/bookwyrm` durch dein Installationsverzeichnis
+    - Ändere `8000` auf deine eigene Portnummer
+    - Flower wurde hier deaktiviert, da es nicht automatisch mit dem Passwort in der `.env` Datei konfiguriert ist
+- Du kannst nun BookWyrm mit folgendem Befehl ausführen: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- Die Anwendung sollte auf deiner Domain laufen. Wenn du die Domain lädst, siehst du eine Konfigurationsseite, die deine Instanzeinstellungen bestätigt und ein Formular zum Erstellen eines Administratorkontos. Benutze deinen Admin-Code um dich zu registrieren.
+- Möglicherweise möchtest du BookWyrm so konfigurieren, dass es mit einem System-Dienst automatisch ausgeführt wird. Hier ist ein Beispiel:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+Du musst einen Cron-Job einrichten, damit der Dienst beim Neustart automatisch starten kann.
+
+Glückwunsch! Du hast es geschafft!! Konfigure deine Instanz wie es dir gefällt.
+
+## Mitmachen
+
+Siehe [Mitmachen](https://joinbookwyrm.com/get-involved/) für Details.
diff --git a/locale/de_DE/content/running_bookwyrm/install-prod.md b/locale/de_DE/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..858f57dd
--- /dev/null
+++ b/locale/de_DE/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installation in Produktion Date: 2021-05-18 Order: 1
+- - -
+
+Dieses Projekt ist noch jung und im Moment nicht sehr stabil und deshalb solltest du bei der Verwendung in Produktion mit Vorsicht vorgehen.
+
+## Servereinrichtung
+- Hole einen Domänennamen und konfiguriere DNS für deinen Server. Du musst die Nameserver Ihrer Domain auf deinen DNS-Provider auf den Server verweisen, auf dem BookWyrm läuft. Hier sind Anweisungen für [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Setze den Server mit geeigneten Firewalls für den Betrieb einer Web-Anwendung auf (dieser Befehlssatz ist mit Ubuntu 20.04 getestet). Hier sind Anweisungen für [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Richte einen E-Mail-Dienst (wie [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) und die entsprechenden SMTP/DNS-Einstellungen ein. Benutze die Dokumentation des Dienstes für die Konfiguration des DNS
+- [Docker und docker-compose installieren](https://docs.docker.com/compose/install/)
+
+## BookWyrm installieren und konfigurieren
+
+Der `-Produktionszweig` von BookWyrm enthält eine Reihe von Werkzeugen die nicht auf dem `main`-Zweig sind, die für den Betrieb in der Produktion geeignet sind zum Beispiel `docker-compose`-Änderungen, um die Standardbefehle oder die Konfiguration von Containern zu aktualisieren und individuelle Änderungen an der Container-Konfiguration, um Dinge wie SSL oder regelmäßige Sicherungen zu aktivieren.
+
+Anleitung für das Ausführen von BookWyrm in der Produktion:
+
+- Hole den Code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Wechsel zum `Produktionszweig`: `git checkout production`
+- Erstelle deine Umgebungsvariablendatei `cp .env.example .env` und aktualisiere Folgendes:
+    - `SECRET_KEY` | Eine schwer zu erratende geheime Zeichenfolge
+    - `DOMAIN` | Deine Webdomain
+    - `EMAIL` | E-Mail-Adresse für die Verifizierung der certbot-Domain
+    - `POSTGRES_PASSWORD` | Setze sicheres Passwort für die Datenbank
+    - `REDIS_ACTIVITY_PASSWORD` | Setze ein sicheres Passwort für das Redis Activity Subsystem
+    - `REDIS_BROKER_PASSWORD` | Setze ein sicheres Passwort für das Redis Queue Broker Subsystem
+    - `FLOWER_USER` | Dein eigener Benutzername für den Zugriff auf den Flower Queue Monitor
+    - `FLOWER_PASSWORD` | Dein eigenes sicheres Passwort für den Zugriff auf Flower Queue Monitor
+    - `EMAIL_HOST_USER` | Die "von"-Adresse, die die App beim Senden von E-Mails verwendet
+    - `EMAIL_HOST_PASSWORD` | Das von deinem E-Mail-Dienst bereitgestellte Passwort
+- Nginx konfigurieren
+    - Erstelle eine Kopie der Konfiguration der Produktionsvorlage und setze sie für die Verwendung in nginx `cp nginx/production nginx/default.conf`
+    - Aktualisiere `nginx/default.conf`:
+        - Ersetze `your-domain.com` mit deinem Domain-Namen überall in der Datei (einschließlich der Zeilen, die derzeit auskommentiert sind)
+        - Wenn du die `www`-Subdomain nicht verwendest, entferne die www.your-domain.com-Version der Domain aus dem `server_name` im ersten Serverblock in `nginx/default.conf` und entferne das `-d www.${DOMAIN}`-Flag am Ende des Befehls `certbot` in `docker-compose.yml`.
+        - Wenn du einen anderen Webserver auf deinem Host-Rechner betreibst, musst du den [Reverse-Proxy-Anweisungen](/reverse-proxy.html) folgen
+- Initialisiere die Datenbank durch Ausführen von `./bw-dev migrate`
+- Führe die Anwendung aus (dies sollte auch ein Certbot-Ssl-Zertifikat für deine Domain einrichten) mit `docker-compose up --build` und stelle sicher, dass alle Images erfolgreich erstellt werden
+    - Wenn du andere Dienste auf deinem Host-Rechner betreibst, kannst du auf Fehler stoßen, dass Dienste fehlschlagen, wenn du versuchst, sich an einen Port zu binden. Siehe die [Fehlerbehebungsanleitung](#port_conflicts) für Hinweise dies zu beheben.
+- Wenn Docker erfolgreich gebaut wurde, stoppe den Prozess mit `STRG-C`
+- HTTPS-Weiterleitung einrichten
+    - In `docker-compose.yml` kommentiere den aktiven certbot-Befehl, der das Zertifikat installiert und entfernen die Kommentarzeile unten, die automatische Erneuerungen einstellt.
+    - In `nginx/default.conf`entferne die Kommentarzeilen 18 bis 50, um die Weiterleitung zu HTTPS zu aktivieren. Du solltest zwei `Server`-Blöcke aktiviert haben
+- Richte einen `cron`-Job ein, um deine Zertifikate aktuell zu halten (Lets Encrypt-Zertifikate laufen nach 90 Tagen ab)
+    - Gebe `crontab -e` ein, um die cron-Datei im Host zu bearbeiten
+    - fügen eine Zeile zum Erneuern einmal am Tag hinzu: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- Wenn du einen externen Speicher für statische Assets und Mediendateien verwenden möchtest (z. B. einen S3-kompatiblen Dienst), [befolge die Anweisungen](/external-storage.html) bis es dir mitteilt, wieder hierherzukommen
+- Initialisieren die Anwendung mit `./bw-dev setup` und kopiere den Admin-Code, der beim Erstellen deines Admin-Kontos verwendet werden soll.
+    - Die Ausgabe von `./bw-dev setup` sollte mit deinem Admin-Code abgeschlossen werden. Du kannst den Code jederzeit erhalten, indem du `./bw-dev admin_code` auf der Befehlszeile ausführst. Hier ist eine Beispielausgabe:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Starte Docker-Compose im Hintergrund mit: `docker-compose up -d`
+- Die Anwendung sollte auf deiner Domain laufen. Wenn du die Domain lädst, erhälst du eine Konfigurationsseite, die deine Instanzeinstellungen bestätigt und ein Formular zum Erstellen eines Administratorkontos. Benutze deinen Admin-Code, um dich zu registrieren.
+
+Glückwunsch! Du hast es geschafft!! Konfigurieren deine Instanz, wie du möchtest.
+
+
+## Sicherungskopien
+
+BookWyrms db Service speichert täglich um Mitternacht UTC eine Sicherungskopie seiner Datenbank in sein `/backups`-Verzeichnis. Sicherungen heißen `backup__%Y-%m-%d.sql`.
+
+Der Datenbankdienst hat ein optionales Skript zum periodischen Beschneiden des Backup-Verzeichnisses, so dass alle aktuellen täglichen Sicherungen beibehalten werden, aber für ältere Backups werden nur wöchentliche oder monatliche Backups aufbewahrt. Um dieses Skript zu aktivieren:
+
+- Kommentiere die letzte Zeile in `postgres-docker/cronfile` aus
+- baue deine Instanz erneut mit `docker-compose up --build`
+
+Du kannst mit `docker cp` Backups aus dem Backup-Volume auf deinen Host-Rechner kopieren:
+
+- Führe `docker-compose ps` aus, um den vollständigen Namen des Datenbankdienstes zu bestätigen (es ist wahrscheinlich `bookwyrm_db_1`.
+- Führe `docker cp <container_name>:/backups <host machine path>` aus
+
+## Port-Konflikte
+
+BookWyrm hat mehrere Dienste, die auf ihren Standard-Ports laufen. Dies bedeutet, dass, je nachdem, was auf deinem Host-Rechner läuft, können Sie auf Fehler beim Erstellen oder Ausführen von BookWyrm stoßen, wenn Versuche fehlschlagen, sich an diese Ports zu binden.
+
+Wenn dies geschieht, musst du deine Konfiguration ändern, um Dienste auf verschiedenen Ports auszuführen. Dies kann eine oder mehrere Änderungen der folgenden Dateien erfordern:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (Sie erstellen diese Datei selbst während des Setups)
+
+Wenn du bereits einen Webserver auf deinem Rechner betreibst, musst du einen Reverse-Proxy einrichten.
+
+## Verbinde dich
+
+Da BookWyrm ein junges Projekt ist, arbeiten wir noch immer an einem stabilen Veröffentlichungsplan und es gibt viele Fehler und große Änderungen. Es gibt ein GitHub Team, das markiert werden kann, wenn es etwas Wichtiges über ein Update gibt und dem du beitreten kannst, indem du deinen GitHub-Namen teilst. Es gibt einige Möglichkeiten, sich mit uns in Kontakt zu setzen:
+
+ - Öffne ein Issue oder einen Pull Request, um deine Instanz zur [offiziellen Liste](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md) hinzuzufügen
+ - Erreiche das Projekt auf [Mastodon](https://tech.lgbt/@bookwyrm) oder [maile den Betreuern](mailto:mousereeve@riseup.net) direkt deinen GitHub-Benutzernamen
+ - Trete dem [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) Chatraum bei
diff --git a/locale/de_DE/content/running_bookwyrm/moderation.md b/locale/de_DE/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..cb6bb0f0
--- /dev/null
+++ b/locale/de_DE/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocken
+Benutzer*innen haben die Möglichkeit, andere Benutzer*innen eigenständig zu sperren, ohne dass ein*e Moderator*in eingreift. In der "Föderierten Server"-Admin-Ansicht können Administratoren sehen, wie viele Benutze*innenr einer Instanz von lokalen Benutzer*innen blockiert wurden.
+
+## Meldungen
+Benutzer*innen können über das Menü "mehr Optionen" in der Fußzeile von Beiträgen und die Folgen-/Entfolgen-Buttons für Benutzer*innen melden. Wenn ein Bericht erstellt wird, erhalten alle Benutzer*innen mit Administratorrechten eine Benachrichtigung.
+
+Wenn ein Bericht erstellt wird, gibt es einige Optionen, wie der/die Moderator*in reagieren kann.
+- Sende eine Direktnachricht an der/die gemeldete*n Benutzer*in.
+- Den gemeldeten Status löschen.
+- Den Account deaktivieren. Für lokale Benutzer*innen wird dies dazu führen, dass sie sich nicht einloggen können und ihr Konto wird nicht in der Anwendung angezeigt. Für entfernte Benutzer*innen lehnt der Server eingehende Aktivitäten dieses Accounts ab und dieser Account wird bei der Suche nicht angezeigt.
+
+## Moderation auf Instanzebene
+Moderator*innen können ganze Instanzen blockieren. Dadurch wird verhindert, dass alle Aktivitäten, die aus dieser Instanz kommen, gemieden werden und alle Konten aus dieser Instanz lokal deaktiviert werden.
+
+Wenn die Instanz nicht blockiert ist, werden alle Benutzer*innen, die durch den Block deaktiviert wurden, wieder aktiviert.
+
+Moderator*innen können auch Blocklisten hochladen, um Server in großen Mengen zu blockieren.
diff --git a/locale/de_DE/content/running_bookwyrm/monitoring-queue.md b/locale/de_DE/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..53086e75
--- /dev/null
+++ b/locale/de_DE/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Überwachungswarteschlange
+Date: 2022-11-23
+Order: 6
+---
+
+Es kann passieren, dass deine Instanz langsam ist. Eine Option wäre die Warteschlange zu inspizieren, um zu sehen, ob einige Jobs hängen. Lies weiter, um zu erfahren, wie.
+
+## Celery
+
+BookWyrm verwendet [Celery](https://docs.celeryq.dev/en/stable/) um Hintergrundjobs zu verwalten.
+
+## Flower
+
+Um Celery-Jobs in Echtzeit zu sehen, verwendet BookWyrm [Flower](https://flower.readthedocs.io/en/latest/).
+
+Falls Du [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100)  nicht geändert hast, findest Du den Service auf [Port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). Das ist: `https://MY_DOMAIN_NAME:8888/`.
+
+### Aufgaben
+
+Du findest unter [`@app.task` kommentiert](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) Aufgaben in der Codebase.
diff --git a/locale/de_DE/content/running_bookwyrm/optional_features.md b/locale/de_DE/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..7d124c7f
--- /dev/null
+++ b/locale/de_DE/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optionale Funktionen Date: 2021-08-02 Order: 8
+- - -
+
+Einige Funktionen von BookWyrm müssen aktiviert werden, um zu funktionieren.
+
+## Vorschaubilderzeugung
+
+Standardmäßig verwendet BookWyrm das Logo der Instanz (oder das Standardlogo) als OpenGraph Vorschaubild. Alternativ kannst du die Erstellung von Vorschaubildern für Bücher, Benutzer und die Website aktivieren.
+
+Die Vorschaubilder werden für große OpenGraph Bilder vergrößert (verwendet von Twitter unter dem Namen `summary_large_image`). Abhängig von der Art des Bildes wird der Inhalt sein:
+
+- das Standardinstanzbild zeigt das große Logo an, zusammen mit dem Namen der Instanz und ihrer Url
+- Das Profilbild zeigt den Avatar und den Anzeigenamen an (in Form von name@instanz)
+- das Buchbild zeigt sein Titelbild, Titel, Untertitel (falls vorhanden), Autor und Bewertung (falls vorhanden) an
+
+Diese Bilder werden an verschiedenen Stellen aktualisiert:
+
+- Instanzbild: wenn der Instanzname oder das große Logo geändert werden
+- Profilbild: wenn der Anzeigename oder das Avatar geändert wird
+- Buchbild: wenn der Titel, Autor oder das Cover geändert oder wenn eine neue Bewertung hinzugefügt wird
+
+### Vorschaubilder aktivieren
+
+Um die Funktion mit den Standardeinstellungen zu aktivieren, Sie müssen die Zeile `ENABLE_PREVIEW_IMAGES=true` in Ihrer `.env` Datei auskommentieren (entfernen Sie das Zeichen `#` am Anfang). Alle neuen Aktualisierungstermine führen zur Erzeugung des entsprechenden Bildes.
+
+Beispiele für diese Bilder können in der [Beschreibung der Funktions-Pull-Anfrage](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink) angesehen werden.
+
+### Vorschaubilder erzeugen
+
+Wenn du diese Einstellung aktivierst, nachdem die Instanz gestartet wurde, wurden einige Bilder möglicherweise nicht generiert. Ein Befehl wurde hinzugefügt, um die Bildgenerierung zu automatisieren. Um eine Ressourcenüberlastung zu verhindern, wenn Sie **EINE MENGE** Bilder erzeugen, müssen Sie das Argument `--all` (oder `-a`) übergeben, um die Erzeugung der Vorschaubilder für alle Benutzer und Bücher zu starten. Ohne dieses Argument wird nur die Seitenvorschau generiert.
+
+Benutzer- und Buchvorschaubilder werden asynchron erzeugt: Die Aufgabe wird an Flower gesendet. Etwas Zeit kann benötigt werden, bevor alle Bücher und Benutzer*innen ein funktionierendes Vorschaubild haben. Wenn du ein gutes Buch 📖, ein Kätzchen 🐱 oder einen Kuchen 🍰 hast, ist dies der perfekte Zeitpunkt, um ihnen Aufmerksamkeit 💖 zu schenken.
+
+### Optionale Einstellungen
+
+Du möchstest deine Vorschaubilder anpassen? Hier sind die Optionen:
+
+- `PREVIEW_BG_COLOR` legt die Farbe für den Vorschauhintergrund fest. Du kannst einen Farbwert angeben, wie `#b00cc0` oder die folgenden Werte `use_dominant_color_light` oder `use_dominant_color_dark`. Diese extrahieren eine dominante Farbe aus dem Buchcover und verwenden es in einem hellen bzw. dunklen Thema.
+- `PREVIEW_TEXT_COLOR` legt die Farbe für den Text fest. Abhängig von der Auswahl für die Hintergrundfarbe solltest du einen Wert finden, der einen ausreichenden Kontrast hat, um das Bild zugänglich zu machen. Ein Kontrastverhältnis von 1:4.5 wird empfohlen.
+- `PREVIEW_IMG_WIDTH` und `PREVIEW_IMG_HEIGHT` werden die Dimensionen des Bildes einstellen. Momentan funktioniert das System am besten mit Bildern mit horizontaler Ausrichtung.
+- `PREVIEW_DEFAULT_COVER_COLOR` legt die Farbe für Bücher ohne Cover fest.
+
+Alle Farbvariablen akzeptieren Werte, die im Modul `ImageColor` von Pillow als Farben erkannt werden können: [Erfahren Sie mehr über Farben von Pillow](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Entferne Vorschaubilder für entfernte Accounts
+
+Vor Bookwyrmversion 0.5.4 wurden auch Vorschaubilder für entfernte Nutzer erstellt. Da es in Hinblick auf Speicherplatz und Rechenleistung verschwenderisch war, wurde diese Generation gestoppt. Wenn du alle Bilder löschen möchtest, die zuvor für entfernte Accounts erstellt wurden, wurde ein neuer Befehl hinzugefügt:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+Dieser Befehl wird die Eigenschaft `user.preview_image` in der Datenbank für entfernte Benutzer leeren und die entsprechenden Dateien löschen.
diff --git a/locale/de_DE/content/running_bookwyrm/reverse-proxy.md b/locale/de_DE/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..0e4c06b1
--- /dev/null
+++ b/locale/de_DE/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Verwenden eines Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## BookWyrm hinter einem Reverse-Proxy ausführen
+Wenn du einen anderen Webserver auf Ihrem Rechner betreibst, solltest du ihn als Proxy für Web-Anfragen an BookWyrm einrichten.
+
+Die Standardkonfiguration von BookWyrm hat bereits einen nginx-Server, der Anfragen an die Django-App weiterleitet, die SSL verarbeitet und statische Dateien direkt bedient. Die statischen Dateien werden in einem Docker Volume gespeichert, auf das mehrere BookWyrm Dienste zugreifen, daher wird es nicht empfohlen, diesen Server komplett zu entfernen.
+
+Um BookWyrm hinter einem Reverse-Proxy auszuführen, führe folgende Änderungen aus:
+
+- In `nginx/default.conf`:
+    - Kommentiere die zwei Standardserver aus
+    - Kommentiere den Server beschrift als Reverse-Proxy Server aus
+    - Ersetze `your-domain.com` durch deinen Domain-Namen
+- In `docker-compose.yml`:
+    - In `-services` -> `nginx` -> `ports`, kommentiere die Standard-Ports aus und füge `- 8001:8001` hinzu
+    - In `services` -> `nginx` -> `volumes` kommentiere die beiden Volumes aus, die mit `./certbot/` beginnen
+    - In `services` kommentiere den `certbot` Dienst aus
+
+An dieser Stelle folge den Anweisungen [Setup](#server-setup) wie aufgeführt. Sobald Docker läuft, kannst du auf deine BookWyrm-Instanz zugreifen unter `http://localhost:8001` (**HINWEIS:** Dein Server ist nicht über `https` erreichbar).
+
+Schritte zum Einrichten eines Reverse-Proxys sind vom Server abhängig.
+
+#### Nginx
+
+Bevor du nginx einrichten kannst, musst du Ihr nginx-Konfigurationsverzeichnis finden, das abhängig von deiner Plattform und nginx-Installation ist. Weitere Informationen findest du im [nginx Guide](http://nginx.org/en/docs/beginners_guide.html).
+
+Um deinen Server einzurichten:
+
+- Stelle in deiner `nginx.conf`-Datei sicher, dass `include servers/*;` nicht auskommentiert ist.
+- Erstelle im nginx-`Server`-Verzeichnis eine neue Datei, die nach deiner Domain benannt ist und die folgenden Informationen enthält:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+Um mit einem SSL-Block einzurichten:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- führe `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com` aus
+- nginx neustarten
+
+Wenn alles richtig funktioniert hat, sollte deine BookWyrm-Instanz nun extern zugänglich sein.
+
+*Hinweis: Der `proxy_set_header Host $host;` ist unerlässlich; wenn du ihn nicht einbindest, werden eingehende Nachrichten von föderierten Servern abgelehnt.*
+
+*Hinweis: Der Pfad der SSL Zertifikate kann je nach Betriebssystem Ihres Servers variieren*
+
diff --git a/locale/de_DE/content/running_bookwyrm/updating.md b/locale/de_DE/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..1a609a3a
--- /dev/null
+++ b/locale/de_DE/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Deine Instanz updaten Date: 2022-11-17 Order: 3
+- - -
+
+Wenn Änderungen im Produktionszweig verfügbar sind, kannst du sie mit dem Befehl `./bw-dev update` installieren und auf deine Instanz übertragen. Das macht eine Reihe von Dingen:
+
+- `git pull` holt den aktualisierten Code aus dem git Repository. Wenn es Konflikte gibt, musst du möglicherweise `git pull` separat ausführen und die Konflikte lösen, bevor du das `./bw-dev update`-Skript erneut probieren kannst.
+- `docker-compose build` baut die Images neu auf, was sicherstellt, dass die richtigen Pakete installiert sind. Dieser Schritt dauert lange und wird nur benötigt, wenn die Abhängigkeiten (einschließlich pip `requirements.txt` Pakete) geändert wurden, daher kannst du es auskommentieren, wenn du einen schnelleren Updatepfad haben möchten und es nicht stört, ihn bei Bedarf zu kommentieren.
+- `docker-compose run --rm web python manage.py migrate` startet die Django-Datenbankmigrationund verwendet die neu gebrauten Docker Images.
+- `Docker-Compose führen --rm web python manage.py collectstatic --no-input` lädt alle aktualisierten statischen Dateien (wie JavaScript und CSS)
+- `Docker komponieren; docker-compose up -d` startet alle Docker Container neu und nutzt die neu erstellten Images (Achtung: Ausfallzeit beim Neustart)
+
+## Aktivitätsstreams neu erstellen
+
+Feeds für alle Benutzer*innen werden in Redis gespeichert. Um einen Stream erneut zu befüllen, benutze den Verwaltungsbefehl:
+
+``` { .sh }
+./bw-dev populate_streams
+# oder verwenden Sie docker-compose direkt
+docker-compose run --rm web python manage.py populate_streams
+```
+
+Wenn etwas furchtbar schief gelaufen ist, können die Streamdaten gelöscht werden.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/de_DE/content/using_bookwyrm/adding-books.md b/locale/de_DE/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..7c7a043e
--- /dev/null
+++ b/locale/de_DE/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Bücher hinzufügen
+Date: 2022-07-29
+Order: 2
+---
+
+Es gibt einige verschiedene Möglichkeiten, um Bücher zu deiner BookWyrm-Instanz hinzuzufügen! Wenn du das gesuchte Buch nicht finden kannst, versuche diese Optionen in der Reihenfolge -- es ist besser, ein Buch zu importieren als eines von Grund auf neu zu erstellen.
+
+## Bücher aus anderen Katalogen laden
+
+Wenn das gesuchte Buch in deiner Instanz nicht verfügbar ist, gibt es einige verschiedene Möglichkeiten, es hinzuzufügen. Der beste Weg ist, sie von einer externen Quelle zu importieren -- deine Instanz kann Bücher von anderen BookWyrm-Instanzen laden, sowie [OpenLibrary](http://openlibrary.org/) und [Inventaire](http://inventaire.io/). Wenn es keine Suchergebnisse für Ihre Anfrage gibt, werden diese Quellen automatisch abgefragt und erscheint mit einem Button zum "**Buch importieren**". Wenn es lokale Suchergebnisse gibt, die nicht das sind, was Sie suchen, können Sie auf den Link "**Ergebnisse aus anderen Katalogen laden**" klicken, um mehr Ergebnisse zu laden.
+
+
+## Eine weitere Ausgabe hinzufügen
+
+Wenn du das gesuchte Buch gefunden hast, es aber die falsche Ausgabe ist, kannst du eine andere Ausgabe aus der Liste der Ausgaben hinzufügen. Klicke auf den Link unter der Beschreibung, der angibt, wie viele Ausgaben es gibt (zum Beispiel "**4 Ausgaben**"). Am unteren Rand der Editionsliste befindet sich ein Button zum "**Eine weitere Ausgabe hinzufügen**".
+
+## Ein komplett neues Buch hinzufügen
+
+Sobald du versucht hast, nach deinem Buch zu suchen, es aus einem anderen Katalog zu importieren und findest nur andere Ausgaben des Buchs, kannst du ein neues Buch manuell hinzufügen. Der Link zum manuellen Hinzufügen eines Buches befindet sich am Ende der Suchseite, wenn externe Kataloge angezeigt werden. Du kannst auch direkt zu `/create-book` in deiner Instanz navigieren.
diff --git a/locale/de_DE/content/using_bookwyrm/posting-statuses.md b/locale/de_DE/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..0298ca8d
--- /dev/null
+++ b/locale/de_DE/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Beitragsstatus Date: 2022-04-30 Order: 1
+- - -
+
+Das Schreiben auf BookWyrm beginnt mit einem Buch. Benutzer*innen können im Verlauf oder vor kurzem gelesene Bücher aus dem Abschnitt "Ihre Bücher" kommentieren oder von der eigenen Seite eines Buches aus. Von dort aus können Benutzer*innen antworten und eine Unterhaltung starten. BookWyrm Beiträge können Formatierungen wie fett, kursiv und Links mit [Markdown](https://www.markdownguide.org/cheat-sheet/) beinhalten.
+
+Wenn Sie mit dem [Posten auf Mastodon](https://docs.joinmastodon.org/user/posting/) vertraut sind, wirst du feststellen, dass der BookWyrm-Status analoge Sichtbarkeitseinstellungen, Inhaltswarnungen und Erwähnungen enthält. Umfragen, benutzerdefinierte Emoji und Anhänge werden jedoch noch nicht unterstützt.
+
+## Typen von Status
+
+### Kommentare von Nutzer*innen
+
+Es gibt drei Arten von Beiträgen, auf die Benutzer*innen direkt auf Bücher antworten können: Rezensionen, Kommentare und Zitate. Kommentare reagieren auf allgemeine Aspekte eines Buches, Zitate beziehen sich auf bestimmte Passagen und Rezensionen befassen sich mit Büchern insgesamt. Benutzer*innen können auch auf Status antworten.
+
+| Komponente      | Rezensionen | Kommentar | Zitat | Antwort |
+| --------------- | ----------- | --------- | ----- | ------- |
+| Textfeld        | ✔           | ✔         | ✔     | ✔       |
+| Spoiler-Warnung | ✔           | ✔         | ✔     | ✔       |
+| Seitennummer    |             | ✔         | ✔     |         |
+| Zitat           |             |           | ✔     |         |
+| Bewertung       | ✔           |           |       |         |
+| Titelfeld       | ✔           |           |       |         |
+
+
+### Lesestatusaktualisierungen
+
+Der Status wird generiert, wenn ein*e Benutzer*in angibt, dass sie lesen will, begonnen hat oder ein Buch gelesen hat.
+
+## Text
+Text kann beinhalten:
+
+- Erwähnungen (@Benutzer)
+- URLs (`http(s)://` wird nicht angezeigt)
+- Einige [Markdown-Formatierungen](https://www.markdownguide.org/cheat-sheet/)
+  - fett
+  - kursiv
+  - Zitatblock
+  - Aufzählungsliste
+  - Links
+
diff --git a/locale/el_GR/LC_MESSAGES/messages.po b/locale/el_GR/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..7f5d61c8
--- /dev/null
+++ b/locale/el_GR/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-08-04 15:22\n"
+"Last-Translator: \n"
+"Language-Team: Greek\n"
+"Language: el_GR\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: el\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr "BookWyrm Documentation"
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr "Ο οδηγός σας για τη χρήση και συμβολή στο BookWyrm"
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr "Πώς να χρησιμοποιήσετε και να συμβάλετε"
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr "BookWyrm: Κοινωνική Ανάγνωση και Κριτική"
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "Εγγραφή"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr "Εμπλακείτε"
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "Υποστήριξη"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr "Κώδικας"
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr "Documentation"
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr "<strong>Το BookWyrm</strong> είναι συνεργατικό, αντι-εταιρικό λογισμικό που συντηρείται από <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr "Υποστηρίξτε το BookWyrm στο <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr "Συμμετοχή"
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr "BookWyrm on GitHub"
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr "Συνεισφέρετε σε αυτή τη σελίδα"
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr "Μάθετε περισσότερα"
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr "Επικοινωνία με συντηρητή"
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr "Άδεια χρήσης"
+
diff --git a/locale/el_GR/content/codebase/activitypub.md b/locale/el_GR/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/el_GR/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/el_GR/content/codebase/permissions.md b/locale/el_GR/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/el_GR/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/el_GR/content/contributing/contributing.md b/locale/el_GR/content/contributing/contributing.md
new file mode 100644
index 00000000..ef27abc6
--- /dev/null
+++ b/locale/el_GR/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Τίτλος: Πώς να συνεισφέρετε Ημερομηνία: 2021-04-12 Σειρά: 1
+- - -
+
+Υπάρχουν πολλοί τρόποι με τους οποίους μπορείτε να συνεισφέρετε σε αυτό το έργο, ανεξάρτητα από το επίπεδο τεχνικής εξειδίκευσής σας.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/el_GR/content/contributing/debug_toolbar.md b/locale/el_GR/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/el_GR/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/el_GR/content/contributing/install-dev.md b/locale/el_GR/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/el_GR/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/el_GR/content/contributing/style_guide.md b/locale/el_GR/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/el_GR/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/el_GR/content/contributing/translation.md b/locale/el_GR/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/el_GR/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/el_GR/content/index.md b/locale/el_GR/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/el_GR/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/el_GR/content/pages/index.md b/locale/el_GR/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/el_GR/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/el_GR/content/running_bookwyrm/cli.md b/locale/el_GR/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..e7025995
--- /dev/null
+++ b/locale/el_GR/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Συντομεύσεις πληκτρολογίου
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### Πάνω
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Το μέγεθος της βάσης δεδομένων στο δίσκο:
+
+### initdb
+
+Το μέγεθος της βάσης δεδομένων στο δίσκο:
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Το μέγεθος της βάσης δεδομένων στο δίσκο: **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Κόμβος
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/el_GR/content/running_bookwyrm/external-storage.md b/locale/el_GR/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/el_GR/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/el_GR/content/running_bookwyrm/install-prod-dockerless.md b/locale/el_GR/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/el_GR/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/el_GR/content/running_bookwyrm/install-prod.md b/locale/el_GR/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/el_GR/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/el_GR/content/running_bookwyrm/moderation.md b/locale/el_GR/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/el_GR/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/el_GR/content/running_bookwyrm/monitoring-queue.md b/locale/el_GR/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/el_GR/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/el_GR/content/running_bookwyrm/optional_features.md b/locale/el_GR/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/el_GR/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/el_GR/content/running_bookwyrm/reverse-proxy.md b/locale/el_GR/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/el_GR/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/el_GR/content/running_bookwyrm/updating.md b/locale/el_GR/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/el_GR/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/el_GR/content/using_bookwyrm/adding-books.md b/locale/el_GR/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..1df1739e
--- /dev/null
+++ b/locale/el_GR/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Προσθέτοντας Βιβλία
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+Αν βρήκατε το βιβλίο που θέλατε, αλλά όχι τη σωστή έκδοση, μπορείτε να προσθέσετε μια άλλη έκδοση από τη λίστα των εκδόσεων. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. Ο σύνδεσμος για να προσθέσετε χειροκίνητα ένα βιβλίο βρίσκεται στο κάτω μέρος της σελίδας αναζήτησης όταν εμφανίζονται οι εξωτερικοί κατάλογοι. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/el_GR/content/using_bookwyrm/posting-statuses.md b/locale/el_GR/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/el_GR/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/en_Oulipo/LC_MESSAGES/messages.po b/locale/en_Oulipo/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..7e381776
--- /dev/null
+++ b/locale/en_Oulipo/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Oulipo\n"
+"Language: en_Oulipo\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: ou\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/en_Oulipo/content/codebase/activitypub.md b/locale/en_Oulipo/content/codebase/activitypub.md
new file mode 100644
index 00000000..b3bc9287
--- /dev/null
+++ b/locale/en_Oulipo/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm works with [ActivityPub](http://activitypub.rocks/) to trasnmit user activity across BookWyrm instantiations and any ActivityPub software, such as [Mastodon](https://joinmastodon.org/). For book data, BookWyrm has a handful of Activity forms which are not standard, but work across BookWyrm instantiations.
+
+## Activities and Objects
+
+### Accounts and following
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/en_Oulipo/content/codebase/permissions.md b/locale/en_Oulipo/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/en_Oulipo/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/en_Oulipo/content/contributing/contributing.md b/locale/en_Oulipo/content/contributing/contributing.md
new file mode 100644
index 00000000..6705fb02
--- /dev/null
+++ b/locale/en_Oulipo/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: Contributing Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Ask for Things
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Coding contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/en_Oulipo/content/contributing/debug_toolbar.md b/locale/en_Oulipo/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/en_Oulipo/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/en_Oulipo/content/contributing/install-dev.md b/locale/en_Oulipo/content/contributing/install-dev.md
new file mode 100644
index 00000000..eadde567
--- /dev/null
+++ b/locale/en_Oulipo/content/contributing/install-dev.md
@@ -0,0 +1,55 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+:::bash linenums=False
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+:::bash linenums=False
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+:::shell linenums=False
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+:::shell linenums=False
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+:::shell linenums=False
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/en_Oulipo/content/contributing/style_guide.md b/locale/en_Oulipo/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/en_Oulipo/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/en_Oulipo/content/contributing/translation.md b/locale/en_Oulipo/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/en_Oulipo/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/en_Oulipo/content/index.md b/locale/en_Oulipo/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/en_Oulipo/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/en_Oulipo/content/pages/index.md b/locale/en_Oulipo/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/en_Oulipo/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/en_Oulipo/content/running_bookwyrm/cli.md b/locale/en_Oulipo/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/en_Oulipo/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/en_Oulipo/content/running_bookwyrm/external-storage.md b/locale/en_Oulipo/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/en_Oulipo/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/en_Oulipo/content/running_bookwyrm/install-prod-dockerless.md b/locale/en_Oulipo/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/en_Oulipo/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/en_Oulipo/content/running_bookwyrm/install-prod.md b/locale/en_Oulipo/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..eb2cbaa3
--- /dev/null
+++ b/locale/en_Oulipo/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,98 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+:::shell linenums=False
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/en_Oulipo/content/running_bookwyrm/moderation.md b/locale/en_Oulipo/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/en_Oulipo/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/en_Oulipo/content/running_bookwyrm/monitoring-queue.md b/locale/en_Oulipo/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/en_Oulipo/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/en_Oulipo/content/running_bookwyrm/optional_features.md b/locale/en_Oulipo/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/en_Oulipo/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/en_Oulipo/content/running_bookwyrm/reverse-proxy.md b/locale/en_Oulipo/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..539dd2ea
--- /dev/null
+++ b/locale/en_Oulipo/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,113 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+:::nginx linenums=false
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+:::nginx linenums=false
+
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/en_Oulipo/content/running_bookwyrm/updating.md b/locale/en_Oulipo/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..5da85779
--- /dev/null
+++ b/locale/en_Oulipo/content/running_bookwyrm/updating.md
@@ -0,0 +1,29 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+:::bash linenums=False
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+:::bash linenums=False
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/en_Oulipo/content/using_bookwyrm/adding-books.md b/locale/en_Oulipo/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/en_Oulipo/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/en_Oulipo/content/using_bookwyrm/posting-statuses.md b/locale/en_Oulipo/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/en_Oulipo/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/es_ES/LC_MESSAGES/messages.po b/locale/es_ES/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..313b0465
--- /dev/null
+++ b/locale/es_ES/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-09-10 21:23\n"
+"Last-Translator: \n"
+"Language-Team: Spanish\n"
+"Language: es_ES\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: es-ES\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr "Documentación de BookWyrm"
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr "Tu guía para usar y contribuir a BookWyrm"
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr "Cómo usar y contribuir"
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr "BookWyrm: Lectura y reseñas sociales"
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "Únete"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr "Involúcrate"
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "Soporte técnico"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr "Código"
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr "Documentación"
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr "<strong>BookWyrm</strong> es un software colaborativo anticorporativo mantenido por <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr "Apoya BookWyrm en <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr "Involúcrate"
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr "BookWyrm en GitHub"
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr "Contribuir a esta página"
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr "Más información"
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr "Contactar con le encargade"
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr "Licencia"
+
diff --git a/locale/es_ES/content/codebase/activitypub.md b/locale/es_ES/content/codebase/activitypub.md
new file mode 100644
index 00000000..4223f241
--- /dev/null
+++ b/locale/es_ES/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Título: ActivityPub Fecha: 2021-04 Pedido: 1
+- - -
+
+BookWyrm utiliza el protocolo [ActivityPub](http://activitypub.rocks/) para enviar y recibir actividad de usuario entre otras instancias de BookWyrm y otros servicios que implementan ActivityPub, como [Mastodon](https://joinmastodon.org/). Para manejar los datos de los libros, BookWyrm tiene un puñado de tipos de actividades extendidas que no son parte del estándar, pero son legibles para otras instancias de BookWyrm.
+
+## Actividades y objetos
+
+### Usuarios y relaciones
+Las interacciones de las relaciones de usuario siguen la especificación estándar de ActivityPub.
+
+- `Seguir`: solicita recibir estados de un usuario y ver sus estados que tienen la opción de privacidad «sólo seguidores» activado
+- `Aceptar`: aprueba la acción `Seguir` y finaliza la relación
+- `Rechazar`: deniega una acción `Seguir`
+- `Bloquear`: evita que los usuarios vean los estados de los demás, y evita que el usuario bloqueado vea el perfil del actor
+- `Actualizar`: actualiza el perfil y la configuración de un usuario
+- `Eliminar`: desactiva un usuario
+- `Deshacer`: deshace un `Seguir` o un `Bloquear`
+
+### Estados
+#### Tipos de objetos
+
+- `Nota`: en servicios como Mastodon, las `Nota`s son el tipo de estado principal. Contienen el cuerpo de un mensaje, pueden tener archivos adjuntos, mencionar a otres usuaries y ser una respuesta a cualquier tipo de estado. En BookWyrm, las `Nota`s pueden crearse únicamente como mensajes directos o como respuestas a otros estados.
+- `Reseña`: una reseña es un estado relacionado con un libro (indicado por el campo `inReplyToBook`) que posee un título, un cuerpo y una valoración numérica entre 0 (no valorado) y 5.
+- `Comentario`: un comentario sobre un libro menciona al libro y tiene un cuerpo del mensaje.
+- `Cita`: Una cita posee un cuerpo del mensaje, un extracto de un libro y menciona al libro.
+
+
+#### Actividad
+
+- `Crear`: guarda un nuevo estado en la base de datos.
+
+   **Observación**: BookWyrm solo acepta `Crear` una actividad si:
+
+   - Es un mensaje directo (como `Nota`s con `directo` como nivel de privacidad, que menciona a une usuarie local),
+   - Está relacionado con un libro (es un tipo de estado personalizado que incluye el campo `inReplyToBook`),
+   - Responde a estados existentes guardados en la base de datos
+- `Eliminar`: suprime un estado
+- `Me gusta`: marca el estado como favorito
+- `Difundir`: impulsa el estado en la línea de tiempo de quien realiza la acción
+- `Deshacer`: deshacer el `Me gusta` o el `Difundir`
+
+### Colecciones
+Los libros y listas de une usuarie están representados por [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objetos
+
+- `Estantería`: la colección de libros de une usuarie. Por defecto, cada usuarie tiene las estanterías `para leer`, `leyendo actualmente` y `leído`, las cuales sirven para llevar un registro del progreso de lectura.
+- `Lista`: una colección de libros a la que pueden contribuir otres usuaries aunque no sean quienes han creado la lista.
+
+#### Actividad
+
+- `Crear`: añade una estantería o una lista a la base de datos.
+- `Eliminar`: suprime una estantería o una lista.
+- `Añadir`: añade un libro a una estantería o lista.
+- `Eliminar`: quita un libro de una estantería o lista.
+
+
+## Serialización alternativa
+Puesto que BookWyrm emplea tipos de objetos personalizados (`Reseña`, `Comentario`, `Cita`) que no son compatibles con ActivityPub, los estados son transformados en tipos estándar cuando se envían a o se ven desde servicios diferentes a BookWyrm. Las `Reseñas`s se convierten en `Artículo`s y los `Comentario`s y las `Cita`s se convierten en `Nota`s, con un enlace al libro y una imagen de portada adjunta.
diff --git a/locale/es_ES/content/codebase/permissions.md b/locale/es_ES/content/codebase/permissions.md
new file mode 100644
index 00000000..bd88bcb4
--- /dev/null
+++ b/locale/es_ES/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Título: Permisos Fecha: 18-04-2021 Pedido: 2
+- - -
+
+El acceso del usuario a diferentes características se controla usando el [sistema de autenticación integrado](https://docs.djangoproject.com/en/3.2/topics/auth/default/) de Django. Cuando se crea una instancia, el script `initdb` crea un conjunto de permisos, que son asignados a grupos. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/es_ES/content/contributing/contributing.md b/locale/es_ES/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/es_ES/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/es_ES/content/contributing/debug_toolbar.md b/locale/es_ES/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/es_ES/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/es_ES/content/contributing/install-dev.md b/locale/es_ES/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/es_ES/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/es_ES/content/contributing/style_guide.md b/locale/es_ES/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/es_ES/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/es_ES/content/contributing/translation.md b/locale/es_ES/content/contributing/translation.md
new file mode 100644
index 00000000..34b94a4a
--- /dev/null
+++ b/locale/es_ES/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contribuyendo a las traducciones
+
+Puedes unirte al proyecto de traducción en [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Lenguaje en género neutro
+
+Siempre que sea posible, las traducciones de BookWyrm deberían utilizar un lenguaje neutral en cuanto al género. Esto aplica incluso si un lenguaje utiliza el masculino como género neutro, o si utiliza algo similar a "él/ella". También es importante que las traducciones sean claras, concisas y legibles para un lector de pantalla, y a veces estos objetivos están en conflicto; no hay una única respuesta perfecta para esto, y la solución depende del idioma.
+
+Como principio rector, trata de valorar más un lenguaje inclusivo y neutral para el género en lugar de la correción formal o las guías de estilo oficialmente aprobadas. En Español, por ejemplo, muchas guías de estilo formal utilizan los pronombres "ella" o "él" al referirse a un individuo, pero sería mejor en BookWyrm usar el género-neutro "elle" en su lugar.
+
+Si tienes dudas sobre cómo abordar un problema de traducción, comenta en la traducción o abre un [tema de discusión](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) para abordar preguntas más generales.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/es_ES/content/index.md b/locale/es_ES/content/index.md
new file mode 100644
index 00000000..75ea1de0
--- /dev/null
+++ b/locale/es_ES/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Título: Hola Fecha: 2021-04-13
+- - -
+
+BookWryrm es una red social para registrar tu lectura, hablar sobre libros, escribir reseñas y descubrir que es lo siguiente por leer. La federación permite usuarios de BookWyrm unirse a pequeñas y confiables comunidades con las que conectar entre sí y otros servicios de ActivyPub como Mastodon y Pleroma.
+
+## Características
+Dado que el proyecto está todavía en sus primeras etapas, las características crecen cada día, y hay mucho espacio para sugerencias e ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Publicar sobre libros
+    - Redacta reseñas, con o sin calificaciones, que se agregan a la página del libro
+    - Redacta otros tipos de estados sobre libros, como:
+        - Comentarios en un libro
+        - Citas o extractos
+    - Responde a estados
+    - Ve reseñas agregadas de un libro a través de instancias de BookWyrm asociadas
+    - Diferencia reseñas y calificaciones locales y federadas en tu feed de actividad
+- Seguimiento de tu actividad de lectura
+    - Guarda libros en las estanterías por defecto "para leer", "leyendo actualmente" y "leído"
+    - Añade estantes personalizados
+    - Registrar las fechas de inicio y de término de lectura, así como actualizaciones de progreso durante el camino
+    - Actualiza a tus seguidores sobre la actividad de lectura (opcionalmente, y con controles granulares de privacidad)
+    - Crea listas de libros que pueden estar abiertos a envíos de cualquiera, curadas, o únicamente editadas por el creador
+- Federación con ActivityPub
+    - Transmite y recibe los estados y la actividad del usuarie
+    - Compartir datos de libros entre instancias para crear una base de datos en red de metadatos
+    - Identificar libros compartidos entre instancias y contenido asociado
+    - Sigue e interactúa con usuarios a través de instancias de BookWyrm
+    - Interopera con los servicios de ActivityPub que no son de BookWyrm (actualmente Mastodon es soportado)
+- Granular privacy controls
+    - Niveles de privacidad privados, solo para seguidores y público para las publicaciones, estantes y listas
+    - Opción para que les usuaries aprueben manualmente a sus seguidores
+    - Permitir bloqueo y marcado para moderación
diff --git a/locale/es_ES/content/pages/index.md b/locale/es_ES/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/es_ES/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/es_ES/content/running_bookwyrm/cli.md b/locale/es_ES/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/es_ES/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/es_ES/content/running_bookwyrm/external-storage.md b/locale/es_ES/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/es_ES/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/es_ES/content/running_bookwyrm/install-prod-dockerless.md b/locale/es_ES/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/es_ES/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/es_ES/content/running_bookwyrm/install-prod.md b/locale/es_ES/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/es_ES/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/es_ES/content/running_bookwyrm/moderation.md b/locale/es_ES/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/es_ES/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/es_ES/content/running_bookwyrm/monitoring-queue.md b/locale/es_ES/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/es_ES/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/es_ES/content/running_bookwyrm/optional_features.md b/locale/es_ES/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/es_ES/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/es_ES/content/running_bookwyrm/reverse-proxy.md b/locale/es_ES/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/es_ES/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/es_ES/content/running_bookwyrm/updating.md b/locale/es_ES/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/es_ES/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/es_ES/content/using_bookwyrm/adding-books.md b/locale/es_ES/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..3e8121cb
--- /dev/null
+++ b/locale/es_ES/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+¡Hay varias maneras para añadir libros a tu instancia de BookWyrm! Cuando no puedas encontrar el libro que estás buscando, intenta estas opciones en orden -- es mejor importar un libro que crear uno desde cero.
+
+## Cargar libros de otros catálogos
+
+Si el libro que estás buscando no está disponible en tu instancia, hay varias maneras de añadirlo. La mejor manera es importarlo desde una fuente externa -- tu instancia puede cargar libros desde otras instancias de BookWyrm, así como de [OpenLibrary](http://openlibrary.org/) e [Inventaire](http://inventaire.io/). Si no hay resultados de búsqueda para tu consulta, estas fuentes serán automáticamente consultadas, y se mostrará con un botón a "**Importar libro**". Si hay resultados de búsqueda locales que no son lo que buscas, puede hacer clic en el enlace "**Cargar resultados de otros catálogos**" para cargar más resultados.
+
+
+## Añadir otra edición
+
+Si encuentras el libro que quieres, pero no la edición correcta, puedes añadir otra edición a la obra de la lista de ediciones. Haga clic en el enlace debajo de la descripción que le indica cuántas ediciones hay (por ejemplo, "**4 ediciones**"). En la parte inferior de la lista de ediciones, hay un botón para "**Añadir otra edición**".
+
+## Añadir un libro completamente nuevo
+
+Una vez que hayas intentado buscar tu libro, importarlo desde otro catálogo, y encontrar otras ediciones del libro, puedes añadir un nuevo libro manualmente. El enlace para añadir manualmente un libro está en la parte inferior de la página de búsqueda cuando se muestran catálogos externos. También puedes navegar directamente a `/create-book` en tu instancia.
diff --git a/locale/es_ES/content/using_bookwyrm/posting-statuses.md b/locale/es_ES/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..90e037f0
--- /dev/null
+++ b/locale/es_ES/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Título: Publicando estados Fecha: 2022-04-30 Pedido: 1
+- - -
+
+Publicar en BookWyrm empieza con un libro. Usuarios pueden comentar sobre libros que están en leyendo o ya han acabado en la sección de "Tus Libros" o desde la página de inicio de un libro. Desde ahí, los usuarios pueden responder y empezar una conversación. Las publicaciones de BookWyrm incluyen formatos como negritas, itálicas y enlaces usando [lenguaje de marcado](https://www.markdownguide.org/cheat-sheet/).
+
+Si estás familiarizado con [publicar en Mastodon](https://docs.joinmastodon.org/user/posting/), encontrarás que los estados de BookWyrm configuraciones análogas de visibilidad, advertencias de contenido y menciones. Sin embargo, encuestas, emojis personalizados y los archivos adjuntos aún no son compatibles.
+
+## Tipos de estados
+
+### Comentario de usuario
+
+Hay tres tipos de publicaciones que un usuario puede crear directamente en respuesta a libros: reseñas, comentarios y citas. Comentarios a aspectos generales de un libro, citas que pertenecen a un pasaje en específico y reseñas que tratan del libro en general. Los usuarios también puede responder a esos estados.
+
+| Componente        | Reseña | Comentario | Cita | Respuesta |
+| ----------------- | ------ | ---------- | ---- | --------- |
+| Campo de texto    | ✔      | ✔          | ✔    | ✔         |
+| Alerta de spoiler | ✔      | ✔          | ✔    | ✔         |
+| Número de página  |        | ✔          | ✔    |           |
+| Cita              |        |            | ✔    |           |
+| Puntuación        | ✔      |            |      |           |
+| Campo de título   | ✔      |            |      |           |
+
+
+### Leyendo actualizaciones de estados
+
+Estados son generados cuando un usuario indica que quiere leer, que está leyendo o que ha finalizado un libro.
+
+## Texto
+Los textos incluyen:
+
+- Menciones (@usuario)
+- URLs (`http(s)://` no se muestra)
+- Algunos [ formatos de Markdown](https://www.markdownguide.org/cheat-sheet/)
+  - negrita
+  - itálicas
+  - citas en bloque
+  - listas de viñetas
+  - enlaces
+
diff --git a/locale/eu_ES/LC_MESSAGES/messages.po b/locale/eu_ES/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..5ab3f4bf
--- /dev/null
+++ b/locale/eu_ES/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-12-27 02:51\n"
+"Last-Translator: \n"
+"Language-Team: Basque\n"
+"Language: eu_ES\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: eu\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr "BookWyrm-en Dokumentazioa"
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr "BookWyrm erabili eta laguntzeko gida"
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr "Nola Erabili eta Lagundu"
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr "BookWyrm: Irakurketa eta iritzi soziala"
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "Batu"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr "Parte hartu"
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "Laguntza"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr "Kodea"
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr "Dokumentazioa"
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr "<strong>BookWyrm</strong> <a href='https://www.mousereeve.com/'>Mouse Reeve</a>-k mantentzen duen lankidetzako eta enpresen-aurkako softwarea da."
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr "Lagundu BookWyrm <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>en."
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr "Parte hartu"
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr "BookWyrm GitHub-en"
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr "Lagundu orrialde honi"
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr "Informazio gehiago"
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr "Arduradunarekin harremanetan jarri"
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr "Lizentzia"
+
diff --git a/locale/eu_ES/content/codebase/activitypub.md b/locale/eu_ES/content/codebase/activitypub.md
new file mode 100644
index 00000000..5b673588
--- /dev/null
+++ b/locale/eu_ES/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Izenburua: ActivityPub Eguna: 2021-04-20 Ordena: 1
+- - -
+
+BookWyrm-ek [Activity Pub](http://activitypub.rocks/) protokoloa erabiltzen du erabiltzailearen jarduera bidaltzeko eta jasotzeko, BookWyrm instantzien eta ActivityPub ezarria duten beste zerbitzu baten artean, [Mastodon](https://joinmastodon.org/) bezala. Liburuko datuak erabiltzeko, BookWyrm-ek estandarrak ez diren Activity motako hainbat gehigarri erabiltzen ditu, baina BookWyrm-en beste instantziekin erabilgarriak direnak.
+
+## Jarduerak eta Objektuak
+
+### Erabiltzaileak eta harremanak
+Erabiltzaile-harremanaren elkarrekintzek Activity Pub-en berezitasun estandarrari jarraitzen diote.
+
+- `Jarraitu`: erabiltzaile baten egoera jasotzeko eskatzen du eta pribatutasun-aukera «jarraitzaileak soilik» aktibatuta duten egoerak erakusten ditu
+- `Onartu`: `Jarraitzea` onartzen eta harremana gauzatzen du
+- `Ukatu`: `Jarraitze` bati uko egiten dio
+- `Blokeatu`: erabiltzaileek bestearen egoerak ikustea eragozten du eta blokeatutako erabiltzaileak aktorearen profila ikustea eragozten du
+- `Eguneratu`: erabiltzaile baten profila eta konfigurazioa eguneratzen ditu
+- `Ezabatu`: erabiltzaile bat desaktibatzen du
+- `Desegin`: desegiten ditu `Jarraitze` bat edo `Blokeo` bat
+
+### Egoerak
+#### Objektu motak
+
+- `Oharra`: Mastodon bezalako zerbitzuetan, `Oharra` elementuak egoera-mota nagusia dira. Barne hartzen dute mezu eremu bat, fitxategi erantsiak, erabiltzaileak aipa ditzakete eta edozein motatako estatutuen erantzunak izan daitezke. BookWyrm-en, `Oharra` elementuak zuzeneko mezu gisa soilik sor daitezke edo beste egoera batzuei emandako erantzun gisa.
+- `Kritika`: Kritika bidalketa bat da, liburu bati zuzenduta (`LiburuariBuruz` eremuak adierazita). Kritika batek honako atal hauek ditu: izenburua, gorputza eta 0 (kalifikatu gabea) eta 5 arteko kalifikazioa.
+- `Iruzkina`: Liburu bati buruzko iruzkin batek liburu bat aipatzen du eta mezu gorputz bat dauka.
+- `Aipua`: Aipu batek du mezuaren gorpuntz bat eta liburu baten zati bat, eta liburu bat aipatzen du.
+
+
+#### Jarduerak
+
+- `Sortu`: bidalketa berri bat gordetzen du datu-basean.
+
+   **Oharra**: BookWyrm-ek `Sortu` jarduerak baimentzen ditu baldin eta:
+
+   - Mezu zuzenak badira (hots, `Oharra` elementuak `zuzena` pribatutasun mailarekin, tokiko erabiltzailearen aipamenarekin),
+   - Liburu batekin lotuta badira ( `LiburariBuruz` eremua barne duen egoera pertsonalizatuko mota batekoa),
+   - Datu-basean gordetako egoerei emandako erantzunak
+- `Ezabatu`: Egoera bat ezabatzen du
+- `Atsegin`: Sortzen du gogoko bat egoeretan
+- `Partekatu`: Egoera sustatzen du aktorearen kronologian
+- `Desegin`: Desegiten ditu `Atsegin` bat edo `Partekatu` bat
+
+### Bildumak
+[`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection) elementuari esker erabiltzaile baten liburuak eta zerrendak ager daitezke
+
+#### Objektuak
+
+- `Apalategia`: Erabiltzaile baten liburu bilduma. Lehenespenez, erabiltzaile bakoitzak hainbat atal ditu, irakurtketaren aurrerapenari jarraitzeko: `irakurtzekoak`, `irakurtzen hasitakoak` eta `irakurriak`.
+- `Zerrenda`: Zerrenda sortu zuen erabiltzaileaz besteko elementuak izan ditzakeen liburu-bilduma.
+
+#### Jarduerak
+
+- `Sortu`: Gehitu apal bat edo zerrenda bat datu-basean.
+- `Ezabatu`: Ezabatu apal bat edo zerrenda bat.
+- `Gehitu`: Liburu bat gehitzen du apal edo zerrenda batean.
+- `Kendu`: Apal edo zerrenda batetik liburu bat ezabatzen du.
+
+
+## Serializazio alternatiboa
+BookWyrm-ek Activity Pub-ekin bateragarriak ez diren objektu pertsonalizatu motak (`Kritika`, `Iruzkina`, `Aipua`) erabiltzen dituenez, egoerak tipo estandar bihurtzen dira BookWyrm ez diren zerbitzuek bidaltzen edo ikusten dituztenean. `Kritikak`, `Artikulu` bihurtzen dira, eta `Iruzkinak` eta `Aipuak` `Ohar` bihurtzen dira, libururako esteka batekin eta erantsitako azaleko irudi batekin.
diff --git a/locale/eu_ES/content/codebase/permissions.md b/locale/eu_ES/content/codebase/permissions.md
new file mode 100644
index 00000000..625b15dd
--- /dev/null
+++ b/locale/eu_ES/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Izenburua: Baimenak Eguna: 2021-04-18 Ordena: 2
+- - -
+
+Erabiltzailearen hainbat ezaugarritarako sarbidea Djangoko [autentifikazio-sistema integratuaren](https://docs.djangoproject.com/en/3.2/topics/auth/default/) bidez kontrolatzen da. Instantzia bat sortzen denean, `initdb` sriptak taldeei esleitutako baimen sorta bat sortzen du. Lehenespenez, erabiltzaile berri guztiak `editor` taldeari esleitzen dira eta horrela liburuaren metadatuak aldatzeko eskubidea dute.
+
+Administrazio instantziak `superuser` estatusa izan behar du. Horrek Djangoren administraziorako sarbidea (`/admin`) ematen dio eta erabiltzaile horri baimen guztiak ematen dizkio.
+
+## Baimenak eta taldeak
+Taula honek lau taldeak erakusten ditu (administratzailea, moderatzailea, editorea eta erabiltzailea) eta talde horien erabiltzaileei dagozkien baimenak:
+
+|                                   | administratzailea | moderatzailea | editorea | erabiltzailea |
+| --------------------------------- | ----------------- | ------------- | -------- | ------------- |
+| instantziaren ezarpenak aldatzea  | ✔️                | -             | -        | -             |
+| erabiltzaile baten maila aldatzea | ✔️                | -             | -        | -             |
+| federazioa kudeatzea              | ✔️                | ✔️            | -        | -             |
+| gonbidapenak sortzea              | ✔️                | ✔️            | -        | -             |
+| erabiltzaileak deskaktibatzea     | ✔️                | ✔️            | -        | -             |
+| mezuak ezabatzea                  | ✔️                | ✔️            | -        | -             |
+| liburuak editatzea                | ✔️                | ✔️            | ✔️       | -             |
+ azalak linean ezartzea            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/eu_ES/content/contributing/contributing.md b/locale/eu_ES/content/contributing/contributing.md
new file mode 100644
index 00000000..f2dd97ad
--- /dev/null
+++ b/locale/eu_ES/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Izenburua: Nola lagundu Eguna: 2021-04-12 Ordena: 1
+- - -
+
+Proiektu honetan laguntzeko hainbat modu daude, esperientzia teknikoko maila guztietarako.
+
+## Iruzkinak eta funtzionalitateei buruzko eskaerak
+Ongi etorria senti zaitez akatsak jakinarazteko, iradokizunak, funtzio berrietarako eskaerak eta gauzen funtzionamenduari buruzko ideiak aurkezteko, eta horiek [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues) bidez bidaltzeko.
+
+## Koderako ekarpenak
+Koderako ekarpenak ongi etorriak dira! Ez badakizu nondik hasi, begira iezaiozu ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) etiketari. BookWyrm eskala txikiko proiektua denez, haren egitura ez da oso formala, baina euskarri pertsonalizaturako gaitasun handia du, hainbat forma har ditzake: galderak neurrira egin, binomioan programatu, bideo-deiak egin, etab. Beraz, lasai jarri gurekin harremanetan.
+
+Proiektuari edo ekarpenei buruzko galderarik baduzu, [BookWyrm matrix txatean](https://app.element.io/#/room/#bookwyrm:matrix.org) sar zaitezke.
+
+## Itzulpena
+Ingelesez gain beste hizkuntza bat hitz egiten duzu? BookWyrm itzulpenen beharrean dago! Gehitzen edo aldatzen ahal dituzu itzulpenak hemen: [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Finantza laguntza
+BookWyrm pasio-proiektua da, publizitaterik gabea, eta ez du asmorik enpresen finantziazioa edo finantza-harremanak bilatzeko. Proiektua martxan izaten lagundu nahi baduzu, diru-sustengatzaile bihur zaitezke plataforma hauen bidez: [Patreon](https://www.patreon.com/bookwyrm) edo [OpenCollective](https://opencollective.com/bookwyrm), edo aldi baterako emaitza eginez [PayPal](https://paypal.me/oulipo) webgunean.
diff --git a/locale/eu_ES/content/contributing/debug_toolbar.md b/locale/eu_ES/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..3dc383ac
--- /dev/null
+++ b/locale/eu_ES/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Izenburua: Django Debug Toolbar Eguna: 2022-05-16 Ordena: 5
+- - -
+
+BookWyrm-ek adar konfiguratu bat dauka [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/) exekutatzeko. Adar hori ez da inoiz `main`-ean fusionatuko eta baditu zenbait hobekuntza, tresna-barrarekin funtzionarazten dutenak, baina arriskutsuak dira produkzioan bertan edo handik gertu dagoen ingurunean erabiltzeko. Adar hori erabiltzeko, urrats batzuetatik pasa beharko zara funtzionarazteko.
+
+## Konfigurazioa
+
+- Git erabiliz, jarri tresna-barrako [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) adarrean
+- Adarra eguneratu `main`-etik `git merge main` erabiliz. Adarra eguneratua da aldian behin, baina azken bertsioari begira berantean izanen da ziur aski.
+- Berreraiki Docker irudiak `docker-compose up --build` erabiliz Debug Toolbar lib-a instalatu dela `requirements.txt`-etik
+- Aplikazion sartu `web` irudiaren bidez zuzenki (`nginx` bidez sartu ordez) `8000` ataka erabiliz
diff --git a/locale/eu_ES/content/contributing/install-dev.md b/locale/eu_ES/content/contributing/install-dev.md
new file mode 100644
index 00000000..aa6f6011
--- /dev/null
+++ b/locale/eu_ES/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Izenburua: Garapen ingurumena Eguna: 2021-04-12 Ordena: 3
+- - -
+
+## Aurrebaldintzak
+
+Jarraibide hauen arabera, BookWyrm ari zara garatzen Docker erabiliz. Ezer baino lehenago instalatu behar dituzu [Docker](https://docs.docker.com/engine/install/) eta [docker-compose](https://docs.docker.com/compose/install/).
+
+## Garapen ingurunearen konfigurazioa
+
+- Eskura ezazu [GitHub-etik BookWyrm-en kode-basea](https://github.com/bookwyrm-social/bookwyrm). Paketearen [fork bat sortu](https://docs.github.com/en/get-started/quickstart/fork-a-repo) dezakezu, ondotik [erabili `git clone` kodea deskargatzeko](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) zure ordenagailuan.
+- Joan zure ordenagailuko kodea duen direktoriora, orain direktorio honetatik lan egingo duzu.
+- Konfigura ezazu zure garapen-inguruneko aldagaien artxiboa, inguruneko adibide-fitxategia (`.env.example`) `.env` izeneko fitxategi berri batean kopiatuz. Komando-lerroan, hori egin dezakezu idatziz:
+``` { .sh }
+cp .env.example .env
+```
+- `.env` lerroan aldatu `DEBUG` eta idatzi `true`
+- Aukera gisa, [ngrok](https://ngrok.com/) gisako zerbitzua erabil dezakezu domeinu-izen bat konfiguratzeko, ondoren, ezarri `.env` fitxategian `DOMAIN` balioa, ngrok bidez sortutako domeinu-izena erabiliz.
+
+- Konfiguratu nginx garapenerako, nginx konfigurazio-fitxategia (`nginx/development`) kopiatuz `nginx/default.conf` izeneko fitxategi berrian:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Hasi aplikazioa. Komando-lerroan, exekutatu:
+``` { .sh }
+./bw-dev build            # Eraiki docker irudiak
+./bw-dev setup            # Inizializatu datu-basea eta abiarazi migrazioak
+./bw-dev up               # Hasi docker edukitzaileak
+```
+- Konpilazioa bukatuta, `http://localhost:1333` instantziara irits zaitezke eta admin erabiltzaile bat sor dezakezu.
+
+Kuriosa bazara: `./bw-dev` komandoa shell skript soil bat da eta beste hainbat tresna exekutatzen ditu: aurreko komandoen ordez, zuk `docker-compose build` edo `docker-compose up` exekutatzen ahal zenuen zuzenean, nahi izanez gero. `./bw-dev` komandoak leku bakar batean biltzen ditu erosotasun gehiagorako. Exekutatu komando hori argumenturik gabe eskura dauden komandoen zerrenda lortzeko, irakurri dagokion [dokumentazio-orria](/command-line-tool.html) edo ireki fitxategia eta berrikusi zehatz-mehatz komando bakoitzak egiten duena!
+
+### Ereduak editatzea edo sortzea
+
+Eredu bat aldatzen edo sortzen baduzu, seguruenik datu-basearen egitura aldatuko duzu. Aldaketa horiek eragina izan dezaten, Djangoko `makemigrations` komandoa exekutatu beharko duzu [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations) berri bat sortzeko, eta, ondoren, `migrate` komandoa, azken hau migratzeko:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Fitxategi estatikoak editatzea
+CSS edo JavaScript kodea editatzen duzun bakoitzean, berriro exekutatu beharko duzu `collectstatic` komandoa, zure aldaketek eragina izan dezaten:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+[yarn instalatuta](https://yarnpkg.com/getting-started/install) baduzu, exekuta dezakezu `yarn watch:static`, `bookwyrm/static` errepertorioan aldaketa bat gertatzen den bakoitzean aurreko scripta automatikoki exekutatzeko.
diff --git a/locale/eu_ES/content/contributing/style_guide.md b/locale/eu_ES/content/contributing/style_guide.md
new file mode 100644
index 00000000..7aee0ef9
--- /dev/null
+++ b/locale/eu_ES/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Izenburua: Estiloen gida Eguna: 2021-10-20 Ordena: 4
+- - -
+
+## Pull eskariak
+
+BookWyrm-en kodean parte-hartzeko asmoa duzu, bikaina da! Arazo ireki bat konpondu nahi baduzu, hobe da iruzkin bat uztea elkarrizketan, lana bikoiztu ez dadin. Saiatu pull eskarien gaiari mugatzen, eta kontzentratu zure arreta gai bakar batean. Horrela, irakurgarriagoa izaten da eta zati batek aldaketak behar baditu, ez ditu beste aldeak atzeratzen.
+
+Arazo bat nola konpondu ez badakizu edo konpontzeko prest ez bazaude, lasai egon. Nahikoa da pull eskaeran iruzkin bat egitea, eta txanda hartuko dugu 💖.
+
+Pull eskaerek egiaztapen automatizatu guztiak egin behar dituzte bat egin baino lehen, hala nola estilo-egiaztapenak, Linters globalak, segurtasun-kontrola eta proba unitarioak.
+
+## Linting-a
+
+### Orokorra
+
+[EditorConfig](https://editorconfig.org) erabiltzen dugu indentazio eta lerro koherenteak mantentzeko.
+
+### Python
+
+BookWyrm-ek [Black](https://github.com/psf/black) kodearen formatzailea erabiltzen du Python kodearen oinarriaren koherentzia mantentzeko. Pull eskaera berri guztiak GitHuben ekintzekin egiaztatzen dira, eta automatikoki konpon daitezke kode-estiloko arazoak `./bw-dev black` exekutatuz
+
+Kodea Pylint-ekin ere egiaztatzen da GitHuben ekintza baten bidez. Pylint-en ohartarazpenei ekin behar zaie pull eskaerak bateratu baino lehen, baina zure iritziaren araberakoa da iradokizuna erabili edo oharra ezabatu behar den. Ohar bat ezabatzeko, gehitu iruzkin bat amaieran edo oharrak aipatzen diren aitzineko lerroan: `# pylint: disable=warning-name`
+
+### Txantiloiak (HTML)
+
+Zure pull eskaria, [curlylint](https://www.curlylint.org) linter-rak egiaztatuko du Django txantiloietarako.
+
+### CSS
+
+[Stylelint](https://stylelint.io) erabiltzen dugu CSS arau guztiak egiaztatzeko. Pylint-ekin bezala, [stylelint desaktiba dezakezu](https://stylelint.io/user-guide/ignore-code) arau jakin baterako, baina horretarako justifikazio ona beharko duzu.
+
+### JavaScript
+
+[ESLint](https://eslint.org)ek egiaztatzen ditu JavaScript-ean egin aldaketa guztiak. ESLint-ek zure JavaScript kodea (funtzionatzen badu ere) gustuko ez badu, egiaztatu linter mezua arazo zehatz horretarako.
+
+## Diseinu inklusiboa
+
+Bookwyrm-ek ahalik eta inklusiboena eta eskuragarriena izan nahi du.
+
+Kodearekin ekarpenak egiten dituzunean, egiaztatu [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354), pull eskari bat proposatu aurretik. Irisgarritasunari buruzko aholkuetarako, [A11Y-101](https://www.a11y-101.com/development) ere baliabide baliagarria da. Zure orrialde txantiloiak eleaniztunak izateko moduari buruzko informazioa lortzeko, kontsultatu [Itzulpenak atala](/translations.html).
+
+Hona hemen Bookwyrm-eko kolaboratzaileek gogoan hartu behar dituzten elementu batzuk:
+
+### Formularioak
+
+* Soilik erabili `input[type="checkbox"]` edo `input[type="radio"]` honen barnean: `<label>`
+* Kontrol-kaxarik eta irrati-botoirik ez baduzu ezartzen `<label>` barnean, `<label>`a dagokion elementuaren _ondoren_ jarri behar da
+
+### Botoiak eta Estekak
+
+* Erabili `<button>` elementu bat JavaScript ekintza bat aktibatzeko helburua duen orotarako (adibidez: formulario bat ezkutatu edo erakusteko) edo `POST` eskaria bat bidaltzeko (adibidez, formulario bat aurkezteko)
+* Erabili `<a>` elementu bat `GET` eskaria eragiten duen gauza orotarako. Usaian, esteka batek (`<a>`) ez du botoi (`class="button"`) baten itxura izan behar, nahiz eta salbuespen batzuk dauden "Ezeztatu" botoiak bezala. Zalantzarik izanez gero, aholku bat eska ezazu zure pull eskarian
diff --git a/locale/eu_ES/content/contributing/translation.md b/locale/eu_ES/content/contributing/translation.md
new file mode 100644
index 00000000..69fa313c
--- /dev/null
+++ b/locale/eu_ES/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Izenburua: Itzulpenak Eguna: 2021-10-20 Ordena: 2
+- - -
+
+## Itzultzen lagundu
+
+BookWyrm-en itzulpen proiektuarekin bat egin dezakezu hemen: [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Genero-hizkuntza neutrala
+
+Ahal den neurrian, BookWyrm-en itzulpenek genero neutrala duen hizkuntza erabili behar dute. Hizkuntza batek gizakia genero neutral gisa betetzen ez badu ere aplikatzen da hori, edo gizonezko eta emakumezkoen aldaera nabarmentzen badu izenordain batzuen bidez. Garrantzitsua da, halaber, itzulpenak argiak, zehatzak eta irakurgarriak izatea pantaila bidezko irakurlearentzat, eta, batzuetan, helburu horiek gatazkan daude; ez dago erantzun perfekturik eta bakarra, irtenbidea hizkuntzaren araberakoa da.
+
+Ideia nagusi gisa, saiatu balio handiagoa jartzen hizkuntza neutral eta inklusiboari, hizkuntza formal zuzenari edo ofizialki onartutako estilo-liburuei baino. Ingelesez, adibidez, estilo-gida askok eskatzen dute "she" edo "he" izenordain berezi bat erabiltzea gizabanako bati dagokionez, baina BookWyrmen hobe da "they" izenordain berezi ez-generikoa erabiltzea haren ordez.
+
+Itzulpen arazo bati nola heldu ez badakizu, iruzkindu itzulpena eta ireki [eztabaida gai](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) bat, galdera zabalagoei erantzuteko.
+
+## Jarri txantiloiak itzulgarriak
+
+Bookwyrm-ek Djangoren itzulpen-funtzionalitatea erabiltzen du, orrialdearen edukia erabiltzaileak aukeratutako bistaratze-hizkuntzaren arabera alda dadin. Django dokumentazioak, garapen esparru hori [nola funtzionatzen duen azaltzen du](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code), hona hemen bertsio laburra:
+
+* txantiloiaren testu guztiek itzulpen etiketak barne izan behar dituzte
+* erantsi `{% load i18n %}` txantiloiaren goiko aldean itzulpenak gaitzeko
+* Testu-blokea testu literala bada, `{% trans %}` txantiloiaren etiketa erabil dezakezu
+* Testu-blokeak aldagaiak baldin baditu, txantiloiaren etiketa-bikotea erabili behar duzu `{% blocktrans %}` and `{% endblocktrans %}`. Lerro-espazioak edo -jauziak sartzen badituzu, erabili `trimmed` hizkuntza-fitxategia sortzen denean automatikoki ezabatzeko: `{% blocktrans trimmed %}`
+
+### Adibideak
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Honek gehitua: <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/eu_ES/content/index.md b/locale/eu_ES/content/index.md
new file mode 100644
index 00000000..2fbc02ab
--- /dev/null
+++ b/locale/eu_ES/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Izenburua: Ongi etorri Eguna: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/eu_ES/content/pages/index.md b/locale/eu_ES/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/eu_ES/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/eu_ES/content/running_bookwyrm/cli.md b/locale/eu_ES/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/eu_ES/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/eu_ES/content/running_bookwyrm/external-storage.md b/locale/eu_ES/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/eu_ES/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/eu_ES/content/running_bookwyrm/install-prod-dockerless.md b/locale/eu_ES/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/eu_ES/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/eu_ES/content/running_bookwyrm/install-prod.md b/locale/eu_ES/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/eu_ES/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/eu_ES/content/running_bookwyrm/moderation.md b/locale/eu_ES/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/eu_ES/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/eu_ES/content/running_bookwyrm/monitoring-queue.md b/locale/eu_ES/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/eu_ES/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/eu_ES/content/running_bookwyrm/optional_features.md b/locale/eu_ES/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/eu_ES/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/eu_ES/content/running_bookwyrm/reverse-proxy.md b/locale/eu_ES/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/eu_ES/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/eu_ES/content/running_bookwyrm/updating.md b/locale/eu_ES/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/eu_ES/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/eu_ES/content/using_bookwyrm/adding-books.md b/locale/eu_ES/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..8788e9cc
--- /dev/null
+++ b/locale/eu_ES/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Liburuak gehitu
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/eu_ES/content/using_bookwyrm/posting-statuses.md b/locale/eu_ES/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..d13f8818
--- /dev/null
+++ b/locale/eu_ES/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Izenburua: Bidalketak egin Eguna: 2022-04-30 Ordena: 1
+- - -
+
+BookWyrm-en bidalketak liburu batekin hasten dira. Erabiltzaileek irakurtzen ari diren edo irakurri berri dituzten liburuen gainean iruzkinak egin ditzakete "Zure liburuak" atalean edo liburu baten hasiera orrian. Bertan, erabiltzaileek elkarrizketa bat hasi eta mezuei erantzun ahalko diete. BookWyrm-eko bidalketek formatoa izan dezakete, hala nola letra lodia, etzana eta hiperestekak. Horretarako [Markdown](https://www.markdownguide.org/cheat-sheet/) erabili behar da.
+
+[Mastodonen argitaratzea](https://docs.joinmastodon.org/user/posting/) ezaguna baduzu, konturatuko zara BookWyrm-en bidalketek antzekotasunak dituztela ikusgarritasun ezarpenei, eduki oharrei eta aipuei dagokienez. Hala ere, gaur-gaurkoz, ezin dira inkestak edo eranskinak egin, ezta pertsonalizatutako emojiak erabili.
+
+## Bidalketa motak
+
+### Iruzkinak
+
+Erabiltzaileek hiru bidalketa mota egin ditzakete liburuen gainean: kritikak, iruzkinak eta aipuak. Iruzkinak liburuaren alderdi orokorrei buruzkoak dira, aipuak pasarte zehatz bati buruzkoak eta kritikek liburuaren osotasuna hartzen dute kontuan. Era berean, erabiltzaileek bidalketei erantzun diezaiekete.
+
+| Osagaia           | Kritika | Iruzkina | Aipua | Erantzuna |
+| ----------------- | ------- | -------- | ----- | --------- |
+| Testu-eremua      | ✔       | ✔        | ✔     | ✔         |
+| Spoiler alertak   | ✔       | ✔        | ✔     | ✔         |
+| Orrialde-zenbakia |         | ✔        | ✔     |           |
+| Aipua             |         |          | ✔     |           |
+| Kalifikazioa      | ✔       |          |       |           |
+| Izenburu-eremua   | ✔       |          |       |           |
+
+
+### Irakurketa-egoeraren eguneraketa
+
+Bidalketok sortzen dira erabiltzaile batek adierazten duenean liburu bat irakurri nahi duela, irakurtzen hasi dela edo amaitu duela.
+
+## Testua
+Testuak izan dezake:
+
+- Aipamenak (@erabiltzailea)
+- URLak (`http(s)://` ez da erakusten)
+- [Markdown formatu](https://www.markdownguide.org/cheat-sheet/) batzuk
+  - letra lodia
+  - letra etzana
+  - bloke-aipuak
+  - puntu-zerrendak
+  - estekak
+
diff --git a/locale/fi_FI/LC_MESSAGES/messages.po b/locale/fi_FI/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..214bc7d7
--- /dev/null
+++ b/locale/fi_FI/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Finnish\n"
+"Language: fi_FI\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: fi\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/fi_FI/content/codebase/activitypub.md b/locale/fi_FI/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/fi_FI/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/fi_FI/content/codebase/permissions.md b/locale/fi_FI/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/fi_FI/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/fi_FI/content/contributing/contributing.md b/locale/fi_FI/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/fi_FI/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/fi_FI/content/contributing/debug_toolbar.md b/locale/fi_FI/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/fi_FI/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/fi_FI/content/contributing/install-dev.md b/locale/fi_FI/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/fi_FI/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/fi_FI/content/contributing/style_guide.md b/locale/fi_FI/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/fi_FI/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/fi_FI/content/contributing/translation.md b/locale/fi_FI/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/fi_FI/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/fi_FI/content/index.md b/locale/fi_FI/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/fi_FI/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/fi_FI/content/pages/index.md b/locale/fi_FI/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/fi_FI/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/fi_FI/content/running_bookwyrm/cli.md b/locale/fi_FI/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/fi_FI/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/fi_FI/content/running_bookwyrm/external-storage.md b/locale/fi_FI/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/fi_FI/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/fi_FI/content/running_bookwyrm/install-prod-dockerless.md b/locale/fi_FI/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/fi_FI/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/fi_FI/content/running_bookwyrm/install-prod.md b/locale/fi_FI/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/fi_FI/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/fi_FI/content/running_bookwyrm/moderation.md b/locale/fi_FI/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/fi_FI/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/fi_FI/content/running_bookwyrm/monitoring-queue.md b/locale/fi_FI/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/fi_FI/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/fi_FI/content/running_bookwyrm/optional_features.md b/locale/fi_FI/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/fi_FI/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/fi_FI/content/running_bookwyrm/reverse-proxy.md b/locale/fi_FI/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/fi_FI/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/fi_FI/content/running_bookwyrm/updating.md b/locale/fi_FI/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/fi_FI/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/fi_FI/content/using_bookwyrm/adding-books.md b/locale/fi_FI/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/fi_FI/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/fi_FI/content/using_bookwyrm/posting-statuses.md b/locale/fi_FI/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/fi_FI/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/fr_FR/LC_MESSAGES/messages.po b/locale/fr_FR/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..5139cfa2
--- /dev/null
+++ b/locale/fr_FR/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: French\n"
+"Language: fr_FR\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n > 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: fr\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr "Documentation de BookWyrm"
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr "Votre guide d'utilisation et de contribution à BookWyrm"
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr "Comment utiliser et contribuer"
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr "BookWyrm : Lecture et critique de livres, de manière sociale et décentralisée"
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "Rejoindre"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr "Comment s'impliquer ?"
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "Soutenir"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr "Code"
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr "Documentation"
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr "<strong>BookWyrm</strong> est un logiciel collaboratif et anti-commercial maintenu par <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr "Soutenir BookWyrm sur <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr "Contribuer"
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr "BookWyrm sur GitHub"
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr "Contribuer à cette page"
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr "En savoir plus"
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr "Contact"
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr "Licence"
+
diff --git a/locale/fr_FR/content/codebase/activitypub.md b/locale/fr_FR/content/codebase/activitypub.md
new file mode 100644
index 00000000..70a760c3
--- /dev/null
+++ b/locale/fr_FR/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm utilise le protocole [ActivityPub](http://activitypub.rocks/) pour envoyer et recevoir des activités utilisateur entre des instances de BookWyrm et d’autres services qui implémentent ActivityPub, comme [Mastodon](https://joinmastodon.org/). Pour gérer les données de livres, BookWyrm utilise plusieurs extensions de types d’Activity qui ne font pas partie de la norme, mais sont interopérables avec les autres instances de BookWyrm.
+
+## Activités et Objets
+
+### Utilisateurs et relations
+Les interactions de relations entre les utilisateurs suivent la spécification standard ActivityPub.
+
+- `Follow` : demande à recevoir les statuts d'un utilisateur et consultez leurs statuts qui ont un réglage de lecture réservée aux abonnés
+- `Accept` : approuve un `Follow` et finalise la relation
+- `Reject` : refuse un `Follow`
+- `Block` : empêche les utilisateurs de voir les statuts de l'autre et empêche l'utilisateur bloqué de voir le profil de l'acteur
+- `Update` : met à jour le profil et les paramètres d'un utilisateur
+- `Delete` : désactive un utilisateur
+- `Undo` : inverse un `Follow` ou un `Block`
+
+### Statuts
+#### Types d'Object
+
+- `Note` : Sur les services comme Mastodon, les `Note`s sont le type principal de statut. Ils contiennent un corps de message, des pièces jointes, peuvent mentionner les utilisateurs et être des réponses à des statuts de n'importe quel type. Dans BookWyrm, les `Note`s ne peuvent être créés qu'en tant que messages directs ou en tant que réponses à d'autres statuts.
+- `Critique` : Une critique est un statut en réponse à un livre (indiqué par le champ `inReplyToBook`), qui a un titre, un corps et une évaluation numérique entre 0 (non évalué) et 5.
+- `Comment` : Un commentaire sur un livre mentionne un livre et a un corps de message.
+- `Citation` : Une citation a un corps de message, un extrait d'un livre et mentionne un livre.
+
+
+#### Activities
+
+- `Create` : sauvegarde un nouveau statut dans la base de données.
+
+   **Remarque** : BookWyrm n'accepte les activités `Create` que si elles sont :
+
+   - des messages directs (c'est à dire des `Note`s avec le niveau de confidentialité `direct`, qui mentionnent un utilisateur local),
+   - liées à un livre (d'un type de statut personnalisé qui inclut le champ `inReplyToBook`),
+   - en réponse à des statuts existants enregistrés dans la base de données
+- `Delete` : Supprime un statut
+- `Like` : Crée un favori sur le statut
+- `Announce` : Booste (reposte) le statut dans la chronologie de l'acteur
+- `Undo` : Inverse un `Like` ou un `Announce`
+
+### Collections
+Les livres et listes d'un utilisateurs sont représentés par [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf` : Collection de livres d'un utilisateur. Par défaut, chaque utilisateur a les étagères `to-read` (à lire), `reading` (en cours de lecture), et `read` (livres lus), qui sont utilisées pour suivre la progression de la lecture.
+- `List` : Une collection de livres qui peut avoir des éléments contribués par des utilisateurs autres que celui qui a créé la liste.
+
+#### Activities
+
+- `Create` : sauvegarde une étagère ou une liste dans la base de données.
+- `Delete` : Supprime une étagère ou une liste.
+- `Add` : Ajoute un livre à une étagère ou une liste.
+- `Remove` : Supprime un livre d'une étagère ou d'une liste.
+
+
+## Sérialisation alternative
+Parce que BookWyrm utilise des types d'objets personnalisés (`Review`, `Comment`, `Quotation`) qui ne sont pas pris en charge par ActivityPub, les statuts sont transformés en types standards lorsqu'ils sont envoyés ou vus par des services non-BookWyrm. Les `Review`s sont converties en `Article`s, les `Comment`s et `Quotation`s sont convertis en `Note`s, avec un lien vers le livre et l'image de couverture en pièce jointe.
diff --git a/locale/fr_FR/content/codebase/permissions.md b/locale/fr_FR/content/codebase/permissions.md
new file mode 100644
index 00000000..02806527
--- /dev/null
+++ b/locale/fr_FR/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+L'accès de l'utilisateur aux différentes fonctionnalités est contrôlé à l'aide du [système d'authentification intégré](https://docs.djangoproject.com/en/3.2/topics/auth/default/) de Django. Lorsqu'une instance est créée, le script `initdb` crée un ensemble de permissions, qui sont assignées aux groupes. Par défaut, tous les nouveaux utilisateurs sont assignés au groupe `éditeur` qui leur permet de modifier les métadonnées du livre.
+
+L'administrateur de l'instance doit avoir le statut de `superutilisateur` qui leur donne accès à l'administration de Django (`/admin`) et confère toutes les permissions à cet utilisateur.
+
+## Permissions et groupes
+Ce tableau montre les quatre groupes (administrateur, modérateur, éditeur et utilisateur) et les permissions que les utilisateurs de ce groupe ont :
+
+|                                       | admin | modérateur | éditeur | utilisateur |
+| ------------------------------------- | ----- | ---------- | ------- | ----------- |
+| modifier les paramètres de l'instance | ✔️    | -          | -       | -           |
+| changer le niveau d'un utilisateur    | ✔️    | -          | -       | -           |
+| gérer la fédération                   | ✔️    | ✔️         | -       | -           |
+| créer des invitations                 | ✔️    | ✔️         | -       | -           |
+| désactiver des utilisateurs           | ✔️    | ✔️         | -       | -           |
+| supprimer des posts                   | ✔️    | ✔️         | -       | -           |
+| modifier des livres                   | ✔️    | ✔️         | ✔️      | -           |
+ mettre en ligne les pages couverture
diff --git a/locale/fr_FR/content/contributing/contributing.md b/locale/fr_FR/content/contributing/contributing.md
new file mode 100644
index 00000000..03c5c67b
--- /dev/null
+++ b/locale/fr_FR/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: Comment contribuer Date: 2021-04-12 Order: 1
+- - -
+
+Il y a plusieurs manières de contribuer à ce projet, pour tous les niveaux d'expertise technique.
+
+## Commentaires et demandes de fonctionnalités
+Sentez-vous bienvenu-es de relever des bugs, de soumettre des suggestions, des demandes pour des nouvelles fonctionnalités, et vos idées à propos du fonctionnement des choses, en les soumettant via [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Contribution au code
+Les contributions au code sont bienvenues ! Si vous ne savez pas par où commencer, regardez le tag ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22). Comme BookWyrm est un projet à petite échelle, sa structure n'est pas très formelle, mais nous avons une grande capacité pour du support personnalisé qui peut prendre plusieurs formes : poser vos questions au fur et à mesure, programmation en binôme, appels vidéo, etc, donc sentez-vous à l'aise de nous contacter.
+
+Si vous avez des questions à propos du projet ou des contributions, vous pouvez rejoindre le [chat Matrix de BookWyrm](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Traduction
+Vous parlez une langue autre que l'anglais ? BookWyrm a besoin de traductions ! Vous pouvez ajouter des traductions ou les modifier sur [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Soutien financier
+BookWyrm est un projet de passion, sans publicité, qui n’a aucune intention de chercher des financements ou des relations financières d’entreprises. Si vous souhaitez aider à maintenir le projet, vous pouvez devenir contributeur-ice de support via [Patreon](https://www.patreon.com/bookwyrm), [OpenCollective](https://opencollective.com/bookwyrm), ou faire un don ponctuel via [Paypal](https://paypal.me/oulipo).
diff --git a/locale/fr_FR/content/contributing/debug_toolbar.md b/locale/fr_FR/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffd8c34
--- /dev/null
+++ b/locale/fr_FR/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm a une branche qui est configurée pour exécuter la [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). Cette branche ne sera jamais fusionnée dans `main` et a quelques améliorations qui la font fonctionner avec la barre d'outils, mais qui sont dangereuses à utiliser dans un environnement étant ou approchant de la production. Pour utiliser cette branche, vous devez passer par quelques étapes pour que ça marche.
+
+## Configuration
+
+- Avec git, basez-vous la branche [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar)
+- Mettre à jour la branche depuis `main` en utilisant `git merge main`. La branche est mise à jour périodiquement, mais sera probablement en retard par rapport à la dernière version.
+- Reconstruisez les images Docker en utilisant `docker-compose up --build` pour vous assurer que la lib Debug Toolbar est installée depuis `requirements.txt`
+- Accédez à l'application depuis l'image `web` directement (au lieu d'y accéder via `nginx`) en utilisant le port `8000`
diff --git a/locale/fr_FR/content/contributing/install-dev.md b/locale/fr_FR/content/contributing/install-dev.md
new file mode 100644
index 00000000..eab346e7
--- /dev/null
+++ b/locale/fr_FR/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Environnement de développement Date: 2021-04-12 Order: 3
+- - -
+
+## Prérequis
+
+Ces instructions supposent que vous développez BookWyrm en utilisant Docker. Vous devrez [installer Docker](https://docs.docker.com/engine/install/) et [docker-compose](https://docs.docker.com/compose/install/) avant toute chose.
+
+## Mise en place de l'environnement de développement
+
+- Obtenez une copie de [la base code de BookWyrm depuis GitHub](https://github.com/bookwyrm-social/bookwyrm). Vous pouvez [créer un fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) du dépôt, puis [utiliser `git clone` pour télécharger le code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) sur votre ordinateur.
+- Allez dans le répertoire qui contient le code sur votre ordinateur, vous travaillerez désormais à partir de ce répertoire.
+- Configurez votre fichier de variables d'environnement de développement en copiant le fichier d'environnement d'exemple (`.env.example`) dans un nouveau fichier nommé `.env`. En ligne de commande, vous pouvez le faire en tapant :
+``` { .sh }
+cp .env.example .env
+```
+- Dans `.env`, modifiez la valeur de `DEBUG` en `true`
+- En option, vous pouvez utiliser un service comme [ngrok](https://ngrok.com/) pour configurer un nom de domaine, définissez ensuite dans votre fichier `.env` la valeur de `DOMAIN` en utilisant le nom de domaine généré par ngrok.
+
+- Configurez nginx pour le développement en copiant le fichier de configuration nginx pour le développement (`nginx/development`) vers un nouveau fichier nommé `nginx/default.conf` :
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Lancez l'application. En ligne de commande, exécutez :
+``` { .sh }
+./bw-dev build  # Construit les images docker
+./bw-dev setup  # Initialise la base de données et lance les migrations
+./bw-dev up     # Démarre les conteneurs docker
+```
+- Une fois la compilation terminée, vous pouvez accéder à l'instance sur `http://localhost:1333` et créer un utilisateur admin.
+
+Pour les curieux·ses : la commande `./bw-dev` est un simple script shell qui exécute divers autres outils ; au lieu des commandes ci-dessus, vous auriez pu exécuter `docker-compose build` ou `docker-compose up` directement si vous le souhaitez. `./bw-dev` les rassemble dans un seul endroit pour plus de commodité. Exécutez la commande sans argument pour obtenir une liste des commandes disponibles, lisez la [page de documentation](/command-line-tool.html) dédiée, ou ouvrez le fichier et examinez exactement ce que chaque commande fait !
+
+### Édition ou création du modèle de données
+
+Si vous créez ou modifiez un modèle, vous changerez probablement la structure de la base de données. Pour que ces changements aient des effets, vous devrez utiliser la commande `makemigrations` de Django pour créer un nouveau [fichier de migration Django](https://docs.djangoproject.com/en/3.2/topics/migrations), puis la commande `migrate` pour le migrer :
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Édition des fichiers statiques
+Chaque fois que vous éditez du CSS ou du JavaScript, vous devrez exécuter la commande `collectstatic` de Django pour que vos changements aient un effet :
+``` { .sh }
+./bw-dev collectstatic
+```
+
+Si vous avez [installé yarn](https://yarnpkg.com/getting-started/install), vous pouvez exécuter `yarn watch:static` qui va exécuter automatiquement le script précédent à chaque fois qu'un changement se produit dans le répertoire `bookwyrm/static`.
diff --git a/locale/fr_FR/content/contributing/style_guide.md b/locale/fr_FR/content/contributing/style_guide.md
new file mode 100644
index 00000000..dbaab249
--- /dev/null
+++ b/locale/fr_FR/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+Vous voulez contribuer au code de BookWyrm, c’est génial ! S'il y a un problème ouvert que vous souhaitez corriger, il est préférable de laisser un commentaire dans la conversation pour que le travail ne soit pas dupliqué. Essayez de limiter la portée des pull requests et de concentrer votre attention sur un seul sujet. Comme ça elle est plus facile à relire, et si une partie a besoin de changements elle ne retardera pas les autres parties.
+
+Si vous ne savez pas comment régler un problème, ou que vous n'êtes plus disponible pour le faire, ne vous en faites pas. Laissez simplement un commentaire sur la pull request et nous allons prendre le relais 💖.
+
+Les pull requests doivent valider tous les tests automatiques avant d'être fusionnées, ça inclut des vérifications de style, des linters globaux, un test de sécurité et des tests unitaires.
+
+## Lint
+
+### Global
+
+Nous utilisons [EditorConfig](https://editorconfig.org) pour maintenir la cohérence de l’indentation et des fins de lignes.
+
+### Python
+
+BookWyrm utilise le formateur de code [Black](https://github.com/psf/black) pour maintenir la cohérence de la base de code Python. Toutes les nouvelles pull requests sont vérifiées avec des actions GitHub, et vous pouvez corriger automatiquement les problèmes de style de code en exécutant `./bw-dev black`
+
+Le code est également vérifié avec Pylint via une action GitHub. Les avertissements de Pylint doivent être traités avant que les pull requests soient fusionnées, mais c'est une question de jugement si la suggestion doit être utilisée, ou l'avertissement supprimé. Pour supprimer un avertissement, ajoutez un commentaire à la fin ou sur la ligne précédant les avertissements : `# pylint: disable=nom-de-la-regle`
+
+### Gabarits (HTML)
+
+Votre pull request sera également vérifiée par le linter [curlylint](https://www.curlylint.org) pour les gabarits Django.
+
+### CSS
+
+Nous utilisons [stylelint](https://stylelint.io) pour vérifier toutes les règles CSS. Comme pour Pylint [vous pouvez désactiver le stylelint](https://stylelint.io/user-guide/ignore-code) pour une règle particulière, mais vous aurez besoin d'une bonne justification pour le faire.
+
+### JavaScript
+
+[ESLint](https://eslint.org) vérifie toute modification effectuée en JavaScript. Si ESLint n'aime pas votre JavaScript (même fonctionnel), vérifiez le message linter pour le problème exact.
+
+## Design inclusif
+
+BookWyrm aspire à être aussi inclusif et accessible que possible.
+
+Lorsque vous contribuez du code, vérifiez la [checklist Inclusive Web Design](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) avant de proposer votre pull request. Pour des conseils sur l'accessibilité, [A11Y-101](https://www.a11y-101.com/development) est également une ressource utile. Pour plus d'informations sur la manière de rendre vos gabarits de page multilingues, voir [la section Traductions](/translations.html).
+
+Quelques particularités à garder en tête pour la contribution au code de BookWyrm :
+
+### Formulaires
+
+* N'utiliser `input[type="checkbox"]` ou `input[type="radio"]` qu’à l'intérieur de `<label>`
+* Si vous ne placez pas les cases à cocher et les boutons radio à l'intérieur du `<label>`, le `<label>` doit être placé _après_ l'élément auquel il se rapporte
+
+### Boutons et Liens
+
+* Utilisez un élément `<button>` pour tout ce qui a pour but de déclencher une action JavaScript (par ex. cacher ou révéler un formulaire) ou envoyer une requête `POST` (par ex. soumettre un formulaire)
+* Utilisez un élément `<a>` pour tout ce qui déclenche une requête `GET`. Habituellement, un lien (`<a>`) ne doit pas avoir l’apparence d’un bouton (`class="button"`), bien qu'il y ait quelques exceptions comme les boutons "Annuler". En cas de doute, demandez conseil dans votre pull request
diff --git a/locale/fr_FR/content/contributing/translation.md b/locale/fr_FR/content/contributing/translation.md
new file mode 100644
index 00000000..0d0dbf3e
--- /dev/null
+++ b/locale/fr_FR/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contribuer aux traductions
+
+Vous pouvez rejoindre le projet de traduction de BookWyrm à l'adresse [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Langage non-genré / inclusif
+
+Dans la mesure du possible, les traductions de BookWyrm doivent utiliser une langue non-genrée. Cela s'applique même si une langue désigne le masculin comme genre neutre par défaut, ou si elle utilise quelque chose de similaire à "il/elle". Il est également important que les traductions soient claires, concises et lisibles pour un lecteur d'écran, et parfois ces objectifs sont en conflit ; il n'y a pas de réponse parfaite et unique, la solution dépend de la langue.
+
+En tant que principe directeur, essayez de donner une valeur plus élevée à un langage inclusif et neutre par rapport au langage formel correct ou aux guides de style officiellement approuvés. En anglais par exemple, de nombreux guides de style requièrent qu’un pronom singulier "she" ou "he" soit utilisé en référence à un individu, mais il est préférable dans BookWyrm d'utiliser le pronom singulier non-genré "they" à la place.
+
+Si vous ne savez pas comment aborder un problème de traduction, commentez la traduction ou ouvrez un [sujet de discussion](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) pour répondre aux questions plus larges.
+
+## Rendre les gabarits traduisibles
+
+Bookwyrm profite de la fonctionnalité de traduction de Django pour permettre au contenu de la page de changer en fonction de la langue d'affichage préférée du navigateur. La documentation de Django [fournit une explication utile](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) du fonctionnement, voilà la version courte :
+
+* tous les textes du gabarit doivent inclure des balises de traduction
+* ajoutez `{% load i18n %}` en haut de votre gabarit pour activer les traductions
+* si le bloc de texte est du texte littéral, vous pouvez utiliser la balise `{% trans %}`
+* Si le bloc de texte inclut des variables, vous devez utiliser la paire de balises `{% blocktrans %}` et `{% endblocktrans %}`. Si vous incluez des espaces ou des sauts de ligne, utilisez `trimmed` pour les supprimer automatiquement lorsque le fichier de langue est généré : `{% blocktrans trimmed %}`
+
+### Exemples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/fr_FR/content/index.md b/locale/fr_FR/content/index.md
new file mode 100644
index 00000000..fa288bfc
--- /dev/null
+++ b/locale/fr_FR/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title : Bienvenue Date : 2021-04-13
+- - -
+
+Bookwyrn est un réseau social qui sert à suivre vos lectures, discuter des livres, écrire des commentaires et trouver vos prochaines lectures. La Fédération (à vérifier) permet aux usager-e-s de BookWyrm de joindre des petites communautés de confiance qui peuvent communiquer ensemble, ainsi qu'avec d'autres services d'ActivityPub, comme Mastodon et Pleroma.
+
+## Caractéristiques
+Comme le projet en est encore à ses débuts, ses caractéristiques se développent chaque jour, et il y a encore la place pour des suggestions et des idées. Ouvrez un [problème](https://github.com/bookwyrm-social/bookwyrm/issues) pour commencer la conversation!
+
+- Postez à propos des livres
+    - Composez des commentaires, avec ou sans ratings, qui sont rassemblées sur la page "livre"
+    - Composez d'autres types de statuts à propos des livres, tels que :
+        - Des commentaires à propos d'un livre
+        - Des citations ou des extraits
+    - Répondez aux statuts des autres
+    - Voyez les commentaires d'un livre venant de plusieurs instances connectées de BookWyrm
+    - Différenciez les commentaires et ratings locaux et fédérés dans votre fil d'activité
+- Suivez votre activité de lecture
+    - Organisez vos livres dans les sections par défault "à lire", "présentement en train de lire" et "lu"
+    - Créez des sections personnalisées
+    - Enregistrez les dates du début et de la fin de la lecture et mettez à jour votre progression à mesure
+    - Tenez au courant vos abonné-e-s à propos de votre activité (optionnellement, et avec des contrôles de confidentialité précis)
+    - Créez des listes de livres qui peuvent être soit ouvertes aux suggestions de tout le monde, soit séléctionnées, soit modifiée seulement par le/la créateur-ice
+- Fédération avec ActivityPub
+    - Diffusez et recevez les statuts des utilisateur-ice-s et leur activité
+    - Partagez les données des livres entre les instances pour créer un réseau de métadonnées
+    - Identifiez les livres qui sont partagés entre les instances et rassemblez le contenu similaire
+    - Suivez et interagissez avec les utilisateur-ice-s des différentes instances de BookWyrm
+    - Fonctionnez de manière connectée avec des services d'ActivityPub autre que BookWyrm (présentement, Mastodon est supporté)
+- Contrôle de confidentialité précis
+    - Niveaux de confidentialité privé, "abonné-e-s uniquement" et public pour les posts, les catégories et les listes
+    - Option pour les utilisateur-ice-s d'approuver les abonné-e-s manuellement
+    - Permet de bloquer ou marquer pour modération
diff --git a/locale/fr_FR/content/pages/index.md b/locale/fr_FR/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/fr_FR/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/fr_FR/content/running_bookwyrm/cli.md b/locale/fr_FR/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..33ce8c00
--- /dev/null
+++ b/locale/fr_FR/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Outils en ligne de commande Date: 2021-11-11 Order: 9
+- - -
+
+Les développeur·ses de BookWyrm et les gestionnaires d'une instance peuvent utiliser le script `bw-dev` pour des tâches courantes. Cela peut simplifier vos commandes en les rendant plus courtes, plus faciles à mémoriser et diminuer le risque d'erreur.
+
+Une fois que vous avez installé Bookwyrm [en production](installing-in-production.html) ou [en développement](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), vous pouvez exécuter le script à partir de la ligne de commande avec `./bw-dev` suivi de la sous-commande que vous voulez exécuter.
+
+## Raccourcis Docker
+
+### bash
+
+Ouvez une session interactive `bash` dans le conteneur docker `web`.
+
+### build
+
+Équivalent à `docker-compose build`.
+
+### dbshell
+
+Ouvrir un shell de base de donnée Postgres interactif. On espère que vous savez ce que vous faites.
+
+### runweb args
+
+Exécuter une commande arbitraire (représentée ci-dessus par `args`) dans le conteneur `web`.
+
+Équivalent à `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Exécuter une commande arbitraire dans le conteneur `web` (représenté ci-dessus par `args`) avec les ports exposés. Ceci est utile si vous voulez exécuter des tests `pdb` parce que `runweb` n'affiche pas l'invite de commande `pdb`.
+
+Équivalent à `docker-compose run --rm web`.
+
+### shell
+
+Ouvrir un shell Django interactif à l'intérieur du conteneur docker `web`. Cela sert à exécuter directement des commandes Django.
+
+### up [args]
+
+Démarrer ou redémarrer des conteneurs Docker, en incluant optionnellement des arguments (représentés ci-dessus par `args`). Équivalent à `docker-compose up --build [args]`
+
+## Gérer la base de données
+
+### initdb
+
+Initialiser une base de données.
+
+### makemigrations [appname migration number]
+
+_Cette commande n'est pas disponible sur la branche de `production`_.
+
+Exécute la commande Django `makemigrations` à l'intérieur du conteneur Docker. Si vous avez changé la structure de la base de donnée dans une branche de développement, vous allez devoir exécuter cette commande pour que vos changements s'appliquent. Facultativement, vous pouvez préciser quelle migration exécuter, par exemple `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Exécute la commande Django `migrate` à l'intérieur de votre conteneur Docker. Il faut toujours faire ceci après `makemigrations`.
+
+### resetdb
+
+_Cette commande n'est pas disponible sur la branche de `production`_.
+
+Réinitialise la base de données. **Cette commande va supprimer votre base de données Bookwyrm en entier**, et va ensuite initialiser une nouvelle base de donnée et effectuer toutes les migrations. Vous devriez supprimer tous les fichiers de migration récents que vous ne voulez pas exécuter _avant_ d'exécuter `resetdb`.
+
+## Gérer une instance de Bookwyrm
+
+### compile_themes
+
+Compile tous les thèmes BookWyrm, qui sont des fichiers `*.scss` répertoriés dans `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migre les ressources statiques vers un conteneur Docker ou un compartiment compatible S3, selon le contexte.
+
+### generate_preview_images
+
+Génère des images de prévisualisation pour le site, les utilisateur-ice-s et les livres. Si vous avez une grande base de données, cela peut prendre un temps conséquent. Voir [Optional features : Générer les images de prévisualisation](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Supprime les images de prévisualisation pour les comptes externes. Voir [Optional Features : Supprimer les images de prévisualisation pour les comptes externes](/optional_features.html)
+
+### generate_thumbnails
+
+Génère les miniatures pour les couvertures de livres.
+
+### populate_streams args
+
+Rafraîchit les flux Redis (flux utilisateurs). Vous n'aurez généralement pas besoin d'exécuter cela à moins qu'une erreur n'efface vos flux utilisateurs pour une raison ou une autre. Vous pouvez préciser quel flux en particulier en utilisant l'argument `--stream`.
+
+### populate_list_streams
+
+Rafraîchit le cache Redis des listes. Vous n'aurez généralement pas besoin d'exécuter cela à moins qu'une erreur n'efface les listes de vos utilisateur-ice-s pour une raison ou une autre.
+
+### populate_suggestions
+
+Rafraîchit la liste des comptes suggérés pour tous-tes les utilisateur-ice-s. Vous pouvez exécuter cela afin d'actualiser les suggestions.
+
+### restart_celery
+
+Redémarre le conteneur Docker `celery_worker`.
+
+### update
+
+Lors de changements sur la branche `production`, vous pouvez mettre à jour votre instance sans la rendre indisponible.
+
+Cette commande `git pull` les dernières mises à jour de la branche `production` , construit des images docker si nécessaire, exécute les migrations Django, met à jour les fichiers statiques et redémarre tous les conteneurs Docker.
+
+### admin_code
+
+Récupère le code admin utilisé pour enregistrer l'admin initial sur une nouvelle instance BookWyrm.
+
+## Configuration du stockage compatible S3
+
+Par défaut, BookWyrm stocke localement les ressources statiques (favicon, avatar par défaut, etc.) et les médias (avatars, couvertures de livres, etc.), mais vous pouvez utiliser un service de stockage externe pour ces fichiers. BookWyrm utilise django-storages pour gérer le stockage externe, tel que les services compatibles S3, Apache Libcloud ou SFTP.
+
+Voir [External Storage](/external-storage.html) pour plus d'informations.
+
+### copy_media_to_s3
+
+Migre tous les médias téléchargés d'une instance BookWyrm existante vers un compartiment compatible S3. À utiliser pour un premier téléchargement vers un compartiment vide.
+
+### sync_media_to_s3
+
+Synchronise les médias nouvellement créés ou modifiés d'une instance BookWyrm existante vers un compartiment compatible S3. À utiliser pour s'assurer que tous les fichiers locaux ont été téléchargés vers un compartiment existant.
+
+### set_cors_to_s3 filename
+
+Copie un fichier JSON de règles CORS vers un compartiment S3, où `filename` est le nom de votre fichier JSON (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Développement et test
+
+_Ces commandes ne sont pas disponibles sur la branche `production`_.
+
+### black
+
+BookWyrm utilise le formateur de code [Black](https://github.com/psf/black) pour assurer la cohérence du code Python. Exécutez `black` avant de valider vos modifications afin d'éviter que la tâche `pylint` pour votre pull request n'échoue et ne vous rende triste.
+
+### prettier
+
+BookWyrm utilise [Prettier](https://prettier.io/) pour assurer la cohérence du code JavaScript. Exécutez `prettier` avant de valider vos modifications de scripts afin de formater automatiquement votre code.
+
+### stylelint
+
+BookWyrm utilise [Stylelint](uhttps://stylelint.io/) pour assurer la cohérence des fichiers CSS. Exécutez `stylelintprettier` avant de valider vos modifications de scripts afin de formater automatiquement votre code.
+
+### formatters
+
+Cette commande exécute tous les formateurs de code (`black`, `prettier`, et `stylelint`) à la suite.
+
+### clean
+
+Supprime tous les conteneurs Docker arrêtés.
+
+Correspond à :
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Génère les fichiers de messages pour toutes les chaînes de traduction. Après avoir exécuté `makemessages`, vous devez exécuter `compilemessages` pour compiler les traductions. Voir [makemessages dans Django](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compile les fichiers de traduction. Voir [compilemessages dans Django](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Exécute les tests avec `pytest`.
+
+### deactivate_2fa
+
+Désactive l'authentification à deux facteurs pour un utilisateur donné.
+
+### manual_confirm
+
+Confirme l'adresse e-mail d'un-e utilisateur-ice et l'active.
diff --git a/locale/fr_FR/content/running_bookwyrm/external-storage.md b/locale/fr_FR/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..c6bc4132
--- /dev/null
+++ b/locale/fr_FR/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: Stockage Externe Date: 2021-06-07 Order: 7
+- - -
+
+Par défaut, BookWyrm stocke localement les ressources statiques (favicon, avatar par défaut, etc.) et les médias (avatars, couvertures de livres, etc.), mais vous pouvez utiliser un service de stockage externe pour ces fichiers. BookWyrm utilise `django-storages` pour gérer le stockage externe, tel que les services compatibles S3, Apache Libcloud ou SFTP.
+
+## Services compatibles S3
+
+### Configuration
+
+Créez un compartiment auprès du service compatible S3 de votre choix, ainsi qu'un ID de clé d'accès et une clé d'accès secrète. Ceux-ci peuvent être auto-hébergés, tels que [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) ou [MinIO](https://min.io/) (GNU AGPL v3.0), ou commerciaux ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)...).
+
+Ce guide a été testé avec Object Storage de Scaleway. Si vous utiliser un autre service, partagez votre expérience (en particulier si vous avez dû prendre des mesures différentes) en ouvrant un ticket sur le dépôt de la [Documentation de BookWyrm](https://github.com/bookwyrm-social/documentation).
+
+### Ce qui vous attend
+
+Si vous installez une nouvelle instance de BookWyrm, les étapes seront :
+
+- Configurer votre service de stockage externe
+- Activer le stockage externe sur BookWyrm
+- Démarrer votre instance BookWyrm
+- Mettre à jour le connecteur de l'instance
+
+Si votre instance est déjà en place, et que des images ont été téléchargées sur le stockage local, les étapes seront :
+
+- Configurer votre service de stockage externe
+- Copier vos médias locaux sur le stockage externe
+- Activer le stockage externe sur BookWyrm
+- Redémarrer votre instance BookWyrm
+- Mettre à jour le connecteur de l'instance
+
+### Paramètres de BookWyrm
+
+Modifiez votre fichier `.env` en décommentant les lignes suivantes :
+
+- `AWS_ACCESS_KEY_ID`: votre ID de clé d'accès
+- `AWS_SECRET_ACCESS_KEY`: votre clé d'accès secrète
+- `AWS_STORAGE_BUCKET_NAME`: le nom de votre compartiment
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` pour AWS, `"fr-par"` pour Scaleway ou `"nyc3"` pour Digital Ocean
+
+Si votre service compatible S3 est Amazon AWS, la configuration devrait être terminée. Pour les autres services, vous aurez à décommenter les lignes suivantes :
+
+- `AWS_S3_CUSTOM_DOMAIN`: le domaine qui va mettre à disposition les fichiers, par exemple `"exemple-nom-compartiment-s3.fr-par.scw.cloud"` ou `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: le point de terminaison d'API S3, par exemple `"https://s3.fr-par.scw.cloud"` ou `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copie de vos médias locaux sur le stockage externe
+
+Si votre instance BookWyrm est déjà en cours d'exécution et que des fichiers médias ont été téléchargés (avatars d'utilisateur, couvertures de livres…), vous devrez copier les médias téléchargés sur votre compartiment.
+
+Cette tâche est effectuée avec la commande :
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Activation du stockage externe sur BookWyrm
+
+Pour activer le stockage externe compatible S3, vous devrez modifier votre fichier `.env` en changeant la valeur de la propriété `USE_S3` de `false` à `true`:
+
+```
+USE_S3=true
+```
+
+Si votre stockage externe est accessible via HTTPS (la plupart le sont actuellement), vous devrez également vous assurer que `USE_HTTPS` est défini à `true`, afin que les images soient téléchargées via HTTPS :
+
+```
+USE_HTTPS=true
+```
+
+#### Ressources statiques
+
+Vous devrez ensuite exécuter la commande suivante, afin de copier les ressources statiques vers votre compartiment S3 :
+
+```bash
+./bw-dev collectstatic
+```
+
+#### Paramètres CORS
+
+Une fois que les ressources statiques ont été recueillies, vous devrez configurer CORS pour votre compartiment.
+
+Certains services tels que Digital Ocean mettent à disposition une interface pour cette étape, voir [Documentation de Digital Ocean: Comment configurer CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+Si votre service ne met pas d'interface à disposition, vous pouvez tout de même configurer CORS via la ligne de commande.
+
+Créez un fichier nommé `cors.json` avec le contenu suivant :
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Remplacez `MY_DOMAIN_NAME` par le(s) nom(s) de domaine de votre instance.
+
+Exécutez alors la commande suivante :
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+Une absence de retour signifie que cela a fonctionné.
+
+Si vous installez une nouvelle instance de BookWyrm, vous pouvez retourner aux instructions de configuration dès maintenant. Dans le cas contraire, continuez à lire.
+
+### Redémarrage de votre instance
+
+Une fois la copie des fichiers médias effectuée et les ressources statiques recueillies, vous pouvez charger la nouvelle configuration `.env` et redémarrer votre instance avec la commande :
+
+```bash
+./bw-dev up -d
+```
+
+Si tout se passe bien, votre stockage a été modifié sans arrêt du serveur. Si des polices sont manquantes (et que la console JS de votre navigateur génère des alertes à propos de CORS), quelque chose s'est mal passé [à cette étape](#cors-settings). Dans ce cas, il peut être bon de vérifier les en-têtes d'une requête HTTP pour un fichier sur votre compartiment :
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Remplacez `MY_DOMAIN_NAME` par votre nom de domaine de l'instance, `BUCKET_URL` avec l'URL de votre compartiment, et le chemin du fichier par n'importe quel autre chemin valide sur votre compartiment.
+
+Si vous voyez un message, en particulier un message commençant par `<Error><Code>CORSForbidden</Code>`, cela n'a pas fonctionné. Si vous ne voyez aucun message, cela a fonctionné.
+
+Pour une instance en cours d'utilisation, il peut y avoir quelques fichiers qui ont été créés localement pendant l'intervalle entre la migration des fichiers vers le stockage externe et le redémarrage de l'application. Pour s'assurer que tous les fichiers restants sont téléchargés sur le stockage externe une fois basculé dessus, vous pouvez utiliser la commande suivante, qui copiera uniquement les fichiers qui ne sont pas déjà présents sur le stockage externe :
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Mise à jour du connecteur de l'instance
+
+*Remarque : Vous pouvez sauter cette étape si vous utilisez une version à jour de BookWyrm; en septembre 2021 le « self connector » a été retiré dans [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+Afin que la bonne URL soit utilisée lors de l'affichage des résultats de recherche locale de livres, nous devons modifier la valeur de la racine d'URL des images de couverture.
+
+Les données du connecteur sont accessibles via l'interface d'administration de Django, située à l'url `http://MY_DOMAIN_NAME/admin`. Le connecteur pour votre propre instance est le premier enregistrement dans la base de données, vous pouvez donc accéder au connecteur via cette URL : `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+Le champ _Covers url_ est défini par défaut comme `https://MY_DOMAIN_NAME/images`, vous devez le changer en `https://S3_STORAGE_URL/images`. Ensuite, cliquez sur le bouton _Enregistrer_.
+
+Vous devrez mettre à jour la valeur de _Covers url_ chaque fois que vous changez l'URL de votre stockage.
diff --git a/locale/fr_FR/content/running_bookwyrm/install-prod-dockerless.md b/locale/fr_FR/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..f1ed420a
--- /dev/null
+++ b/locale/fr_FR/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installation sans Docker
+Date: 2022-10-02
+Order: 2
+---
+
+Ce projet est encore jeune et n'est pas, pour le moment, très stable, faites preuve de prudence lors de son utilisation en production. Ce mode d'installation nécessite plus de travail, et est donc à réserver aux administrateurs plus expérimentés. L'installation via docker est recommandée Cette méthode d'installation suppose que vous ayez déjà configuré ssl, avec les certificats à votre disposition
+
+## Configuration du serveur
+- Obtenez un nom de domaine et configurez le DNS pour votre serveur. Vous devez faire pointer les serveurs de noms de domaine de votre fournisseur DNS vers le serveur où vous allez héberger BookWyrm. Voici les instructions pour [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Configurez votre serveur avec des pare-feu appropriés pour l'exécution d'une application web (ces instructions ont été testées avec Ubuntu 20.04). Voici les instructions pour [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Configurez un service de messagerie (tel que [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) et les paramètres SMTP/DNS appropriés. Utilisez la documentation du service pour la configuration de votre DNS
+- Installez les dépendances. Sous debian, cela pourrait ressembler à `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Installez et configurez BookWyrm
+
+La branche `production` de BookWyrm contient un certain nombre d'outils qui ne sont pas sur la branche `main`, prévus pour fonctionner en production, tels que des modifications de `docker-compose` pour mettre à jour les commandes par défaut ou la configuration des conteneurs, ou des modifications spécifiques à des containers pour activer des fonctionnalités telles que SSL ou des sauvegardes régulières. Tous ces changements n'ont pas nécessairement un impact sur l'installation sans docker, mais la branche `production` est néanmoins recommandée
+
+Instructions pour l'exécution de BookWyrm en production sans Docker :
+
+- Créez et déplacez vous dans le répertoire où vous voulez installer BookWyrm. Par exemple `/opt/bookwyrm` : `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Téléchargez le code de l'application : `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Passez sur la branche `production` : `git checkout production`
+- Créez votre fichier de variables d'environnement, `cp .env.example .env`, et mettez à jour ce qui suit :
+    - `SECRET_KEY` | Une chaîne de caractères secrète, difficile à deviner
+    - `DOMAIN` | Votre domaine web
+    - `POSTGRES_PASSWORD` | Utilisez un mot de passe sécurisé pour la base de données
+    - `POSTGRES_HOST` | Mettez à `localhost` (la machine exécutant votre bdd)
+    - `POSTGRES_USER` | Mettez à `bookwyrm` (recommendé) ou une valeur personnalisée (configurée plus tard)
+    - `POSTGRES_DB` | Définir à `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Laissez à blanc (adapté pour une machine locale avec un pare-feu)
+    - `REDIS_ACTIVITY_HOST` | Mettez à `localhost` (la machine exécutant redis)
+    - `REDIS_BROKER_PASSWORD` | Laissez à blanc (adapté pour une machine locale avec un pare-feu)
+    - `REDIS_BROKER_HOST` | Mettez à `localhost` (la machine exécutant redis)
+    - `EMAIL_HOST_USER` | L'adresse d'expéditeur de laquelle votre application enverra des emails
+    - `EMAIL_HOST_PASSWORD` | Le mot de passe fourni par votre service d'emailing
+- Configurez nginx
+    - Copiez le fichier server_config vers le répertoire conf.d de nginx : `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Faites une copie du modèle de configurationde site de production et mettez le en place dans nginx&nbsp;: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Mettez à jour le fichier `bookwyrm.conf` de nginx :
+        - Remplacez `your-domain.com` par votre nom de domaine partout dans le fichier (y compris dans les lignes qui sont pour l'instant commentées)
+        - Remplacez `/app/` avec votre chemin d'installation `/opt/bookwyrm/` partout dans le fichier (y compris dans les commentaires)
+        - Décommentez les lignes 18 à 67 pour activer la redirection vers HTTPS. Vous devriez avoir deux blocs `server` actifs
+        - Remplacez les chemins de `ssl_certificate` et `ssl_certificate_key` par ceux de votre fullchain et privkey
+        - Modifiez la ligne 4 en `server localhost:8000`. Vous pouvez choisir un port différent si vous le souhaitez
+        - Si vous exécutez un autre serveur web sur votre machine hôte, vous devrez suivre [les instructions pour serveur mandataire inverse](/reverse-proxy.html)
+    - Activez la configuration nginx : `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Rechargez la configuration nginx : `systemctl reload nginx`
+- Configurez l'environnement virtuel python
+    - Créez le répertoire venv python dans votre répertoire d'installation : `mkdir venv` `python3 -m venv ./venv`
+    - Installez les dépendances python de bookwyrm avec pip : `./venv/bin/pip3 install -r requirements.txt`
+- Créez la base de données postgresql de bookwyrm. Assurez-vous de remplacer le mot de passe par ce que vous avez défini dans la configuration `.env` :
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrer le schéma de la base de données en exécutant `venv/bin/python3 manage.py migrate`
+- Initialisez la base de données en exécutant `venv/bin/python3 manage.py initdb`
+- Générez les static en exécutant `venv/bin/python3 manage.py collectstatic --no-input`
+- Si vous souhaitez utiliser un stockage externe pour les ressources statiques et les fichiers multimédias (comme un service compatible S3), [suivez les instructions](/external-storage.html) jusqu'à être redirigé ici
+- Créez et configurez votre utilisateur `bookwyrm`
+    - Créez l'utilisateur système bookwyrm: `useradd bookwyrm -r`
+    - Modifiez l’appartenance du répertoire d’installation de bookwyrm : `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - Vous devriez maintenant exécuter les commandes liées à bookwyrm avec l'utilisateur de bookwyrm : `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Générez le code administrateur avec `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, et copiez le pour l'utiliser lors de la création du compte administrateur.
+- Vous pouvez obtenir ce code à n'importe quel moment en ré-exécutant la commande. Voici un exemple de sortie :
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Créez et configurez le script d'exécution
+    - Créez un fichier nommé dockerless-run.sh et remplissez le avec le contenu suivant
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Remplacez `/opt/bookwyrm` par votre répertoire d'installation
+    - Remplacez `8000` par votre numéro de port personnalisé
+    - Flower a été ici désactivé parce qu'il n'est pas configuré automatiquement avec le mot de passe défini dans le fichier `.env`
+- Vous pouvez à présent exécuter BookWyrm avec&nbsp;: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- L'application devrait s'exécuter sur votre domaine. Lorsque vous chargez le domaine, vous devriez obtenir une page de configuration qui confirme vos paramètres d'instance, ainsi qu'un formulaire pour créer un compte d'administrateur. Utilisez votre code d'administration pour vous inscrire.
+- Vous pouvez configurer BookWyrm pour qu'il s'exécute automatique à l'aide d'un service systemd. Voici un exemple :
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+Vous devrez configurer une tâche Cron pour que le service démarre automatiquement au redémarrage du serveur.
+
+Félicitations ! Vous y êtes arrivé !! Configurez votre instance comme vous le souhaitez.
+
+## Participer
+
+Voir [Participer](https://joinbookwyrm.com/get-involved/) pour plus de détails.
diff --git a/locale/fr_FR/content/running_bookwyrm/install-prod.md b/locale/fr_FR/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..36a9b896
--- /dev/null
+++ b/locale/fr_FR/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installation en Production Date: 2021-05-18 Order: 1
+- - -
+
+Ce projet est encore jeune et n'est pas, pour le moment, très stable, faites preuve de prudence lors de son utilisation en production.
+
+## Configuration du serveur
+- Obtenez un nom de domaine et configurez le DNS pour votre serveur. Vous devez faire pointer les serveurs de noms de domaine de votre fournisseur DNS vers le serveur où vous allez héberger BookWyrm. Voici les instructions pour [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Configurez votre serveur avec un pare-feu approprié pour les applications web (cette page de documentation est testée avec Ubuntu 20.04). Voici les instructions pour [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Configurez un service mail (comme [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) et les paramètres SMTP/DNS appropriés. Utilisez la documentation du service pour configurer vos DNS
+- [Installez Docker et docker-compose](https://docs.docker.com/compose/install/)
+
+## Installation et configuration de BookWyrm
+
+La branche `production` de BookWyrm contient nombre d'outils qui ne sont pas sur la branche `main` prévus pour fonctionner en production. Par exemple des changements dans `docker-compose` pour mettre à jour les commandes par défaut ou la configuration des conteneurs et des changements individuels à la configuration des conteneurs pour activer des choses comme SSL ou les sauvegardes régulières.
+
+Instructions pour lancer BookWyrm en production :
+
+- Récupérez le code de l'application : `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Basculez sur la branche `production` : `git checkout production`
+- Créez votre fichier de variables d'environnement, `cp .env.example .env`, et mettez à jour les valeurs suivantes :
+    - `SECRET_KEY` | Une chaîne de caractères, difficile à deviner
+    - `DOMAIN` | Votre nom domaine
+    - `EMAIL` | L'adresse mail qui sera utilisée pour la vérification certbot
+    - `POSTGRES_PASSWORD` | Un mot de passe sécurisé pour la base de données
+    - `REDIS_ACTIVITY_PASSWORD` | Un mot de passe sécurisé pour le Redis d'activités
+    - `REDIS_BROKER_PASSWORD` | Un mot de passe sécurisé pour le Redis de files d'attente
+    - `FLOWER_USER` | Votre propre nom d'utilisateur·ice pour accéder à la surveillance des files d'attente Flower
+    - `FLOWER_PASSWORD` | Votre propre mot de passe sécurisé pour accéder à la surveillance des files d'attente Flower
+    - `EMAIL_HOST_USER` | L'adresse "From" que l'application utilisera pour l'envoi de mail
+    - `EMAIL_HOST_PASSWORD` | Le mot de passe fourni par votre service mail
+- Configuration de Nginx
+    - Faites une copie du modèle de configuration de production pour nginx `cp nginx/production nginx/default.conf`
+    - Mettez à jour `nginx/default.conf` :
+        - Remplacez `your-domain.com` par votre nom de domaine partout dans le fichier (y compris dans les lignes qui sont commentées)
+        - Si vous n'utilisez pas le sous-domaine `www`, retirez le domaine www.your-domain.com de la partie `server_name` dans le premier bloc server de `nginx/default.conf` et retirez l'argument `-d www.${DOMAIN}` à la fin de la commande `certbot` dans `docker-compose.yml`.
+        - Si vous faites fonctionner un autre serveur web sur votre machine, vous devez suivre les [instructions de proxy inverse](/reverse-proxy.html)
+- Initialisez la base de données avec `./bw-dev migrate`
+- Lancez l'application (cela devrait aussi créer un certificat SSL avec Certbot pour votre nom de domaine) avec `docker-compose up --build`, et assurez-vous que toutes les images sont bien construites
+    - Si vous faites fonctionner d'autres services sur votre machine, vous pourriez rencontrer des erreurs avec certains services tentant de s'attribuer un port. Consultez le [guide de dépannage](#port_conflicts) pour avoir des conseils de résolution à ce sujet.
+- Une fois que les images docker sont construites avec succès, arrêtez le processus avec `CTRL-C`
+- Configurez la redirection HTTPS
+    - Dans `docker-compose.yml`, commentez la commande certbot active, qui installe le certificat, et décommentez la ligne suivante, qui configure le renouvellement automatique.
+    - Dans `nginx/default.conf`, décommentez les lignes 18 à 50 pour activer la redirection vers HTTPS. Vous devriez avoir deux blocs `server` activés
+- Configurez une tâche `cron` pour garder le certificat à jour (les certificats Lets Encrypt expire après 90 jours)
+    - Tapez `crontab -e` pour éditer le fichier cron de votre machine
+    - ajoutez une ligne pour tenter un renouvellement une fois par jour : `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- Si vous souhaitez utiliser un stockage externe pour les fichiers statiques et médias (comme un service compatible S3), [suivez les instructions](/external-storage.html) jusqu'à ce que celles-ci indiquent de revenir ici
+- Initialisez l'application avec `./bw-dev setup` et copiez le code admin afin de l'utiliser pour créer votre compte admin.
+    - La sortie de `./bw-dev setup` devrait se terminer par votre code admin. Vous pouvez récupérer votre code à tout moment en lançant `./bw-dev admin_code` depuis la ligne de commande. Voici un exemple du résultat :
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Lancez docker-compose en arrière-plan avec : `docker-compose up -d`
+- L'application devrait fonctionner sur votre nom de domaine. Quand vous chargez le nom de domaine, vous devriez arriver sur une page de configuration pour confirmer les paramètres de votre instance et un formulaire pour créer un compte admin. Utilisez votre code admin pour vous enregistrer.
+
+Bravo ! Vous avez réussi !! Configurez votre instance comme vous le souhaitez.
+
+
+## Sauvegardes
+
+Le service db de BookWyrm créer une copie de sauvegarde de sa base de données dans le dossier `/backups` chaque jour à minuit UTC. Les sauvegardes sont nommées `backup__%Y-%m-%d.sql`.
+
+Le service db possède un script optionnel pour nettoyer périodiquement le dossier des sauvegardes afin que les sauvegardes récentes soient conservées ainsi que les sauvegardes mensuelles et hebdomadaires. Pour activer ce script :
+
+- Décommentez la dernière ligne dans `postgres-docker/cronfile`
+- Reconstruisez votre instance `docker-compose up --build`
+
+Vous pouvez copier les sauvegardes depuis le volume de sauvegardes vers votre machine avec `docker cp` :
+
+- Lancez `docker-compose ps` pour vérifier le nom du service db (probablement `bookwyrm_db_1`).
+- Lancez `docker cp <container_name>:/backups <host machine path>`
+
+## Conflits de port
+
+BookWyrm a plusieurs services fonctionnant sur leurs ports par défaut. Cela veut dire que, en fonction de ce qui fonctionne sur votre machine, vous pouvez rencontrer des erreurs à la construction et au lancement de BookWyrm lorsque les tentatives d'utiliser ces ports échouent.
+
+Si cela arrive, vous devrez changer votre configuration pour lancer ces services sur des ports différents. Cela peut demander des modifications dans les fichiers suivants :
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (Vous créer ce fichier vous-même durant la configuration)
+
+Si vous avez déjà un serveur web sur cette machine, vous devrez configurer un proxy inverse.
+
+## Restez à l'affût
+
+BookWyrm étant un projet jeune, nous travaillons toujours pour planifier une version stable et il y a beaucoup de bogues et de changements cassants. Il y a une équipe GitHub qui peut être mentionnée quand quelque chose d'important à propos d'une mise à jour se passe et que vous pouvez rejoindre en partageant votre nom d'utilisateur·ice GitHub. Il y a plusieurs manières d'entrer en contact :
+
+ - Ouvrir une issue ou une pull request pour ajouter votre propre instance à la [liste officielle](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Contacter le projet sur [Mastodon](https://tech.lgbt/@bookwyrm) ou [envoyer un mail au mainteneur·ice](mailto:mousereeve@riseup.net) directement avec votre nom d'utilisateur·ice GitHub
+ - Rejoindre le salon de discussion [Matrix](https://matrix.to/#/#bookwyrm:matrix.org)
diff --git a/locale/fr_FR/content/running_bookwyrm/moderation.md b/locale/fr_FR/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..fe096314
--- /dev/null
+++ b/locale/fr_FR/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Modération
+- - -
+
+## Bloquage
+Les utilisateur-ices ont l'option de bloquer d'autres utilisateur-ices sans l'intervention d'un-e modérateur⸳ice. Dans la vue d'administration « Instances fédérées », les administrateur-ices peuvent voir combien d'utilisateur-ices d'une instance ont été bloqué-es par des utilisateur-ices locaux-ales.
+
+## Signalements
+Les utilisateur-ices peuvent signaler les statuts ou les utilisateur-ices à partir du menu « Plus d’options » dans le bas de page des messages et des boutons « S’abonner »/« Se désabonner » pour les utilisateur-ices. Lorsqu'un signalement est effectué, tous les utilisateur-ices ayant les droits d'administration recevront une notification.
+
+Lorsqu'un signalement est effectué, les modérateur-ices peuvent y répondre de plusieurs manières.
+- Envoyer un message direct à l'utilisateur-ice signalé-e.
+- Supprimé le statut signalé.
+- Désactiver l'utilisateur-ice. Pour les utilisateur-ices locaux-ales, cela les empêchera de se connecter, et leur compte ne sera plus affiché dans l'application. Pour les utilisateur-ices d'autres instances, le serveur rejettera toute activité de cet-te utilisateur-ice, qui n'apparaîtra également plus dans les recherches.
+
+## Modération au niveau de l'instance
+Les modérateur-ices peuvent bloquer des instances en entier. Cela va bloquer toute activité venant de cette instance et désactiver tous les comptes de cette instance au niveau local.
+
+Si l'instance est ensuite débloquée, les utilisateur-ices qui avaient été désactivé-es seront réactivé-es.
+
+Les modérateur-ices peuvent aussi mettre en ligne des listes pour bloquer plusieurs serveurs à la fois.
diff --git a/locale/fr_FR/content/running_bookwyrm/monitoring-queue.md b/locale/fr_FR/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..896d2023
--- /dev/null
+++ b/locale/fr_FR/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Suivi de la file d'attente
+Date: 2022-11-23
+Order: 6
+---
+
+Il peut arriver que votre instance tourne au ralenti. Une solution est d'inspecter la file d'attente, afin de vérifier si des tâches sont bloquées. Lisez ce qui suit afin de savoir comment.
+
+## Celery
+
+BookWyrm utilise [Celery](https://docs.celeryq.dev/en/stable/) pour la gestion des tâches en arrière‑plan.
+
+## Flower
+
+Pour le suivi en temps réel des tâches de Celery, BookWyrm se repose sur [Flower](https://flower.readthedocs.io/en/latest/).
+
+Si vous n'avez pas modifié [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) jusque là, vous trouverez ce service sur le [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). Pour référence : `https://MY_DOMAIN_NAME:8888/`.
+
+### Tâches
+
+Vous trouverez des tâches [annotées `@app.task`](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) dans le code source.
diff --git a/locale/fr_FR/content/running_bookwyrm/optional_features.md b/locale/fr_FR/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..aef24018
--- /dev/null
+++ b/locale/fr_FR/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Fonctionnalités optionnelles Date: 2021-08-02 Order: 8
+- - -
+
+Certaines fonctionnalités de BookWyrm doivent être activées pour fonctionner.
+
+## Prévisualisation d'images
+
+Par défault, BookWyrm utilise le logo de l'instance (ou le logo par défault) en tant qu'image d'aperçu OpenGraph. Une autre option est d'activer la création d'aperçus pour les livres, les utilisateur-ices et le site web.
+
+Les images d'aperçu seront dimensionnées pour les grandes images OpenGraph (utilisé par Twitter sous le nom `summary_large_image`). Selon le type d'image, son contenu sera :
+
+- l'image par défault de l'instance va afficher le gros logo, avec le nom de l'instance et son url
+- l'image de l'utilisateur-ice va afficher leur photo de profil, nom d'affichage et nom du compte (sous la forme @nom-d'utilisateur@instance)
+- l'image du livre va afficher sa page courverture, titre, sous-titre (s'il y a lieu), auteur-e et "rating" (s'il y a lieu)
+
+Ces images vont être mises à jour à plusieurs occasions :
+
+- image de l'instance : lorsque le nom de l'instance ou le logo sont modifiés
+- image de l'utilisateur-ice : lorsque le nom d'affichage ou la photo de profil sont modifiés
+- image du livre : lorsque le titre, l'auteur-e ou la couverture sont modifiés, ou quand une nouvelle note est ajoutée
+
+### Activer la prévisualisation des images
+
+Pour activer cette fonctionnalité avec les paramètres par défaut, il faut décommenter (retirer le `#` au début de) la ligne `ENABLE_PREVIEW_IMAGES=true` dans le fichier `.env`. Tous les nouveaux événements de mise à jour précédemment mentionnés provoqueront la génération de l'image correspondante.
+
+Des exemples pour ces images peuvent être consultés dans [la description de la pull request de cette fonctionnalité](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Générer les images de prévisualisation
+
+Si ce paramètre est activé après le démarrage de l'instance, certaines images pourraient ne pas avoir été générées. Une commande a été ajoutée pour automatiser la génération d'images. Afin d'éviter une surconsommation de ressources en générant **BEAUCOUP** d'images, il faut passer l'argument `--all` (ou `-a`) au lancement de la génération des images de prévisualisation pour toustes les utilisateur·ices et livres. Sans cet argument, seules les prévisualisations du site seront générées.
+
+Les images de prévisualisation des utilisateur·ices et des livres seront générées de manière asynchrone : la tâche sera envoyée à Flower. Un certain temps peut être nécessaire avant que toutes les images de prévisualisation des utilisateur·ices et des livres soient disponibles. Si vous avez un bon livre 📖, un chaton 🐱 ou un gâteau 🍰, c'est le moment parfait pour leur accorder de l'attention 💖.
+
+### Paramètres facultatifs
+
+Alors comme ça vous voulez personnaliser vos images de prévisualisation ? Voici les possibilités :
+
+- `PREVIEW_BG_COLOR` définit la couleur de fond de l'image de prévisualisation. Il est possible de mettre une valeur de couleur, comme `#b00cc0`, ou les valeurs suivantes : `use_dominant_color_light` ou `use_dominant_color_dark`. Cela va extraire une couleur dominante de la couverture du livre et l'utiliser, respectivement pour le thème clair ou sombre.
+- `PREVIEW_TEXT_COLOR` définit la couleur du texte. En fonction du choix de la couleur de fond, vous devriez trouver une valeur qui a un contraste suffisant pour que l'image soit accessible. Un rapport de contraste de 1:4,5 est recommandé.
+- `PREVIEW_IMG_WIDTH` et `PREVIEW_IMG_HEIGHT` définissent les dimensions de l'image. Actuellement, le système fonctionnera mieux avec des images au format paysage (horizontal).
+- `PREVIEW_DEFAULT_COVER_COLOR` définit la couleur des livres sans couvertures.
+
+Toutes les variables de couleur acceptent des valeurs reconnues par le module `ImageColor` de Pillow : [En apprendre plus sur les noms de couleurs dans Pillow](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Supprimer les images de prévisualisation pour les comptes externes
+
+Avant BookWyrm 0.5.4, des images de prévisualisation étaient générées pour les comptes externes. Comme c'était couteux en termes d'espace disque et de puissance de calcul, cela a été interrompu. Si vous souhaitez supprimer en masse toutes les images précédemment générées pour les comptes distants, une nouvelle commande a été ajoutée :
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+Cette commande va retirer dans la base de données la valeur de la propriété `user.preview_image` pour les comptes externes et supprimer le fichier associé.
diff --git a/locale/fr_FR/content/running_bookwyrm/reverse-proxy.md b/locale/fr_FR/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..6db8a855
--- /dev/null
+++ b/locale/fr_FR/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title : Utilisation d'un serveur mandataire inverse Date: 2021-05-11 Order: 4
+- - -
+
+## Faire fonctionner BookWyrm derrière un proxy inverse
+Si un autre serveur web est installé sur la machine, il serait préférable que ce dernier fasse proxy pour les requêtes vers BookWyrm.
+
+La configuration par défaut de BookWyrm a déjà un serveur Nginx qui sert de proxy pour les requêtes vers l'application Django gérant le SSL et servant directement les fichiers statiques. Les fichiers statiques sont stockés dans un volume Docker accessible par plusieurs services BookWyrm, il est donc déconseillé de complétement retirer ce serveur.
+
+Pour faire fonctionner BookWyrm derrière un proxy inverse, les changements suivants doivent être faits :
+
+- Dans `nginx/default.conf` :
+    - Décommenter les deux blocs "server" par défaut
+    - Décommenter le bloc "server" nommé "Reverse-Proxy server"
+    - Remplacer `your-domain.com` par votre nom de domaine
+- Dans `docker-compose.yml` :
+    - Dans `services` -> `nginx` -> `ports`, décommenter le port par défaut et ajouter `- 8001:8001`
+    - Dans `services` -> `nginx` -> `volumes`, décommenter les deux volumes commançant par `./certbot/`
+    - Dans `services`, décommenter le service `certbot`
+
+À partir de là, il est possible de suivre [les instructions d'installation](#server-setup) telles quelles. Une fois Docker lancé, il est possible d'accéder à l'instance BookWyrm à l'adresse `http://localhost:8001` (**IMPORTANT:** le serveur n'est pas accessible via `https`).
+
+Les étapes pour configurer un proxy inverse dépendent du serveur.
+
+#### Nginx
+
+Avant de pouvoir configurer Nginx, il faudra trouver son dossier de configuration, qui dépend de la plateforme et de la manière dont Nginx a été installé. Voir [le guide de Nginx](http://nginx.org/en/docs/beginners_guide.html) pour plus de détails.
+
+Pour configurer le serveur :
+
+- Dans le fichier `nginx.conf`, vérifier que `include servers/*;` n'est pas commenté.
+- Dans le dossier `servers` de Nginx, créer un nouveau fichier nommé d'après le nom de domaine de l'instance et contenant les informations suivantes :
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+Pour configurer avec un bloc SSL :
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- Exécuter `sudo certbot run --nginx --email VOTRE_ADRESSE_MAIL -d votre-nom-de-domaine.com -d www.votre-nom-de-domaine.com`
+- Redémarrer Nginx
+
+Si tout fonctionne correctement, l'instance BookWyrm devrait à présent être accessible depuis l'extérieur.
+
+*Note : le `proxy_set_header Host $host;` est essentiel ; s'il n'est pas inclus, les messages en provenance des serveurs fédérés seront rejetés.*
+
+*Note : l'emplacement des certificats SSL peut varier selon le système d'exploitation de votre serveur*
+
diff --git a/locale/fr_FR/content/running_bookwyrm/updating.md b/locale/fr_FR/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..29a10ad7
--- /dev/null
+++ b/locale/fr_FR/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Mise à jour de votre instance Date: 2022-11-17 Order: 3
+- - -
+
+Quand des changements sont disponibles sur la branche de production, il est possible de les installer et les faire fonctionner sur l'instance en utilisant la commande `./bw-dev update`. Cela fait plusieurs choses :
+
+- `git pull` récupère le code à jour depuis le dépôt git. S'il y a des conflits, vous pourriez avoir besoin de lancer `git pull` indépendamment et résoudre les conflits avant d'essayer le script `./bw-dev update` à nouveau.
+- `docker-compose build` reconstruit les images, ce qui permet de s'assurer que les bons paquets sont installés. Cette étape prend beaucoup de temps et est nécessaire uniquement lorsque les dépendances (incluant les paquets pip `requirements.txt`) ont changées, il est donc possible de la commenter si on souhaite une mise à jour plus rapide et ne pas être gêné de la décommenter si nécessaire.
+- `docker-compose run --rm web python manage.py migrate` exécute les migrations de base de données dans Django en utilisant les images Docker nouvellement créées
+- `docker-compose run --rm web python manage.py collectstatic --no-input` charge tous les fichiers statiques mis à jour (comme les fichiers JavaScript et CSS)
+- `docker-compose down; docker-compose up -d` redémarrera tous les conteneurs docker et utilisera les images nouvellement construites (attention : l'instance sera inaccessible pendant son redémarrage)
+
+## Reconstruire les flux d'activité
+
+Les flux de chaque utilisateur·ice sont stockés dans Redis. Pour repeupler un flux, il faut utiliser la commande de gestion :
+
+``` { .sh }
+./bw-dev populate_streams
+# Ou en utilisant directement docker-compose
+docker-compose run --rm web python manage.py populate_streams
+```
+
+Si quelque chose s'est terriblement mal passé, le flux de donnée peut être supprimé.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/fr_FR/content/using_bookwyrm/adding-books.md b/locale/fr_FR/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..bbd24b2e
--- /dev/null
+++ b/locale/fr_FR/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Ajout de livres
+Date: 2022-07-29
+Order: 2
+---
+
+Il y a plusieurs façons d'ajouter des livres à votre instance BookWyrm ! Quand vous ne trouvez pas le livre que vous cherchez, essayez ces options dans l'ordre -- il vaut mieux importer un livre que d'en créer un à partir de zéro.
+
+## Chargement de livres à partir d'autres catalogues
+
+Si le livre que vous cherchez n'est pas disponible sur votre instance, il y a plusieurs façons de l'ajouter. La meilleure manière est de l'importer depuis une source externe -- votre instance peut charger des livres depuis d'autres instances BookWyrm, ainsi que d'[OpenLibrary](http://openlibrary.org/) et [Inventaire](http://inventaire.io/). S'il n'y a pas de résultats de recherche à votre requête, ces sources seront automatiquement interrogées, et les réponses s'afficheront avec un bouton « **Importer le livre** ». S'il y a des résultats de recherche locaux qui ne sont pas ceux que vous recherchez, vous pouvez cliquer sur le lien «**Charger les résultats d’autres catalogues**» pour charger plus de résultats.
+
+
+## Ajout d'une nouvelle édition
+
+Si vous avez trouvé le livre que vous cherchiez mais pas dans la bonne édition, vous pouvez ajouter une autre édition à l’œuvre à partir de la liste des éditions. Cliquez sur le lien en dessous de la description qui vous indique le nombre d'éditions (par exemple, « **4 éditions** »). En bas de la liste des éditions il y a un bouton pour « **Ajouter une nouvelle édition** ».
+
+## Ajouter un nouveau livre
+
+Une fois que vous avez essayé sans succès de rechercher votre livre, de l'importez depuis un autre catalogue, et de trouver d'autres éditions de ce livre, vous pouvez ajouter un nouveau livre manuellement. Le lien pour ajouter manuellement un livre se trouve au bas de la page de recherche lorsque les résultats des catalogues externes sont affichés. Vous pouvez également directement ouvrir `/create-book` sur votre instance.
diff --git a/locale/fr_FR/content/using_bookwyrm/posting-statuses.md b/locale/fr_FR/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..f0bf33ec
--- /dev/null
+++ b/locale/fr_FR/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Publication de statuts Date: 2022-04-30 Order: 1
+- - -
+
+La publication sur BookWyrm commence par un livre. Les utilisateurs peuvent commenter les livres en cours ou récemment lus depuis la section « Vos livres » ou depuis la page d'un livre. De là, les utilisateurs peuvent répondre et démarrer une conversation. Les posts sur BookWyrm peuvent inclure un formatage basique avec du gras, de l'italique et des liens, en utilisant [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+Si vous avez de la familiarité avec [les posts sur Mastodon](https://docs.joinmastodon.org/user/posting/), vous trouverez que les statuts de BookWyrm ont des paramètres de visibilité similaires, des avertissements de contenu et des mentions. Cependant les sondages, les emoji personnalisés et les pièces jointes ne sont pas encore prises en charge.
+
+## Types de statuts
+
+### Réactions des utilisateurs
+
+Il y a trois types de posts que les utilisateurs peuvent créer directement en réponse aux livres : les critiques, les commentaires et les citations. Les commentaires répondent aux aspects généraux d'un livre, les citations se rapportent à des passages spécifiques et les critiques traitent des livres dans leur ensemble. Les utilisateurs peuvent également répondre aux statuts.
+
+| Composant                | Critique | Commentaire | Citation | Réponse |
+| ------------------------ | -------- | ----------- | -------- | ------- |
+| Champ de texte           | ✔        | ✔           | ✔        | ✔       |
+| Avertiseement de spoiler | ✔        | ✔           | ✔        | ✔       |
+| Numéro de page           |          | ✔           | ✔        |         |
+| Citation                 |          |             | ✔        |         |
+| Note                     | ✔        |             |          |         |
+| Champ de titre           | ✔        |             |          |         |
+
+
+### État de lecture
+
+Ces statuts sont générés lorsqu'un utilisateur indique qu'il veut lire, a commencé à lire ou a fini de lire un livre.
+
+## Texte
+Le texte peut inclure :
+
+- des mentions d’utilisateurs (@user)
+- des adresses URL (`http(s)://` n'est pas affiché)
+- du [formatage Markdown](https://www.markdownguide.org/cheat-sheet/)
+  - gras
+  - italique
+  - blocs de citation
+  - listes à puces
+  - liens
+
diff --git a/locale/gl_ES/LC_MESSAGES/messages.po b/locale/gl_ES/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..42c785f1
--- /dev/null
+++ b/locale/gl_ES/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-11-26 08:10\n"
+"Last-Translator: \n"
+"Language-Team: Galician\n"
+"Language: gl_ES\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: gl\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr "Documentación BookWyrm"
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr "Guía para usar e contribuír a BookWyrm"
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr "Como Usar e Contribuír"
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr "BookWyrm: Lectura e Recensión Sociais"
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "Únete"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr "Participa"
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "Apoia"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr "Código"
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr "Documentación"
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr "<strong>BookWyrm</strong> é software colaborativo e anti-corporacións mantido por <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr "Apoia a BookWyrm en <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr "Participa"
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr "BookWyrm en GitHub"
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr "Contribúe a esta páxina"
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr "Saber máis"
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr "Contacta"
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr "Licenza"
+
diff --git a/locale/gl_ES/content/codebase/activitypub.md b/locale/gl_ES/content/codebase/activitypub.md
new file mode 100644
index 00000000..bdfc067c
--- /dev/null
+++ b/locale/gl_ES/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Recensión`: unha recensión é un estado en resposta a un libro (presente no campo `enRespostaAoLibro`), que ten un título, corpo e puntuación numérica entre 0 (sen valorar) e 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Cita`: unha cita é unha mensaxe con corpo, fragmento do libro e menciona ao libro.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Estante`: Unha colección de libros da usuaria. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Engadir`: Engade o libro a un estante ou lista.
+- `Eliminar`: Retira un libro dun estante ou lista.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/gl_ES/content/codebase/permissions.md b/locale/gl_ES/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/gl_ES/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/gl_ES/content/contributing/contributing.md b/locale/gl_ES/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/gl_ES/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/gl_ES/content/contributing/debug_toolbar.md b/locale/gl_ES/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/gl_ES/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/gl_ES/content/contributing/install-dev.md b/locale/gl_ES/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/gl_ES/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/gl_ES/content/contributing/style_guide.md b/locale/gl_ES/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/gl_ES/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/gl_ES/content/contributing/translation.md b/locale/gl_ES/content/contributing/translation.md
new file mode 100644
index 00000000..d73b3286
--- /dev/null
+++ b/locale/gl_ES/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Traducións Date: 2021-10-20 Order: 2
+- - -
+
+## Axuda a traducir
+
+Podes unirte ao proxecto de tradución de BookWyrm en [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Linguaxe de xénero neutro
+
+Sempre que sexa posible, as traducións de BookWyrm deberán utilizar unha linguaxe de xénero neutro. Isto é de aplicación incluso se o idioma adopta a forma masculina como xénero neutro, ou se utiliza algo semellante a "el/ela". É importante tamén que as traducións sexan concisas e claras, lexibles para lectores de pantalla, polo que hai veces que estos obxectivos entran en conflito; nada é perfecto, non hai unha solución que contente a todo o mundo, e esta solución depende do idioma en cuestión.
+
+Como criterio superior, intenta poñer máis énfase nunha linguaxe de xénero neutro e inclusivo que na corrección formal ou as guías de estilo oficialmente establecidas. En inglés, por exemplo, as guías de estilo indican a forma singular do pronome "she" ou "he" para referirse a un individuo, pero en BookWyrm avogamos polo uso da forma de xénero neutro singular "they".
+
+Se non tes certeza sobre como afrontar este problema de tradución, fai un comentario na tradución ou abre un [tema de discusión](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) para afrontar o problema nunha instancia superior.
+
+## Facer os modelos traducibles
+
+BookWyrm aproveita as vantaxes da funcionabilidade das traducións de Django para permitir que o contido da páxina varíe en función do idioma elexido. A documentación de Django [proporciona axuda](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) sobre como funciona, pero aquí tes unha versión reducida:
+
+* tódolos modelos do texto deben incluír etiquetas do modelo da tradución
+* engade `{% load i18n %}` na parte superior do modelo para activar as traducións
+* Se o bloque de texto é texto literal, podes usar o modelo de etiqueta `{% trans %}`
+* Se o bloque inclúe variables, debes usar o par de modelos de etiqueta `{% blocktrans %}` e `{% endblocktrans %}`. Se estás incluíndo espazos en branco ou saltos de liña, usa `trimmed` para eliminalos automáticamente cando se crea o ficheiro coa tradución: `{% blocktrans trimmed %}`
+
+### Exemplos
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/gl_ES/content/index.md b/locale/gl_ES/content/index.md
new file mode 100644
index 00000000..3fde9b6c
--- /dev/null
+++ b/locale/gl_ES/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Ben vida Date: 2021-04-13
+- - -
+
+BookWyrm é unha rede social para rexistrar as túas lecturas, falar acerca dos libros, escribir recensións e descubrir novos libros para ler. A Federación permítelle ás persoas usuarias de BookWyrm unirse en pequenas comunidades de confianza que poden conectarse unhas con outras e con outros servizos ActivityPub como Mastodon ou Pleroma.
+
+## Características
+Como o proxecto aínda está nos seus primeiros pasos, o número de funcións dispoñibles aumenta cada día, e hai moito espazo para ideas e suxestións. Abre un [issue](https://github.com/bookwyrm-social/bookwyrm/issues) para continuar a conversa!
+
+- Publicar sobre libros
+    - Escribe recensións, con ou sen valoracións, que serán engadidas á páxina do libro
+    - Escribe outros tipos de estados acerca dos libros, como:
+        - Comentarios nun libro
+        - Citas e extractos
+    - Responder a estados
+    - Ver recensións agregadas entre instancias BookWyrm que estén conectadas
+    - Diferenciar na túa cronoloxía entre recensións e valoracións locais e federadas
+- Seguir a actividade lectora
+    - Coloca os libros nos estantes por defecto "Pendentes", "Lectura actual" e "Lidos"
+    - Crea estantes personais
+    - Garda as datas de comezo/remate da lectura, así como actualizacións do progreso durante a mesma
+    - Pon ao día ás tuas seguidoras acerca do que les (optativo, e con controis de privacidade detallados)
+    - Crea listas de libros que podes abrir a suxestións de outras persoas, xestionadas e editadas só por ti
+- Federación con ActivityPub
+    - Emite e recibe estados e actividades de outras usuarias
+    - Comparte os datos do libro entre instancias para crear unha base de datos distribuída de metadatos
+    - Identifica libros compartidos entre instancias e engade contido relacionado
+    - Sigue e interactúa con usuarias de outras instancias BookWyrm
+    - Interactúa con outros servizos ActivityPub alleos a BookWyrm (actualmente con soporte para Mastodon)
+- Controis de privacidade detallados
+    - Privado, só para seguidoras e público son os niveis de privacidade para publicacións, estantes e listas
+    - Opción para as usuarias para aprobar manualmente as solicitudes de seguimento
+    - Permite bloquear e marcar para moderación
diff --git a/locale/gl_ES/content/pages/index.md b/locale/gl_ES/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/gl_ES/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/gl_ES/content/running_bookwyrm/cli.md b/locale/gl_ES/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..60278264
--- /dev/null
+++ b/locale/gl_ES/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrar todo o multimedia subido desde unha instalación BookWyrm existente a un "bucket" S3-compatible. Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sincronizar o multimedia novo ou que cambiase desde unha instalación BookWyrm existente a un "bucket" S3-compatible. Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/gl_ES/content/running_bookwyrm/external-storage.md b/locale/gl_ES/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/gl_ES/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/gl_ES/content/running_bookwyrm/install-prod-dockerless.md b/locale/gl_ES/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/gl_ES/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/gl_ES/content/running_bookwyrm/install-prod.md b/locale/gl_ES/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/gl_ES/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/gl_ES/content/running_bookwyrm/moderation.md b/locale/gl_ES/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/gl_ES/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/gl_ES/content/running_bookwyrm/monitoring-queue.md b/locale/gl_ES/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/gl_ES/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/gl_ES/content/running_bookwyrm/optional_features.md b/locale/gl_ES/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..72e6e782
--- /dev/null
+++ b/locale/gl_ES/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. Como era un gasto inútil en termos de espazo en disco e capacidade de computación, detívose a creación. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/gl_ES/content/running_bookwyrm/reverse-proxy.md b/locale/gl_ES/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/gl_ES/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/gl_ES/content/running_bookwyrm/updating.md b/locale/gl_ES/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/gl_ES/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/gl_ES/content/using_bookwyrm/adding-books.md b/locale/gl_ES/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..b72fe8d8
--- /dev/null
+++ b/locale/gl_ES/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Engadir Libros
+Date: 2022-07-29
+Order: 2
+---
+
+Hai dous xeitos diferentes de engadir libros á túa instancia BookWyrm! Cando non atopas o libro que buscas, segue estas instruccións en orde -- é mellor importar un libro que crear un novo desde cero.
+
+## Cargar libros desde outros catálogos
+
+Se o libro que buscas non está dispoñible na túa instancia, existen varios xeitos de engadilo. O mellor xeito é importalo desde unha fonte externa -- a túa instancia pode obter libros desde outras instancias BookWyrm, así como de [OpenLibrary](http://openlibrary.org/) e [Inventaire](http://inventaire.io/). Se non obtes resultados para a busca, estas fontes serán consultadas automáticamente, e mostrarán un botón para "**Importar libro**". Se hai resultados locais que non son o que estabas a buscar, podes premer na ligazón "**Cargar resultados doutros catálogos**" para ver máis suxestións.
+
+
+## Engadir outra edición
+
+Se atopaches o libro que buscabas, pero non a edición correcta, podes engadir outra edición desde a lista de edicións. Preme na ligazón debaixo da descrición que indica cantas edicións existen (exemplo, "**4 edicións**"). Debaixo da lista de edición, hai un botón para "**Engadir outra edición**".
+
+## Engadir un libro desde cero
+
+Unha vez intentaches atopar o libro, importalo desde outro catálogo, e outras edicións do libro, podes engadir manualmente un libro novo. A ligazón para engadir manualmente un libro está abaixo na páxina de busca cando se mostran catálogos externos. Tamén podes ir directamente a `/create-book` na túa instancia.
diff --git a/locale/gl_ES/content/using_bookwyrm/posting-statuses.md b/locale/gl_ES/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..6e325367
--- /dev/null
+++ b/locale/gl_ES/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Publicar estados Date: 2022-04-30 Order: 1
+- - -
+
+As publicacións en BookWyrm inicianse a partir dun libro. As usuarias poden comentar o progreso na lectura ou os libros recentes da sección "Os teus libros", ou desde a páxina de incio dun libro. Desde ahí, poderan responder e iniciar unha conversa. As publicacións de BookWyrm poden incluir formato no texto, como letra grosa, cursiva ou ligazóns utilizando [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+Se coñeces o xeito en que se [publica en Mastodon](https://docs.joinmastodon.org/user/posting/), verás que os estados de BookWyrm teñen uns axustes de visibilidade análogos, avisos de contido e mencións. Aínda non temos soporte para as enquisas, emojis personalizados e os adxuntos.
+
+## Tipos de estados
+
+### Comentarios
+
+As usuarias poden facer tres tipos de publicacións en respostas nos libros: recensións, comentarios e citas. Os comentarios responden a aspectos xerais do libro, as citas pertencen a determinadas pasaxes e as recensións ocúpanse do libro en conxunto. As usuarias poden tamén responder aos estados.
+
+| Compoñente        | Recensión | Comentario | Cita | Resposta |
+| ----------------- | --------- | ---------- | ---- | -------- |
+| Campo de texto    | ✔         | ✔          | ✔    | ✔        |
+| Alerta de spoiler | ✔         | ✔          | ✔    | ✔        |
+| Número de páxina  |           | ✔          | ✔    |          |
+| Cita              |           |            | ✔    |          |
+| Valoración        | ✔         |            |      |          |
+| Campo de Título   | ✔         |            |      |          |
+
+
+### Ler actualizacións dos estados
+
+Os estados créanse cando a usuaria indica que quere ler un libro, que comezou a lelo ou xa o rematou.
+
+## Texto
+O texto pode incluir:
+
+- Mencións (@usuaria)
+- URLs (`https(s)://` non se mostra)
+- Certo [formato Markdown](https://www.markdownguide.org/cheat-sheet/)
+  - grosa
+  - cursiva
+  - bloques de cita
+  - lista con puntos
+  - ligazóns
+
diff --git a/locale/he_IL/LC_MESSAGES/messages.po b/locale/he_IL/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..30279a44
--- /dev/null
+++ b/locale/he_IL/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Hebrew\n"
+"Language: he_IL\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=4; plural=n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || n%100==4 ? 2 : 3;\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: he\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/he_IL/content/codebase/activitypub.md b/locale/he_IL/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/he_IL/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/he_IL/content/codebase/permissions.md b/locale/he_IL/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/he_IL/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/he_IL/content/contributing/contributing.md b/locale/he_IL/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/he_IL/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/he_IL/content/contributing/debug_toolbar.md b/locale/he_IL/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/he_IL/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/he_IL/content/contributing/install-dev.md b/locale/he_IL/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/he_IL/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/he_IL/content/contributing/style_guide.md b/locale/he_IL/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/he_IL/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/he_IL/content/contributing/translation.md b/locale/he_IL/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/he_IL/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/he_IL/content/index.md b/locale/he_IL/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/he_IL/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/he_IL/content/pages/index.md b/locale/he_IL/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/he_IL/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/he_IL/content/running_bookwyrm/cli.md b/locale/he_IL/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..882387b4
--- /dev/null
+++ b/locale/he_IL/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+כותרת: כלי שורת הפקודה תאריך: 11-11-2021 מקום: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/he_IL/content/running_bookwyrm/external-storage.md b/locale/he_IL/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..37c3a61b
--- /dev/null
+++ b/locale/he_IL/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+כותרת: אחסון חיצוני תאריך: 07-06-2021 מקום: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/he_IL/content/running_bookwyrm/install-prod-dockerless.md b/locale/he_IL/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..bb064789
--- /dev/null
+++ b/locale/he_IL/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- ניתן להעביר את סכמת מסד הנתונים על ידי הרצה `venv/bin/python3 manage.py migrate`
+- ניתן לאתחל את מסג הנתונים על ידי הרצת `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/he_IL/content/running_bookwyrm/install-prod.md b/locale/he_IL/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/he_IL/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/he_IL/content/running_bookwyrm/moderation.md b/locale/he_IL/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/he_IL/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/he_IL/content/running_bookwyrm/monitoring-queue.md b/locale/he_IL/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..bce8a637
--- /dev/null
+++ b/locale/he_IL/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: תור ניטור
+Date: 23-11-2022
+Order: 6
+---
+
+ייתכנו מקרים בהם המופעים שלך יתנהגו באיטיות יותר. אפשרות אחת תהיה לבדוק את התור כדי לראות אם חלק מהעבודות תקועות. יש לקרוא כדי ללמוד איך.
+
+## Celery
+
+BookWyrm משתמש ב-[Celery](https://docs.celeryq.dev/en/stable/) כדי לנהל את העבודות ברקע.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/he_IL/content/running_bookwyrm/optional_features.md b/locale/he_IL/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..9ad4d4b9
--- /dev/null
+++ b/locale/he_IL/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+כותרת: תכונות אופציונליות תאריך: 02-08-2021 מקום: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/he_IL/content/running_bookwyrm/reverse-proxy.md b/locale/he_IL/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/he_IL/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/he_IL/content/running_bookwyrm/updating.md b/locale/he_IL/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/he_IL/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/he_IL/content/using_bookwyrm/adding-books.md b/locale/he_IL/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/he_IL/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/he_IL/content/using_bookwyrm/posting-statuses.md b/locale/he_IL/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/he_IL/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/hu_HU/LC_MESSAGES/messages.po b/locale/hu_HU/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..d8c1ce53
--- /dev/null
+++ b/locale/hu_HU/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Hungarian\n"
+"Language: hu_HU\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: hu\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/hu_HU/content/codebase/activitypub.md b/locale/hu_HU/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/hu_HU/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/hu_HU/content/codebase/permissions.md b/locale/hu_HU/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/hu_HU/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/hu_HU/content/contributing/contributing.md b/locale/hu_HU/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/hu_HU/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/hu_HU/content/contributing/debug_toolbar.md b/locale/hu_HU/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/hu_HU/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/hu_HU/content/contributing/install-dev.md b/locale/hu_HU/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/hu_HU/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/hu_HU/content/contributing/style_guide.md b/locale/hu_HU/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/hu_HU/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/hu_HU/content/contributing/translation.md b/locale/hu_HU/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/hu_HU/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/hu_HU/content/index.md b/locale/hu_HU/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/hu_HU/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/hu_HU/content/pages/index.md b/locale/hu_HU/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/hu_HU/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/hu_HU/content/running_bookwyrm/cli.md b/locale/hu_HU/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/hu_HU/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/hu_HU/content/running_bookwyrm/external-storage.md b/locale/hu_HU/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/hu_HU/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/hu_HU/content/running_bookwyrm/install-prod-dockerless.md b/locale/hu_HU/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/hu_HU/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/hu_HU/content/running_bookwyrm/install-prod.md b/locale/hu_HU/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/hu_HU/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/hu_HU/content/running_bookwyrm/moderation.md b/locale/hu_HU/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/hu_HU/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/hu_HU/content/running_bookwyrm/monitoring-queue.md b/locale/hu_HU/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/hu_HU/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/hu_HU/content/running_bookwyrm/optional_features.md b/locale/hu_HU/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/hu_HU/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/hu_HU/content/running_bookwyrm/reverse-proxy.md b/locale/hu_HU/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/hu_HU/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/hu_HU/content/running_bookwyrm/updating.md b/locale/hu_HU/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/hu_HU/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/hu_HU/content/using_bookwyrm/adding-books.md b/locale/hu_HU/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/hu_HU/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/hu_HU/content/using_bookwyrm/posting-statuses.md b/locale/hu_HU/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/hu_HU/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/it_IT/LC_MESSAGES/messages.po b/locale/it_IT/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..5d870948
--- /dev/null
+++ b/locale/it_IT/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-12-19 05:09\n"
+"Last-Translator: \n"
+"Language-Team: Italian\n"
+"Language: it_IT\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: it\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr "Documentazione BookWyrm"
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr "La tua guida per utilizzare e contribuire a BookWyrm"
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr "Come utilizzare e contribuire"
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr "BookWyrm: Lettura e Revisione Sociale"
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "Iscriviti"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr "Partecipa"
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "Sostegno"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr "Codice"
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr "Documentazione"
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr "<strong>BookWyrm</strong> è un software collaborativo, anti-aziendale gestito da <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr "Sostieni BookWyrm su <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr "Partecipa"
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr "BookWyrm su GitHub"
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr "Contribuisci a questa pagina"
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr "Ulteriori informazioni"
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr "Contatta il responsabile"
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr "Licenza"
+
diff --git a/locale/it_IT/content/codebase/activitypub.md b/locale/it_IT/content/codebase/activitypub.md
new file mode 100644
index 00000000..499d4031
--- /dev/null
+++ b/locale/it_IT/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Titolo: ActivityPub Data: 2021-04-20 Ordine: 1
+- - -
+
+BookWyrm utilizza il protocollo [ActivityPub](http://activitypub.rocks/) per inviare e ricevere le attività dell'utente tra altre istanze di BookWyrm e altri servizi che implementano ActivityPub, come [Mastodon](https://joinmastodon.org/). Per gestire i dati del libro, BookWyrm ha una manciata di tipi di attività estesi che non fanno parte dello standard, ma sono leggibili ad altre istanze di BookWyrm.
+
+## Attività e oggetti
+
+### Utenti e relazioni
+Le interazioni tra gli utenti seguono le specifiche standard di ActivityPub.
+
+- `Segui`: richiesta di ricevere aggiornamenti di un utente e visualizzare i sui stati che hanno privacy solo follower
+- `Accetta`: approva un `Segui` e finalizza la relazione
+- `Rifiuta`: nega un `Segui`
+- `Blocco`: impedisce agli utenti di vedere gli stati degli altri e impedisce all'utente bloccato di visualizzare il profilo del bloccante
+- `Aggiorna`: aggiorna il profilo e le impostazioni di un utente
+- `Elimina`: disattiva un utente
+- `Annulla`: inverte un `Segui` o `Blocco`
+
+### Stati
+#### Tipologia di oggetto
+
+- `Nota`: Su servizi come Mastodon, `Nota` è il tipo primario di stato. Contengono il corpo del messaggio, gli allegati, possono menzionare gli utenti, ed posso ricevere in risposta qualsiasi tipo di stato. All'interno di BookWyrm, la `Nota`s può essere creata solo come messaggio diretto o come risposta ad altri stati.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: Un commento a un libro parla del libro stesso e ha un corpo messaggio.
+- `Citazione`: Una citazione ha un corpo del messaggio, un estratto da un libro e menziona un libro.
+
+
+#### Attività
+
+- `Crea`: salva un nuovo stato nel database.
+
+   **Note**: BookWyrm accetta attività `Create` solo se sono:
+
+   - Messaggi diretti (cioè, `Note`s con il livello di privacy `direct`, che menzionano un utente locale),
+   - Relativo a un libro (un tipo di stato personalizzato che include il campo `inReplyToBook`),
+   - Risposte agli stati esistenti salvati nel database
+- `Delete`: Rimuove uno stato
+- `Like`: Crea un preferito sullo stato
+- `Annuounce`: Condivide lo stato nella timeline dell'utente
+- `Undo`: Inverte un `Like` o `Announce`
+
+### Collezioni
+I libri e le liste degli utenti sono rappresentati da [`OrdinedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Obiettivi
+
+- `Scaffale`: Collezione di libri di un utente. Per impostazione predefinita, ogni utente ha gli scaffali `da leggere`, `letture correnti`, e `letti` che vengono utilizzati per monitorare i progressi di lettura.
+- `Lista`: Una raccolta di libri che può avere elementi forniti da utenti diversi da quello che ha creato la lista.
+
+#### Attività
+
+- `Crea`: Aggiunge uno scaffale o una lista al database.
+- `Elimina`: Rimuove uno scaffale o una lista.
+- `Aggiungi`: Aggiunge un libro a uno scaffale o una lista.
+- `Rimuovi`: Rimuove un libro da uno scaffale o da una lista.
+
+
+## Serializzazione Alternativa
+Poiché BookWyrm utilizza tipi di oggetti personalizzati (`Recensione`, `Commento`, `Citazione`) che non sono supportati da ActivityPub, gli stati si trasformano in tipi standard quando inviati o visualizzati da servizi non-BookWyrm. `Recensione`s viene convertita in `Articolo`s, `Commento`s e `Citazione`s vengono convertiti in `Nota`s, con un link al libro e l'immagine di copertina allegata.
diff --git a/locale/it_IT/content/codebase/permissions.md b/locale/it_IT/content/codebase/permissions.md
new file mode 100644
index 00000000..60a5eb2f
--- /dev/null
+++ b/locale/it_IT/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Titolo: Permessi Data: 18-04-2021 Ordine: 2
+- - -
+
+L'accesso dell'utente a diverse funzioni è controllato tramite il sistema di autenticazione integrato [di Django](https://docs.djangoproject.com/en/3.2/topics/auth/default/). Quando viene creata un'istanza, lo script `initdb` crea un insieme di permessi, che vengono assegnati ai gruppi. Per impostazione predefinita, a tutti i nuovi utenti viene assegnato il gruppo `editor`, che consente loro di modificare i metadati del libro.
+
+L'amministratore dell'istanza dovrebbe avere lo stato `superuser`, che gli consente l0accesso a Django admin (`/admin`) e conferisce tutte le autorizzazioni al suo utente.
+
+## Permessi e gruppi
+Questa tabella mostra i quattro gruppi (admin, moderatore, editor e utente) e quali permessi gli utenti di quel gruppo hanno:
+
+|                                 | admin | moderatore | editor | utente |
+| ------------------------------- | ----- | ---------- | ------ | ------ |
+| modifica impostazioni istanza   | ✔️    | -          | -      | -      |
+| modifica il livello dell'utente | ✔️    | -          | -      | -      |
+| gestire la federazione          | ✔️    | ✔️         | -      | -      |
+| invito a correggere errori      | ✔️    | ✔️         | -      | -      |
+| disattiva utenti                | ✔️    | ✔️         | -      | -      |
+| cancella post                   | ✔️    | ✔️         | -      | -      |
+| modifica libri                  | ✔️    | ✔️         | ✔️     | -      |
+ carica le copertine           |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/it_IT/content/contributing/contributing.md b/locale/it_IT/content/contributing/contributing.md
new file mode 100644
index 00000000..038d7f0d
--- /dev/null
+++ b/locale/it_IT/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Titolo: Come contribuire Data: 12-04-2021 Ordine: 1
+- - -
+
+Ci sono molti modi in cui puoi contribuire a questo progetto, indipendentemente dal tuo livello di competenza tecnica,.
+
+## Commenti e richieste di funzionalità
+Ti preghiamo di sentirti incoraggiato e benvenuto a segnalare bug, suggerimenti, richieste di caratteristiche, e idee su come le cose dovrebbero funzionare usando [problemi di GitHub](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Contributi al codice
+I contributi al codice vengono accolti con piacere! Se non sei sicuro di dove iniziare, dai un'occhiata al tag ["Buona prima segnalazione"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22). Poiché BookWyrm è un piccolo progetto, non c'è molta struttura formale, ma troverai un'enorme capacità di supporto individuale, come porre domande mentre procedi, pair programming, video chat, e molto altro. Perciò non esitare a unirti a noi.
+
+Se hai domande sul progetto o su come contribuire, puoi unirti alla [stanza BookWyrm su matrix](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Traduzione
+Parli un'altra lingua oltre all'inglese? BookWyrm ha bisogno di localizzazione! Puoi aggiungere e modificare le traduzioni su [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Sostegno Finanziario
+BookWyrm è un progetto nato per passione, senza pubblicità e senza alcuna intenzione di cercare venture funding o relazioni finanziarie aziendali. Se vuoi aiutare a mantenere il progetto in corso, puoi diventare un contributore sostenibile tramite [Patreon](https://www.patreon.com/bookwyrm) o [OpenCollective](https://opencollective.com/bookwyrm), o fare un regalo una tantum tramite [PayPal](https://paypal.me/oulipo).
diff --git a/locale/it_IT/content/contributing/debug_toolbar.md b/locale/it_IT/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..e116ac0a
--- /dev/null
+++ b/locale/it_IT/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Titolo: Django Debug Toolbar Data: 2022-05-16 Ordine: 5
+- - -
+
+BookWyrm ha un ramo che è configurato per avviare [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). Questo ramo non verrà mai unito in `main` e ha alcune modifiche che lo fanno funzionare con la barra degli strumenti, ma pericoloso da usare in qualsiasi cosa assomigli a un ambiente di produzione. Per utilizzare questo ramo, è necessario passare attraverso alcuni passaggi per farlo funzionare.
+
+## Configura
+
+- Utilizzando git, controlla il ramo [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar)
+- Aggiorna il ramo relativo a `main` usando `git merge main`. Il ramo viene aggiornato periodicamente, ma probabilmente sarà più tardi.
+- Ricostruisci le immagini Docker usando `docker-compose up --build` per assicurarsi che la libreria della barra degli strumenti di Debug sia installata da `requirements.txt`
+- Accedi direttamente all'immagine `web` dell'applicazione (invece che tramite `nginx`) utilizzando la porta `8000`
diff --git a/locale/it_IT/content/contributing/install-dev.md b/locale/it_IT/content/contributing/install-dev.md
new file mode 100644
index 00000000..e07d5300
--- /dev/null
+++ b/locale/it_IT/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Titolo: Ambiente di sviluppo Data: 12-04-2021 Ordine: 3
+- - -
+
+## Prerequisiti
+
+Queste istruzioni presuppongono che tu stia sviluppando BookWyrm usando Docker. Dovrai [installare Docker](https://docs.docker.com/engine/install/) e [docker-compose](https://docs.docker.com/compose/install/) per iniziare.
+
+## Impostazioni dell'ambiente di sviluppo
+
+- Ottieni una copia del [codebase di BookWyrm da GitHub](https://github.com/bookwyrm-social/bookwyrm). Puoi [creare un fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) del repository, e poi [usare `git clone` per scaricare il codice](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) sul tuo computer.
+- Vai alla directory che contiene il codice sul tuo computer, lavorerai da qui d'ora in poi.
+- Imposta il file delle variabili di ambiente di sviluppo copiando il file di ambiente di esempio (`. nv.example`) in un nuovo file denominato `.env`. Nella riga di comando, puoi farlo con:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, cambia `DEBUG` in `true`
+- Facoltativamente, puoi usare un servizio come [ngrok](https://ngrok.com/) per impostare un nome di dominio, e impostare la variabile `DOMAIN` nel tuo file`.env` al nome del dominio generato da ngrok.
+
+- Imposta nginx per lo sviluppo copiando il file di configurazione dello sviluppatore nginx (`nginx/development`) in un nuovo file chiamato `nginx/default. onf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Avvia l'applicazione. Dalla riga di comando esegui:
+``` { .sh }
+./bw-dev build        # Costrusce le immagini docker
+./bw-dev setup.      # Inizializza il database ed esegue le migrazioni
+./bw-dev up # Avvia i contenitori docker
+```
+- Una volta completato il build, puoi accedere all'istanza su `http://localhost:1333` e creare un utente amministratore.
+
+Se sei curioso: il comando `./bw-dev` è un semplice script di shell esegue vari altri strumenti: puoi comunque eseguire `docker-compose build` o `docker-compose` direttamente se preferisci. `./bw-dev` li raccoglie in un unico posto comune per comodità. Eseguilo senza argomenti per ottenere un elenco dei comandi disponibili, leggi la [pagina di documentazione](/command-line-tool.html) o aprilo e guardati intorno per vedere esattamente cosa fa ogni comando!
+
+### Modifica o crea dei modelli
+
+Se cambi o crei un modello, probabilmente dovrai cambiare la struttura del database. Affinché queste modifiche abbiano effetto, è necessario eseguire il comando `makemigrations` di Django per creare un nuovo [file di migrazione di Django](https://docs.djangoproject.com/en/3.2/topics/migrations), e poi `migrare`:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Modifica file statici
+Ogni volta che modifichi il CSS o JavaScript, è necessario eseguire nuovamente il comando `collectstatic` di Django affinché le modifiche abbiano effetto:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+Se hai [installato yarn](https://yarnpkg.com/getting-started/install), è possibile eseguire `yarn watch:static` per eseguire automaticamente lo script precedente ogni volta che si verifica un cambiamento nella directory `bookwyrm/static`.
diff --git a/locale/it_IT/content/contributing/style_guide.md b/locale/it_IT/content/contributing/style_guide.md
new file mode 100644
index 00000000..ad1d32ae
--- /dev/null
+++ b/locale/it_IT/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Titolo: Guida di stile Data: 20-10-2021 Ordine: 4
+- - -
+
+## Pull requests
+
+Quindi vuoi contribuire al codice di BookWyrm: fantastico! Se c'è un problema aperto che si desidera risolvere, è utile commentare il problema in modo che il lavoro non venga duplicato. Cerca di mantenere piccola la portata delle richieste nel pull e focalizzati su un singolo argomento. In questo modo è più facile da rivedere, e se una parte ha bisogno di cambiamenti, non bloccherà le altre parti.
+
+Se non sei sicuro di come risolvere qualcosa, o non sei in grado di aggirare il problema, va benissimo, basta lasciare un commento sulla pull request e lo capiremo 💖.
+
+Le richieste di prelievo devono superare tutti i controlli automatici prima che possano essere uniti - questo include controlli di stile, linters globali, un controllo di sicurezza e test di unità.
+
+## Linting
+
+### Globale
+
+Usiamo [EditorConfig](https://editorconfig.org) per mantenere costanti le terminazioni di indentazione e di linea.
+
+### Python
+
+BookWyrm utilizza il formattatore del codice [Black](https://github.com/psf/black) per mantenere coerente lo stile del codebase Python. Tutte le nuove richieste sono controllate con le azioni GitHub e puoi risolvere automaticamente i problemi di stile del codice eseguendo `./bw-dev black`
+
+Il codice è anche controllato con Pylint utilizzando le azioni GitHub. Gli avvertimenti di Pylint devono essere risolti prima che le richieste di pull siano unite, ma è una chiamata di giudizio se il suggerimento deve essere utilizzato, o l'avviso soppresso. Per sopprimere un avviso, aggiungi un commento alla fine o sulla riga sopra gli avvisi: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+La tua richiesta di pull sarà anche controllata dall'linter [curlylint](https://www.curlylint.org) per i modelli Django.
+
+### CSS
+
+Usiamo [stylelint](https://stylelint.io) per controllare tutte le regole CSS. Come con Pylint [puoi disabilitare stylelint](https://stylelint.io/user-guide/ignore-code) per una regola particolare, ma avrai bisogno di una buona motivazione per farlo.
+
+### JavaScript
+
+[ESLint](https://eslint.org) controlla qualsiasi modifica JavaScript che hai apportato. Se a ESLint non piace il tuo JavaScript, controlla il messaggio linter per verificare il problema esatto.
+
+## Progettazione Inclusiva
+
+Bookwyrm mira a essere il più completo e accessibile possibile.
+
+Quando si contribuisce con il codice, controllare la checklist [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) prima di archiviare la tua richiesta pull. Per la consulenza in materia di accessibilità, [A11Y-101](https://www.a11y-101.com/development) è anche una fonte utile. Per informazioni su come rendere i modelli di pagina multilingue, vedere la [sezione Traduzioni](/translations.html).
+
+Alcune cose particolari che i contributori di Bookwyrm hanno trovato utili per ricordare sono:
+
+### Moduli
+
+* Utilizza solo `input[type="checkbox"]` o `input[type="radio"]` dentro `<label>`
+* Se non piazzi caselle di controllo e pulsanti radio all'interno del `<label>`, il `<label>` dovrebbe essere posizionato _dopo_ l'elemento cui si riferisce
+
+### Tasti e collegamenti
+
+* Usa un elemento `<button>` per qualsiasi cosa esistente per attivare un'azione JavaScript (e.. nascondere o svuotare una forma) o invia una richiesta `POST` (ad esempio inviare un modulo)
+* Usa un elemento `<a>` per tutto quello che attiva una richiesta `GET`. Di solito, un elemento di ancoraggio (`<a>`) non dovrebbe essere stilato come pulsante (`class="pulsante"`), anche se ci sono alcune eccezioni, come i pulsanti "Annulla". In caso di dubbio, chieda consiglio nella tua pull request
diff --git a/locale/it_IT/content/contributing/translation.md b/locale/it_IT/content/contributing/translation.md
new file mode 100644
index 00000000..8fbd9014
--- /dev/null
+++ b/locale/it_IT/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Titolo: Traduzioni Data: 2021-10-20 Ordine: 2
+- - -
+
+## Contribuisci alle traduzioni
+
+Puoi partecipare al progetto di traduzione BookWyrm su [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Linguaggio gender-neutral
+
+Laddove possibile, le traduzioni di BookWyrm dovrebbero utilizzare un linguaggio neutro dal punto di vista del genere. Questo vale anche se la lingua utilizza il maschile come un genere neutrale, o se usa qualcosa di simile a "lui/lei". È anche importante che le traduzioni siano chiare, concise e leggibili per un lettore a schermo e a volte questi obiettivi sono in conflitto; non c'è una risposta perfetta, unica e adatta a tutti, e la soluzione dipende dalla lingua.
+
+Come principio guida, cercare di posizionare un valore più alto su un linguaggio inclusivo e neutro che su una correttezza formale o guide di stile ufficialmente approvate. In inglese, per esempio, molte guide di stile formali richiedono un pronome "lei" o "he" singolare da utilizzare quando si riferisce a un individuo, ma sarebbe meglio in BookWyrm utilizzare il genere neutro singolare "loro" invece.
+
+Se non siete sicuri di come meglio affrontare un problema di traduzione, commentate la traduzione o aprite un [argomento di discussione](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) per affrontare domande su larga scala.
+
+## Creare modelli traducibili
+
+Bookwyrm sfrutta la funzionalità di traduzione di Django per consentire ai contenuti della pagina di cambiare a seconda della lingua di visualizzazione scelta dall'utente. La documentazione Django [fornisce un'utile spiegazione](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) di come funziona, ma ecco una versione breve:
+
+* tutto il testo del modello dovrebbe includere i tag del modello di traduzione
+* aggiungi `{% load i18n %}` nella parte superiore del tuo modello per abilitare le traduzioni
+* Se il blocco di testo è un testo letterale, puoi usare il tag modello `{% trans %}`
+* Se il blocco di testo include variabili, dovresti usare la coppia di tag modello `{% blocktrans %}` e `{% endblocktrans %}`. Se stai includendo spazio bianco di riempimento o interruzioni di linea, usa `trimmed` per rimuoverlo automaticamente quando il file locale viene generato: `{% blocktrans trimmed %}`
+
+### Esempi
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/it_IT/content/index.md b/locale/it_IT/content/index.md
new file mode 100644
index 00000000..33ec89ca
--- /dev/null
+++ b/locale/it_IT/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Titolo: Benvenuto Data: 13-04-2021
+- - -
+
+BookWyrm è un social network per monitorare la lettura, parlare di libri, scrivere recensioni, e scoprire cosa leggere dopo. La Federazione permette agli utenti di BookWyrm di unirsi a piccole comunità di fiducia che possono connettersi tra loro e con altri servizi ActivityPub come Mastodon e Pleroma.
+
+## Funzionalità
+Dal momento che il progetto è ancora nelle sue prime fasi, le caratteristiche stanno crescendo ogni giorno, e c'è un sacco di spazio per suggerimenti e idee. Apri una [segnalazione](https://github.com/bookwyrm-social/bookwyrm/issues) per avviare una conversazione!
+
+- Pubblicazioni sui libri
+    - Componi le recensioni, con o senza valutazioni, che vengono aggregate nella pagina del libro
+    - Componi altri tipi di stati sui libri, come:
+        - Commenti su un libro
+        - Citazioni o estratti
+    - Rispondi agli stati
+    - Visualizza le recensioni aggregate di un libro attraverso le istanze di BookWyrm collegate
+    - Differenziare le recensioni locali e federate e la valutazione nel tuo feed di attività
+- Monitorare l'attività di lettura
+    - Libri sugli scaffali "da leggere", "letture correnti" e "letti"
+    - Creare scaffali personalizzati
+    - Salva le date di inizio/fine lettura, così come gli aggiornamenti di avanzamento
+    - Aggiorna chi ti segue sull'attività di lettura (opzionalmente, e con controlli sulla privacy)
+    - Crea liste di libri che possono essere aperte al contributo di chiunque, curate o modificate solo dal creatore
+- Federazione con Activitypub
+    - Trasmetti e ricevi stati e attività dell'utente
+    - Condividere i dati dei libri tra istanze per creare un database di metadati in rete
+    - Identifica i libri condivisi tra istanze e aggrega contenuti correlati
+    - Segui e interagisci con gli utenti tra le istanze di BookWyrm
+    - Interopera con i servizi di ActivityPub diversi da BookWyrm (attualmente, Mastodon è supportato)
+- Controlli specifici sulla privacy
+    - Livelli privati, solo follower e pubblici per la pubblicazione degli scaffali ed elenchi
+    - Opzione per gli utenti di approvare manualmente i follower
+    - Consenti il blocco e la segnalazione per moderazione
diff --git a/locale/it_IT/content/pages/index.md b/locale/it_IT/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/it_IT/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/it_IT/content/running_bookwyrm/cli.md b/locale/it_IT/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..a098ff53
--- /dev/null
+++ b/locale/it_IT/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Titolo: Strumento linea di comando Data: 2021-11-11 Ordine: 9
+- - -
+
+Gli sviluppatori e i gestori di istanze di Bookwyrm possono utilizzare lo script `bw-dev` per le attività comuni. Questo può rendere i tuoi comandi più brevi, più facile da ricordare, e più difficile da sbagliare.
+
+Una volta installato Bookwyrm [in produzione](installing-in-production.html) o [in sviluppo](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), è possibile eseguire lo script dalla riga di comando con `. bw-dev` seguito dal sottocomando che si desidera eseguire.
+
+## Scorciatoie Docker
+
+### bash
+
+Apri una sessione interattiva `bash` all'interno del contenitore `web` docker.
+
+### build
+
+Equivalente a `docker-compose build`.
+
+### dbshell
+
+Apri una shell interattiva per il database Postgres. Spero che tu sappia cosa stai facendo.
+
+### runweb args
+
+Esegue un comando arbitrario (rappresentato da `args`) nel contenitore `web`.
+
+Equivalente a `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Esegue un comando arbitrario nel contenitore `web` (rappresentato sopra da `args`) con porte esposte. Questo è utile se vuoi eseguire `test pdb` perché `runweb` non esporrà il prompt `pdb`.
+
+Equivalente a `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Apri una shell interattiva di Django all'interno del contenitore docker `web`. Puoi usarlo se vuoi eseguire direttamente i comandi della shell Django.
+
+### up [args]
+
+Avvia o riavvia i contenitori Docker, opzionalmente includi gli argomenti (rappresentati da `args`). Equivalente a `docker-compose up --build [args]`
+
+## Gestione del database
+
+### initdb
+
+Inizializza un database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Esegue il comando `makemigrations` di Django all'interno del contenitore Docker. Se hai cambiato la struttura del database in un ramo di sviluppo, dovrai eseguirlo così che le modifiche abbiano effetto. Facoltativamente, puoi specificare una migrazione specifica da eseguire, ad esempio `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Esegue il comando `migrate` di Django all'interno del contenitore Docker. È sempre necessario eseguire questo dopo `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resetta il database. **Questo comando eliminerà l'intero database di Bookwyrm**, quindi avvierà un nuovo database ed eseguirà tutte le migrazioni. È necessario eliminare qualsiasi file di migrazione recente che non si desidera eseguire, _prima di_ eseguire `resetdb`.
+
+## Gestione di un'istanza Bookwyrm
+
+### compile_themes
+
+Compila tutti i temi di BookWyrm, che sono file `*.scss` in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Genera un'anteprima per siti, utenti e libri. Può richiedere un po' di tempo se il database è molto grande. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Genera le thumbnail per le copertine dei libri.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Riavvia il contenitore Docker `celery_worker`.
+
+### update
+
+Quando ci sono cambiamenti in `production`, puoi aggiornare la tua istanza senza tempo fuori servizio.
+
+Questo comando fa `git pull` degli ultimi aggiornamenti sul branch `production`, genera immagini docker se necessario, esegue migrazioni Django, aggiorna i file statici e riavvia tutti i contenitori Docker.
+
+### admin_code
+
+Ottiene il codice amministratore segreto utilizzato per registrare l'utente amministratore iniziale su una nuova istanza di BookWyrm.
+
+## Impostazione dello storage compatibile con S3
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Sviluppo e test
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compila file di traduzione. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Esegui test con `pytest`.
+
+### deactivate_2fa
+
+Disattiva l'autenticazione a due fattori per un determinato utente.
+
+### manual_confirm
+
+Conferma l'email degli utenti, imposta l'utente a attivare.
diff --git a/locale/it_IT/content/running_bookwyrm/external-storage.md b/locale/it_IT/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..782674fa
--- /dev/null
+++ b/locale/it_IT/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Titolo: Archivio esterno Data: 2021-06-07 Ordine: 7
+- - -
+
+Per impostazione predefinita, BookWyrm utilizza memoria locale per le risorse statiche (favicon, avatar predefinito, ecc., e i supporti (avatar utente, copertine di libri, ecc.), ma è possibile utilizzare un servizio di archiviazione esterno per servire questi file. BookWyrm utilizza `django-storages` per gestire l'archiviazione esterna, come servizi compatibili con S3, Apache Libcloud o SFTP.
+
+## Servizi S3 Compatibili
+
+### Configurazione
+
+Crea un secchio al tuo servizio S3 compatibile, insieme ad un ID chiave di accesso e a una chiave di accesso segreto. Questi possono essere ospitati autonomamente, come [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) o [MinIO](https://min.io/) (GNU AGPL v3.), o commerciale ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+Questa guida è stata testata contro l'archivio oggetti di Scaleway. Se utilizzi un altro servizio, per favore condividi la tua esperienza (specialmente se hai dovuto fare passi diversi) scrivendo sul repository [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation).
+
+### Cosa ti aspetta
+
+Se stai iniziando una nuova istanza di BookWyrm, il processo sarà:
+
+- Imposta il tuo servizio di archiviazione esterno
+- Attiva memoria esterna su BookWyrm
+- Avvia la tua istanza BookWyrm
+- Aggiorna il connettore dell'istanza
+
+Se hai già avviato la tua istanza e le immagini sono state caricate nell'archivio locale, il processo sarà:
+
+- Configura il tuo servizio di archiviazione esterno
+- Copia i file multimediali locali su memoria esterna
+- Abilitare memoria esterna su BookWyrm
+- Riavvia l'istanza di BookWyrm
+- Aggiornare il connettore istanza
+
+### Impostazioni BookWyrm
+
+Modifica il tuo file `.env` senza commentare le righe seguenti:
+
+- `AWS_ACCESS_KEY_ID`: ID della tua chiave di accesso
+- `AWS_SECRET_ACCESS_KEY`: la chiave di accesso segreto
+- `AWS_STORAGE_BUCKET_NAME`: nome del tuo bucket
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` per AWS, `"fr-par"` per Scaleway o `"nyc3"` per l'Oceano digitale
+
+Se il servizio compatibile con S3 è Amazon AWS, è necessario essere impostati. In caso contrario, dovrete annullare il commento alle seguenti righe:
+
+- `AWS_S3_CUSTOM_DOMAIN`: il dominio che servirà le risorse, ad esempio `"example-bucket-name.s3.fr-par.scw.cloud"` o `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: l'endpoint S3 API, ad esempio `"https://s3.fr-par.scw.cloud"` o `"한://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copia media locali su memoria esterna
+
+Se l'istanza BookWyrm è già in esecuzione e i media sono stati caricati (avatar utente, copertine del libro…), dovrai migrare i media caricati sul tuo secco.
+
+Questo compito è stato fatto con il comando:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Attiva memoria esterna su BookWyrm
+
+Per attivare la memoria esterna compatibile con S3, dovrai modificare la tua `. nv` file cambiando il valore della proprietà per `USE_S3` da `false` a `vero`:
+
+```
+USE_S3=true
+```
+
+Se la memoria esterna viene servita su HTTPS (che la maggior parte sono attualmente), avrai anche bisogno di assicurarsi che `USE_HTTPS` sia impostato su `true`in modo che le immagini saranno caricate su HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Risorsa statiche
+
+Quindi, è necessario eseguire il seguente comando, per copiare gli asset statici nel proprio bucket S3:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### Impostazioni CORS
+
+Una volta che gli asset statici sono stati raccolti, è necessario impostare il CORS per il vostro secco.
+
+Alcuni servizi come Digital Ocean forniscono un'interfaccia per impostarla, vedi [Digital Ocean doc: Come configurare CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+Se il servizio non fornisce un'interfaccia, è comunque possibile configurare CORS con la riga di comando.
+
+Creare un file chiamato `cors.json`con il seguente contenuto:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www. Y_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Sostituire `MY_DOMAIN_NAME` con il nome di dominio della tua istanza.
+
+Quindi, eseguire il comando seguente:
+
+```bash
+./bw-dev set_cors_to_s3 cors.jsonName
+```
+
+Nessuna uscita significa che dovrebbe essere buona.
+
+Se stai iniziando una nuova istanza di BookWyrm, puoi tornare alle istruzioni di configurazione in questo momento. In caso negativo, continuare a leggere.
+
+### Riavviare l'istanza
+
+Una volta che la migrazione dei media è stata fatta e gli asset statici sono raccolti, è possibile caricare la nuova `. configurazione nv` e riavvia l'istanza con:
+
+```bash
+./bw-dev su -d
+```
+
+Se tutto va bene, la tua memoria è stata cambiata senza tempi di inattività server. Se mancano alcuni tipi di carattere (e la console JS del tuo browser si illumina con avvisi sul CORS), qualcosa è andato storto [qui](#cors-settings). In questo caso potrebbe essere bene controllare le intestazioni di una richiesta HTTP contro un file sul vostro secchi:
+
+```bash
+curl -X OPTIONS -H 'Origine: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-method: GET"
+```
+
+Sostituire `MY_DOMAIN_NAME` con il nome del dominio di istanza, `BUCKET_URL` con l'URL per il tuo secchio, è possibile sostituire il percorso del file con qualsiasi altro percorso valido sul tuo secco.
+
+Se vedi un messaggio, soprattutto un messaggio che inizia con `<Error><Code>CORSForbidden</Code>`, non ha funzionato. Se non vedi alcun messaggio, ha funzionato.
+
+Per un esempio attivo, ci può essere una manciata di file che sono stati creati localmente durante il tempo tra la migrazione dei file all'archivio esterno, e riavviare l'app in modo che usi la memoria esterna. Per garantire che tutti i file rimanenti siano caricati nella memoria esterna dopo il passaggio all'esterno, puoi usare il seguente comando, che caricherà solo i file che non sono già presenti nella memoria esterna:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Aggiornando il connettore istanza
+
+*Nota: È possibile saltare questo passo se si esegue una versione aggiornata di BookWyrm; nel settembre 2021 il "connettore di auto" è stato rimosso in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+Affinché l'URL corretto possa essere utilizzato quando si visualizzano i risultati di ricerca locali di un libro dobbiamo modificare il valore per la base URL delle immagini di copertina.
+
+I dati del connettore possono essere accessibili tramite l'interfaccia di amministrazione Django, situata all'url `http://MY_DOMAIN_NAME/admin`. Il connettore per la tua istanza è il primo record del database, quindi puoi accedere al connettore con questo URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+Il campo _Covers url_ è definito per impostazione predefinita come `https://MY_DOMAIN_NAME/images`, devi modificarlo in `https://S3_STORAGE_URL/images`. Quindi, fare clic sul pulsante _Salva_ e voila<unk>!
+
+Dovrai aggiornare il valore per _Copertina url_ ogni volta che cambi l'URL per la tua archiviazione.
diff --git a/locale/it_IT/content/running_bookwyrm/install-prod-dockerless.md b/locale/it_IT/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..dbd26bbb
--- /dev/null
+++ b/locale/it_IT/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installazione Senza Docker
+Date: 2022-10-02
+Order: 2
+---
+
+Questo progetto è ancora giovane e al momento non è molto stabile, quindi vi prego di procedere con cautela quando si esegue in produzione. Questo metodo di installazione è più coinvolto, e quindi è per admin più esperti. L'installazione via docker è raccomandato. Questo metodo di installazione assume che tu hai ssl configurato con certifiche disponibili
+
+## Configurazione server
+- Ottieni un nome di dominio e imposta il DNS per il server. Dovrai indicare i nameservers del tuo dominio sul tuo provider DNS al server in cui ospiterai BookWyrm. Qui ci sono istruzioni per [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Impostare il server con firewall appropriati per l'esecuzione di un'applicazione web (questo set di istruzioni viene testato contro Ubuntu 20.04). Qui ci sono istruzioni per [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Impostare un servizio email (come [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) e le impostazioni SMTP/DNS appropriate. Utilizza la documentazione del servizio per configurare il DNS
+- Installare le dipendenze. Su debian questo potrebbe apparire come `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`,
+
+## Installa e configura BookWyrm
+
+Il ramo di produzione `` di BookWyrm contiene una serie di strumenti non presenti sul ramo `principale` che sono adatti per funzionare nella produzione, come `docker-compose` modifiche per aggiornare i comandi o la configurazione predefinita dei container, e cambiamenti individuali alla configurazione del contenitore per abilitare cose come SSL o backup regolari. Non tutte queste modifiche effetto l'installazione dockerless, tuttavia il ramo `production` è ancora consigliato
+
+Istruzioni per la gestione di BookWyrm in produzione senza Docker:
+
+- Crea ed inserisci anche la directory che vuoi installare bookwyrm. Per esempio, `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Scarica il codice applicativo: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Passa al ramo `produzione`: `git checkout production`
+- Crea il tuo file delle variabili di ambiente, `cp .env.example .env`e aggiorna quanto segue:
+    - `SECRET_KEY` <unk> Una stringa segreta di personaggi difficile da indovinare
+    - `DOMANDA` <unk> Il tuo dominio web
+    - `POSTGRES_PASSWORD` <unk> Imposta una password sicura per il database
+    - `POSTGRES_HOST` <unk> Impostare a `localhost` (la macchina che esegue il vostro db)
+    - `POSTGRES_USER` <unk> Impostare a `bookwyrm` (raccomandato) o qualcosa di personalizzato (configurato in seguito)
+    - `POSTGRES_DB` <unk> Impostare a `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` <unk> Impostare a nulla (multare su una macchina locale con un firewall)
+    - `REDIS_ACTIVITY_HOST` <unk> Impostare su `localhost` (la macchina che esegue redis)
+    - `REDIS_BROKER_PASSWORD` <unk> Impostare a nulla (multare su una macchina locale con un firewall)
+    - `REDIS_BROKER_HOST` <unk> Imposta su `localhost` (la macchina che esegue redis)
+    - `EMAIL_HOST_USER` <unk> L'indirizzo "da" che la tua app utilizzerà quando invierai un'email
+    - `EMAIL_HOST_PASSWORD` <unk> La password fornita dal vostro servizio email
+- Configura nginX
+    - Copia il server_config in nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Crea una copia della configurazione del modello di produzione e impostalo per l'uso in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Aggiorna nginx `bookwyrm.conf`:
+        - Sostituisci `your-domain.com` con il tuo nome di dominio ovunque nel file (incluse le righe che sono attualmente commentate)
+        - Sostituisci `/app/` con la tua directory di installazione `/opt/bookwyrm/` ovunque nel file (incluso commentato)
+        - Decommenta le righe da 18 a 67 per consentire l'inoltro a HTTPS. Dovresti avere abilitato due blocchi `server`
+        - Cambia i percorsi `ssl_certificate` e `ssl_certificate_key` alla tua catena completa e alla tua posizione privkey
+        - Cambia la riga 4 in modo che dica `server localhost:8000`. Puoi scegliere una porta diversa qui se desideri
+        - Se stai utilizzando un altro web-server sulla tua macchina host, dovrai seguire le istruzioni [reverse-proxy](/reverse-proxy.html)
+    - Abilita la configurazione nginx: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`Name
+     - Ricarica nginx: `systemctl reload nginx`
+- Configura l'ambiente virtuale python
+    - Rendi la directory python venv nella tua directory di installazione: `mkdir venv` `python3 -m venv ./venv`
+    - Installa le dipendenze di python di bookwyrm con pip: `./venv/bin/pip3 install -r requirements.txt`
+- Crea il database postgresql di bookwyrm. Assicurati di cambiare la password in quello che hai impostato nel config: `.env`:
+
+    `sudo -i -u postgres psql`
+
+```
+CREA bookwyrm UTILIZZATORE CON PASSWORD 'securedbypassword123';
+
+CREA DATABASE bookwyrm TEMPLATE template0 CODIFICAZIONE 'UNICODIZIONE'.
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+CONSERVARE TUTTI I PRIVILEGI SUL bookwyrm di DATABASE A bookwyrm;
+
+\q
+```
+
+- Migrare lo schema del database eseguendo `venv/bin/python3 manage.py Migrate`
+- Inizializza il database con `venv/bin/python3 manage.py initdb`
+- Crea lo statico eseguendo `venv/bin/python3 manage.py collectstatico --no-input`
+- Se si desidera utilizzare un archivio esterno per risorse statiche e file multimediali (come un servizio compatibile con S3), [segui le istruzioni](/external-storage.html) fino a quando ti dice di tornare qui
+- Crea e imposta il tuo utente di `bookwyrm`
+    - Crea il bookwyrm di sistema utente: `useradd bookwyrm -r`
+    - Cambia il proprietario della tua cartella di installazione in bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - Ora dovresti eseguire i comandi relativi a bookwyrm come utente bookwyrm: `sudo -u bookwyrm echo Io sono l'utente $(whoami)`
+
+- Generare il codice di amministrazione con `sudo -u bookwyrm venv/bin/python3 manage. y admin_code`, e copia il codice di amministrazione da usare quando crei il tuo account amministrativo.
+- È possibile ottenere il tuo codice in qualsiasi momento rieseguendo quel comando. Ecco un risultato di esempio:
+
+``` { .sh }
+*********************************************
+Usa questo codice per creare il tuo account amministratore:
+c6c35779-af3a-4091-b330-c026610920d6
+***********************************************************
+```
+
+- Crea e configurare lo script di esecuzione
+    - Crea un file chiamato dockerless-run.sh e riempirlo con i seguenti contenuti
+
+``` { .sh }
+#!/bin/bash
+
+# stop se un processo non riesce
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.:8000 &
+
+# sedano
+/opt/bookwyrm/venv/bin/sedano -A celerywyrm worker -l info -Q High_priority,medium_priority, ow_priority &
+/opt/bookwyrm/venv/bin/sedano -A battuto celerywyrm -l INFO --scheduler django_celery_beat. chedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/sedano -A fiore di sedano sedano &
+```
+    - Sostituisci `/opt/bookwyrm` con la cartella di installazione
+    - Cambia `8000` al tuo numero di porta personalizzato
+    - Flower è stato disabilitato qui perché non è autoconfigurato con la password impostata nel file `.env`
+- Puoi ora eseguire BookWyrm con: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- L'applicazione deve essere in esecuzione nel tuo dominio. Quando carichi il dominio, dovresti ottenere una pagina di configurazione che confermi le impostazioni dell'istanza e un modulo per creare un account amministratore. Usa il tuo codice amministratore per registrarsi.
+- Si consiglia di configurare BookWyrm per autorun con un servizio di sistema. Ecco un esempio:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online. arget
+
+[Service]
+User=bookwyrm
+Type=simple
+Riavvio=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+È necessario impostare un lavoro di Cron per avviare automaticamente il servizio su un riavvio del server.
+
+Congratulazioni! Ce l'hai fatta!! Configura la tua istanza come preferisci.
+
+## Partecipa
+
+Vedi [Partecipa](https://joinbookwyrm.com/get-involved/) per dettagli.
diff --git a/locale/it_IT/content/running_bookwyrm/install-prod.md b/locale/it_IT/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..0d10ce9f
--- /dev/null
+++ b/locale/it_IT/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Configurazione server
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Installa Docker e docker-compose](https://docs.docker.com/compose/install/)
+
+## Installa e configura BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Ecco un output di esempio:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congratulazioni! Ce l'hai fatta!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/it_IT/content/running_bookwyrm/moderation.md b/locale/it_IT/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/it_IT/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/it_IT/content/running_bookwyrm/monitoring-queue.md b/locale/it_IT/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..f8fc1c5a
--- /dev/null
+++ b/locale/it_IT/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Coda Da Monitoraggio
+Date: 2022-11-23
+Order: 6
+---
+
+Ci potrebbero essere eventi dove le tue istanze si comportano lentamente. Una opzione sarebbe quella di ispezionare la coda per vedere, se alcuni lavori si bloccano. Continua a leggere per capire come.
+
+## Celery
+
+BookWyrm sta usando [Sedery](https://docs.celeryq.dev/en/stable/) per gestire processi in background.
+
+## Flower
+
+Per guardare lavori di Celery in tempo reale BookWyrm utilizza [Fiore](https://flower.readthedocs.io/en/latest/).
+
+Nel caso in cui non sia stato possibile modificare il docker-compose.yml [``](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) è possibile trovare il servizio su [porta 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). Vale a dire: `https://MY_DOMAIN_NAME:8888/`.
+
+### Compiti
+
+Puoi trovare [`@app.task` annotati](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) attività nel codebase.
diff --git a/locale/it_IT/content/running_bookwyrm/optional_features.md b/locale/it_IT/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/it_IT/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/it_IT/content/running_bookwyrm/reverse-proxy.md b/locale/it_IT/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/it_IT/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/it_IT/content/running_bookwyrm/updating.md b/locale/it_IT/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..62884168
--- /dev/null
+++ b/locale/it_IT/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Titolo: Aggiornare la tua istanza Data: 2022-11-17 Ordine: 3
+- - -
+
+Quando ci sono cambiamenti disponibili nel ramo di produzione, è possibile installare e farli funzionare sulla vostra istanza utilizzando il comando `. aggiornamento bw-dev`. Questo fa un certo numero di cose:
+
+- `git pull` ottiene il codice aggiornato dal repository Git. Se si verificano conflitti, potrebbe essere necessario eseguire `git pull` separatamente e risolvere i conflitti prima di provare `. bw-dev aggiornamento` di nuovo script.
+- `docker-compose build` ricostruisce le immagini, garantendo che i pacchetti corretti siano installati. Questo passaggio richiede molto tempo ed è necessario solo quando le dipendenze (compresi i requisiti pip `. xt` pacchetti) sono cambiate, in modo da poter commentare fuori se si desidera un percorso di aggiornamento più rapido e non dispiacere-commentare se necessario.
+- `docker-compose run --rm web python manage.py migrate` esegue le migrazioni del database in Django utilizzando le immagini Docker appena create
+- `docker-compose run --rm web python manage.py collectstatic --no-input` carica qualsiasi file statico aggiornato (come JavaScript e CSS)
+- `docker-compose giù: docker-compose up -d` riavvierà tutti i contenitori docker e userà le immagini di nuova costruzione (attenzione: tempi di fermo durante il riavvio)
+
+## Ricostruisci flussi attività
+
+I feed di ogni utente sono memorizzati in Redis. Per ripopolare un flusso, utilizzare il comando gestione:
+
+``` { .sh }
+./bw-dev populate_streams
+# O utilizza docker-compose direttamente
+docker-compose run --rm web python manage.py populate_streams
+```
+
+Se qualcosa è andato terribilmente male, i dati del flusso possono essere cancellati.
+
+``` { .sh }
+docker-compose esegui --rm web python manage.py erase_stream
+```
diff --git a/locale/it_IT/content/using_bookwyrm/adding-books.md b/locale/it_IT/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..ada33aa3
--- /dev/null
+++ b/locale/it_IT/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Aggiungere libri
+Date: 2022-07-29
+Order: 2
+---
+
+Ci sono alcuni modi diversi per aggiungere libri alla vostra istanza BookWyrm! Quando non trovi il libro che stai cercando, provare queste opzioni in ordine -- è meglio importare un libro che crearne uno da zero.
+
+## Carica libri da altri cataloghi
+
+Se il libro che stai cercando non è disponibile sulla tua istanza, ci sono diversi modi per aggiungerlo. Il modo migliore è quello di importarlo da una fonte esterna -- la tua istanza può importare libri da altre istanze di BookWyrm, così come [OpenLibrary](http://openlibrary.org/) e [Inventaire](http://inventaire.io/). Se non ci sono risultati per la tua ricerca, queste fonti verranno automaticamente interrogate, e verrà visualizzate con un pulsante "**Importa libro**". Se ci sono i risultati di ricerca locali che non sono quello che stai cercando, è possibile cliccare sul link "**Carica i risultati da altri cataloghi**" per caricare più risultati.
+
+
+## Aggiungere un'altra versione
+
+Se hai trovato il libro che vuoi, ma non la giusta edizione, puoi aggiungere un'altra edizione al lavoro dalla lista delle edizioni. Clicca sul link sottostante la descrizione che ti dice quante edizioni ci sono (per esempio, "4 edizioni****"). Nella parte inferiore della lista delle edizioni, c'è un pulsante per "**Aggiungere un'altra edizione**".
+
+## Aggiunge un libro nuovo
+
+Una volta che hai provato a cercare il tuo libro, importandolo da un altro catalogo e trovare altre edizioni del libro, puoi aggiungere un nuovo libro manualmente. Il link per aggiungere manualmente un libro è nella parte inferiore della pagina di ricerca quando vengono visualizzati cataloghi esterni. È inoltre possibile navigare direclty a `/create-book` sulla tua istanza.
diff --git a/locale/it_IT/content/using_bookwyrm/posting-statuses.md b/locale/it_IT/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..87fb31bf
--- /dev/null
+++ b/locale/it_IT/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Titolo: Stato di pubblicazione Data: 2022-04-30 Ordine: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Tipi di status
+
+### Commento dell'utente
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/ja_JP/LC_MESSAGES/messages.po b/locale/ja_JP/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..9fa66663
--- /dev/null
+++ b/locale/ja_JP/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Japanese\n"
+"Language: ja_JP\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: ja\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr "BookWyrm ドキュメント"
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr "BookWyrmの使用と貢献のためのガイド"
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr "使い方と貢献する方法"
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr "BookWyrm: ソーシャルリーディングとレビュー"
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "参加する"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr "活動に参加する"
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "お問い合わせ"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr "ソースコード"
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr "ドキュメンテーション"
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr "<strong>BookWyrm</strong> は、<a href='https://www.mousereeve.com/'>Mouse Reeve</a> によって維持されている、共同作業による反企業的なソフトウェアです。"
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr "<a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a> で BookWyrm をサポート。"
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr "BookWyrm on GitHub"
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr "このページへの貢献"
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr "詳しく見る"
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/ja_JP/content/codebase/activitypub.md b/locale/ja_JP/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/ja_JP/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/ja_JP/content/codebase/permissions.md b/locale/ja_JP/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/ja_JP/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/ja_JP/content/contributing/contributing.md b/locale/ja_JP/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/ja_JP/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/ja_JP/content/contributing/debug_toolbar.md b/locale/ja_JP/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/ja_JP/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/ja_JP/content/contributing/install-dev.md b/locale/ja_JP/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/ja_JP/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/ja_JP/content/contributing/style_guide.md b/locale/ja_JP/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/ja_JP/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/ja_JP/content/contributing/translation.md b/locale/ja_JP/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/ja_JP/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/ja_JP/content/index.md b/locale/ja_JP/content/index.md
new file mode 100644
index 00000000..a139a720
--- /dev/null
+++ b/locale/ja_JP/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## 機能紹介
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- 本について投稿
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - ステータスへ返信
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- 読書アクティビティを追跡
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- 詳細なプライバシー管理
+    - 投稿、本棚、リストのための非公開、フォロワーのみ、および公開のプライバシーレベル
+    - ユーザーが手動でフォロワーを承認するためのオプション
+    - ブロックとモデレーションのフラグ付けが可能
diff --git a/locale/ja_JP/content/pages/index.md b/locale/ja_JP/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/ja_JP/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/ja_JP/content/running_bookwyrm/cli.md b/locale/ja_JP/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/ja_JP/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/ja_JP/content/running_bookwyrm/external-storage.md b/locale/ja_JP/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/ja_JP/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/ja_JP/content/running_bookwyrm/install-prod-dockerless.md b/locale/ja_JP/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/ja_JP/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/ja_JP/content/running_bookwyrm/install-prod.md b/locale/ja_JP/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/ja_JP/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/ja_JP/content/running_bookwyrm/moderation.md b/locale/ja_JP/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/ja_JP/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/ja_JP/content/running_bookwyrm/monitoring-queue.md b/locale/ja_JP/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/ja_JP/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/ja_JP/content/running_bookwyrm/optional_features.md b/locale/ja_JP/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/ja_JP/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/ja_JP/content/running_bookwyrm/reverse-proxy.md b/locale/ja_JP/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/ja_JP/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/ja_JP/content/running_bookwyrm/updating.md b/locale/ja_JP/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/ja_JP/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/ja_JP/content/using_bookwyrm/adding-books.md b/locale/ja_JP/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/ja_JP/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/ja_JP/content/using_bookwyrm/posting-statuses.md b/locale/ja_JP/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/ja_JP/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/ko_KR/LC_MESSAGES/messages.po b/locale/ko_KR/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..81c74725
--- /dev/null
+++ b/locale/ko_KR/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Korean\n"
+"Language: ko_KR\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: ko\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/ko_KR/content/codebase/activitypub.md b/locale/ko_KR/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/ko_KR/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/ko_KR/content/codebase/permissions.md b/locale/ko_KR/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/ko_KR/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/ko_KR/content/contributing/contributing.md b/locale/ko_KR/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/ko_KR/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/ko_KR/content/contributing/debug_toolbar.md b/locale/ko_KR/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/ko_KR/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/ko_KR/content/contributing/install-dev.md b/locale/ko_KR/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/ko_KR/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/ko_KR/content/contributing/style_guide.md b/locale/ko_KR/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/ko_KR/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/ko_KR/content/contributing/translation.md b/locale/ko_KR/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/ko_KR/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/ko_KR/content/index.md b/locale/ko_KR/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/ko_KR/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/ko_KR/content/pages/index.md b/locale/ko_KR/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/ko_KR/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/ko_KR/content/running_bookwyrm/cli.md b/locale/ko_KR/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/ko_KR/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/ko_KR/content/running_bookwyrm/external-storage.md b/locale/ko_KR/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/ko_KR/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/ko_KR/content/running_bookwyrm/install-prod-dockerless.md b/locale/ko_KR/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/ko_KR/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/ko_KR/content/running_bookwyrm/install-prod.md b/locale/ko_KR/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/ko_KR/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/ko_KR/content/running_bookwyrm/moderation.md b/locale/ko_KR/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/ko_KR/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/ko_KR/content/running_bookwyrm/monitoring-queue.md b/locale/ko_KR/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/ko_KR/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/ko_KR/content/running_bookwyrm/optional_features.md b/locale/ko_KR/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/ko_KR/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/ko_KR/content/running_bookwyrm/reverse-proxy.md b/locale/ko_KR/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/ko_KR/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/ko_KR/content/running_bookwyrm/updating.md b/locale/ko_KR/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/ko_KR/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/ko_KR/content/using_bookwyrm/adding-books.md b/locale/ko_KR/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/ko_KR/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/ko_KR/content/using_bookwyrm/posting-statuses.md b/locale/ko_KR/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/ko_KR/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/lt_LT/LC_MESSAGES/messages.po b/locale/lt_LT/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..d087bb8a
--- /dev/null
+++ b/locale/lt_LT/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Lithuanian\n"
+"Language: lt_LT\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=4; plural=(n%10==1 && (n%100>19 || n%100<11) ? 0 : (n%10>=2 && n%10<=9) && (n%100>19 || n%100<11) ? 1 : n%1!=0 ? 2: 3);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: lt\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/lt_LT/content/codebase/activitypub.md b/locale/lt_LT/content/codebase/activitypub.md
new file mode 100644
index 00000000..16d3e6d6
--- /dev/null
+++ b/locale/lt_LT/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Nariai ir santykiai
+Narių santykių sąveika atitinka standartinę „ActivityPub“ specifikaciją.
+
+- `Sekti`: užklausa gauti nario būsenas ir peržiūrėti tas, kurios turi tik stebėtojų privatumą
+- `Patvirtinti`: patvirtina kvietimą `Sekti` ir finalizuoja santykį
+- `Atmesti`: atmeta prašymą `Sekti`
+- `Blokuoti`: neleisti nariams matyti vienas kito būsenų ir neleisti užblokuotam nariui matyti profilio
+- `Atnaujinti`: atnaujina nario paskyrą ir nustatymus
+- `Ištrinti`: išaktyvuoja narį
+- `Grąžinti į pradinę būseną`: pakeičia `Sekimo` arba `Blokavimo` būseną
+
+### Būsenos
+#### Objekto tipai
+
+- `Užrašas`: tokiose paslaugose, kaip „Mastodon“, `Užrašas` yra pirminis būsenos tipas. Juose yra žinutė, prisegtukai, galima minėti narius arba atsakyti į bet kokio tipo būsenas. „BookWyrm“ `Užrašus` galima sukurti kaip tiesiogines žinutes arba atsakymus į kitas būsenas.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Komentaras`: knygos komentare minima knyga ir yra pranešimo tekstas.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Veiklos
+
+- `Sukurti`: išsaugo naują būseną duomenų bazėje.
+
+   **Užrašas**: „BookWyrm“ priima tik `Sukūrimo` veiklas, jei jos:
+
+   - Tiesioginės žinutės (pvz., `Užrašas`, kurio privatumo lygis `tiesioginis` ir minintis vietos narį);
+   - Susiję su knyga (būsenos tipas, kuriame yra laukelis `inReplyToBook`);
+   - Atsako į duomenų bazėje išsaugotas būsenas
+- `Ištrinti`: ištrina būseną
+- `Patinka`: pažymi, kad būsena patinka
+- `Pranešimas`: iškelia būseną į laiko juostą
+- `Grąžinti į pradinę būseną`: pakeičia `Patinka` arba `Pranešimo` būseną
+
+### Kolekcijos
+Naudotojo knygas ir sąrašus reprezentuoja [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objektai
+
+- `Lentyna`: nario knygų kolekcija. Kiekvienas naudotojas turi lentynas `perskaityti`, `skaitoma` ir `perskaityta`, kurios padeda sekti progresą.
+- `Sąrašas`: knygų rinkinys, kuriame gali būti kitų narių knygų, o ne tik sąrašą sukūrusių narių.
+
+#### Veiklos
+
+- `Sukurti`: prideda lentyną arba sąrašą į duomenų bazę.
+- `Ištrinti`: pašalina lentyną arba sąrašą.
+- `Pridėti`: prideda knygą į lentyną arba sąrašą.
+- `Pašalinti`: pašalina knygą iš lentynos arba sąrašo.
+
+
+## Alternatyvus serializavimas
+Kadangi „BookWyrm“ naudoja pasirinktinius objektų tipus (`Apžvalga`, `Komentaras`, `Citavimas`), kurių „ActivityPub“ nepalaiko, siunčiamos būsenos transformuojamos į standartinius tipus, kai siunčia arba peržiūri ne „BookWyrm“. `Apžvalga` paverčiama `Straipsniu`, o `Komentaras` ir `Citavimas` paverčiami `Užrašu` su nuoroda į knygą ir prisegtą viršelio nuotrauką.
diff --git a/locale/lt_LT/content/codebase/permissions.md b/locale/lt_LT/content/codebase/permissions.md
new file mode 100644
index 00000000..18f636f5
--- /dev/null
+++ b/locale/lt_LT/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Pavadinimas: Leidimai Data: 2021-04-18 Užsakymas: 2
+- - -
+
+Naudotojų prieiga prie įvairių funkcijų kontroliuojama per Django [integruotą autentifikacijos sistemą](https://docs.djangoproject.com/en/3.2/topics/auth/default/). Kai sukuriamas serveris, `initdb` scenarijus sukuria leidimų rinkinį, kuris priskiriamas prie grupių. Visi nauji nariai priskiriami prie `redaktoriaus` grupės, todėl jie gali redaguoti knygos metaduomenis.
+
+Serverio administratorius turi `supernaudotojo` teisę, kurios dėka gaunama prieiga prie Django administratoriaus (`/admin`) ir nariui suteikiami visi leidimai.
+
+## Leidimai ir grupės
+Šioje lentelėje rodomos keturios grupės (administratoriaus, moderatoriaus, redaktoriaus ir nario) bei kokius leidimus turi tos grupės naudotojas:
+
+|                        | administratorius | moderatorius | editor | user |
+| ---------------------- | ---------------- | ------------ | ------ | ---- |
+| edit instance settings | ✔️               | -            | -      | -    |
+| change user level      | ✔️               | -            | -      | -    |
+| manage federation      | ✔️               | ✔️           | -      | -    |
+| issue invites          | ✔️               | ✔️           | -      | -    |
+| deactivate users       | ✔️               | ✔️           | -      | -    |
+| delete posts           | ✔️               | ✔️           | -      | -    |
+| edit books             | ✔️               | ✔️           | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/lt_LT/content/contributing/contributing.md b/locale/lt_LT/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/lt_LT/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/lt_LT/content/contributing/debug_toolbar.md b/locale/lt_LT/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..6befb7d1
--- /dev/null
+++ b/locale/lt_LT/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Nustatyti
+
+- Naudodami git, išsičekautinkite į šaką [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar)
+- Komanda `git merge main` atnaujinkite savo šaką su `main` pakeitimais. Nors šaka periodiškai atnaujinama, gali būti, kad joje nėra naujausių pakeitimų.
+- Iš naujo subildinkite „Docker“, naudodami komandą `docker-compose up --build`, kad iš failo `requirements.txt` įdiegtumėte „Debug Toolbar“ biblioteką
+- Pasiekite programos `puslapį` tiesiogiai (o ne per `nginx`), naudodami portą `8000`
diff --git a/locale/lt_LT/content/contributing/install-dev.md b/locale/lt_LT/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/lt_LT/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/lt_LT/content/contributing/style_guide.md b/locale/lt_LT/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/lt_LT/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/lt_LT/content/contributing/translation.md b/locale/lt_LT/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/lt_LT/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/lt_LT/content/index.md b/locale/lt_LT/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/lt_LT/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/lt_LT/content/pages/index.md b/locale/lt_LT/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/lt_LT/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/lt_LT/content/running_bookwyrm/cli.md b/locale/lt_LT/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/lt_LT/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/lt_LT/content/running_bookwyrm/external-storage.md b/locale/lt_LT/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/lt_LT/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/lt_LT/content/running_bookwyrm/install-prod-dockerless.md b/locale/lt_LT/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/lt_LT/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/lt_LT/content/running_bookwyrm/install-prod.md b/locale/lt_LT/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..928f0c5f
--- /dev/null
+++ b/locale/lt_LT/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Inicializuokite duomenų bazę, paleidę `./bw-dev migrate`
+- Paleiskite programą (tai taip pat turėtų nustatyti Certbot ssl sertifikatą jūsų domenui) su `docker-compose up --build` ir įsitikinkite, kad visi vaizdai susikūrė sėkmingai
+    - Jei savo serveryje taip pat esate paleidę kitas paslaugas, galite gauti klaidų, pranešančių, kad paslaugoms nepavyksta naudoti porto. Norėdami išspręsti šią problemą, skaitykite [problemų sprendimo vadovą](#port_conflicts).
+- Kai sėkmingai susibildins dokeris, sustabdykite procesą, paspausdami `CTRL-C`
+- Nukreipkite HTTPS
+    - Faile `docker-compose.yml` atkomentuokite aktyvią certbot komandą, kuri diegia sertifikatą, taip pat atkomentuokite žemiau esančią eilutę, atsakingą už automatinius atnaujinimus.
+    - Norėdami įjungti HTTPS persiuntimą, faile `nginx/default.conf` atkomentuokite nuo 18 iki 50 eilutės. Turėtumėte būti įjungę du `serverio` blokus
+- Nustatykite `kroną`, kad sertifikatai visada būtų atnaujinti (užšifruokite sertifikatų galiojimo pasibaigimą už 90 dienų)
+    - Rašykite `crontab -e`, kad paredaguotumėte esamą krono failą
+    - pridėkite eilutę, kad programa bandytų atnaujinti kartą per dieną: `5 0 * * * cd /kelias/iki/jūsų/bookwyrm && docker-compose run --rm certbot`
+- Jei statinių ir medijos failų (pvz., su S3 paslauga susijusių failų) saugojimui norite naudoti išorinę saugyklą, [atlikite instrukcijose nurodytus žingsnius](/external-storage.html), kurie jus galiausiai nukreips grįžti čia
+- Inicializuokite savo programą komanda `./bw-dev setup` ir, kai kursite administratoriaus paskyrą, nukopijuokite administratoriaus kodą.
+    - `./bw-dev setup` išvestis turėtų baigtis jūsų administratoriaus kodu. Savo kodą galite gauti bet kuriuo metu, komandinėje eilutėje parašydami `./bw-dev admin_code`. Pateikiamas išvesties pavyzdys:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/lt_LT/content/running_bookwyrm/moderation.md b/locale/lt_LT/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/lt_LT/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/lt_LT/content/running_bookwyrm/monitoring-queue.md b/locale/lt_LT/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/lt_LT/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/lt_LT/content/running_bookwyrm/optional_features.md b/locale/lt_LT/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/lt_LT/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/lt_LT/content/running_bookwyrm/reverse-proxy.md b/locale/lt_LT/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/lt_LT/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/lt_LT/content/running_bookwyrm/updating.md b/locale/lt_LT/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/lt_LT/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/lt_LT/content/using_bookwyrm/adding-books.md b/locale/lt_LT/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..0acb22ce
--- /dev/null
+++ b/locale/lt_LT/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+Jei radote norimą knygą, tačiau nerandate norimo šios knygos leidimo, galite iš leidimų sąrašo prie darbo pridėti kitą leidimą. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. Nuoroda manualiai pridėti knygą yra paieškos puslapio apačioje, kai rodomi išoriniai katalogai. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/lt_LT/content/using_bookwyrm/posting-statuses.md b/locale/lt_LT/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/lt_LT/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/nl_NL/LC_MESSAGES/messages.po b/locale/nl_NL/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..3fae0f41
--- /dev/null
+++ b/locale/nl_NL/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-12-10 15:43\n"
+"Last-Translator: \n"
+"Language-Team: Dutch\n"
+"Language: nl_NL\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: nl\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr "BookWyrm Documentatie"
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr "Jouw handleiding om BookWyrm te gebruiken en er aan bij te dragen"
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr "Hoe te gebruiken en bij te dragen"
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr "BookWyrm: Sociaal Lezen en Beoordelen"
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "Wordt lid"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr "Doe mee"
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "Ondersteuning"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr "Broncode"
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr "Documentatie"
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr "<strong>BookWyrm</strong> is collaboratieve, anti-bedrijf software onderhouden door <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr "Steun BookWyrm op <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr "Doe mee"
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr "BookWyrm on GitHub"
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr "Draag bij aan deze pagina"
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr "Ontdek meer"
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr "Neem contact op met de beheerder"
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr "Licentie"
+
diff --git a/locale/nl_NL/content/codebase/activitypub.md b/locale/nl_NL/content/codebase/activitypub.md
new file mode 100644
index 00000000..eb08ac08
--- /dev/null
+++ b/locale/nl_NL/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Titel: ActivityPub Datum: 2021-04-20 Volgorde: 1
+- - -
+
+BookWyrm maakt gebruik van het [ActivityPub](http://activitypub.rocks/) protocol voor het verzenden en ontvangen van gebruikersactiviteit tussen andere BookWyrm instanties en andere diensten die ActivityPub implementeren zoals [Mastodon](https://joinmastodon.org/). Om gegevens van boeken te verwerken heeft BookWyrm een handvol uitgebreide activiteitstypen die niet deel zijn van de standaard, maar leesbaar zijn voor andere BookWyrm instanties.
+
+## Activiteiten en Objecten
+
+### Gebruikers en relaties
+Gebruikersrelatie interacties volgen de standaard ActivityPub specificatie.
+
+- `Follow`: verzoek om statussen van een gebruiker te ontvangen en hun statussen met alleen volgers-only privacy te bekijken
+- `Accept`: keurt een `Follow` goed en voltooit de relatie
+- `Reject`: weigert een `Follow`
+- `Block`: voorkomen dat gebruikers elkaars statussen zien, en voorkomt dat de geblokkeerde gebruiker het profiel van de speler bekijkt
+- `Update`: updates het profiel en instellingen van een gebruiker
+- `Delete`: deactiveert een gebruiker
+- `Undo`: draait een `Follow` of `Block` terug
+
+### Statussen
+#### Objecttypes
+
+- `Note`: Voor diensten zoals Mastodon, `Note`s zijn het primaire status type. Ze bevatten een bericht, bijlagen, kunnen gebruikers vermelden en zijn antwoorden op statussen van elk type. Binnen BookWyrm kan `Note`s alleen worden gemaakt als directe berichten of als antwoord op andere statussen.
+- `Review`: Een recensie is een status in reactie op een boek (aangegeven door het `inReplyToBook` veld) die een titel, lichaam en numerieke beoordeling tussen 0 (niet beoordeeld) en 5 heeft.
+- `Comment`: Een reactie op een boek vermeldt een boek en bevat een bericht.
+- `Quotation`: Een citaat heeft een bericht, een extract uit een boek en vermeldt een boek.
+
+
+#### Activiteiten
+
+- `Create`: slaat een nieuwe status op in de database.
+
+   **Let op**: BookWyrm accepteert alleen `Create` activiteiten als ze zijn:
+
+   - Directe berichten (d.w.z. `Note`met het privacyniveau `direct`, die een lokale gebruiker vermeldt),
+   - Gerelateerd aan een boek (van een aangepast statustype dat het veld `inReplyToBook` bevat),
+   - Antwoorden op bestaande statussen opgeslagen in de database
+- `Delete`: Verwijdert een status
+- `Like`: Maakt een favoriet aan op de status
+- `Announce`: Vergroot de status in de tijdlijn van de speler
+- `Undo`: draait een `Like` of `Announce` terug
+
+### Verzamelingen
+De boeken en lijsten van gebruikers worden vertegenwoordigd door [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objecten
+
+- `Shelf`: Een boekverzameling van gebruikers. Standaard heeft elke gebruiker een `om te lezen`, `lezen`, en `gelezen` plank die gebruikt worden om de leesvoortgang bij te houden.
+- `List`: Een verzameling boeken waarbij items kunnen worden bijgedragen door andere gebruikers dan degene die de lijst hebben gemaakt.
+
+#### Activiteiten
+
+- `Aanmaken`: Voegt een plank of een lijst toe aan de database.
+- `Delete`: Verwijdert een plank of lijst.
+- `Add`: Voegt een boek toe aan een plank of lijst.
+- `Remove`: Verwijdert een boek van een plank of lijst.
+
+
+## Alternatieve serialisatie
+Omdat BookWyrm gebruikmaakt van aangepaste objecttypes (`Review`, `Comment`, `Quotation`) die niet worden ondersteund door ActivityPub, worden statussen omgezet in standaard types wanneer ze worden verzonden naar of bekeken door niet-BookWyrm diensten. `Review`s worden omgezet in `Article`s, en `Comment`s en `Quotation`s worden omgezet in `Note`s, met een koppeling naar het boek en de bijgevoegde omslagafbeelding.
diff --git a/locale/nl_NL/content/codebase/permissions.md b/locale/nl_NL/content/codebase/permissions.md
new file mode 100644
index 00000000..b8ff99a7
--- /dev/null
+++ b/locale/nl_NL/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Titel: Permissies Datum: 2021-04-18 Bestelling: 2
+- - -
+
+Gebruikerstoegang tot verschillende functies wordt gecontroleerd met behulp van Django's [ingebouwde authenticatie systeem](https://docs.djangoproject.com/en/3.2/topics/auth/default/). Wanneer een instantie is gecreëerd, maakt het `initdb` script een set van machtigingen aan, die zijn toegewezen aan groepen. Standaard krijgen alle nieuwe gebruikers de `editor` groep toegewezen waarmee ze de metadata van het boek kunnen bewerken.
+
+De instantie administrator moet de status van `supergebruiker` hebben waarmee ze toegang krijgen tot Django beheerder (`/admin`) en alle rechten toe-eigent aan die gebruiker.
+
+## Machtigingen en groepen
+Deze tabel toont de vier groepen (admin, moderator, editor en gebruiker) en welke rechten gebruikers in de betreffende groep hebben:
+
+|                                 | beheerder | bemiddelaar | redacteur | gebruiker |
+| ------------------------------- | --------- | ----------- | --------- | --------- |
+| instantie instellingen bewerken | ✔️        | -           | -         | -         |
+| verander gebruikersniveau       | ✔️        | -           | -         | -         |
+| federatie beheren               | ✔️        | ✔️          | -         | -         |
+| uitnodigingen uitgeven          | ✔️        | ✔️          | -         | -         |
+| gebruikers deactiveren          | ✔️        | ✔️          | -         | -         |
+| berichten verwijderen           | ✔️        | ✔️          | -         | -         |
+| boeken bewerken                 | ✔️        | ✔️          | ✔️        | -         |
+ boekomslagen uploaden            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/nl_NL/content/contributing/contributing.md b/locale/nl_NL/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/nl_NL/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/nl_NL/content/contributing/debug_toolbar.md b/locale/nl_NL/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/nl_NL/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/nl_NL/content/contributing/install-dev.md b/locale/nl_NL/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/nl_NL/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/nl_NL/content/contributing/style_guide.md b/locale/nl_NL/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/nl_NL/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/nl_NL/content/contributing/translation.md b/locale/nl_NL/content/contributing/translation.md
new file mode 100644
index 00000000..48b42f31
--- /dev/null
+++ b/locale/nl_NL/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Vertalingen
+- - -
+
+## Bijdragen aan vertalingen
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/nl_NL/content/index.md b/locale/nl_NL/content/index.md
new file mode 100644
index 00000000..8f4eb4f6
--- /dev/null
+++ b/locale/nl_NL/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Titel: Welkom Datum: 2021-04-13
+- - -
+
+BookWyrm is een sociaal netwerk om je lezen te volgen, te praten over boeken, beoordelingen te schrijven en te ontdekken wat je verder kan lezen. Federatie stelt BoekenWyrm gebruikers er toe in staat om deel te nemen aan kleine, vertrouwde gemeenschappen die met elkaar kunnen verbinden en met andere ActivityPub diensten zoals Mastodon en Pleroma.
+
+## Functies
+Aangezien het project zich nog in de beginfase bevindt, groeien de functies elke dag en is er veel ruimte voor suggesties en ideeën. Open een [probleem](https://github.com/bookwyrm-social/bookwyrm/issues) om het gesprek te beginnen!
+
+- Publicaties plaatsen van boeken
+    - Recensies samenstellen met of zonder beoordelingen, die worden geaggregeerd in de pagina van het boek
+    - Stel andere soorten statussen op voor boeken, zoals:
+        - Reacties op een boek
+        - Citaten of uittreksels
+    - Reageer op status
+    - Bekijk geaggregeerde recensies van een boek door verbonden BookWyrm instanties
+    - Onderscheid lokale en globale recensies en beoordelingen in uw activiteiten-feed
+- Houd leesactiviteit bij
+    - Schuif boeken op standaard "te lezen", "momenteel aan het lezen," en "gelezen" planken
+    - Maak aangepaste planken aan
+    - Sla onderweg lezen-/afrondingsdatums en voortgangsupdates op
+    - Informeer volgers over je lees activiteit (en optioneel, met fijnmazige privacy-controles)
+    - Maak lijsten met boeken die open zijn voor inzendingen van iedereen, samengesteld of alleen bewerkt door diens maker
+- Federatie met ActivityPub
+    - Verzend en ontvang gebruikersstatussen en -activiteit
+    - Deel boekgegevens tussen instanties om een netwerkdatabase van gegevens te maken
+    - Identificeer gedeelde boeken over instanties en voeg gerelateerde inhoud samen
+    - Volg en verbind met gebruikers over BookWyrm instanties
+    - Integreer met niet-BookWyrm ActivityPub diensten (momenteel wordt Mastodon ondersteund)
+- Fijnmazige privacy-controles
+    - Privé, alleen volgelingen, en openbare privacyniveaus voor publicaties, planken en lijsten
+    - Mogelijkheid voor gebruikers om handmatig volgers goed te keuren
+    - Blokkeren en markeren voor bemiddelen toestaan
diff --git a/locale/nl_NL/content/pages/index.md b/locale/nl_NL/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/nl_NL/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/nl_NL/content/running_bookwyrm/cli.md b/locale/nl_NL/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/nl_NL/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/nl_NL/content/running_bookwyrm/external-storage.md b/locale/nl_NL/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/nl_NL/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/nl_NL/content/running_bookwyrm/install-prod-dockerless.md b/locale/nl_NL/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/nl_NL/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/nl_NL/content/running_bookwyrm/install-prod.md b/locale/nl_NL/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/nl_NL/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/nl_NL/content/running_bookwyrm/moderation.md b/locale/nl_NL/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/nl_NL/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/nl_NL/content/running_bookwyrm/monitoring-queue.md b/locale/nl_NL/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/nl_NL/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/nl_NL/content/running_bookwyrm/optional_features.md b/locale/nl_NL/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/nl_NL/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/nl_NL/content/running_bookwyrm/reverse-proxy.md b/locale/nl_NL/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/nl_NL/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/nl_NL/content/running_bookwyrm/updating.md b/locale/nl_NL/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/nl_NL/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/nl_NL/content/using_bookwyrm/adding-books.md b/locale/nl_NL/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..c5bbd5e7
--- /dev/null
+++ b/locale/nl_NL/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Boeken toevoegen
+Date: 2022-07-29
+Order: 2
+---
+
+Er zijn een aantal verschillende manieren om boeken toe te voegen aan je BookWyrm instantie! Wanneer je het boek waar je naar op zoek bent niet kunt vinden probeer de opties in genoemde volgorde -- het is beter om een boek te importeren dan er eentje vanuit het niets te maken.
+
+## Boeken uit andere catalogi laden
+
+Als het boek dat je zoekt niet beschikbaar is in je instantie, zijn er een enkele verschillende manieren om het toe te voegen. De beste manier is om deze te importeren uit een externe bron -- je instantie kan boeken laden uit andere BookWyrm instanties, evenals vanuit [OpenLibrary](http://openlibrary.org/) en [Inventaire](http://inventaire.io/). Als er geen zoekresultaten zijn voor uw zoekopdracht, zullen deze bronnen automatisch worden bevraagd, en verschijnt er een "**Importeer boek**" knop. Als er lokale zoekresultaten niet zijn wat je zoekt, klik dan op de "**Laad resultaten van andere catalogi**" koppeling om meer resultaten te laden.
+
+
+## Een editie toevoegen
+
+Als je het boek dat je wilt vinden, maar deze niet de juiste editie is, kun je nog een editie toevoegen aan het werk vanuit de lijst met edities. Klik op de koppeling onder de beschrijving die je vertelt hoeveel edities er zijn (bijvoorbeeld "**4 edities**"). Onder aan de lijst met edities, is er een knop om "**Een andere editie** " toe te voegen.
+
+## Een geheel nieuw boek toevoegen
+
+Nadat je hebt geprobeerd om naar je boek te zoeken, importeer deze vanuit een andere catalogus en zoek naar andere edities van het boek, deze kan je handmatig een nieuw boek toevoegen. De koppeling om handmatig een boek toe te voegen staat onderaan de zoekpagina als externe catalogi worden weergegeven. Je kunt ook direct navigeren naar `/create-book` in je instantie.
diff --git a/locale/nl_NL/content/using_bookwyrm/posting-statuses.md b/locale/nl_NL/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..e362eac1
--- /dev/null
+++ b/locale/nl_NL/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Titel: Statussen publiceren Datum: 2022-04-30 Bestelling: 1
+- - -
+
+Plaatsen op BookWyrm begint met een boek. Gebruikers kunnen commentaar geven op de voortgang of recent gelezen boeken vanuit het "Jouw boeken" gedeelte, of vanaf de landingspagina van een boek. Vanaf daar kunnen gebruikers antwoorden en een gesprek beginnen. BookWyrm publicaties kunnen opmaak zoals dikgedrukt, schuingedrukt en koppelingen bevatten met behulp van [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+Als je bekend bent met [berichten op Mastodon](https://docs.joinmastodon.org/user/posting/)dan zie je dat BookWyrm statussen gelijksoortige zichtbaarheidsinstellingen, waarschuwingen van inhoud en vermeldingen hebben. Echter, enquêtes, aangepaste emoji en bijlagen worden nog niet ondersteund.
+
+## Soorten statussen
+
+### Gebruiker commentaar
+
+Er zijn drie soorten publicaties die gebruikers rechtstreeks kunnen maken in reactie op boeken: recensies, opmerkingen en citaten. Opmerkingen reageren op algemene aspecten van een boek, citaties hebben betrekking op specifieke passages en recensies gaan over boeken in het algemeen. Gebruikers kunnen ook antwoorden op statussen.
+
+| Onderdeel            | Recensie | Reactie | Citaat | Antwoorden |
+| -------------------- | -------- | ------- | ------ | ---------- |
+| Tekstveld            | ✔        | ✔       | ✔      | ✔          |
+| Spoiler waarschuwing | ✔        | ✔       | ✔      | ✔          |
+| Paginanummer         |          | ✔       | ✔      |            |
+| Citaat               |          |         | ✔      |            |
+| Beoordeling          | ✔        |         |        |            |
+| Titel veld           | ✔        |         |        |            |
+
+
+### Lees status updates
+
+Statussen worden gegenereerd wanneer een gebruiker aangeeft te willen lezen, te zijn begonnen met lezen, te willen lezen, of het hebben uitgelezen van een boek.
+
+## Tekst
+Tekst kan bevatten:
+
+- Vermeldingen (@user)
+- URLs (`http(s)://` wordt niet weergegeven)
+- Sommige [Markdown opmaak](https://www.markdownguide.org/cheat-sheet/)
+  - dikgedrukt
+  - schuingedrukt
+  - blokcitaat
+  - opsomming lijsten
+  - koppelingen
+
diff --git a/locale/no_NO/LC_MESSAGES/messages.po b/locale/no_NO/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..60aebb41
--- /dev/null
+++ b/locale/no_NO/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Norwegian\n"
+"Language: no_NO\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: no\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/no_NO/content/codebase/activitypub.md b/locale/no_NO/content/codebase/activitypub.md
new file mode 100644
index 00000000..5d092ca3
--- /dev/null
+++ b/locale/no_NO/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Tittel: ActivityPub Dato: 2021-04-20 Rekkefølge: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/no_NO/content/codebase/permissions.md b/locale/no_NO/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/no_NO/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/no_NO/content/contributing/contributing.md b/locale/no_NO/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/no_NO/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/no_NO/content/contributing/debug_toolbar.md b/locale/no_NO/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/no_NO/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/no_NO/content/contributing/install-dev.md b/locale/no_NO/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/no_NO/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/no_NO/content/contributing/style_guide.md b/locale/no_NO/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/no_NO/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/no_NO/content/contributing/translation.md b/locale/no_NO/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/no_NO/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/no_NO/content/index.md b/locale/no_NO/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/no_NO/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/no_NO/content/pages/index.md b/locale/no_NO/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/no_NO/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/no_NO/content/running_bookwyrm/cli.md b/locale/no_NO/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/no_NO/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/no_NO/content/running_bookwyrm/external-storage.md b/locale/no_NO/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/no_NO/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/no_NO/content/running_bookwyrm/install-prod-dockerless.md b/locale/no_NO/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/no_NO/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/no_NO/content/running_bookwyrm/install-prod.md b/locale/no_NO/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..aab91ee4
--- /dev/null
+++ b/locale/no_NO/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - Om du kjører andre web-tjenere på vertsmaskina må du følge [revers-proxy instruksjonene](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/no_NO/content/running_bookwyrm/moderation.md b/locale/no_NO/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/no_NO/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/no_NO/content/running_bookwyrm/monitoring-queue.md b/locale/no_NO/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/no_NO/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/no_NO/content/running_bookwyrm/optional_features.md b/locale/no_NO/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/no_NO/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/no_NO/content/running_bookwyrm/reverse-proxy.md b/locale/no_NO/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/no_NO/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/no_NO/content/running_bookwyrm/updating.md b/locale/no_NO/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/no_NO/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/no_NO/content/using_bookwyrm/adding-books.md b/locale/no_NO/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/no_NO/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/no_NO/content/using_bookwyrm/posting-statuses.md b/locale/no_NO/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/no_NO/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/pl_PL/LC_MESSAGES/messages.po b/locale/pl_PL/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..ac67f2dc
--- /dev/null
+++ b/locale/pl_PL/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-08-02 14:01\n"
+"Last-Translator: \n"
+"Language-Team: Polish\n"
+"Language: pl_PL\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: pl\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr "Dokumentacja BookWyrm"
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr "Twój przewodnik korzystania z oraz udzielania się w BookWyrm"
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr "Jak korzystać oraz udzielić się"
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr "BookWyrm: Społeczność czytelników"
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "Dołącz"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr "Udziel się"
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "Wsparcie"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr "Kod źródłowy"
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr "Dokumentacja"
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr "<strong>BookWyrm</strong> to współtworzone, antykorporacyjne oprogramowanie zarządzane przez <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr "Wspieraj BookWyrm poprzez <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr "Udziel się"
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr "BookWyrm na GitHub"
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr "Udziel się na tej stronie"
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr "Dowiedz się więcej"
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr "Skontaktuj się z opiekunem"
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr "Licencja"
+
diff --git a/locale/pl_PL/content/codebase/activitypub.md b/locale/pl_PL/content/codebase/activitypub.md
new file mode 100644
index 00000000..c28e4229
--- /dev/null
+++ b/locale/pl_PL/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm korzysta z protokołu [ActivityPub](http://activitypub.rocks/) do wysyłania i odbierania aktywności użytkownika pomiędzy instancjami BookWyrm oraz innymi usługami, które korzystają z ActivityPub, takimi jak [Mastodon](https://joinmastodon.org/). Do obsługi danych na temat książek BookWyrm posiada kilka rozszerzonych typów Aktywności, które nie są częścią standardu, ale są czytelne dla innych instancji BookWyrm.
+
+## Aktywności i obiekty
+
+### Użytkownicy i stosunki
+Interakcje stosunków między użytkownikami są zgodne ze specyfikacją ActivityPub.
+
+- `Obserwuj`: poproś o otrzymywanie statusów od użytkownika oraz przeglądanie ich statusów, które mogą wyświetlić tylko obserwujący
+- `Akceptuj`: zatwierdza `Obserwowanie` i nawiązuje stosunek
+- `Odmów`: odrzuca `Obserwowanie`
+- `Zablokuj`: uniemożliwia użytkownikowi wzajemne wyświetlanie statusów oraz uniemożliwia wyświetlanie profilu
+- `Aktualizuj`: aktualizuje profil i ustawienia użytkownika
+- `Usuń`: dezaktywuje użytkownika
+- `Cofnij`: anuluje `Obserwowanie` lub `Zablokowanie`
+
+### Statusy
+#### Typy obiektów
+
+- `Notatka`: W usługach takich jak Mastodon, `Notatki` są podstawowym typem statusów. Zawierają treść wiadomości, załączniki, wzmianki o użytkownikach oraz są odpowiedziami na inne statusy dowolnego typu. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Komentarz`: komentarz do książki wspomina o książce i zawiera treść.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Aktywności
+
+- `Tworzenie`: zapisuje nowy status w bazie danych.
+
+   **Uwaga**: BookWyrm akceptuje aktywności `Tworzenie`, tylko jeśli:
+
+   - Są wiadomościami bezpośrednimi (np. `Notatki` z ustawieniem `bezpośrednie`, które wspominają lokalnego użytkownika),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Usuń`: Usuwa status
+- `Polub`: Dodaje reakcję do statusu
+- `Ogłoś`: Promuje status do osi czasu podmiotu
+- `Cofnij`: Anuluje `Polub` lub `Ogłoś`
+
+### Kolekcje
+Listy oraz książki użytkownika są reprezentowane przez [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Obiekty
+
+- `Półka`: Kolekcja książek użytkownika. Domyślnie, każdy użytkownik posiada półkę `do przeczytania`, `czytane` oraz `przeczytane`, które są używane do bycia na bieżąco z postępem czytania.
+- `Lista`: Kolekcja książek, która może zawierać elementy od użytkowników innych niż jej autor.
+
+#### Aktywności
+
+- `Utwórz`: Dodaje półkę lub listę do bazy danych.
+- `Usuń`: Usuwa półkę lub listę.
+- `Dodaj`: Dodaje książkę na półkę lub do listy.
+- `Usuń`: Usuwa książkę z półki lub listy.
+
+
+## Alternatywna serializacja
+BookWyrm wykorzystuje niestandardowe typy obiektów (`Recenzja`, `Komentarz`, `Cytat`), które nie są obsługiwane przez ActivityPub, dlatego statusy są zamieniane na standardowe typy, gdy są wysyłane do lub wyświetlane w usługach poza BookWyrm. `Recenzja` jest konwertowana na `Artykuł`, a `Komentarz` oraz `Cytat` są konwertowane na `Notatki` z odnośnikiem do książki oraz załączonym obrazem okładki.
diff --git a/locale/pl_PL/content/codebase/permissions.md b/locale/pl_PL/content/codebase/permissions.md
new file mode 100644
index 00000000..a102032b
--- /dev/null
+++ b/locale/pl_PL/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Uprawnienia Date: 2021-04-18 Order: 2
+- - -
+
+Dostęp użytkowników do różnych funkcji jest kontrolowany przez [wbudowany system uwierzytelniania](https://docs.djangoproject.com/en/3.2/topics/auth/default/) Django. Gdy zostaje utworzona instancja, skrypt `initdb` tworzy zestaw uprawnień, które są przypisywane do grup. Domyślnie wszyscy nowi użytkownicy zostają przypisani do grupy `edytor`, co umożliwia im edytowanie metadanych książek.
+
+Administrator instancji powinien mieć status `superużytkownik`, co daje mu dostęp do panelu administracyjnego Django (`/admin`) oraz przyznaje mu wszystkie uprawnienia.
+
+## Uprawnienia i grupy
+Ta tabela zawiera cztery grupy (administrator, moderator, edytor oraz użytkownik) oraz uprawnienia użytkowników w tych grupach:
+
+|                               | administrator | moderator | edytor | użytkownik |
+| ----------------------------- | ------------- | --------- | ------ | ---------- |
+| edytowanie ustawień instancji | ✔️            | -         | -      | -          |
+| zmiana poziomu użytkownika    | ✔️            | -         | -      | -          |
+| zarządzanie federacją         | ✔️            | ✔️        | -      | -          |
+| wysyłanie zaproszeń           | ✔️            | ✔️        | -      | -          |
+| dezaktywacja użytkowników     | ✔️            | ✔️        | -      | -          |
+| usuwanie wpisów               | ✔️            | ✔️        | -      | -          |
+| edytowanie książek            | ✔️            | ✔️        | ✔️     | -          |
+ przesyłanie okładek            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/pl_PL/content/contributing/contributing.md b/locale/pl_PL/content/contributing/contributing.md
new file mode 100644
index 00000000..ec53c75a
--- /dev/null
+++ b/locale/pl_PL/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: Udzielanie się Date: 2021-04-12 Order: 1
+- - -
+
+Istnieje wiele sposobów na udzielenie się w tym projekcie, niezależnie od Twojego poziomu doświadczenia.
+
+## Opinie i sugestie funkcji
+Zachęcamy do zgłaszania błędów, sugestii, funkcji oraz pomysłów poprzez [GitHub](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Prace nad kodem
+Zachęcamy do udziału w pracach na kodem! Jeśli nie masz pewności, gdzie zacząć, sprawdź znacznik ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22). Ponieważ BookWyrm to mały projekt, nie istnieje zbyt wiele formalnych struktur, ale istnieje miejsce na bliską współpracę, która może przybrać formę zadawania pytań, wspólnego programowania, rozmów wideo itp.
+
+Jeśli masz pytania odnośnie projektu lub udzielania się, możesz dołączyć do [czatu matrix BookWyrm](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Tłumaczenie
+Czy posługujesz się językami poza angielskim? BookWyrm czeka na tłumaczenia! Możesz dodawać i edytować tłumaczenia na [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Wsparcie finansowe
+BookWyrm to projekt niezawierający reklam projekt tworzony z pasją i bez zamiaru poszukiwania ryzykownego finansowania przez przedsiębiorstwa. Jeśli chcesz, aby ten projekt trwał i rozwijał się dalej, możesz zostać wspierającym na [Patreon](https://www.patreon.com/bookwyrm) lub [OpenCollective](https://opencollective.com/bookwyrm) lub też wysłać jednorazowy prezent przez [PayPal](https://paypal.me/oulipo).
diff --git a/locale/pl_PL/content/contributing/debug_toolbar.md b/locale/pl_PL/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..0d874f5f
--- /dev/null
+++ b/locale/pl_PL/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm posiada gałąź skonfigurowaną do uruchamiania [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). Ta gałąź nigdy nie zostanie złączona z `główna` i posiada kilka ulepszeń, które umożliwiają pracę z paskiem narzędzi, ale nie są bezpieczne do używania z czymkolwiek przypominającym środowisko oficjalne. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/pl_PL/content/contributing/install-dev.md b/locale/pl_PL/content/contributing/install-dev.md
new file mode 100644
index 00000000..8b9d18fe
--- /dev/null
+++ b/locale/pl_PL/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Środowisko programistyczne Date: 2021-04-12 Order: 3
+- - -
+
+## Wymagania wstępne
+
+Te instrukcje zakładają, że rozwijasz BookWyrm przy użyciu Docker. Aby rozpocząć, należy [zainstalować Docker](https://docs.docker.com/engine/install/) i [docker-compose](https://docs.docker.com/compose/install/).
+
+## Konfigurowanie środowiska programistycznego
+
+- Uzyskaj kopię [kodu BookWyrm z GitHub](https://github.com/bookwyrm-social/bookwyrm). Możesz [zduplikować](https://docs.github.com/en/get-started/quickstart/fork-a-repo) repozytorium, a następnie [użyć `git clone`, aby pobrać kod](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) na swój komputer.
+- Katalog, na którym znajduje się kod na Twoim komputerze to miejsce, z którego od teraz będziesz pracować.
+- Skonfiguruj plik zmiennych środowiskowych swojego środowiska programistycznego kopiując przykładowy plik (`.env.example`) do nowego pliku o nazwie `.env`. W wierszu polecenia można to zrobić następująco:
+``` { .sh }
+cp .env.example .env
+```
+- W pliku `.env` zmień `DEBUG` na `true`
+- Jeśli chcesz, możesz skorzystać z usług, takich jak [ngrok](https://ngrok.com/), aby skonfigurować nazwę domeny oraz ustawić zmienną `DOMAIN` w swoim pliku `.env` dla nazwy domeny wygenerowanej przez ngrok.
+
+- Skonfiguruj nginx w celu programowania kopiując plik konfiguracyjny nginx (`nginx/development`) do nowego pliku o nazwie `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Uruchom aplikację. W wierszu polecenia wykonaj:
+``` { .sh }
+./bw-dev build            # Kompiluje obraz docker
+./bw-dev setup            # Inicjuje bazę danych i uruchamia migracje
+./bw-dev up               # Uruchamia kontenery docker
+```
+- Po zakończeniu kompilacji możesz uzyskać dostęp pod `ttp://localhost:1333` i utworzyć konto administratora.
+
+Dla ciekawskich: polecenie `./bw-dev` to prosty skrypt uruchamiający wiele różnych narzędzi: powyżej możesz pominąć je i wykonać `docker-compose build` lub `docker-compose up` bezpośrednio, jeśli chcesz. `./bw-dev` po prostu gromadzi je wszystkie w jednym miejscu. Uruchom polecenia bez argumentów, aby uzyskać listę dostępnych poleceń, odczytać [stronę dokumentacji](/command-line-tool.html) dla niego lub otwórz ją i rozejrzyj się, aby sprawdzić, co dokładnie robi dane polecenie!
+
+### Edytowanie lub tworzenie modeli
+
+Zmieniając lub tworząc model prawdopodobnie ulegnie zmianie struktura bazy danych. Aby te zmiany zostały zastosowane, należy uruchomić polecenie Django `makemigrations`, aby utworzyć nowy [plik migracji Django](https://docs.djangoproject.com/en/3.2/topics/migrations), a następnie przenieść go (`migrate`):
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Edytowanie plików statycznych
+Za każdym razem, gdy edytujesz CSS lub JavaScript, należy ponownie uruchomić polecenie Django `collectstatic`, aby miany zostały zastosowane:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+Jeśli [zainstalowano yarn](https://yarnpkg.com/getting-started/install), możesz wykonać `yarn watch:static`, aby automatycznie wykonać poprzedni skrypt za każdym razem, gdy zajdzie zmiana w katalogu `bookwyrm/static`.
diff --git a/locale/pl_PL/content/contributing/style_guide.md b/locale/pl_PL/content/contributing/style_guide.md
new file mode 100644
index 00000000..0ac03a77
--- /dev/null
+++ b/locale/pl_PL/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Prośby o scalenie
+
+Jeśli chcesz udzielić się w kodzie BookWyrm, to świetnie! Jeśli istnieje otwarty problem, który chcesz naprawić, możesz zamieścić komentarz do niego, tak aby niczego nie powielać. Staraj się, aby zakres próśb o scalenie był mały i skupiony na jednym temacie. Dzięki temu łatwiej będzie ją sprawdzić i sprawniej wprowadzić zmiany.
+
+Jeśli nie masz pewności, jak coś naprawić lub nie możesz się za to zabrać, to nic nie szkodzi i wystarczy, że zamieścisz komentarz do prośby o scalenie i wspólnie znajdziemy rozwiązanie 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Szablony (HTML)
+
+Twoje prośby o scalenie zostaną również sprawdzone przez [curlylint](https://www.curlylint.org) w poszukiwaniu szablonów Django.
+
+### CSS
+
+Korzystamy z [stylelint](https://stylelint.io), do sprawdzania zasad CSS. Tak jak w przypadku Pylint [możesz wyłączyć stylelint](https://stylelint.io/user-guide/ignore-code) dla konkretnej zasady, ale należy mieć ku temu dobry powód.
+
+### JavaScript
+
+[ESLint](https://eslint.org) sprawdza wszelkie wprowadzone zmiany w JavaScript. Jeśli ESLint nie będzie współpracował z Twoim kodem JavaScript, sprawdź wiadomości narzędzia po więcej informacji.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Niektórymi z aspektów, które współtwórcy BookWyrm uznali za przydatne do zapamiętania są:
+
+### Formularze
+
+* Używaj wyłącznie znaczników `input[type="checkbox"]` lub `input[type="radio"]` w znaczniku `<label>`
+* Jeśli nie umieścisz pól jedno- i wielokrotnego wyboru w znaczniku `<label>`, wówczas należy go umieścić _za_ elementem, do którego się odwołuje
+
+### Przyciski i odnośniki
+
+* Użyj znacznika `<button>` dla czegokolwiek, co istnieje, aby wywołać instrukcję JavaScript (np. ukrywanie i pokazywanie fomrularza) lub wysyła żądanie `POST` (np. przesłanie formularza)
+* Użyj znacznika `<a>` dla czegokolwiek, co wywołuje żądanie `GET`. Zazwyczaj element znacznika odnośnika (`<a>`) nie powinien być stylizowany jako przycisk (`class="button"`), ale istnieje kilka wyjątków, takich jak przyciski "Anuluj". W razie wątpliwości zapytaj o poradę w swojej prośbie o scalenie
diff --git a/locale/pl_PL/content/contributing/translation.md b/locale/pl_PL/content/contributing/translation.md
new file mode 100644
index 00000000..059fa719
--- /dev/null
+++ b/locale/pl_PL/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Tłumaczenia Date: 2021-10-20 Order: 2
+- - -
+
+## Udzielanie się w tłumaczeniach
+
+Możesz dołączyć do projektu tłumaczenia BookWyrm na [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Język neutralny płciowo
+
+Tam, gdzie to możliwe, tłumaczenia BookWyrm powinny zawierać neutralne płciowo wyrazy. Ma to zastosowanie również, gdy rodzaj męski jest traktowany jako neutralny lub istnieje coś podobnego do "on/ona". Równie ważne jest, aby przetłumaczone treści były jasne, zwięzłe i czytelne dla użytkownika, a czasami te wartości nie idą w parze; nie ma jednej odpowiedzi na wszystkie aspekty, więc należy wykorzystać wszelkie zasoby języka.
+
+Poświęć więcej uwagi na integrację oraz neutralny płciowo język niż na poprawność lub oficjalne formy stylizacji. Na przykład w języku angielskim wiele formalnych zwrotów wymaga użycia zaimka "ona" lub "on", gdy odnosimy się do osoby, ale lepiej będzie, jeśli na BookWyrm zastosujemy neutralne płciowo "ono/oni".
+
+Jeśli nie masz pewności, jak najlepiej podejść do problemu z tłumaczeniem, dodaj komentarz do tłumaczenia lub utwórz [dyskusję](https://translate.joinbookwyrm.com/project/bookwyrm/discussions), aby uzyskać odpowiedź na bardziej zawiłe pytania.
+
+## Umożliwianie tłumaczenia szablonów
+
+BookWyrm korzysta z funkcji tłumaczenia Django, aby umożliwić zmienianie treści strony w zależności od języka wybranego przez użytkownika. Dokumentacja Django [zawiera pomocne objaśnienia](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code), jak to działa, a tutaj krótkie jej podusmowanie:
+
+* cały tekst szablonu powinien zawierać znaczniki tłumaczenia szablonu
+* dodaj `{% load i18n %}` na górze szablonu, aby umożliwić tłumaczenia
+* Jeśli blok tekstu jest tekstem dosłownym, możesz skorzystać z znacznika szablonu `{% trans %}`
+* Jeśli blok tekstu zawiera zmiennie, należy użyć pary znaczników `{% blocktrans %}` oraz `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Przykłady
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Dodane przez <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/pl_PL/content/index.md b/locale/pl_PL/content/index.md
new file mode 100644
index 00000000..ae6489a3
--- /dev/null
+++ b/locale/pl_PL/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Witaj Date: 2021-04-13
+- - -
+
+BookWyrm to sieć społecznościowa do śledzenia swojego czytania, rozmów o książkach, pisania recenzji oraz odkrywania swoich kolejnych książek. Federacja umożliwia użytkownikom BookWyrm dołączanie do małych, zaufanych społeczności, które mogą łączyć się ze sobą i z innymi usługami ActivityPub, takimi jak Mastodon i Pleroma.
+
+## Funkcje
+Ponieważ projekt jest nadal we wczesnej fazie rozwoju, funkcje są dodawane każdego dnia, a miejsca na sugestie i pomysły Ci u nas pod dostatkiem. Utwórz [wątek](https://github.com/bookwyrm-social/bookwyrm/issues), aby rozpocząć dysksuję!
+
+- Zamieszczanie treści o książkach
+    - Twórz recenzje z ocenami lub bez, które będą zamieszczane na stronie książki
+    - Publikuj pozostałe rodzaje statusów o książkach, takie jak:
+        - Komentarze do ksiażęk
+        - Cytaty lub fragmenty
+    - Odpowiadaj na statusy
+    - Przeglądaj zebrane recenzje książki pomiędzy połączonymi instancjami BookWyrm
+    - Oddzielaj lokalne i sfederowane recenzje oraz oceny na swoim kanale aktywności
+- Śledź aktywność czytania
+    - Umieszczaj książki na domyślnych półkach "do przeczytania", "obecnie czytanie" oraz "przeczytane"
+    - Twórz własne półki
+    - Przechowuj daty rozpoczęcia/ukończenia czytania oraz aktualizacje postępu z upływem czasu
+    - Dziel się swoją aktywnością czytania z obserwującymi (opcjonalnie i z bardzo precyzyjnymi ustawieniami prywatności)
+    - Twórz listy książek, które mogą być otwarte na dodawanie do nich sugestii, nadzorowane oraz edytowalne tylko przez twórcę
+- Federacja dzięki ActivityPub
+    - Przekazuj i odbieraj statusy oraz aktywność użytkowników
+    - Udostępniaj dane o książkach pomiędzy instancjami, aby tworzyć połączoną bazę danych metadanych
+    - Identyfikuj książki dostępne pomiędzy instancjami oraz agreguj powiązane treści
+    - Obserwuj i działaj wspólnie z użytkownikami pomiędzy instancjami BookWyrm
+    - Współpracuj z usługami ActivityPub spoza BookWyrm (obecnie obsługiwany jest Mastodon)
+- Szczegółowe ustawienia prywatności
+    - Ustaw swoje wpisy, półki oraz listy jako prywatne, tylko dla obserwujących lub publiczne
+    - Skorzystaj z opcji ręcznego zatwierdzania obserwujących
+    - Zezwalaj na blokowanie i zgłaszanie w celu moderacji
diff --git a/locale/pl_PL/content/pages/index.md b/locale/pl_PL/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/pl_PL/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/pl_PL/content/running_bookwyrm/cli.md b/locale/pl_PL/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..60ee8f6d
--- /dev/null
+++ b/locale/pl_PL/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Programiści BookWyrm oraz menedżerowie instancji mogą skorzystać ze skryptu `bw-dev` do częstych zadań. Może to skrócić Twoje polecenia, ułatwić ich zapamiętanie i utrudnić zepsucie czegoś.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Skróty Docker
+
+### bash
+
+Otwórz interaktywną sesję `bash` w kontenerze `web` dockera.
+
+### build
+
+Równoznaczne z kompilacją `docker-compose`.
+
+### dbshell
+
+Otwiera interaktywną powłokę bazy danych Postgres. Mam nadzieję, że wiesz, co robisz.
+
+### runweb args
+
+Wykonuje dowolne polecenie (reprezentowane powyżej przez `args`) w kontenerze `web`.
+
+Równoznaczne z `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Zarządzanie bazą danych
+
+### initdb
+
+Inicjuje bazę danych.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_To polecenie nie jest dostępne w gałęzi `production`_.
+
+Zeruje bazę danych. **To polecenie spowoduje usunięcie całej Twojej bazy danych BookWyrm** oraz zainicjuje świeżą bazę danych i wykona wszystkie migracje. Należy usunąć wszystkie najnowsze pliki migracji, których nie chcesz użyć _przed_ wykonaniem `resetdb`.
+
+## Zarządzanie instancją BookWyrm
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/pl_PL/content/running_bookwyrm/external-storage.md b/locale/pl_PL/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..95e47d8b
--- /dev/null
+++ b/locale/pl_PL/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### Co Cię czeka
+
+Jeśli rozpoczynasz nową instancję BookWyrm, proces będzie zawierał:
+
+- Konfigurację usługi pamięci zewnętrznej
+- Aktywację pamięci zewnętrznej na BookWyrm
+- Uruchomienie swojej instancji BookWyrm
+- Aktualizację łącznika instancji
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+To zadanie wykonywane jest poleceniem:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Aktywowanie pamięci zewnętrznej dla BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/pl_PL/content/running_bookwyrm/install-prod-dockerless.md b/locale/pl_PL/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..181b31e0
--- /dev/null
+++ b/locale/pl_PL/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. W systemie Debian może to wyglądać następująco: `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Usuń znacznik komentarza w wierszach od 18 do 67, aby włączyć przekierowanie HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+Należy skonfigurować zadanie Cron, aby usługa była uruchamiana po ponownym uruchomieniu serwera.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/pl_PL/content/running_bookwyrm/install-prod.md b/locale/pl_PL/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..114a6b80
--- /dev/null
+++ b/locale/pl_PL/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Skonfiguruj swój serwer z odpowiednimi zasadami zapory do uruchamiania aplikacji internetowych (ten zestaw instrukcji został przetestowany na Ubuntu 20.04). Oto instrukcje dla [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Zainstaluj i skonfiguruj BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | Trudny do odgadnięcia, tajny ciąg znaków
+    - `DOMAIN` | Twoja domena sieciowa
+    - `EMAIL` | Adres e-mail używany do weryfikacji domeny przez bota certyfikującego
+    - `POSTGRES_PASSWORD` | Ustaw bezpieczne hasło dla bazy danych
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Konfiguracja nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Gratulacje! Udało się!! Skonfiguruj swoją instancję jak tylko chcesz.
+
+
+## Kopie zapasowe
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. Aby aktywować ten skrypt:
+
+- Usuń znaczniki komentarza w ostatnim wierszu w pliku `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Konflikty portów
+
+BookWyrm posiada wiele usług, które działają na ich domyślnych portach. Oznacza to, że w zależności od tego, co jeszcze działa na Twoim komputerze hosta, możesz napotkać błędy podczas kompilowania lub uruchamiania BookWyrm, gdy próby powiązania z tymi portami zakończą się niepowodzeniem.
+
+Jeśli tak się stanie, należy zmienić konfigurację, aby usługi działały na różnych portach. Może to wymagać jednej lub więcej zmian w następujących plikach:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (Tworzysz ten plik podczas konfiguracji)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. Istnieje kilka sposobów na kontakt:
+
+ - Utwórz problem lub prośbę o scalenie, aby dodać swoją instancję do [oficjalnej listy](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Dołącz do pokoju rozmów na [Matrix](https://matrix.to/#/#bookwyrm:matrix.org)
diff --git a/locale/pl_PL/content/running_bookwyrm/moderation.md b/locale/pl_PL/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..3074ba29
--- /dev/null
+++ b/locale/pl_PL/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderacja Date: 2021-04-18 Order: 5
+- - -
+
+## Blokowanie
+Użytkownicy mają możliwość samodzielnego zablokowania pozostałych użytkowników bez interwencji moderatora. Z panelu administracyjnego "Sfederowane serwery" administratorzy mogą zobaczyć, ilu użytkowników z instancji zostało zablokowanych przez użytkowników lokalnych.
+
+## Zgłoszenia
+Użytkownicy mogą zgłaszać statusy lub użytkowników z menu "więcej opcji" w stopce wpisu oraz przycisków obserwuj/nie obserwuj. Gdy zgłoszenie zostaje utworzone, wszyscy użytkownicy z uprawnieniami administratora otrzymają powiadomienie.
+
+Wówczas, istnieje kilka sposobów, w jakie moderacja może postąpić.
+- Wysłanie bezpośredniej wiadomości do zgłoszonego użytkownika.
+- Usunięcie zgłoszonego statusu.
+- Dezaktywacja użytkownika. Dla użytkowników lokalnych spowoduje to, że nie będą mogli się oni zalogować, a ich konto nie zostanie wyświetlone w aplikacji. Dla użytkowników zdalnych serwer odrzuci jakiekolwiek przychodzące aktywności od tych użytkowników i nie zostaną oni wyświetlenie w wyszukiwaniu.
+
+## Moderacja na poziomie instancji
+Moderatorzy mogą zablokować całe instancje. Zapobiegnie to odbieraniu jakichkolwiek aktywności przychodzących od tej instancji oraz lokalnie dezaktywuje wszystkie konta z tej instancji.
+
+Jeśli instancja zostanie odblokowana, wszyscy zdezaktywowani użytkownicy zostaną aktywowani ponownie.
+
+Moderatorzy mogą również przesyłać listy blokowania wielu serwerów.
diff --git a/locale/pl_PL/content/running_bookwyrm/monitoring-queue.md b/locale/pl_PL/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/pl_PL/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/pl_PL/content/running_bookwyrm/optional_features.md b/locale/pl_PL/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..81d63da5
--- /dev/null
+++ b/locale/pl_PL/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Niektóre z funkcji BookWyrm należy aktywować, aby były dostępne.
+
+## Generowanie obrazów podglądu
+
+Domyślnie BookWyrm używa logo instancji (lub domyślnego logo) jako obrazu podglądu OpenGraph. Możesz jednak włączyć generowanie obrazów podglądu dla książek, użytkowników oraz strony internetowej.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). W zależności od typu obrazu zawartością będzie:
+
+- domyślny obraz instancji wyświetlający duże logo wraz z nazwą instancji oraz jej adresem URL
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- obraz książki wyświetli jej okładkę, podtytuł (jeśli dotyczy), autora oraz oceny (jeśli dotyczy)
+
+Te obrazy będą aktualizowane w różnych momentach:
+
+- obraz instancji: gdy nazwa instancji lub duże logo ulegną zmianie
+- obraz użytkownika: gdy wyświetlana nazwa lub awatar ulegną zmianie
+- obraz książki: gdy tytuł(y), autorzy lub okładka ulegnie zmianie lub zostanie dodana nowa ocena
+
+### Aktywacja podglądów obrazów
+
+Aby aktywować tę funkcję z domyślnymi ustawieniami, należy usunąć znacznik komentarza (usunąć `#` z przodu) wiersza `ENABLE_PREVIEW_IMAGES=true` w pliku `.env`. Wszystkie wspomniane nowe zdarzenia aktualizacji spowodują wygenerowanie odpowiedniego obrazu.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generowanie obrazów podglądu
+
+Jeśli aktywujesz to ustawienie po uruchomieniu instancji, niektóre obrazy mogą nie zostać wygenerowane. Zostało dodane polecenie do automatyzacji generowania obrazów. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Bez tego argumentu zostanie wygenerowany tylko podgląd witryny.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Może minąć trochę czasu zanim wszystkie książki oraz użytkownicy będą mieć działające obrazy podglądu. Jeśli masz dobrą książkę 📖, zwierzątko 🐱 lub przekąskę 🍰 to jest to idealny moment na poświecenie im trochę uwagi 💖.
+
+### Ustawienia opcjonalne
+
+Chcesz dostosować swoje obrazy podglądu? Oto dostępne opcje:
+
+- `PREVIEW_BG_COLOR` definiuje kolor tła dla obrazu podglądu. Możesz podać wartość koloru, taką jak `#b00cc0` lub użyć wartości `use_dominant_color_light` lub `use_dominant_color_dark`. Pozwoli to na wyodrębnienie dominującego koloru z okładki książki oraz użycie do odpowiednio w jasnym i ciemnym motywie.
+- `PREVIEW_TEXT_COLOR` definiuje kolor tekstu. W zależności od wybranego koloru tła, należy znaleźć wartość o odpowiednim kontraście, aby obraz był czytelny. Zalecany kontrast wynosi 1:4.5.
+- `PREVIEW_IMG_WIDTH` oraz `PREVIEW_IMG_HEIGHT` definiują wymiary obrazu. Obecnie system najlepiej współpracuje z obrazami o poziomej orientacji.
+- `PREVIEW_DEFAULT_COVER_COLOR` definiuje color książek bez okładki.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/pl_PL/content/running_bookwyrm/reverse-proxy.md b/locale/pl_PL/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..ac665f78
--- /dev/null
+++ b/locale/pl_PL/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Przed konfiguracją nginx należy zlokalizować swój katalog konfiguracji nginx, który jest zależny od platformy i jak nginx został zainstalowany. Sprawdź [przewodnik nginx](http://nginx.org/en/docs/beginners_guide.html) po więcej szczegółów.
+
+Aby skonfigurować swój serwer:
+
+- Upewnij się, że w pliku `nginx.conf` wiersz `include servers/*;` nie jest zawarty w komentarzu.
+- W swoim katalogu `servers` utwórz nowy plik z nazwą Twojej domeny zawierający następujące informacje:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+Do konfiguracji bloku SSL:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- wykonaj `sudo certbot run --nginx --email TWÓJ_EMAIL -d twoja-domena.pl -d www.twoja-domena.pl`
+- uruchom ponownie nginx
+
+Jeśli wszystko przebiegło pomyślnie, Twoja instancja BookWyrm powinna być od teraz dostępna z zewnątrz.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Uwaga: lokalizacja certyfikatów SSL może różnić się w zależności od systemu operacyjnego Twojego serwera*
+
diff --git a/locale/pl_PL/content/running_bookwyrm/updating.md b/locale/pl_PL/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..d8f1bfdd
--- /dev/null
+++ b/locale/pl_PL/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Aktualizowanie instancji Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. Wykonuje ono kilka rzeczy:
+
+- `git pull` wczytuje zaktualizowany kod z repozytorium git. Jeśli wystąpią konflikty, może być konieczne wykonanie `git pull` oddzielnie i rozwiązanie konfliktów przez ponownym wypróbowaniem skryptu `./bw-dev update`.
+- `docker-compose build` ponownie kompiluje obrazy, co zapewnia zainstalowanie odpowiednich pakietów. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/pl_PL/content/using_bookwyrm/adding-books.md b/locale/pl_PL/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..6a903853
--- /dev/null
+++ b/locale/pl_PL/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Dodawanie książek
+Date: 2022-07-29
+Order: 2
+---
+
+Istnieje kilka sposobów na dodawanie książek do swojej instancji BookWyrm! Jeśli nie możesz znaleźć książki, której szukasz, wypróbuj te opcje w ich kolejności -- lepiej jest zaimportować książkę niż tworzyć ją od nowa.
+
+## Wczytywanie książek z pozostałych katalogów
+
+Jeśli książka, której szukasz nie jest dostępna w Twojej instancji, istnieje kilka sposób, aby ją dodać. Najlepszym z nich jest importowanie jej z zewnętrznego źródła -- Twoja instancja może wczytać książki z pozostałych instancji BookWyrm oraz [OpenLibrary](http://openlibrary.org/) i [Inventaire](http://inventaire.io/). Jeśli nie ma wyników wyszukiwania dla Twojego zapytania, zostanie ono automatycznie przekierowane do tych źródeł i pokażą się z przyciskiem "**Importuj książkę**". Jeśli istnieją lokalne wyniki wyszukiwania, które nie są tym, czego szukasz, naciśnij na odnośnik "**Wczytaj wyniki z pozostałych katalogów**", aby wczytać więcej wyników.
+
+
+## Dodawanie innego wydania
+
+Jeśli znajdziesz właściwą książkę, ale nie odpowiednie wydanie, możesz dodać inne wydanie z listy wydań. Naciśnij na odnośnik poniżej opisu, który zawiera ilość wydań (na przykład: "**4 wydania**"). Na dole listy wydań umieszczony jest przycisk "**Dodaj inne wydanie**".
+
+## Dodawanie zupełnie nowej książki
+
+Po wypróbowaniu szukania książki, importowania jej z pozostałych katalogów oraz szukania innych wydań książki, możesz dodać nową książkę ręcznie. Odnośnik do ręcznego dodania książki umieszczony jest na dole strony wyszukiwania, gdy pokazane są zewnętrzne katalogi. Możesz również bezpośrednio przejść do `/create-book` na swojej instancji.
diff --git a/locale/pl_PL/content/using_bookwyrm/posting-statuses.md b/locale/pl_PL/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..8b7a063f
--- /dev/null
+++ b/locale/pl_PL/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Zamieszczanie statusów Date: 2022-04-30 Order: 1
+- - -
+
+Na BookWyrm zaczyna się to od książki. Użytkownicy mogą komentować czytane lub ostatnio przeczytane książki z sekcji "Twoje książki" lub ze strony książki. Stamtąd użytkownicy mogą odpowiadać na i rozpoczynać rozmowy. Wpisy na BookWyrm mogą zawierać formatowanie, takie jak pogrubienie, kursywę lub odnośniki używając [Znaczników](https://www.markdownguide.org/cheat-sheet/).
+
+Jeśli nie jest Ci obce [zamieszczanie wpisów na Mastodon](https://docs.joinmastodon.org/user/posting/), odkryjesz wówczas, że statusy BookWyrm mają analogiczne ustawienia widoczności, ostrzeżenia o treści oraz wzmianki. Jednakże ankiety, własne emotikony oraz załączniki nie są jeszcze obsługiwane.
+
+## Typy statusów
+
+### Komentarz użytkownika
+
+Istnieją trzy typy wpisów, które użytkownicy mogą tworzyć bezpośrednio w odpowiedzi na książkę: recenzje, komentarze oraz cytaty. Komentarze odnoszą się do ogólnych aspektów książki, cytaty do określonych fragmentów, a recenzje do całości książki. Użytkownicy mogą również odpowiadać na statusy.
+
+| Element              | Recenzja | Komentarz | Cytat | Odpowiedź |
+| -------------------- | -------- | --------- | ----- | --------- |
+| Pole tekstowe        | ✔        | ✔         | ✔     | ✔         |
+| Ostrzeżenie o treści | ✔        | ✔         | ✔     | ✔         |
+| Numer strony         |          | ✔         | ✔     |           |
+| Cytat                |          |           | ✔     |           |
+| Ocena                | ✔        |           |       |           |
+| Pole tytułu          | ✔        |           |       |           |
+
+
+### Aktualizacje statusu czytania
+
+Statusy są generowane, gdy użytkownik wskaże, że chce przeczytać książkę, zaczął ją czytać lub ukończył tę czynność.
+
+## Tekst
+Tekst może zawierać:
+
+- Wzmianki (@użytkownik)
+- Adresy URL (`http(s)://` nie jest wyświetlane)
+- Niektóre ze [Znaczników](https://www.markdownguide.org/cheat-sheet/)
+  - pogrubienie
+  - kursywa
+  - cytat
+  - lista punktowana
+  - odnośniki
+
diff --git a/locale/pt_BR/LC_MESSAGES/messages.po b/locale/pt_BR/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..1205960b
--- /dev/null
+++ b/locale/pt_BR/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Portuguese, Brazilian\n"
+"Language: pt_BR\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: pt-BR\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/pt_BR/content/codebase/activitypub.md b/locale/pt_BR/content/codebase/activitypub.md
new file mode 100644
index 00000000..6e058e7a
--- /dev/null
+++ b/locale/pt_BR/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm usa o protocolo [ActivityPub](http://activitypub.rocks/) para enviar e receber as atividades dos usuários entre instâncias BookWyrm e outros serviços que utilizem o ActivityPub, como o [Mastodon](https://joinmastodon.org/). Para lidar com dados de livros, a BookWyrm tem uma série de tipos estendidos de Atividade (Activity) que não são parte do padrão, mas são legíveis para instâncias BookWyrm.
+
+## Atividades e Objetos
+
+### Usuários e relações
+As interações de relação entre usuários seguem a especificação padrão do ActivityPub.
+
+- `Seguir (Follow)`: pedir para receber as publicações de um usuário e ver suas publicações privadas, apenas para seguidores
+- `Aceitar (Accept)`: aprova um pedido para `Seguir` e finaliza a relação
+- `Rejeitar (Reject)`: recusa um pedido para `Seguir`
+- `Bloquear (Block)`: impede que usuários vejam as publicações uns dos outros, e impede que o usuário bloqueado visualize o perfil do agente
+- `Atualizar (Update)`: atualize o perfil do usuário e suas configurações
+- `Excluir (Delete)`: desativa um usuário
+- `Desfazer (Undo)`: reverte um pedido de `Seguir` ou `Bloquear`
+
+### Publicações
+#### Tipos de objetos
+
+- `Nota (Note)`: em serviços como o Mastodon, a `Nota`s é o tipo primário de publicação. Elas contêm o corpo da mensagem, os anexos, podem mencionar usuários e também serem respostas a publicações de qualquer tipo. Na BookWyrm, uma `Nota`s só pode ser criada como uma mensagem direta ou como respostas a outras publicações.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comentário (Comment)`: Um comentário sobre um livro menciona um livro e tem o corpo da mensagem.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Atividades (Activities)
+
+- `Criar (Create)`: salva uma nova publicação no banco de dados.
+
+   **Lembrete**: A BookWyrm só aceita atividades `Criar (Create)` se elas forem:
+
+   - Mensagens diretas (ou seja, `Nota`s com o nível de privacidade `direto (direct)`, que menciona um usuário local),
+   - Relacionadas a um livro (de um tipo de publicação que possua o campo `inReplyToBook`),
+   - Respostas a publicações já salvas no banco de dados
+- `Excluir (Delete)`: apaga uma publicação
+- `Curtir (Like)`: Adiciona um favorito ao status
+- `Compartilhar (Announce)`: compartilha a publicação na linha do tempo do agente
+- `Desfazer (Undo)`: reverte um `Curtir (Like)` ou um `Compartilhar (Announce)`
+
+### Coleções
+Os livros dos usuários e suas listas são representadas com [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objetos
+
+- `Estante (Shelf)`: a coleção de livros de um usuário. Por padrão, todo usuário possui as estantes `to-read (para-ler)`, `reading (lendo)`, e `read (lido)`, elas servem para companhar o andamento da leitura.
+- `Lista (List)`: uma coleção de livros que podem ter itens submetidos por outros usuários além do criador da lista.
+
+#### Atividades (Activities)
+
+- `Criar (Create)`: salva uma estante ou uma lista no banco de dados.
+- `Excluir (Delete)`: exclui uma estante ou lista.
+- `Adicionar (Add)`: adiciona um livro a uma estante ou lista.
+- `Remover (Remove)`: exclui um livro de uma estante ou lista.
+
+
+## Serialização alternativa
+Uma vez que a BookWyrm utiliza tipos de objetos especiais (`Resenha (Review)`, `Comentário (Comment)`, `Citação (Quotation)`) que não são compatíveis com o ActivityPub, as publicações são transformadas em objetos do tipo padrão quando são enviadas ou visualizadas por serviços que não a BookWyrm. `Resenhas (Reviews)` são transformadas em `Artigo (Article)`, e `Comentários (Comments)` e `Citações (Quotations)` são transformados em `Notas (Notes)` com um link para o livro e a imagem de capa no anexo.
diff --git a/locale/pt_BR/content/codebase/permissions.md b/locale/pt_BR/content/codebase/permissions.md
new file mode 100644
index 00000000..031bc4ac
--- /dev/null
+++ b/locale/pt_BR/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissões Date: 2021-04-18 Order: 2
+- - -
+
+O acesso do usuário às diferentes funções do serviço é controlado pelo [sistema nativo de autenticação](https://docs.djangoproject.com/en/3.2/topics/auth/default/) do Django. Quando uma instância é criada, o script `initdb` cria um conjunto de permissões que são atribuídas a grupos. Por padrão, todos os novos usuários são colocados no grupo `editor`, que permite que eles editem metadados de livros.
+
+A pessoa que administra a instância deve ser do grupo `superuser`, que dá a ela acesso à administração do Django (`/admin`) e a todas as permissões.
+
+## Permissões e grupos
+Esta tabela mostra os quatro grupos (admin, moderador, editor e usuário) e que permissões usuários nesses grupos têm:
+
+|                                   | administrador | moderador | editor | usuário |
+| --------------------------------- | ------------- | --------- | ------ | ------- |
+| editar configurações da instância | ✔️            | -         | -      | -       |
+| mudar nível do usuário            | ✔️            | -         | -      | -       |
+| gerir federação                   | ✔️            | ✔️        | -      | -       |
+| enviar convites                   | ✔️            | ✔️        | -      | -       |
+| desativar usuários                | ✔️            | ✔️        | -      | -       |
+| excluir publicações               | ✔️            | ✔️        | -      | -       |
+| editar livros                     | ✔️            | ✔️        | ✔️     | -       |
+ enviar capas            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/pt_BR/content/contributing/contributing.md b/locale/pt_BR/content/contributing/contributing.md
new file mode 100644
index 00000000..13eaff57
--- /dev/null
+++ b/locale/pt_BR/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+Há muitas formas de contribuir com o projeto qualquer que esja seu nível de conhecimento técnico.
+
+## Feedback e pedido de recursos
+Sinta-se à vontade para reportar bugs, dar sugestões, solicitar funções e dar ideias de como acha que as coisas deviam ser no [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Contribuições de código
+Contribuições de código são muito bem-vindas! Se você não sabe por onde começar, dê uma olhada na tag ["Bom para iniciantes" ("Good first issue")](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. A BookWyrm é um projeto pequeno e não temos muita estrutura formal, mas há uma grande possibilidade de ajuda direta e acompanhamento, que pode envolver fazer perguntas enquanto você faz as coisas, programação em pares/pareamento, conversas em vídeo, etc., então sinta-se à vontade para falar com a gente.
+
+Se tiver alguma dúvida sobre o projeto ou sobre como contribuir, você pode entrar no [ chat Matrix da BookWyrm](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Tradução
+Você fala alguma língua além do inglês? A BookWyrm precisa de localização! Você pode criar e editar traduções em [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Apoio financeiro
+A BookWyrm é um projeto apaixonado e sem anúncios sem intenção de conseguir financiamento de risco ou relações de financiamento corporativo. Se você quiser manter o projeto funcionando, pode fazer uma contribuição recorrente pelo [Patreon](https://www.patreon.com/bookwyrm) ou [OpenCollective](https://opencollective.com/bookwyrm) ou fazer uma doação única pelo [PayPal](https://paypal.me/oulipo).
diff --git a/locale/pt_BR/content/contributing/debug_toolbar.md b/locale/pt_BR/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/pt_BR/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/pt_BR/content/contributing/install-dev.md b/locale/pt_BR/content/contributing/install-dev.md
new file mode 100644
index 00000000..e0ec3bc7
--- /dev/null
+++ b/locale/pt_BR/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Pré-requisitos
+
+Estas instruções supoem que você esteja rodando a BookWyrm utilizando o Docker. Você vai precisar [instalar o Docker](https://docs.docker.com/engine/install/) e o [docker-compose](https://docs.docker.com/compose/install/) para começar.
+
+## Configurando o ambiente de desenvolvimento
+
+- Faça uma cópia do [código da BookWyrm no GitHub](https://github.com/bookwyrm-social/bookwyrm). Você pode [criar uma bifurcação (fork)](https://docs.github.com/en/get-started/quickstart/fork-a-repo) do repositório e então [usar `git clone` pra baixar o código](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) para seu computador.
+- Vá ao diretório onde o código foi baixado no seu computador; você trabalhará a partir dele daqui em diante.
+- Configure as variáveis do seu ambiente de trabalho copiando o arquivo de ambiente de exemplo (`.env.example`) e renomeando o arquivo para `.env`. Na linha de comando, você pode fazer assim:
+``` { .sh }
+cp .env.example .env
+```
+- No `.env`, altere `DEBUG` para `true`
+- Facultativamente, você pode usar algum serviço como o [ngrok](https://ngrok.com/) para configurar um domínio e apontar a variável `DOMAIN` do seu arquivo `.env` para o domínio gerado pelo ngrok.
+
+- Configure o nginx para o ambiente de desenvolvimento copiando o arquivo de configuração para desenvolvimento (`nginx/development`) e renomeando o arquivo para `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Inicie o aplicativo. In the command line, run:
+``` { .sh }
+./bw-dev build            # Gera a imagem docker
+./bw-dev setup            # Inicializa o banco de dados e executa as migrações
+./bw-dev up               # Inicia os containers do docker
+```
+- Uma vez completado o build, você pode acessar a instância no endereço `http://localhost:1333` e criar um usuário administrador.
+
+Se estiver curiosa: o comando `./bw-dev` é um shell script simples que executa várias ferramentas: no exemplo acima, você poderia pular o script e executar `docker-compose build` ou `docker-compose up` diretamente, se preferir. `./bw-dev` só junta esses comandos em um só, por conveniência. Execute-o sem argumentos para ver uma lista de comandos disponíveis, leia a [página da documentação](/command-line-tool.html) ou abra o arquivo para dar uma olhada no que cada comando faz!
+
+### Editando e criando Modelos (Models)
+
+Se você quiser editar ou criar um modelo, você provavelmente vai alterar a estrutura do banco de dados. Para que essas alterações funcionem, você precisará executar o comando `makemigrations` do Django para criar um novo [arquivo de migrações do Django](https://docs.djangoproject.com/en/3.2/topics/migrations) e então `migrá-lo`:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editando arquivos estáticos
+Toda vez que você alterar o CSS ou o JavaScript, você precisará rodar o comando `collectstatic`do Django para que as alterações passem a funcionar:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+Se você tiver o [yarn instalado](https://yarnpkg.com/getting-started/install), você pode executar `yarn watch:static` para executar automaticamente o script toda vez que houver alguma mudança no diretório `bookwyrm/static`.
diff --git a/locale/pt_BR/content/contributing/style_guide.md b/locale/pt_BR/content/contributing/style_guide.md
new file mode 100644
index 00000000..1f41a24e
--- /dev/null
+++ b/locale/pt_BR/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+Então você quer contribuir com a BookWyrm? Show! Se houver algum problema aberto no repositório que você quer consertar, deixer um comentário para que o trabalho não seja feito mais de uma vez. Tente manter o escopo dos pull requests pequenos e focados em uma única questão. Assim é mais fácil revisar, e se alguma parte precisar ser alterada, isso não atrapalhará as outras partes.
+
+Se você não sabe exatamente como consertar alguma coisa, ou se não consegue fazê-lo, está tudo bem! Só deixe um comentário no pull request e vamos descobrir 💖.
+
+Os pull requests passam por todas as verificações automáticas antes de serem mesclados - isso inclui verificações de estilos, linters globais, uma verificação de segurança e testes unitários.
+
+## Linting
+
+### Global
+
+Usamos o [EditorConfig](https://editorconfig.org) para manter uma identação e fins de linha consistentes.
+
+### Python
+
+A BookWyrm usa o formatador de código [Black](https://github.com/psf/black) pra manter o código Python com um estilo consistente. Todas as novas pull requests são verificadas com ações do GitHub, e você pode corrigir problemas nos códigos de estilo executando `./bw-dev black`
+
+Os códigos também são chegados pelo Pylint usando GitHub Actions. Os avisos do Pylint devem ser analisados antes da pull request ser mesclada, mas é uma questão de escolha se a sugestão deve ser acatada ou o aviso, suprimido. Para suprimir o aviso, coloque um comentário no fim ou na linha acima do aviso: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Suas pull requests também vão ser verificadas pelo linter [curlylint](https://www.curlylint.org) dos templates do Django.
+
+### CSS
+
+Usamos o [stylelint](https://stylelint.io) para conferir todas as regras de CSS. Como no Pylint, [você pode disativar o stylelint](https://stylelint.io/user-guide/ignore-code) para alguma regra particular, mas você vai precisar de uma boa justificativa para fazê-lo.
+
+### JavaScript
+
+[ESLint](https://eslint.org) verifica todas as modificações em JavaScript que você fizer. Se o ESLint não gostar do seu JavaScript, dê uma olhada na mensagem do linter para ver qual é o problema.
+
+## Design inclusivo
+
+A BookWyrm quer ser o mais inclusiva e acessível possível.
+
+Quando for contribuir com código, dê uma olhada na [Check list de web design inclusivo](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) antes de enviar o pull request. Para sugestões de acessibilidade, o [A11Y-101](https://www.a11y-101.com/development) também é uma fonte útil. Para saber como fazer seus templates serem compatíveis com vários idiomas, veja a [seção Traduções](/translations.html).
+
+Algumas coisas que colaboradores da BookWyrm acharam boas de se lembrar:
+
+### Formulários
+
+* Só use `input[type="checkbox"]` ou `input[type="radio"]` dentro `<label>`
+* Se você não colocar os botões de checkbox e radio dentro do `<label>`, o `<label>` deve ser colocado _depois_ do elemento ao que ele está relacionado
+
+### Botões e links
+
+* Use um elemento `<button>` para tudo que sirva para disparar uma ação de JavaScript (ex: esconder ou mostrar um formulário) ou enviar uma solicitação `POST` (ex: enviar um formulário)
+* Use um elemento `<a>` para tudo que faça uma solicitação `GET`. Normalmente um elemento de âncora (`<a>`) não costuma ser estilizado como um botão (`class="button"`), mas há algumas exceções, como os botões de "Cancelar". Se tiver alguma dúvida, peça sugestões no seu pull request
diff --git a/locale/pt_BR/content/contributing/translation.md b/locale/pt_BR/content/contributing/translation.md
new file mode 100644
index 00000000..dc13c6ef
--- /dev/null
+++ b/locale/pt_BR/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+TItle: Traduções Date: 2021-10-20 Order: 2
+- - -
+
+## Colaborar com traduções
+
+Você pode participar do projeto de tradução da BookWorm no [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Linguagem neutra
+
+As traduções da BookWyrm devem usar marcação de gênero neutra o máximo possível. Isso se aplica mesmo se a língua utiliza o masculino como gênero neutro padrão, ou se possui algo similiar a "ele/ela". Também é importante que as traduções sejam claras, concisas e legíveis em leitores de tela, e às vezes esses objetivos entram em conflito; não há uma solução perfeita para todos os problemas, e a solução depende do idioma.
+
+Como elemento norteador, tente dar mais ênfase ao aspecto inclusivo e ao uso de palavras de gênero neutro do que se fiar à correção formal ou a guias de estilo oficiais. No Inglês, por exemplo, muitos guias de estilo formais exigem que se use um pronome singular "she" ou "he" para se referir a um indivíduo, mas na BookWyrm seria melhor utilizar o pronome singular neutro "they".
+
+Se você não sabe como resolver algum problema de tradução, abra um [tópico de discussão](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) para tratar de problemas mais amplos.
+
+## Fazendo templates traduzíveis
+
+A BookWyrm se utiliza da função de tradução do Django para fazer com que o conteúdo das páginas mude dependendo da língua da interface selecionada pelo usuário. A documentação do Django traz [uma ótima explicação](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) de como ela funciona, mas aqui temos uma versão mais curta:
+
+* todo texto no template deve incluir as tags de tradução de template
+* adicione `{% load i18n %}` no início do arquivo de template pra ativar as traduções
+* Se o bloco de texto for literal, você pode usar a tag `{% trans %}`
+* Se o bloco de texto tiver variáveis, você deve usar o par de tags `{% blocktrans %}` e `{% endblocktrans %}`. Se você estiver usando espaços em brancos ou quebras de linha, use `trimmed` para removê-los automaticamente quando o arquivo de localização for gerado: `{% blocktrans trimmed %}`
+
+### Exemplos
+
+```html
+<p>{% trans "Esta lista está vazia" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Adicionado por <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/pt_BR/content/index.md b/locale/pt_BR/content/index.md
new file mode 100644
index 00000000..d8244a4c
--- /dev/null
+++ b/locale/pt_BR/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+A BookWyrm é uma rede social para acompanhar sua leitura, falar sobre livros, escrever resenhas e achar outro livro pra ler em seguida. A federação permite que usuários da BookWyrm participem de comunidades pequenas e confiáveis que podem se conectar entre si, e também a outros serviços ActivityPub, como o Mastodon e o Pleroma.
+
+## Funcionalidades
+Uma vez que o projeto está ainda na fase inicial, as funcionalidades crescem a cada dia, e ainda há muito espaço para sugestões e ideias. Abra um [problema](https://github.com/bookwyrm-social/bookwyrm/issues) para conversarmos!
+
+- Fazendo publicações sobre livros
+    - Escreva resenhas com ou sem nota que aparecerão na página do livro
+    - Escreva outros tipos de publicações sobre livros, como:
+        - Comentários sobre um livro
+        - Citações ou resumos
+    - Respostas a publicações
+    - Veja as resenhas sobre um livro de várias instâncias BookWyrm conectadas
+    - Diferencie resenhas locais e federadas e as notas na sua página de atividades
+- Acompanhe sua leitura
+    - Coloque livro nas prateleiras padrão, "para-ler", "lendo" e "lido"
+    - Crie prateleiras personalizadas
+    - Guarde as datas em que começou ou terminou de ler um livro, além de atualizações sobre o andamento de sua leitura
+    - Envia aos seguidores as atividades de leitura (opcionalmente, e com privacidade de controle granular)
+    - Crie listas de livros que podem ser abertas às submissões de outros usuários, aberta à submissão mas com processo de aprovação ou apenas organizada por quem a criou
+- Federação com o ActivityPub
+    - Envie e receba publicações de usuários e suas atividades
+    - Compartilhe informações sobre livros entre instâncias para criar um banco de dados de metadados distribuído
+    - Identifique livros compartilhados entre instâncias e agregue conteúdos relacionados
+    - Siga e interaja com usuários entre diferentes instâncias BookWyrm
+    - Opere junto com outros serviços ActivityPub (atualmente somos compatíveis com o Mastodon)
+- Controle de privacidade granular
+    - Níveis de privacidade privado, só para seguidores e público para publicações, estantes e listas
+    - Opção para que usuários aprovem seguidores manualmente
+    - Permite bloquear e sinalizar para a moderação
diff --git a/locale/pt_BR/content/pages/index.md b/locale/pt_BR/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/pt_BR/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/pt_BR/content/running_bookwyrm/cli.md b/locale/pt_BR/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..922c4c58
--- /dev/null
+++ b/locale/pt_BR/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Desenvolvedores e administradores de instâncias Bookwyrm podem usar o script `bw-dev` para tarefas cotidianas. Isso pode tornar seus comandos mais curtos, mais fáceis de lembrar e mais difíceis de serem confundidos.
+
+Se tiver uma instalado uma instância BookWyrm [em produção](installing-in-production.html) ou [em desenvolvimento](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), você pode executar o script pela linha de comando com `./bw-dev` seguido com um subcomando para executar.
+
+## Atalhos do Docker
+
+### bash
+
+Abre uma sessão `bash` interativa dentro do container `web` do Docker.
+
+### build
+
+Equivalente ao `docker-compose build`.
+
+### dbshell
+
+Abre um shell interativo do banco de dados Postgres. Espero que você saiba o que está fazendo.
+
+### runweb args
+
+Executa um comando arbitrário (representado acima pelo `args`) no container `web`.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Executa um comando arbitrário no container `web` (representado acima por `args`) com as portas expostas. Isso é útil para quando você quer executar testes `pdb` porque o `runweb` não irá expor o promp `pdb`.
+
+Equivalente ao `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Abre um shell interativo Django dentro do container `web` do Docker. Você pode usar isso se quiser executar comandos do shell do Django diretamente.
+
+### up [args]
+
+Inicia ou reinicia containers do Docker, incluindo opcionalmente quaisquer argumentos (representados acima por `args`). Equivalente ao `docker-compose up --build [args]`
+
+## Gerenciando o banco de dados
+
+### initdb
+
+Inicializa um banco de dados.
+
+### makemigrations [appname migration number]
+
+_Este comando não está disponível no branch `produção`_.
+
+Executa o comando `makemigrations` do Django dentro do seu container Docker. Se você alterou a estrutura do banco de dados em um branch de desenvolvimento, você precisará executar este comando para que suas alterações tenham efeito. Facultativamente, você pode especificar alguma migração para executar, p. ex. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Executa o comando `migrate` do Django dentro de seu container Docker. Você sempre irá precisar executá-lo após o `makemigrations`.
+
+### resetdb
+
+_Este comando não está disponível no branch `produção`_.
+
+Reinicia o banco de dados. **Este comando vai excluir todo o banco de dados da BookWyrm**, criar outro banco de dados e executar todas as migrações. Você deve deletar todos os arquivos de migração recentes que não quer rodar _antes_ de executar `resetdb`.
+
+## Gerenciando uma instância BookWyrm
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Configurando um armazenamento compatível com S3
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Desenvolvimento e teste
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/pt_BR/content/running_bookwyrm/external-storage.md b/locale/pt_BR/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..bf86f0ef
--- /dev/null
+++ b/locale/pt_BR/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+Por padrão, a BookWyrm usa o armazenamento local para os arquivos estáticos (ícones, avatar padrão, etc.) e as mídias (avatares dos usuários, capas de livros, etc.), mas você pode usar um armazenament externo para distribuir esses arquivos. A BooKWyrm utiliza o `django-storages` para lidar com o armazenamento externo, como serviços compatíveis com S3, Apache Libcloud ou SFTP.
+
+## Serviços compatíveis com S3
+
+### Configuração
+
+Crie um bucket em seu serviço compatível com S3 favorito, junto com uma Access Key ID e uma Scret Access Key. Eles podem ser auto-hospedados, como [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) ou [MinIO](https://min.io/) (GNU AGPL v3.0), ou comercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+Este guia foi testado no Scaleway Object Storage. Se você usa outro serviço, por favor nos conte sua experiência (especialmente se fez algum outro passo) criando um problema (issue) no repositório da [documentação da BookWyrm Documentation](https://github.com/bookwyrm-social/documentation).
+
+### O que lhe espera
+
+Se você está iniciando uma nova instância BookWyrm, o processo será:
+
+- Configurar seu serviço de armazenamento externo
+- Habilitar o armazenamento externo na BookWyrm
+- Inicie sua instância BookWyrm
+- Atualize o conector da instância
+
+Se você já iniciou a instância, e imagens foram enviadas para o armazenamento local, o processo será:
+
+- Configure seu serviço de armazenamento externo
+- Copie sua mídia local para o armazenamento externo
+- Habilite o armazenamento externo na BookWyrm
+- Reinicie sua instância BookWyrm
+- Atualize o conector da instância
+
+### Configurações da BookWyrm
+
+Edite seu arquivo `.env` descomentando as seguintes linhas:
+
+- `AWS_ACCESS_KEY_ID`: sua ID de acesso
+- `AWS_SECRET_ACCESS_KEY`: sua chave de acesso secreta
+- `AWS_STORAGE_BUCKET_NAME`: o nome do seu bucket
+- `AWS_S3_REGION_NAME`: p.ex. `"eu-west-1"` para a AWS, `"fr-par"` para a Scaleway ou `"nyc3"` para a Digital Ocean
+
+Se seu serviço compatível com S3 for a Amazon AWS, já está tudo pronto. Se não, você deverá descomentar as seguintes linhas:
+
+- `AWS_S3_CUSTOM_DOMAIN`: o domínio que irá servir os arquivos, p.ex `"example-bucket-name.s3.fr-par.scw.cloud"` ou `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: o endpoint da API S3, p. ex `"https://s3.fr-par.scw.cloud"` ou `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copiando a mídia local para o armazenamento externo
+
+Se sua instância BookWyrm já está rodando e já recebeu mídias (avatares de usuários, capas de livros…), você precisará migrar essa mídia enviada para seu bucket.
+
+Essa tarefá é feita com o comando:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Habilitando o armazenamento externo na BookWyrm
+
+Para habilitar o armazenamento externo compatível com S3, você deverá editar seu arquivo `.env` e mudar a propriedade da variável `USE_S3` de `false` para `true`:
+
+```
+USE_S3=true
+```
+
+Se seu armazenamento externo está servindo via HTTPS (como a maioria hoje em dia), você também precisará se certificar de que `USE_HTTPS` seja `true` para que as imagens carreguem via HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Arquivos estáticos
+
+Então, para copiar os arquivos estáticos para o seu bucket S3 você precisará executar o seguinte comando:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### Configurações do CORS
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. Se algumas fontes não aparecem (e o console JS do seu navegador alerta sobre o CORS), algo deu errado [aqui](#cors-settings). Nesse caso pode ser bom conferir os headers da solicitação HTTP em algum arquivo no seu bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MEU_DOMINIO' http://ENDEREÇO_DO_BUCKET/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Substitua `MEU_DOMINIO` com o domínio da sua instância e `ENDEREÇO_DO_BUCKET` com o endereço de seu bucket. Você pode substituir o caminho dos arquivos para algum que seja válido em seu bucket.
+
+Se você ver alguma mensagem, especialmente alguma que comece com `<Error><Code>CORSForbidden</Code>`, não deu certo. Se você não ver mensagem alguma, funcionou.
+
+Em uma instância ativa pode haver vários arquivos criados localmente durante a migração para o armazenamento externo, e reiniciar a aplicação pode fazê-la utilizar o armazenamento externo. Para garantir que os arquivos restantes sejam enviados ao armazenamento externo depois de alterar, você pode usar o seguinte comando, que irá enviar apenas arquivos que ainda não estejam no armazenamento externo:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Atualizando o conector da instância
+
+*Aviso: você pode pular este passo se está utilizando uma versão atualizada da BookWyrm; em setembro de 2021, o "self connector" foi removido no [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+Para que o endereço correto seja utilizado ao mostrar resultados da pesquisa de livros locais, temos que alterar o valor da base do URL das imagens de capa.
+
+Os dados do conector podem ser acessados pela interface de administração do Django presentes no endereço `http://MY_DOMAIN_NAME/admin`. O conector da sua própria instância é o primeiro registro no banco de dados, então você pode acessá-lo pelo seguinte endereço: `https://MEU_DOMINIO/admin/bookwyrm/connector/1/change/`.
+
+O campo _URL das capas (Covers url)_ é, por padrão, `https://MEU_DOMINIO/images`, você deve mudá-lo para `https://ENDEREÇO_DO_ARMAZENAMENTO_S3/images`. Então clique o botão de _Salvar_ e voilà!
+
+Você deverá atualizar o valor do _Covers url_ toda vez que alterar o endereço de seu armazenamento.
diff --git a/locale/pt_BR/content/running_bookwyrm/install-prod-dockerless.md b/locale/pt_BR/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/pt_BR/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/pt_BR/content/running_bookwyrm/install-prod.md b/locale/pt_BR/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..e3b97c35
--- /dev/null
+++ b/locale/pt_BR/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+Este projeto ainda é jovem e não está, no momento, muito estável, então tenha cuidado ao rodá-lo em produção.
+
+## Configuração do servidor
+- Obtenha um domínio e configure o DNS para seu servidor. Você deverá apontar os nameservers do seu domínio no provedor de DNS ao servidor onde você hospedará a BookWyrm. Aqui estão as instruções para a [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Configure o seu servidor com firewalls adequados a uma aplicação web (estas instruções foram testadas no Ubuntu 20.04). Aqui estão as instruções para a [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Configure um serviço de email (como o [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) e as configurações corretas de SMTP/DNS. Use a documentação do serviço para configurar seu DNS
+- [Instale o Docker e docker-compose](https://docs.docker.com/compose/install/)
+
+## Instale e configure a BookWyrm
+
+O branch `produção (production)` da BookWyrm tem uma série de ferramentas indisponíveis no branch `principal (main)` que servem para a execução em produção, como alterações no `docker-compose` para atualizar os comandos padrão, configuração de containers e alterações individuais nas configurações dos containers para ativar coisas com SSL ou backups comuns.
+
+Instruções para rodar a BookWyrm em produção:
+
+- Obtenha o código da aplicação: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Mude para o branch `produção (production)`: `git checkout production`
+- Crie seu arquivo de variáveis do ambiente, `cp .env.example .env`, e atualize o seguinte:
+    - `SECRET_KEY` | Uma string de caracteres difíceis de descobrir
+    - `DOMAIN` | Seu domínio
+    - `EMAIL` | Um endereço de email para ser usado na verificação de domínio do certbot
+    - `POSTGRES_PASSWORD` | Defina uma senha segura para o banco de dados
+    - `REDIS_ACTIVITY_PASSWORD` | Defina uma senha segura para o subsistema Redis Activity
+    - `REDIS_BROKER_PASSWORD` | Defina uma senha segura para o subsistema Redis queue broker
+    - `FLOWER_USER` | Seu nome de usuário para acessar o monitor de filas Flower
+    - `FLOWER_PASSWORD` | Sua senha segura para acessar o monitor de filas Flower
+    - `EMAIL_HOST_USER` | O endereço do recipiente que o aplicativo usará para enviar emails
+    - `EMAIL_HOST_PASSWORD` | A senha do seu serviço de email
+- Configure o nginx
+    - Faça uma cópia do template da configuração de produção e ative-o no ngix `cp nginx/production nginx/default.conf`
+    - Atualize o `nginx/default.conf`:
+        - Substitua `your-domain.com` com seu domínio em todos os lugares do arquivo (incluindo as linhas comentadas)
+        - Se você não estiver utilizando o subdomínio `www`, exclua a versão do domínio www.your-domain.com do `server_name` no primeiro bloco server no `nginx/default.conf` e exclua a flag `-d www.${DOMAIN}` no fim do comando `certbot` no `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Rode a aplicação (e isso deve também configurar o certificado ssl do Certbot para seu domínio) com `docker-compose up --build`, e certifique-se de que todas as imagens foram construidas com sucesso
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/pt_BR/content/running_bookwyrm/moderation.md b/locale/pt_BR/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..2245b834
--- /dev/null
+++ b/locale/pt_BR/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Usuários têm a opção de bloquear outros usuários por conta própria, sem a intervenção da moderação. Da página da administração "Servidores federados", administradores podem ver quantos usuários de uma instância foram bloqueadas por usuários locais.
+
+## Denúncias
+Usuários podem denunciar publicações ou usuários a partir do menu "mais opções" no rodapé das publicações e no menu seguir/deixar de seguir dos usuários. Quando uma denúncia é feita, todos os usuários com permissão de administração receberão uma notificação.
+
+Quando uma denuncia é feita, há algumas formas de o moderador respondê-la.
+- Enviar uma mensagem direta ao usuário denunciado.
+- Excluir a publicação denunciada.
+- Desativar o usuário. Para usuários locais, isso os deixará incapazes de logar, e suas contas não aparecerão na aplicação. Para usuários remotos, o servidor irá rejeitar todas as atividades desse usuário, e eles não aparecerão nas buscas.
+
+## Moderação a nível da instância
+Moderadores podem bloquear instâncias inteiras. Isso fará com que nenhuma atividade dessa instância chegue, e desativará todas as contas daquela instância localmente.
+
+Se a instância for desbloqueada, todos os seus usuários que foram desativados serão reativados.
+
+Moderadores também podem enviar blocklists para bloquear servidores em massa.
diff --git a/locale/pt_BR/content/running_bookwyrm/monitoring-queue.md b/locale/pt_BR/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/pt_BR/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/pt_BR/content/running_bookwyrm/optional_features.md b/locale/pt_BR/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..6d9bc755
--- /dev/null
+++ b/locale/pt_BR/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Alguns recursos da BookWyrm devem ser habilitados para funcionar.
+
+## Geração de pré-visualização
+
+Por padrão, a BookWyrm usa a logo da instância (ou a padrão) como uma imagem de pré-vusalização OpenGraph. Você pode também habilitar a criação de pré-visualização para livros, usuários e para todo o site.
+
+As imagens de pré-visualização serão do tamanho grande do OpenGraph (usado pelo twitter com o nome de `summary_large_image`). Dependendo do tipo de imagem, seus conteúdos serão:
+
+- a imagem padrão da instância mostrará a logo grande e o nome da instância e seu endereço
+- a imagem do usuário mostrará seu avatar, nome de exibição e arroba (na forma usuário@instância)
+- a imagem do livro mostrará sua capa, título, subtítulo (se tiver), autor e avaliação (se tiver)
+
+Essas imagens serão atualizadas em vários casos:
+
+- imagem da instância: quando o nome da instância ou a logo são alterados
+- imagem do usuário: quando o nome de exibição ou o avatar são alterados
+- imagem do livro: quando o título, a autoria ou a capa são alterados, ou quando uma nova avaliação é feita
+
+### Habilitando imagens de pré-visualização
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/pt_BR/content/running_bookwyrm/reverse-proxy.md b/locale/pt_BR/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/pt_BR/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/pt_BR/content/running_bookwyrm/updating.md b/locale/pt_BR/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/pt_BR/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/pt_BR/content/using_bookwyrm/adding-books.md b/locale/pt_BR/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/pt_BR/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/pt_BR/content/using_bookwyrm/posting-statuses.md b/locale/pt_BR/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/pt_BR/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/pt_PT/LC_MESSAGES/messages.po b/locale/pt_PT/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..4552d5f6
--- /dev/null
+++ b/locale/pt_PT/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Portuguese\n"
+"Language: pt_PT\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: pt-PT\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/pt_PT/content/codebase/activitypub.md b/locale/pt_PT/content/codebase/activitypub.md
new file mode 100644
index 00000000..90093b30
--- /dev/null
+++ b/locale/pt_PT/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Avaliação`: Uma avaliação é um status em resposta a um livro (indicado pelo campo `inReplyToBook` ), que tem um título, corpo e classificação numérica entre 0 (não avaliado) e 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Citação`: uma citação tem um corpo de mensagem, um resumo de um livro e menciona um livro.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/pt_PT/content/codebase/permissions.md b/locale/pt_PT/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/pt_PT/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/pt_PT/content/contributing/contributing.md b/locale/pt_PT/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/pt_PT/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/pt_PT/content/contributing/debug_toolbar.md b/locale/pt_PT/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/pt_PT/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/pt_PT/content/contributing/install-dev.md b/locale/pt_PT/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/pt_PT/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/pt_PT/content/contributing/style_guide.md b/locale/pt_PT/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/pt_PT/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/pt_PT/content/contributing/translation.md b/locale/pt_PT/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/pt_PT/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/pt_PT/content/index.md b/locale/pt_PT/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/pt_PT/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/pt_PT/content/pages/index.md b/locale/pt_PT/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/pt_PT/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/pt_PT/content/running_bookwyrm/cli.md b/locale/pt_PT/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..646c7f91
--- /dev/null
+++ b/locale/pt_PT/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrar todas as mídias enviadas de uma instalação existente do BookWyrm para um "bucket" compatível com S3. Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Migrar todas as mídias enviadas de uma instalação existente do BookWyrm para um "bucket" compatível com S3. Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/pt_PT/content/running_bookwyrm/external-storage.md b/locale/pt_PT/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/pt_PT/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/pt_PT/content/running_bookwyrm/install-prod-dockerless.md b/locale/pt_PT/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..833f09b5
--- /dev/null
+++ b/locale/pt_PT/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. No debian, isso pode aparecer com `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Descomente linhas 18 a 67 para ativar o encaminhamento para HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+Você precisará configurar um trabalho Cron para o serviço começar automaticamente ao reiniciar um servidor.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/pt_PT/content/running_bookwyrm/install-prod.md b/locale/pt_PT/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/pt_PT/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/pt_PT/content/running_bookwyrm/moderation.md b/locale/pt_PT/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/pt_PT/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/pt_PT/content/running_bookwyrm/monitoring-queue.md b/locale/pt_PT/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/pt_PT/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/pt_PT/content/running_bookwyrm/optional_features.md b/locale/pt_PT/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..708f38c2
--- /dev/null
+++ b/locale/pt_PT/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. Como se tratava de um desperdício em termos de espaço em disco e poder de computação, essa geração foi travada. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/pt_PT/content/running_bookwyrm/reverse-proxy.md b/locale/pt_PT/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/pt_PT/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/pt_PT/content/running_bookwyrm/updating.md b/locale/pt_PT/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/pt_PT/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/pt_PT/content/using_bookwyrm/adding-books.md b/locale/pt_PT/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/pt_PT/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/pt_PT/content/using_bookwyrm/posting-statuses.md b/locale/pt_PT/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/pt_PT/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/ro_RO/LC_MESSAGES/messages.po b/locale/ro_RO/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..f73b1d56
--- /dev/null
+++ b/locale/ro_RO/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Romanian\n"
+"Language: ro_RO\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : (n==0 || (n%100>0 && n%100<20)) ? 1 : 2);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: ro\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr "Documentație BookWyrm"
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr "Ghidul dvs. pentru a folosi și contribui la BookWyrm"
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr "Cum să folosiți și să contribuiți"
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr "BookWyrm: citit social și recenzii"
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "Alăturați-vă"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr "Implicați-vă"
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "Susțineți"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr "Cod"
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr "Documentație"
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr "<strong>BookWyrm</strong> este un program colaborativ, anti-corporație, menținut de <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr "Susțineți BookWyrm pe <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr "Alăturați-vă"
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr "BookWyrm pe GitHub"
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr "Contribuiți la această pagină"
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr "Aflați mai multe"
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr "Contactați responsabilul"
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr "Licență"
+
diff --git a/locale/ro_RO/content/codebase/activitypub.md b/locale/ro_RO/content/codebase/activitypub.md
new file mode 100644
index 00000000..256b1bb6
--- /dev/null
+++ b/locale/ro_RO/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivitatePub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm folosește protocolul [ActivityPub](http://activitypub.rocks/) pentru a trimite și primi activitatea utilizatorului între alte instanțe BookWyrm și alte servicii care implementează ActivityPub, precum [Mastodon](https://joinmastodon.org/). Pentru a gestiona datele cărților, BookWyrm are câteva tipuri Activity extinse care nu fac parte din standard, dar înțelese de alte instanțe BookWyrm.
+
+## Activități și obiecte
+
+### Utilizatori și relații
+Interacțiunile dintre relațiile utilizatorilor respectă specificația ActivityPub.
+
+- `Follow`: solicitați să primiți stări de la un utilizator și să le vizualizați pe cele cu confidențialitatea „numai urmăritori”
+- `Accept`: aprobă o `cerere de urmărire` și finalizează relația
+- `Reject`: respinge o `cerere de urmărire`
+- `Block`: împiedică utilizatorii de a își vedea unul altuia stările și împiedică utilizatorul blocat de a vizualiza profilul actorului
+- `Update`: actualizează profilul și setările unui utilizator
+- `Delete`: dezactivează un utilizator
+- `Undo`: anulează o `cerere de urmărire` sau `de blocare`
+
+### Stări
+#### Tipuri de obiecte
+
+- `Notă`: pe servicii precum Mastodon, `Notele` sunt tipul principal de stare. Ele conțin corpul mesajului, atașamentele, pot menționa utilizatori și pot fi răspunsuri la stări de orice tip. În cadrul BookWyrm, `notele` pot fi create ca mesaje directe sau ca răspunsuri la alte stări.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comentariu`: un comentariu despre o carte menționează cartea respectivă și are un corp de mesaj.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activități
+
+- `Create`: salvează o nouă stare în baza de date.
+
+   **Note**: BookWyrm acceptă activități de `Create` numai dacă sunt:
+
+   - Mesaje directe (de exemplu `Note` cu nivel de confidențialitate `direct`, care menționează un utilizator local),
+   - În legătură cu o carte (de un tip de stare personalizat care include câmpul `inReplyToBook`),
+   - Răspunsuri la stări existente salvate în baza de date
+- `Delete`: elimină o stare
+- `Like`: marchează starea ca favorit
+- `Announce`: partajează starea pe fluxul actorului
+- `Undo`: anulează `Like` sau `Announce`
+
+### Colecții
+Cărțile și listele utilizatorului sunt reprezentate de [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Obiecte
+
+- `Shelf`: o colecție de cărți a utilizatorului. În mod implicit, fiecare utilizator are un raft „`de citit`”, „`în curs de citire`” și „`citit`” pentru a urmări progresul de lectură.
+- `List`: o colecție de cărți care poate avea articole contribuite de alți utilizatori.
+
+#### Activități
+
+- `Create`: adaugă un raft sau o listă în baza de date.
+- `Delete`: înlătură un raft sau o listă.
+- `Add`: adaugă o carte pe un raft sau într-o listă.
+- `Remove`: înlătură o carte de pe un raft sau dintr-o listă.
+
+
+## Serializare alternativă
+Deoarece BookWyrm folosește propriile tipuri de obiecte (`Review`, `Comment`, `Quotation`) care nu sunt suportate de ActivityPub, stările sunt transformate în tipuri standard când sunt trimise sau vizualizate de servicii din afara BookWyrm. `Review`s sunt convertite în `Article`s, iar `Comment`s și `Quotation`s sunt convertite în `Note`s cu o legătură către cartea și imaginea de copertă atașate.
diff --git a/locale/ro_RO/content/codebase/permissions.md b/locale/ro_RO/content/codebase/permissions.md
new file mode 100644
index 00000000..a596b6f6
--- /dev/null
+++ b/locale/ro_RO/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Titlu: Permisiuni Dată: 18-04-2021 Ordine: 2
+- - -
+
+Accesul utilizatorului la diferite funcționalități este controlat folosind [sistemul de autentificare încorporat din Django](https://docs.djangoproject.com/en/3.2/topics/auth/default/). Când o instanță este creată, scriptul `initdb` creează o serie de permisiune ce sunt asociate unor grupuri. În mod implicit, toți utilizatorilor noi li se atribuie grupul `editor` care le permite să modifica metadatele cărților.
+
+Administratorul de rețea ar trebui să aibă statutul de `super utilizator` care îi dă acces la adminul din Django (`/admin`) și lui conferă toate permisiunile.
+
+## Permisiuni și grupuri
+Acest tabel arată cele patru grupuri (admin, moderator, editor și utilizator) și ce permisiuni au utilizatorii din fiecare grup:
+
+|                                     | admin | moderator | editor | utilizator |
+| ----------------------------------- | ----- | --------- | ------ | ---------- |
+| modificarea setărilor instanței     | ✔️    | -         | -      | -          |
+| schimbarea nivelului utilizatorului | ✔️    | -         | -      | -          |
+| gestionarea federației              | ✔️    | ✔️        | -      | -          |
+| trimiterea de invitații             | ✔️    | ✔️        | -      | -          |
+| dezactivarea utilizatorilor         | ✔️    | ✔️        | -      | -          |
+| ștergerea postărilor                | ✔️    | ✔️        | -      | -          |
+| editarea cărților                   | ✔️    | ✔️        | ✔️     | -          |
+ încărcatul de coperți            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/ro_RO/content/contributing/contributing.md b/locale/ro_RO/content/contributing/contributing.md
new file mode 100644
index 00000000..92f6bcb3
--- /dev/null
+++ b/locale/ro_RO/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+Există multe moduri în care puteți contribui la acest proiect, indiferent de nivelul dvs. de expertiză technică.
+
+## Retroacțiuni (feedback) și sugestii de funcționalități
+Vă încurajăm și sunteți binevenit să indicați buguri, sugestii și idei despre cum ar trebui lucrurile să meargă folosind [tichetele GitHub](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Contribuții la cod
+Contribuțiile la cod sunt mai mult ca binevenite! Dacă nu știți de unde să începeți, aruncați o privire la eticheta [„Primul bun tichet”](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22). Deoarece BookWyrm este un proiect mic, nu există nicio structură formală, dar există o mare capacitate de asistență personală, precum pusul unei întrebări, programare în pereche, chat video etc., așa că simțiți-vă liber să ne contactați.
+
+Dacă aveți întrebări despre proiect sau despre modul de contribuire, puteți să vă alăturați [chatului Matrix BookWyrm](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Traduceri
+Vorbiți mai multe limbi străine? BookWyrm are nevoie de localizare! Puteți adăuga și edita traduceri la [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Suport financiar
+BookWyrm este un proiect de pasiune fără publicități, fără intenții de a căuta finanțare prin capital de risc sau relații financiare corporative. Dacă doriți să ajutați proiectul să continue, puteți deveni un contribuitor regulat prin [Patreon](https://www.patreon.com/bookwyrm) sau [OpenCollective](https://opencollective.com/bookwyrm) sau să faceți un cadou punctual prin [PayPal](https://paypal.me/oulipo).
diff --git a/locale/ro_RO/content/contributing/debug_toolbar.md b/locale/ro_RO/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..dfd6bd24
--- /dev/null
+++ b/locale/ro_RO/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm are o ramură care este configurată să ruleze [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). Această ramură nu va fi niciodată fuzionată cu `main` și are câteva modificări care o fac să funcționeze cu bara de instrumente, dar nesigură de utilizat în ceva asemănător unui mediu de producție. Pentru a folosi această ramură, va trebui să urmăriți câțiva pași pentru a o configura.
+
+## Configurare
+
+- Folosind git, deplasați-vă pe ramura [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar)
+- Actualizați ramura relativ la `main` folosind `git merge main`. Ramura este actualizată periodic dar este probabil ca ea să fie în urmă.
+- Reconstruiți imaginea Docker folosind `docker-compose up --build` pentru a vă asigura că biblioteca de instrumente de depanare este instalată din `requirements.txt`
+- Accesați imaginea aplicației `web` direct (în loc de `nginx`) folosind portul `8000`
diff --git a/locale/ro_RO/content/contributing/install-dev.md b/locale/ro_RO/content/contributing/install-dev.md
new file mode 100644
index 00000000..20ddc8e5
--- /dev/null
+++ b/locale/ro_RO/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Cerințe preliminare
+
+Aceste instrucțiuni presupun că dezvoltați BookWyrm folosind Docker. Va trebui să [instalați Docker](https://docs.docker.com/engine/install/) și [docker-compose](https://docs.docker.com/compose/install/) pentru a începe.
+
+## Configurați mediul de dezvoltare
+
+- Obțineți o copie a [bazei de cod BookWyrm de pe GitHub](https://github.com/bookwyrm-social/bookwyrm). Puteți [crea un fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) al depozitului și apoi [folosi `git clone` pentru a descărca codul](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) pe calculatorul dumneavoastră.
+- Mergeți în dosarul care conține codul pe calculatorul dvs, veți lucra aici de aici în colo.
+- Configurați fișierul de variabile de mediu al dvs. copiind fișierul de mediu exemplu (`.env.example`) într-un nou fișier numit `.env`. În linia de comandă, puteți face asta cu:
+``` { .sh }
+cp .env.example .env
+```
+- În `.env`, schimbați `DEBUG` în `true`
+- Opțional, puteți folosi un serviciu precum [ngrok](https://ngrok.com/) pentru a configura un nume de domeniu și seta variabila `DOMAIN` în fișierul dumneavoastră `.env` în numele de domeniu generat de ngrok.
+
+- Configurați nginx pentru dezvoltare prin copierea fișierului de configurație nginx (`nginx/development`) într-un nou fișier numit `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Porniți aplicația. În linia de comandă, rulați:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Odată compilarea terminată, puteți accesa instanța la `http://localhost:1333` și crea un utilizator administrator.
+
+Dacă sunteți curios: comanda `./bw-dev` este un simplu script shell care rulează multe alte comenzi: deasupra, ați putea sări peste ea și rula `docker-compose build` sau `docker-compose up` direct dacă doriți. `./bw-dev` doar le colectează într-un singur loc pentru conveniență. Rulați-o fără argumente pentru a obține o listă a comenzilor disponibile, citiți [pagina de documentație](/command-line-tool.html) pentru ea sau deschideți-o pentru a vedea ce face fiecare comandă!
+
+### Editați sau configurați modele
+
+Dacă schimbați sau creați un model, veți schimba probabil structura bazei de date. Pentru ca aceste schimbă să aibă efect va trebui să rulați comanda Django `makemigrations` pentru a crea un nou [fișier de migrare Django](https://docs.djangoproject.com/en/3.2/topics/migrations) și apoi `migrate`:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editați fișiere statice
+De fiecare dată când editați CSS sau JavaScript, va trebui să rulați comanda Django `collectstatic` pentru ca schimbările dvs. să aibă efect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+Dacă aveți [yarn instalat](https://yarnpkg.com/getting-started/install), puteți rula `yarn watch:static` pentru a rula automat scriptul precedent de fiecare dată când o schimbare are loc în dosarul `bookwyrm/static`.
diff --git a/locale/ro_RO/content/contributing/style_guide.md b/locale/ro_RO/content/contributing/style_guide.md
new file mode 100644
index 00000000..9f03b5ea
--- /dev/null
+++ b/locale/ro_RO/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Cereri de extragere (pull requests)
+
+Deci vreți să contribuiți la codul BookWyrm: super! Dacă există un tichet nerezolvat pe care ați vrea să-l rezolvați, este util să lăsați un comentariu pentru ca munca să nu fie duplicată. Încercați să păstrați obiectivul cererilor de extragere mic și concentrat pe o singură temă. În acest fel este mai ușor de revizuit, iar dacă o parte are nevoie de schimbări, nu le va bloca pe celelalte.
+
+Dacă nu sunteți sigur de cum să rezolvați ceva sau nu vă descurcați, este complet în regulă. Doar lăsați un comentariu la cererea de extragere și ne vom descurca 💖.
+
+Cererile de extragere au nevoie de a trece verificările automate înainte de a fi fuzionate. Acestea includ verificări de stil, lintere globale, o verificare de securitate și teste unitare.
+
+## Linting
+
+### Global
+
+Folosim [EditorConfig](https://editorconfig.org) pentru a menține indentarea și finalul liniilor consecvente.
+
+### Python
+
+BookWyrm folosește formatorul de cod [Black](https://github.com/psf/black) pentru a menține stilul codului consistent. Toate cererile noi de extragere sunt verificate cu acțiunile GitHub și puteți regla în modul automat problemele de stil de cod rulând `./bw-dev black`
+
+Codul este de asemenea verificat cu Pylint folosind acțiunile GitHub. Avertismentele Pylint trebuie abordate înainte ca cererile de extragere să fie fuzionate, dar este un apel de judecată dacă sugestia ar trebui folosită sau suprimată. Pentru a șterge un avertisment, adăugați un comentariu la finalul sau deasupra avertismentului: `# pylint: disable=warning-name`
+
+### Șabloane (HTML)
+
+Cererile dumneavoastră de extragere vor fi de asemenea verificate de linterul [curlylint](https://www.curlylint.org) pentru șabloanele Django.
+
+### CSS
+
+Folosim [stylelint](https://stylelint.io) pentru a verifica toate regulile CSS. Ca și în cazul lui Pylint [puteți dezactiva stylelint](https://stylelint.io/user-guide/ignore-code) pentru o regulă particulară, dar veți avea nevoie de o bună justificare pentru a face asta.
+
+### JavaScript
+
+[ESLint](https://eslint.org) verifică orice modificare JavaScript pe care ați făcut-o. Dacă lui ESLint nu-i place munca dvs. JavaScript, verificați mesajul linterului pentru problema exactă.
+
+## Design inclusiv
+
+BookWyrm dorește să fie cât mai inclusiv și accesibil posibil.
+
+Când contribuiți la cod, verificați [lista Design Web Inclusiv](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) înainte de a depune cererea dvs. de extragere. Pentru sfaturi de accesibilitate, [A11Y-101](https://www.a11y-101.com/development) este de asemenea o resursă utilă. Pentru informații despre cum să faceți șablonul de pagină bilingv, consultați [secțiunea de Traduceri](/translations.html).
+
+Câteva lucruri care li s-au părut contribuitorilor BookWyrm util de reținut sunt:
+
+### Formulare
+
+* Folosiți numai `input[type="checkbox"]` sau `input[type="radio"]` în interiorul `<label>`
+* Dacă nu vă plac casetele de selectare sau butoanele radio în interiorul `<label>`, `<label>` ar trebui plasat _după_ elementul la care se referă
+
+### Butoane și legături
+
+* Folosiți `<button>` pentru orice obiect care declanșează o acțiune JavaScript (de exemplu ascunsul sau afișatul unui formular) sau trimisul unei cereri `POST` (de exemplu trimiterea unui formular)
+* Folosiți`<a>` pentru orice obiect care declanșează o cerere `GET`. De obicei, un element ancoră (`<a>`) nu ar trebui stilizat ca un buton (`class="button"`), deși există unele excepții precum butoanele de "Anulați". Dacă aveți dubii, cereți sfaturi în cererile dvs. de extragere
diff --git a/locale/ro_RO/content/contributing/translation.md b/locale/ro_RO/content/contributing/translation.md
new file mode 100644
index 00000000..5374be84
--- /dev/null
+++ b/locale/ro_RO/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contribuiți la traducere
+
+Puteți să vă alăturați proiectului de traducere BookWyrm la [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Limbaj neutru de gen
+
+Ori de câte ori este posibil, traducerile BookWyrm ar trebui să folosească limbaj de gen neutru. Asta se aplică dacă o limbă folosește în mod implicit genul masculin ca gen neutru sau dacă folosește ceva similar precum „el/ea”. Este de asemenea important ca traducerile să fie clare, concise și lizibile pentru un cititor de ecran. Uneori, aceste obiective intră în conflict. Nu există un răspuns perfect, universal valabil. Soluția depinde de limbă.
+
+Ca directivă principală, încercați să acordați prioritate unui limbaj incluziv și neutru decât unui limbaj formal corect sau aprobat în mod oficial. În engleză, de exemplu, foarte multe recomandări de stil necesită un pronume persoana I „she” sau „he” pentru a se referi la un individ, dar ar fi mai bine ca în BookWyrm să se folosească în schimb „they”, neutru din punct de vedere al genului.
+
+Dacă nu sunteți siguri despre cum să abordați cel mai bine o problemă de traducere, lăsați un comentariu sau deschideți [un subiect de discuție](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) pentru a adresa întrebări la scară mai largă.
+
+## Traducerea șabloanelor
+
+BookWyrm profită de funcționalitățile de traducere Django pentru a permite conținutului paginii să se schimbe în funcție de limba de afișare aleasă de utilizator. Documentația Django [oferă o explicație utilă](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) despre cum funcționează acest proces, dar iată versiunea scurtă:
+
+* toate șabloanele text trebuie să includă taguri de șabloane de traducere
+* adăugați `{% load i18n %}` în partea de sus a șablonului dvs. pentru a activa traducerile
+* Dacă blocul de text este text literal, puteți folosiți tagul șablon `{% trans %}`
+* Dacă blocul de text include variabile, ar trebui să folosiți perechea de taguri șablon `{% blocktrans %}` și `{% endblocktrans %}`. Dacă includeți spațiu alb sau treceri la linie nouă, folosiți `trimmed` pentru a le înlătura automat când fișierul de localizare este generat: `{% blocktrans trimmed %}`
+
+### Exemple
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/ro_RO/content/index.md b/locale/ro_RO/content/index.md
new file mode 100644
index 00000000..e483c36b
--- /dev/null
+++ b/locale/ro_RO/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Bun venit Date: 13-04-2021
+- - -
+
+BookWyrm este o rețea socială pentru a urmări cititul dvs., vorbi despre cărți, scrie recenzii și descoperi ce să citiți în continuare. Federarea permite utilizatorilor BookWyrm să se alăture unor comunități mici și de încredere care se pot conecta una cu cealaltă și cu alte servicii ActivityPub precum Mastodon și Pleroma.
+
+## Caracteristici
+Cum proiectul este încă în fazele timpuri, caracteristicile cresc în fiecare zi. Există o mulțime de spațiu pentru sugestii și idei. Deschideți un [tichet](https://github.com/bookwyrm-social/bookwyrm/issues) pentru a continua conversația!
+
+- Postări despre cărți
+    - Redactați recenzii, cu sau fără evaluări, agregate în continuare pe pagina cărții
+    - Redactați alte tipuri de stări despre cărți, precum:
+        - Comentarii despre o carte
+        - Citate sau extrase
+    - Răspundeți stărilor
+    - Vizualizați recenzii agregate ale unei cărți de pe instanțe BookWyrm conectate
+    - Diferențiați recenzii locale și federate și evaluări în fluxul dvs. de activitate
+- Urmăriți activitatea dvs. de lectură
+    - Puneți cărți pe rafturile prestabilite „de citit”, „în curs de citire” și „citit”
+    - Creați rafturi personalizate
+    - Înregistrați datele de început și sfârșit de lectură, cât și actualizările de progres
+    - Țineți la curent urmăritorii despre activitatea de citit (opțional cu control granulat a confidențialității)
+    - Creați liste de cărți care pot fi deschise modificărilor tuturor sau modificate numai de creator
+- Federație cu ActivityPub
+    - Difuzați și primiți stări și activități de la utilizatori
+    - Partajați date despre cărți între instanțe pentru a crea o bază de metadate la nivel de rețea
+    - Identificați cărțile partajate între instanțe și agregați conținutul conex
+    - Urmăriți și interacționați cu utilizatori de pe alte instanțe BookWyrm
+    - Inter operațional cu servicii ActivityPub în afara BookWyrm (în prezent, Mastodon este suportat)
+- Controale granulate a confidențialității
+    - Nivele de confidențialitate privat, numai urmăritorii și public pentru postări, rafturi și liste
+    - Opțiune pentru utilizatori de a aproba manual urmăritorii
+    - Permite blocarea și semnalarea pentru moderare
diff --git a/locale/ro_RO/content/pages/index.md b/locale/ro_RO/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/ro_RO/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/ro_RO/content/running_bookwyrm/cli.md b/locale/ro_RO/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..073b28c0
--- /dev/null
+++ b/locale/ro_RO/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Dezvoltatorii BookWyrm și managerii de instanțe pot folosi scriptul `bw-dev` pentru sarcinile comune. Poate face comenzile dvs. mai scurte, mai ușor de reținut și mai greu de confundat.
+
+Odată ce ați instalat BookWyrm [în producție](installing-in-production.html) sau [în dezvoltare](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), puteți rula scriptul din linia de comandă cu `./bw-dev` urmat de o subcomandă pe care doriți să o rulați.
+
+## Scurtături Docker
+
+### bash
+
+Deschide o sesiune interactivă de `bash` în interiorul containerului docker `web`.
+
+### build
+
+Echivalent cu `docker-compose build`.
+
+### dbshell
+
+Deschide un shell interactiv pentru baza de date Postgres. Sper că știți ceea ce faceți.
+
+### runweb args
+
+Rulează o comandă arbitrară (reprezentată deasupra de `args`) în containerul `web`.
+
+Echivalent cu `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Rulează o comandă arbitrară în containerul `web` (reprezentată deasupra de `args`) cu porturile expuse. Aceasta este utilă dacă vreți să rulați teste `pdb` deoarece `runweb` nu expune promptul `pdb`.
+
+Echivalent cu `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Deschide un shell interactiv Django în interiorul containerului docker `web`. O veți folosi dacă vreți să rulați comenzi de shell Django direct.
+
+### up [args]
+
+Pornește sau repornește containerele Dcoker, opțional incluzând orice argument(reprezentat mai sus de `args`). Echivalent cu `docker-compose up --build [args]`
+
+## Gestionarea bazei de date
+
+### initdb
+
+Inițializează o bază de date.
+
+### makemigrations [appname migration number]
+
+_Această comandă nu este disponibilă în ramura de `producție`_.
+
+Rulează comanda Django `makemigrations` în interiorul containerului dvs. Docker. Dacă ați schimbat structura bazei de date în ramura de dezvoltare veți avea nevoie să o rulați pentru ca schimbările dvs. să aibă efect. Opțional, puteți specifica o migrație specifică pe care să o rulați, de ex. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Rulează comanda Django `migrate` în interiorul containerului dvs. Docker. Veți avea nevoie mereu de a o rula după `makemigrations`.
+
+### resetdb
+
+_Această comandă nu este disponibilă în ramura de `producție`_.
+
+Resetează baza de date. **Această comandă va șterge întreaga bază de date BookWyrm**, iar apoi va iniția o bază de date nouă și rula toate migrațiile. Va trebui să ștergeți orice fișier de migrație recent pe care nu vreți să-l rulați _înainte_ de a rula `resetdb`.
+
+## Gestionarea unei instanțe BookWyrm
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Configurați stocare S3 compatibilă
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Dezvoltare și testare
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/ro_RO/content/running_bookwyrm/external-storage.md b/locale/ro_RO/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..7eed7c75
--- /dev/null
+++ b/locale/ro_RO/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+În mod implicit, BookWyrm folosește stocarea locală pentru modelele statice (favicon, avatarul de bază etc.) și media (avatarurile utilizatorilor, coperțile cărților etc.), dar puteți folosi un serviciu de stocare extern pentru a deservi aceste fișiere. BookWyrm folosește `django-storages` pentru a manipula stocarea externă, precum servicii S3 compatibile, Apache Libcloud sau SFTP.
+
+## Servicii S3 compatibile
+
+### Configurare
+
+Creați o „găleată” la serviciul dvs. S3 compatibil împreună cu ID-ul unei chei de acces și o cheie de acces secretă. Acestea pot fi auto-găzduite, precum [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) sau [MinIO](https://min.io/) (GNU AGPL v3.0) sau comerciale ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+Acest ghid a fost testat cu Scaleway Object Storage. Dacă folosiți un alt serviciu, vă rugăm partajați experiența dvs. (în special dacă a trebuit să urmați pași diferiți) completând un tichet pe depozitul [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation).
+
+### Ce vă așteaptă
+
+Dacă începeți o nouă instanță BookWyrm, procesul va fi:
+
+- Configurarea serviciul dvs. extern de stocare
+- Activatul stocării externii pe BookWyrm
+- Porniți instanța BookWyrm
+- Actualizați conectorul instanței
+
+Dacă ați început deja o instanță și imaginile au fost încărcate în stocarea internă, procesul va fi:
+
+- Configurați serviciul dvs. extern de stocare
+- Copiați fișierele media locale pe stocarea externă
+- Activați stocarea externă pe BookWyrm
+- Reporniți instanța BookWyrm
+- Actualizați conectorul instanței
+
+### Setări BookWyrm
+
+Editați fișierul dvs. `.env` decomentând următoarele linii:
+
+- `AWS_ACCESS_KEY_ID`: ID-ul cheie de acces al dvs.
+- `AWS_SECRET_ACCESS_KEY`: cheia de acces secretă a dvs.
+- `AWS_STORAGE_BUCKET_NAME`: numele „găleții” dvs.
+- `AWS_S3_REGION_NAME`: de ex. `"eu-west-1"` pentru AWS, `"fr-par"` pentru Scaleway sau `"nyc3"` pentru Digital Ocean
+
+Dacă serviciul dvs. S3 compatibil este Amazon AWS, ar trebui să fie deja setat. Dacă nu, va trebui să decomentați următoarele linii:
+
+- `AWS_S3_CUSTOM_DOMAIN`: domeniul care va deservi modelele, de ex. `"example-bucket-name.s3.fr-par.scw.cloud"` sau `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: punctul final al API-ului S3 (S3 API endpoint), de ex. `"https://s3.fr-par.scw.cloud"` sau `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copiați fișierele media locale pe stocarea externă
+
+Dacă instanța dvs. BookWyrm rulează deja și fișierele media au fost încărcate (avatare de utilizator, coperți de cărți…), va trebui să migrați fișierele media încărcate pe „găleata” (bucket) dvs.
+
+Această sarcină este realizată de comanda:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Activați stocarea externă pentru BookWyrm
+
+Pentru a activa stocarea externă S3 compatibiliă, va trebui să editați fișierul dvs. `.env` schimbând valoarea proprietății pentru `USE_S3` din `false` în `true`:
+
+```
+USE_S3=true
+```
+
+Dacă stocarea externă a dvs. este deservită prin HTTPS (cel mai des în prezent), veți avea nevoie de asemenea să vă asigurați că `USE_HTTPS` este setat la `true`, în așa fel încât imaginile vor fi încărcate prin HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Modele statice
+
+Apoi, veți avea nevoie să rulați următoarea comandă pentru a copia modelele statice către „găleata” dvs. S3:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### Setări CORS
+
+Odată ce modelele statice au fost colectate, veți avea nevoie să configurați CORS pentru găleata dvs.
+
+Unele servicii precum Digital Ocean oferă o interfață de configurare, vedeți [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+Dacă serviciul dvs. nu oferă o interfață, încă puteți configura CORS în linia de comandă.
+
+Creați un fișier numit `cors.json` cu conținutul următor:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Înlocuiți `MY_DOMAIN_NAME` cu numele domeniului/domeniilor ale instanței dvs.
+
+Apoi rulați următoarea comandă:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+Dacă nu afișează nimic este de bine.
+
+Dacă începeți o instanță nouă BookWyrm, puteți reveni la instrucțiunile de configurare acum. Dacă nu, continuați să citiți.
+
+### Reporniți instanța dvs.
+
+Odată ce migrarea fișierelor media a fost făcută și modelele statice colectate, puteți încărca noua configurare `.env` și reporni instanța cu:
+
+```bash
+./bw-dev up -d
+```
+
+Dacă totul decurge cum trebuie, stocarea dvs. a fost schimbată fără timp de oprire. Dacă unele fonturi lipsesc (și consola JS a navigatorului dvs. vă arată alerte CORS), atunci ceva a mers greșit [here](#cors-settings). În acest caz, ar fi bine să verificați antetele unei cereri HTTP cu un fișier al „găleții” dvs:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Înlocuiți `MY_DOMAIN_NAME` cu numele domeniului instanței dvs., `BUCKET_URL` cu URL-ul pentru găleata dvs. Puteți înlocui calea fișierului co orice altă cale validă pentru găleata dvs.
+
+Dacă vedeți vrun mesaj, în special un mesaj începând cu `<Error><Code>CORSForbidden</Code>`, nu a funcționat. Dacă nu vedeți niciun mesaj, atunci a mers.
+
+Pentru o instanță activă, s-ar putea să fie câteva fișiere care au fost create local în timpul migrării fișierelor pe stocarea externă. Reporniți aplicația pentru a folosi stocarea externă. Pentru a vă asigura că orice fișier rămas este încărcat pe stocarea externă după schimbare, puteți folosi comanda următoare, care va încărca numai fișierele care nu sunt prezente pe stocarea externă:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Actualizați conectorul instanței
+
+*Notă: puteți sări acest pas dacă rulați o versiune actualizată de BookWyrm. În septembrie 2021, „conectorul de raft” a fost înlăturat în [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+Pentru ca URL-ul corect să fie utilizat la afișarea rezultatelor de căutare pentru cărțile locale, va trebui să modificați valoarea pentru URL de bază a imaginilor de copertă.
+
+Datele conectorului pot fi accesate cu interfața de admin Django, situată la URL-ul `http://MY_DOMAIN_NAME/admin`. Conectorul pentru propria voastră instanță este prima intrare în baza de date, deci puteți să-l accesați prin acest URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+Câmpul _Covers url_ este definit în mod implicat ca `https://MY_DOMAIN_NAME/images`. Trebuie să-l schimbați cu `https://S3_STORAGE_URL/images`. Apoi, apăsați butonul _Save_. Voilà!
+
+Va trebui să actualizați valoarea pentru _Covers url_ de fiecare dată când schimbați URL-ul pentru stocarea dvs.
diff --git a/locale/ro_RO/content/running_bookwyrm/install-prod-dockerless.md b/locale/ro_RO/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/ro_RO/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/ro_RO/content/running_bookwyrm/install-prod.md b/locale/ro_RO/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..f0cb574c
--- /dev/null
+++ b/locale/ro_RO/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+Acest proiect este încă tânăr și nu foarte stabil în acest moment, așa că vă rugăm să continuați cu precauție atunci când rulați în producție.
+
+## Configurarea server-ului
+- Obțineți un nume de domeniu și configurați DNS-ul pentru server-ul dvs. Veți avea nevoie să indicați numele server-ului furnizorului dvs. DNS pentru server-ul unde veți găzdui BookWyrm. Iată instrucțiunile pentru [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Configurați server-ul dvs. cu paravanele de protecție (firewalls) adecvate pentru rularea unei aplicații web (acest set de instrucțiuni a fost testat cu Ubuntu 20.04). Iată instrucțiunile pentru [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Configurați un serviciu email (precum [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) și setările adecvate SMTP/DNS. Folosiți documentația serviciului pentru configurarea DNS dvs.
+- [Instalați Docker și docker-compose](https://docs.docker.com/compose/install/)
+
+## Instalați și configurați BookWyrm
+
+Ramura de `producție` BookWyrm conține un număr de unelte care nu sunt prezente pe ramura `main` și care sunt potrivite pentru rularea în producție, precum `docker-compose` care schimbă comenzile de bază sau configurarea containerelor și schimbări individuale pentru a activa lucruri precum SSL sau copii de rezervă regulate (regular backups).
+
+Instrucțiuni pentru rularea BookWyrm în producție:
+
+- Obțineți codul aplicației: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Comutați la ramura de `production`: `git checkout production`
+- Creați un fișier cu variabilele de mediu, `cp .env.example .env` și actualizați următoarele:
+    - `SECRET_KEY` | Un șir de caractere secret, greu de ghicit
+    - `DOMAIN` | Domeniul dvs. web
+    - `EMAIL` | Adresa de email utilizată pentru verificarea de domeniu certbot
+    - `POSTGRES_PASSWORD` | Setați o parolă sigură pentru baza de date
+    - `REDIS_ACTIVITY_PASSWORD` | Setați o parolă sigură pentru subsistemul Redis Activity
+    - `REDIS_BROKER_PASSWORD` | Setați o parolă sigură pentru „Redis queue broker subsystem”
+    - `FLOWER_USER` | Setați propriul nume de utilizator pentru accesarea „Flower queue monitor”
+    - `FLOWER_PASSWORD` | Setați propria parolă sigură pentru accesul la „Flower queue monitor”
+    - `EMAIL_HOST_USER` | Adresa „de la” pe care aplicația dvs. o va folosi pentru trimiterea email-urilor
+    - `EMAIL_HOST_PASSWORD` | Parola furnizată de serviciul dvs. email
+- Configurare nginx
+    - Faceți o copie a șablonului de configurare de producție și setați-l pentru a fi utilizat de nginx `cp nginx/production nginx/default.conf`
+    - Actualizați `nginx/default.conf`:
+        - Înlocuiți `your-domain.com` cu numele domeniului dvs. peste tot în fișier (inclusiv liniile care sunt momentan comentate)
+        - Dacă nu folosiți subdomeniul `www`, înlăturați versiunea www.your-domain.com a domeniului din `server_name` în primul bloc al server-ului în `nginx/default.conf` și înlăturați opțiunea `-d www.${DOMAIN}` de la finalul comenzii `certbot` din `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Inițializați baza de date rulând `./bw-dev migrate`
+- Rulați aplicația cu `docker-compose up --build` (acest lucru ar trebui să configureze de asemenea un Certbot ssl cert pentru domeniul dvs.) și asigurați-vă că toate imaginile au fost compilate cu succes
+    - Dacă rulați alte servicii pe calculatorul gazdă al dvs., s-ar putea să vă confruntați cu erori când serviciile eșuează încercând să se lege la un port. Vedeți [ghidul de depanare](#port_conflicts) pentru sfaturi despre rezolvarea acestor probleme.
+- Când Docker s-a compilat cu succes, opriți procesul cu `CTRL-C`
+- Configurați redirecționarea HTTPS
+    - În `docker-compose.yml`, comentați comanda certbot activă, care instalează certificatul, și decomentați linia de mai jos, care configurează automat reînnoirea.
+    - În `nginx/default.conf`, decomentați de la linia 18 până la 50 pentru a activa redirecționarea HTTPS. Ar trebui să aveți două blocuri `server` activate
+- Configurați o sarcină (job) `cron` pentru a păstra certificatele dvs. actualizate (certificatele Lets Encrypt expiră după 90 de zile)
+    - Tastați `crontab -e ` pentru a edita fișierul dvs. cron pe mașina gazdă
+    - adăugați o linie pentru a încerca reînnoirea o dată pe zi: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- Dacă doriți să folosiți un mediu de stocare externă pentru modelele statice și fișierele media (precum un serviciu S3 compatibil), [urmați instrucțiunile](/external-storage.html) până când vă spune să reveniți aici
+- Inițializați aplicația cu `./bw-dev setup` și copiați codul adminului pentru a îl folosi când vă creați contul dvs. de admin.
+    - Afișajul `./bw-dev setup` ar trebui să se termine cu codul dvs. de admin. Puteți obține codul dvs. oricând rulând `./bw-dev admin_code` din linia de comandă. Iată un exemplu de afișaj:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Rulați docker-compose în fundal cu: `docker-compose up -d`
+- Aplicația ar trebui să ruleze la domeniul dvs. Când încărcați domeniul, ar trebui să obțineți o pagină de configurare ce confirmă setările instanței dvs. și un formular pentru crearea unui cont de admin. Folosiți codul dvs. de admin pentru înregistrare.
+
+Felicitări! Ați reușit! Configurați instanța dvs. oricum doriți.
+
+
+## Copii de rezervă
+
+Serviciul db al BookWyrm creează o copie de rezervă în dosarul său `/backups` în fiecare zi la miezul nopții UTC. Copiile de rezervă sunt numite `backup__%Y-%m-%d.sql`.
+
+Serviciul db are un script opțional ce șterge periodic dosarul cu copii de rezervă în așa fel încât toate copiile recente sunt păstrate, dar în cazul celor mai vechi, doar cele săptămânale sau lunare sunt păstrate. Pentru a activa acest script:
+
+- Decomentați linia finală în `postgres-docker/cronfile`
+- recompilați instanța dvs. `docker-compose up --build`
+
+Puteți copia copii de rezervă din volumul cu copii de rezervă către mașina dvs. gazdă cu `docker cp`:
+
+- Rulați `docker-compose ps` pentru a confirma numele întreg al serviciul db (probabil `bookwyrm_db_1`).
+- Rulați `docker cp <container_name>:/backups <host machine path>`
+
+## Conflicte la porturi
+
+BookWyrm are multiple servicii care rulează pe porturile lor implicite. Asta înseamnă că, depinzând de ce altceva rulați pe mașina dvs. gazdă, s-ar putea să vă confruntați cu erori la compilarea sau rularea BookWyrm când conectarea la aceste porturi eșuează.
+
+Dacă se întâmplă acest lucru, veți avea nevoie să schimbați fișierul dvs. de configurare pentru a rula serviciile pe porturi diferite. Acest lucru poate necesita una sau multe schimbări ale următoarelor fișiere:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (Dvs. creați acest fișier în timpul configurării)
+
+Dacă rulați deja un server web pe mașina dvs., veți avea nevoie să configurați un reverse-proxy.
+
+## Conectați-vă
+
+Deoarece BookWyrm este un proiect tânăr, încă lucrăm la un program de lansare stabil, existând o mulțime de buguri și schimbări care strică totul. Avem o echipă GitHub care poate fi notificată când este ceva important de știut despre o actualizare, echipă căreia vă puteți alătura partajând numele dvs. GitHub. Există câteva moduri de a lua legătura:
+
+ - Deschideți un tichet sau o cerere de extragere pentru a adăuga instanța dvs. la [lista oficială](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Contactați proiectul pe [Mastodon](https://tech.lgbt/@bookwyrm) sau prin [email-ul maintainer-ului](mailto:mousereeve@riseup.net) direct cu numele dvs. GitHub
+ - Alăturați-vă salonului de discuție (chat room) [Matrix](https://matrix.to/#/#bookwyrm:matrix.org)
diff --git a/locale/ro_RO/content/running_bookwyrm/moderation.md b/locale/ro_RO/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..56a8b9e0
--- /dev/null
+++ b/locale/ro_RO/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocare
+Utilizatorii au opțiunea de a bloca alți utilizatori pe cont propriu fără ca un moderator să intervină. Din punctul de vedere al adminului de „Servere federate”, administratorii pot vedea cât de mulți utilizatori de pe o instanță au fost blocați de utilizatori locali.
+
+## Raporturi
+Utilizatorii pot raporta stări sau utilizatori din meniul „mai multe opțiuni” din subsolul postărilor și din butoanele de urmărire/dezabonare pentru utilizatori. Când un raport este făcut, toți utilizatorii cu permisiunea de admin vor primi o notificare.
+
+Când un raport este făcut, există câteva opțiuni cu privire la modul în care moderatorul poate răspunde.
+- Să trimită un mesaj direct utilizatorului raportat.
+- Să șteargă starea raportată.
+- Să dezactiveze utilizatorul. Face ca utilizatorii locali să nu se mai poată autentifica și contul lor nu va fi afișat în aplicație. Pentru utilizatorii de la distanță, serverul va respinge orice activitate venind de la ei și nu vor fi afișați în rezultatele căutărilor.
+
+## Moderare la nivel de instanță
+Moderatorii pot bloca instanțe întregi. Acest lucru va împiedica orice activitate venind de la instanța respectivă și dezactiva local toate conturile sale.
+
+Dacă instanța este deblocată, toți utilizatorii dezactivați de blocare vor fi reactivați.
+
+Moderatorii pot de asemenea încărca liste de blocare pentru a bloca servere în masă.
diff --git a/locale/ro_RO/content/running_bookwyrm/monitoring-queue.md b/locale/ro_RO/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/ro_RO/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/ro_RO/content/running_bookwyrm/optional_features.md b/locale/ro_RO/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..e4e3675c
--- /dev/null
+++ b/locale/ro_RO/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Unele funcționalități BookWyrm trebuie să fie activate pentru a funcționa.
+
+## Previzualizarea generării de imagine
+
+În mod implicit, BookWyrm folosește logo-ul instanței (sau logo-ul de bază) ca imagine de previzualizare OpenGraph. Ca alternativă, puteți activa generarea de imagini de previzualizare pentru cărți, utilizatori și site-uri web.
+
+Imaginile de previzualizare vor fi dimensionate pentru imagini OpenGraph mari (folosite de Twitter sub denumirea de `summay_large_image`). Depinzând de tipul imaginii, conținutul va fi:
+
+- imaginea implicită a instanței va afișa logo-ul mare, împreună cu numele instanței și URL-ul său
+- imaginea de utilizator va afișa avatarul său, numele său afișat, numele de utilizator (sub forma numeutilizator@instanță)
+- imaginea de carte va afișa coperta sa, titlul, subtitlul (dacă este cazul), autorul și ratingul (dacă este cazul)
+
+Aceste imagini vor fi actualizate în diferite puncte:
+
+- imaginea instanței: când numele instanței sau logo-ul mare au fost schimbate
+- imaginea de utilizator: când numele afișat sau avatarul au fost schimbate
+- imaginea de carte: când titlul/titlurile, autorul/autorii sau coperta au fost schimbați sau o nouă recenzie este adăugată
+
+### Activați imaginile de previzualizare
+
+Pentru a activa această funcționalitate cu setările implicite, trebuie să decomentați (să înlăturați `#` din fața) liniei `ENABLE_PREVIEW_IMAGES=true` în fișierul dvs. `.env`. Toate evenimentele noi de actualizare menționate anterior vor cauza generarea imaginii corespunzătoare.
+
+Exemple pentru aceste imaginii pot fi vizualizate pe [descrierea cererii de extragere a funcționalității](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generarea imaginilor de previzualizare
+
+Dacă activați această setare după ce instanța dvs. a fost pornită, s-ar putea ca unele imagini să nu fi fost generate. O comandă a fost adăugată pentru a automatiza generarea de imagini. Pentru a preveni consumarea excesivă de resurse prin generarea **MULTOR** imagini, trebuie să transmiteți argumentul `--all` (sau `-a`) pentru a începe generarea imaginilor de previzualizare pentru toți utilizatorii și toate cărțile. Fără acest argument, numai previzualizarea site-ului va fi generată.
+
+Imaginile de previzualizare pentru utilizatori și cărți vor fi generate asincron: sarcina va fi trimisă către Flower. S-ar putea să fie nevoie de ceva timp ca toate cărțile și toți utilizatorii să aibă o imagine de previzualizare funcțională. Dacă aveți o carte bună 📖, un pisoi 🐱 sau o prăjitură 🍰, acum este momentul perfect pentru a le acorda ceva atenție 💖.
+
+### Setări opționale
+
+Deci vreți să vă personalizați imaginile de previzualizare? Iată câteva opțiuni:
+
+- `PREVIEW_BG_COLOR` va seta culoarea de fundal a imaginii de previzualizare. Puteți furniza o valoare de culoare, precum `#b00cc0` sau următoarele valori: `use_dominant_color_light` sau `use_dominant_color_dark`. Acestea vor extrage culoarea dominantă a coperții cărții și o vor folosi într-o temă deschisă, respectiv întunecată.
+- `PREVIEW_TEXT_COLOR` va seta culoarea pentru text. Depinzând de alegerea dumneavoastră pentru culoarea de fundal, trebuie să găsiți o valoarea care are suficient contrast pentru ca imaginea să fie lizibilă. Se recomandă un raport de contrast 1:4,5.
+- `PREVIEW_IMG_WIDTH` și `PREVIEW_IMG_HEIGHT` vor seta dimensiunile imaginii. În prezent, sistemul va funcționa cel mai bine cu imagini având o orientare peisaj (orizontală).
+- `PREVIEW_DEFAULT_COVER_COLOR` va seta culoarea pentru cărțile fără copertă.
+
+Toate variabilele de culoare acceptă valori care pot fi recunoscute ca atare de modulul `ImageColor` a lui Pillow: [Aflați mai multe despre numele de culori Pillow](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/ro_RO/content/running_bookwyrm/reverse-proxy.md b/locale/ro_RO/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..24e3225d
--- /dev/null
+++ b/locale/ro_RO/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Rularea BookWyrm în spatele unui Reverse-Proxy
+Dacă rulați un alt server web pe mașina dvs., trebuie să-l configurați să transmită cererile web către BookWyrm.
+
+Configurația BookWyrm de bază are deja un server nginx care redirecționează cererile către aplicația Django care se ocupă de SSL și deservește în mod direct fișierele statice. Fișierele statice sunt stocate într-un volum Docker la care au acces mai multe servicii BookWrym, deci nu este recomandat să înlăturați complet acest server.
+
+Pentru a rula BookWyrm în spatele unui reverse-proxy, faceți următoarele schimbări:
+
+- În `nginx/default.conf`:
+    - Comentați cele două servere implicite
+    - Decomentați server-ul etichetat „Reverse-Proxy server”
+    - Înlocuiți `your-domain.com` cu numele domeniului dvs.
+- În `docker-compose.yml`:
+    - În `services` -> `nginx` -> `ports`, comentați porturile implicite și adăugați `- 8001:8001`
+    - În `services` -> `nginx` -> `volumes`, comentați cele două volume care încep `./certbot/`
+    - În `services`, comentați serviciul `certbot`
+
+În acest moment, puteți urmări instrucțiunile [setup](#server-setup) listate. Odată ce Docker rulează, puteți accesa instanța dvs. de BookWyrm la `http://localhost:8001` (**NOTĂ:** serverul dvs. nu este accesibil prin `https`).
+
+Pașii pentru configurarea unui reverse-proxy sunt independenți de server.
+
+#### Nginx
+
+Înainte de a putea configura nginx, veți avea nevoie să localizați dosarul dvs. de configurare nginx, care este dependent de platforma dvs. și de cum ați instalat nginx. Vedeți [ghidul nginx](http://nginx.org/en/docs/beginners_guide.html) pentru detalii.
+
+Pentru a configura serverul dvs.:
+
+- În fișierul dvs. `nginx.conf`, asigurați-vă că `include servers/*;` nu este comentat.
+- În dosarul dvs. nginx `servers`, creați un nou fișier numit după domeniul dvs. conținând următoarele informații:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+Pentru a configura un bloc SSL:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- rulați `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- reporniți nginx
+
+Dacă totul a funcționat corect, instanța dvs. BookWyrm ar trebui să fie acum accesibilă din exterior.
+
+*Notă: `proxy_set_header Host $host;` este esențial; dacă nu-l includeți, mesajele primite de la serverele federate vor fi respinse.*
+
+*Notă: locația certificatelor SSL poate varia în funcție de SO (sistemul de operare) al serverului dvs.*
+
diff --git a/locale/ro_RO/content/running_bookwyrm/updating.md b/locale/ro_RO/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..2d0c48d2
--- /dev/null
+++ b/locale/ro_RO/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+Când sunt schimbări disponibile în ramura de producție, puteți să le instalați și rula utilizând comanda `./bw-dev update` pe instanța dvs. Aceasta face mai multe de lucruri:
+
+- `git pull` obține codul actualizat de pe depozitul git. Dacă sunt conflicte, s-ar putea să aveți nevoie să rulați `git pull` separat și să rezolvați conflictele înainte de a reîncerca scriptul `./bw-dev update`.
+- `docker-compose build` recompilează imaginile, ceea ce asigură că pachetele corecte au fost instalate. Acest pas durează mult timp și este necesar numai dacă dependențele (inclusiv pachetele pip `requirements.txt`) s-au schimbat, deci puteți să-l comentați dacă vreți o cale de actualizare mai rapidă și nu vă deranjează să-l decomentați când este necesar.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Recompilați fluxurile de activitate
+
+Fluxurile pentru fiecare utilizator sunt stocate în Redis. Pentru a repopula un flux, folosiți comanda de gestionare:
+
+``` { .sh }
+./bw-dev populate_streams
+# Sau folosiți direct docker-compose
+docker-compose run --rm web python manage.py populate_streams
+```
+
+Dacă ceva a mers groaznic, datele fluxului pot fi șterse.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/ro_RO/content/using_bookwyrm/adding-books.md b/locale/ro_RO/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..b0ab5da1
--- /dev/null
+++ b/locale/ro_RO/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+Există câteva modalități diferite de a adăuga cărți instanței dvs. BookWyrm! Când nu găsiți o carte pe care o căutați, încercați aceste opțiuni în ordine: este mai bine să importați o carte decât să creați una de la zero.
+
+## Încărcarea de cărți din alte cataloage
+
+Dacă cartea pe care o căutați nu este disponibilă pe instanța dvs., există câteva moduri diferite de a o adăuga. Cel mai bun mod este de a o importa dintr-o sursă exterioară -- instanța dvs. poate încărca cărți din alte instanțe BookWyrm, precum și din [OpenLibrary](http://openlibrary.org/) și [Inventaire](http://inventaire.io/). Dacă nu există rezultate pentru interogarea dvs., aceste surse vor fi automat întrebate și vor arăta un buton cu „**Importați carte**”. Dacă există rezultate locale care nu sunt ceea ce căutați, puteți face clic pe legătura „**Încărcați rezultate din alte cataloage**” pentru a încărca mai multe rezultate.
+
+
+## Adăugați o nouă ediție
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). În partea de jos a listei de ediții este un buton „**Adăugați o altă ediție**”.
+
+## Adăugați o carte complet nouă
+
+Odată ce ați încercat să găsiți cartea dvs., să o importați dintr-un alt catalog și să găsiți alte ediții ale cărții, puteți adăuga o carte nouă manual. The link to manually add a book is at the bottom of the search page when external catalogs are shown. Puteți de asemenea naviga direct la `/create-book` de pe instanța dvs..
diff --git a/locale/ro_RO/content/using_bookwyrm/posting-statuses.md b/locale/ro_RO/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..d64f96bf
--- /dev/null
+++ b/locale/ro_RO/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Postatul pe BookWyrm începe cu o carte. Utilizatorii pot comenta o carte citită recent sau în curs de citire din secțiunea „Cărțile dvs.” sau de pe pagina principală a unei cărți. De acolo, utilizatorii pot răspunde sau începe o conversație. Postările BookWyrm pot include text formatat precum bold, italic sau legături folosind [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+Dacă sunteți familiar cu [postatul pe Mastodon](https://docs.joinmastodon.org/user/posting/), veți vedea că stările BookWyrm au setări de vizibilitate similare, avertismente de conținut și mențiuni. Totuși, sondajele, emoticoanele personalizate și atașamentele nu sunt încă implementate.
+
+## Tipuri de stări
+
+### Comentariu de utilizator
+
+Acestea sunt trei tipuri de postări pe care utilizatorii pot să le creeze direct ca răspuns cărților: recenzii, comentarii și citate. Comentariile corespund aspectelor generale ale unei cărți, citatele unor pasaje specifice și recenziile tratează cărțile în general. Utilizatorii pot de asemenea răspunde stărilor.
+
+| Componentă          | Recenzie | Comentariu | Citat | Răspuns |
+| ------------------- | -------- | ---------- | ----- | ------- |
+| Câmp text           | ✔        | ✔          | ✔     | ✔       |
+| Alertă de divulgare | ✔        | ✔          | ✔     | ✔       |
+| Numărul paginii     |          | ✔          | ✔     |         |
+| Citat               |          |            | ✔     |         |
+| Evaluare            | ✔        |            |       |         |
+| Câmp titlu          | ✔        |            |       |         |
+
+
+### Actualizări a stărilor de lectură
+
+Stările sunt generate când un utilizator indică ceea ce vrea să citească, a început să citească sau a terminat de citit o carte.
+
+## Text
+Textul poate să includă:
+
+- Mențiuni (@utilizator)
+- URL-uri (`http(s)://` nu este afișat)
+- [Formatare Markdown](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italic
+  - citate bloc
+  - liste neordonate
+  - legături
+
diff --git a/locale/ru_RU/LC_MESSAGES/messages.po b/locale/ru_RU/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..7ed62d76
--- /dev/null
+++ b/locale/ru_RU/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Russian\n"
+"Language: ru_RU\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=4; plural=((n%10==1 && n%100!=11) ? 0 : ((n%10 >= 2 && n%10 <=4 && (n%100 < 12 || n%100 > 14)) ? 1 : ((n%10 == 0 || (n%10 >= 5 && n%10 <=9)) || (n%100 >= 11 && n%100 <= 14)) ? 2 : 3));\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: ru\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/ru_RU/content/codebase/activitypub.md b/locale/ru_RU/content/codebase/activitypub.md
new file mode 100644
index 00000000..c011c583
--- /dev/null
+++ b/locale/ru_RU/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Название: Статус сообщения Дата: 2021-04-30 Заказ: 1
+- - -
+
+BookWyrm использует протокол [ActivityPub](http://activitypub.rocks/) для отправки и получения активности пользователей между другими экземплярами BookWyrm и другими службами, реализующими ActivityPub, такими как [Mastodon](https://joinmastodon.org/). Для обработки книжных данных BookWyrm имеет несколько типов расширенных действий, которые не являются частью стандарта, но разборчивы к другим экземплярам BookWyrm.
+
+## Действия и объекты
+
+### Пользователи и отношения
+Взаимодействие между пользователями соответствует стандартной спецификации ActivityPub.
+
+- `Follow (Подпишитесь на)`: запрос на получение статусов от пользователя и просмотрите их статусы, в которых есть только подписчики
+- `Accept (Принять)`: одобряет `Следовать` и фиксирует взаимоотношения
+- `Reject (Отклонить)`: запрещает `Follow (подписку)`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Действия
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+Книги и списки пользователей представлены [`Заказной Коллекцией`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Потому что BookWyrm использует пользовательские типы объектов (`Обзор`, `Комментарий`, `Цитаты`) которые не поддерживаются программой ActivityPub, статусы преобразуются в стандартные типы при отправке или просмотре службами не BookWyrm. `Отзыв`с конвертируются в `Статьи`с, и `Комментарий`s и `цитата`s преобразуются в `Примечание`s, с ссылкой на книгу и прикрепленное изображение обложки.
diff --git a/locale/ru_RU/content/codebase/permissions.md b/locale/ru_RU/content/codebase/permissions.md
new file mode 100644
index 00000000..40d8518f
--- /dev/null
+++ b/locale/ru_RU/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Название: Разрешения Дата: 2021-04-18 Заказ: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/ru_RU/content/contributing/contributing.md b/locale/ru_RU/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/ru_RU/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/ru_RU/content/contributing/debug_toolbar.md b/locale/ru_RU/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/ru_RU/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/ru_RU/content/contributing/install-dev.md b/locale/ru_RU/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/ru_RU/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/ru_RU/content/contributing/style_guide.md b/locale/ru_RU/content/contributing/style_guide.md
new file mode 100644
index 00000000..0c2ca701
--- /dev/null
+++ b/locale/ru_RU/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Ваш запрос на слияние также будет проверен [curlylint](https://www.curlylint.org) для шаблонов Django.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/ru_RU/content/contributing/translation.md b/locale/ru_RU/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/ru_RU/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/ru_RU/content/index.md b/locale/ru_RU/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/ru_RU/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/ru_RU/content/pages/index.md b/locale/ru_RU/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/ru_RU/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/ru_RU/content/running_bookwyrm/cli.md b/locale/ru_RU/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/ru_RU/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/ru_RU/content/running_bookwyrm/external-storage.md b/locale/ru_RU/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/ru_RU/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/ru_RU/content/running_bookwyrm/install-prod-dockerless.md b/locale/ru_RU/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/ru_RU/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/ru_RU/content/running_bookwyrm/install-prod.md b/locale/ru_RU/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..a6ad58c2
--- /dev/null
+++ b/locale/ru_RU/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Инициализировать базу данных, запустив `./bw-dev мигрировать`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/ru_RU/content/running_bookwyrm/moderation.md b/locale/ru_RU/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/ru_RU/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/ru_RU/content/running_bookwyrm/monitoring-queue.md b/locale/ru_RU/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/ru_RU/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/ru_RU/content/running_bookwyrm/optional_features.md b/locale/ru_RU/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/ru_RU/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/ru_RU/content/running_bookwyrm/reverse-proxy.md b/locale/ru_RU/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/ru_RU/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/ru_RU/content/running_bookwyrm/updating.md b/locale/ru_RU/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/ru_RU/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/ru_RU/content/using_bookwyrm/adding-books.md b/locale/ru_RU/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..8270feff
--- /dev/null
+++ b/locale/ru_RU/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+Если вы нашли книгу, которую вы хотите, но не правильный вариант, вы можете добавить еще одну редакцию в работу из списка изданий. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/ru_RU/content/using_bookwyrm/posting-statuses.md b/locale/ru_RU/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..49fe8a39
--- /dev/null
+++ b/locale/ru_RU/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Название: Статус сообщения Дата: 2022-04-30 Заказ: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/sl_SI/LC_MESSAGES/messages.po b/locale/sl_SI/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..158efbe5
--- /dev/null
+++ b/locale/sl_SI/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-12-13 06:56\n"
+"Last-Translator: \n"
+"Language-Team: Slovenian\n"
+"Language: sl_SI\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=4; plural=(n%100==1 ? 1 : n%100==2 ? 2 : n%100==3 || n%100==4 ? 3 : 0);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: sl\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "Pridruži se"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "Podpora"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr "Licenca"
+
diff --git a/locale/sl_SI/content/codebase/activitypub.md b/locale/sl_SI/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/sl_SI/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/sl_SI/content/codebase/permissions.md b/locale/sl_SI/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/sl_SI/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/sl_SI/content/contributing/contributing.md b/locale/sl_SI/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/sl_SI/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/sl_SI/content/contributing/debug_toolbar.md b/locale/sl_SI/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/sl_SI/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/sl_SI/content/contributing/install-dev.md b/locale/sl_SI/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/sl_SI/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/sl_SI/content/contributing/style_guide.md b/locale/sl_SI/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/sl_SI/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/sl_SI/content/contributing/translation.md b/locale/sl_SI/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/sl_SI/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/sl_SI/content/index.md b/locale/sl_SI/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/sl_SI/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/sl_SI/content/running_bookwyrm/cli.md b/locale/sl_SI/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/sl_SI/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/sl_SI/content/running_bookwyrm/external-storage.md b/locale/sl_SI/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/sl_SI/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/sl_SI/content/running_bookwyrm/install-prod-dockerless.md b/locale/sl_SI/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/sl_SI/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/sl_SI/content/running_bookwyrm/install-prod.md b/locale/sl_SI/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/sl_SI/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/sl_SI/content/running_bookwyrm/moderation.md b/locale/sl_SI/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/sl_SI/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/sl_SI/content/running_bookwyrm/monitoring-queue.md b/locale/sl_SI/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/sl_SI/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/sl_SI/content/running_bookwyrm/optional_features.md b/locale/sl_SI/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/sl_SI/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/sl_SI/content/running_bookwyrm/reverse-proxy.md b/locale/sl_SI/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/sl_SI/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/sl_SI/content/running_bookwyrm/updating.md b/locale/sl_SI/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/sl_SI/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/sl_SI/content/using_bookwyrm/adding-books.md b/locale/sl_SI/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/sl_SI/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/sl_SI/content/using_bookwyrm/posting-statuses.md b/locale/sl_SI/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/sl_SI/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/sr_SP/LC_MESSAGES/messages.po b/locale/sr_SP/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..c1772141
--- /dev/null
+++ b/locale/sr_SP/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Serbian (Cyrillic)\n"
+"Language: sr_SP\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: sr\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/sr_SP/content/codebase/activitypub.md b/locale/sr_SP/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/sr_SP/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/sr_SP/content/codebase/permissions.md b/locale/sr_SP/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/sr_SP/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/sr_SP/content/contributing/contributing.md b/locale/sr_SP/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/sr_SP/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/sr_SP/content/contributing/debug_toolbar.md b/locale/sr_SP/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/sr_SP/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/sr_SP/content/contributing/install-dev.md b/locale/sr_SP/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/sr_SP/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/sr_SP/content/contributing/style_guide.md b/locale/sr_SP/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/sr_SP/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/sr_SP/content/contributing/translation.md b/locale/sr_SP/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/sr_SP/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/sr_SP/content/index.md b/locale/sr_SP/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/sr_SP/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/sr_SP/content/pages/index.md b/locale/sr_SP/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/sr_SP/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/sr_SP/content/running_bookwyrm/cli.md b/locale/sr_SP/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/sr_SP/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/sr_SP/content/running_bookwyrm/external-storage.md b/locale/sr_SP/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/sr_SP/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/sr_SP/content/running_bookwyrm/install-prod-dockerless.md b/locale/sr_SP/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/sr_SP/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/sr_SP/content/running_bookwyrm/install-prod.md b/locale/sr_SP/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/sr_SP/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/sr_SP/content/running_bookwyrm/moderation.md b/locale/sr_SP/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/sr_SP/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/sr_SP/content/running_bookwyrm/monitoring-queue.md b/locale/sr_SP/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/sr_SP/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/sr_SP/content/running_bookwyrm/optional_features.md b/locale/sr_SP/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/sr_SP/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/sr_SP/content/running_bookwyrm/reverse-proxy.md b/locale/sr_SP/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/sr_SP/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/sr_SP/content/running_bookwyrm/updating.md b/locale/sr_SP/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/sr_SP/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/sr_SP/content/using_bookwyrm/adding-books.md b/locale/sr_SP/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/sr_SP/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/sr_SP/content/using_bookwyrm/posting-statuses.md b/locale/sr_SP/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/sr_SP/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/sv_SE/LC_MESSAGES/messages.po b/locale/sv_SE/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..75eaf9f4
--- /dev/null
+++ b/locale/sv_SE/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2023-01-03 12:05\n"
+"Last-Translator: \n"
+"Language-Team: Swedish\n"
+"Language: sv_SE\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: sv-SE\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr "BookWyrm-dokumentation"
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr "Din guide till att använda och bidra till BookWyrm"
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr "Hur man använder och bidrar"
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr "BookWyrm: Social läsning och recensering"
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "Gå med"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr "Engagera dig"
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "Hjälp"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr "Kod"
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr "Dokumentation"
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr "<strong>BookWyrm</strong> är kollaborativ, företagsfientlig programvara som underhålls av <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr "Stöd BookWyrm på <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr "Engagera dig"
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr "BookWyrm på GitHub"
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr "Bidra till den här sidan"
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr "Läs mer"
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr "Kontakta ansvarig"
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr "Licens"
+
diff --git a/locale/sv_SE/content/codebase/activitypub.md b/locale/sv_SE/content/codebase/activitypub.md
new file mode 100644
index 00000000..9bc17f97
--- /dev/null
+++ b/locale/sv_SE/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Aktiviteter och objekt
+
+### Användare och relationer
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statusar
+#### Objekttyper
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Aktiviteter
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Ta bort`: Tar bort en status
+- `Gilla`: skapar en favorit på statusen
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Samlingar
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objekt
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Aktiviteter
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/sv_SE/content/codebase/permissions.md b/locale/sv_SE/content/codebase/permissions.md
new file mode 100644
index 00000000..3856fd55
--- /dev/null
+++ b/locale/sv_SE/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Behörigheter och grupper
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| inaktivera användare   | ✔️    | ✔️        | -      | -    |
+| ta bort inlägg         | ✔️    | ✔️        | -      | -    |
+| redigera böcker        | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/sv_SE/content/contributing/contributing.md b/locale/sv_SE/content/contributing/contributing.md
new file mode 100644
index 00000000..81d97e67
--- /dev/null
+++ b/locale/sv_SE/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Översättning
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Finansiellt stöd
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/sv_SE/content/contributing/debug_toolbar.md b/locale/sv_SE/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/sv_SE/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/sv_SE/content/contributing/install-dev.md b/locale/sv_SE/content/contributing/install-dev.md
new file mode 100644
index 00000000..c149ea50
--- /dev/null
+++ b/locale/sv_SE/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Starta applikationen. Kör på kommandoraden:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/sv_SE/content/contributing/style_guide.md b/locale/sv_SE/content/contributing/style_guide.md
new file mode 100644
index 00000000..b66304dc
--- /dev/null
+++ b/locale/sv_SE/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Mallar (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Formulär
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Knappar och länkar
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/sv_SE/content/contributing/translation.md b/locale/sv_SE/content/contributing/translation.md
new file mode 100644
index 00000000..0af3f593
--- /dev/null
+++ b/locale/sv_SE/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Könsneutralt språk
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/sv_SE/content/index.md b/locale/sv_SE/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/sv_SE/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/sv_SE/content/pages/index.md b/locale/sv_SE/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/sv_SE/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/sv_SE/content/running_bookwyrm/cli.md b/locale/sv_SE/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..5b731719
--- /dev/null
+++ b/locale/sv_SE/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Kompilerar alla BookWyrm-teman, `*.scss`-filer listade i `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/sv_SE/content/running_bookwyrm/external-storage.md b/locale/sv_SE/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/sv_SE/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/sv_SE/content/running_bookwyrm/install-prod-dockerless.md b/locale/sv_SE/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/sv_SE/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/sv_SE/content/running_bookwyrm/install-prod.md b/locale/sv_SE/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/sv_SE/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/sv_SE/content/running_bookwyrm/moderation.md b/locale/sv_SE/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/sv_SE/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/sv_SE/content/running_bookwyrm/monitoring-queue.md b/locale/sv_SE/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/sv_SE/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/sv_SE/content/running_bookwyrm/optional_features.md b/locale/sv_SE/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/sv_SE/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/sv_SE/content/running_bookwyrm/reverse-proxy.md b/locale/sv_SE/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/sv_SE/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/sv_SE/content/running_bookwyrm/updating.md b/locale/sv_SE/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/sv_SE/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/sv_SE/content/using_bookwyrm/adding-books.md b/locale/sv_SE/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/sv_SE/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/sv_SE/content/using_bookwyrm/posting-statuses.md b/locale/sv_SE/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/sv_SE/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/tr_TR/LC_MESSAGES/messages.po b/locale/tr_TR/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..525b36c2
--- /dev/null
+++ b/locale/tr_TR/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Turkish\n"
+"Language: tr_TR\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: tr\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/tr_TR/content/codebase/activitypub.md b/locale/tr_TR/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/tr_TR/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/tr_TR/content/codebase/permissions.md b/locale/tr_TR/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/tr_TR/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/tr_TR/content/contributing/contributing.md b/locale/tr_TR/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/tr_TR/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/tr_TR/content/contributing/debug_toolbar.md b/locale/tr_TR/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/tr_TR/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/tr_TR/content/contributing/install-dev.md b/locale/tr_TR/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/tr_TR/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/tr_TR/content/contributing/style_guide.md b/locale/tr_TR/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/tr_TR/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/tr_TR/content/contributing/translation.md b/locale/tr_TR/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/tr_TR/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/tr_TR/content/index.md b/locale/tr_TR/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/tr_TR/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/tr_TR/content/pages/index.md b/locale/tr_TR/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/tr_TR/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/tr_TR/content/running_bookwyrm/cli.md b/locale/tr_TR/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/tr_TR/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/tr_TR/content/running_bookwyrm/external-storage.md b/locale/tr_TR/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/tr_TR/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/tr_TR/content/running_bookwyrm/install-prod-dockerless.md b/locale/tr_TR/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/tr_TR/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/tr_TR/content/running_bookwyrm/install-prod.md b/locale/tr_TR/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/tr_TR/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/tr_TR/content/running_bookwyrm/moderation.md b/locale/tr_TR/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/tr_TR/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/tr_TR/content/running_bookwyrm/monitoring-queue.md b/locale/tr_TR/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/tr_TR/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/tr_TR/content/running_bookwyrm/optional_features.md b/locale/tr_TR/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/tr_TR/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/tr_TR/content/running_bookwyrm/reverse-proxy.md b/locale/tr_TR/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/tr_TR/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/tr_TR/content/running_bookwyrm/updating.md b/locale/tr_TR/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/tr_TR/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/tr_TR/content/using_bookwyrm/adding-books.md b/locale/tr_TR/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/tr_TR/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/tr_TR/content/using_bookwyrm/posting-statuses.md b/locale/tr_TR/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/tr_TR/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/uk_UA/LC_MESSAGES/messages.po b/locale/uk_UA/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..1d40d793
--- /dev/null
+++ b/locale/uk_UA/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Ukrainian\n"
+"Language: uk_UA\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=4; plural=((n%10==1 && n%100!=11) ? 0 : ((n%10 >= 2 && n%10 <=4 && (n%100 < 12 || n%100 > 14)) ? 1 : ((n%10 == 0 || (n%10 >= 5 && n%10 <=9)) || (n%100 >= 11 && n%100 <= 14)) ? 2 : 3));\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: uk\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/uk_UA/content/codebase/activitypub.md b/locale/uk_UA/content/codebase/activitypub.md
new file mode 100644
index 00000000..5dd76304
--- /dev/null
+++ b/locale/uk_UA/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm використовує [ActivityPub](http://activitypub.rocks/) протокол для надсилання та отримання діяльності користувача між іншими екземплярами BookWyrm та іншими службами, що реалізують ActivityPub, як [Mastodon](https://joinmastodon.org/). Для обробки даних книги, BookWyrm має декілька розширених типів діяльності, які не є частиною стандарту, але вони зрозумілі для інших екземплярів BookWyrm.
+
+## Діяльність та об'єкти
+
+### Користувачі та зв'язки
+Користувацькі взаємодії слідують стандартній специфікації ActivityPub.
+
+- `Follow`: запит на отримання статусів від користувача і перегляд їхніх статусів, що мають followers-only конфіденційність
+- `Accept`: затверджує `Follow` запит і завершує формування зв'язку
+- `Reject`: відмовляє `Follow` запит
+- `Block`: не дає користувачам бачити статуси одне одного та не дозволяє заблокованому користувачу переглядати профіль персони
+- `Update`: оновлює профіль користувача та налаштування
+- `Delete`: деактивує користувача
+- `Undo`: скасовує `Follow` або `Block`
+
+### Статуси
+#### Типи об'єктів
+
+- `Note`: На службах, таких як Mastodon, `Note` - це основний тип статусу. Вони містять тіло повідомлення, вкладення, можуть згадувати користувачів та відповідати на статуси будь-якого типу. У додатку BookWyrm `Note` можна створювати лише як прямі повідомлення або відповідати на інші статуси.
+- `Review`: Відгук - це статус у відповідь на книгу (вказану полем `ReplyToBook`), який має заголовок, тіло та числовий рейтинг між 0 (нема рейтингу) і 5.
+- `Comment`: коментар до книги, який згадує книгу і має тіло повідомлення.
+- `Quotation`: цитата має тіло повідомлення, уривок з книги та згадує книгу.
+
+
+#### Activities (дії)
+
+- `Create`: збереже новий статус в базі даних.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Видаляє статус
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities (дії)
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Альтернативна серіалізація
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/uk_UA/content/codebase/permissions.md b/locale/uk_UA/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/uk_UA/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/uk_UA/content/contributing/contributing.md b/locale/uk_UA/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/uk_UA/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/uk_UA/content/contributing/debug_toolbar.md b/locale/uk_UA/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/uk_UA/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/uk_UA/content/contributing/install-dev.md b/locale/uk_UA/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/uk_UA/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/uk_UA/content/contributing/style_guide.md b/locale/uk_UA/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/uk_UA/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/uk_UA/content/contributing/translation.md b/locale/uk_UA/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/uk_UA/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/uk_UA/content/index.md b/locale/uk_UA/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/uk_UA/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/uk_UA/content/pages/index.md b/locale/uk_UA/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/uk_UA/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/uk_UA/content/running_bookwyrm/cli.md b/locale/uk_UA/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..cae37392
--- /dev/null
+++ b/locale/uk_UA/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Розробники і менеджери bookwyrm можуть використовувати скрипт `bw-dev` для загальних завдань. Це може зробити команди коротшими, зручнішими до запам'ятання, і складніше робити помилки.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Компілює всі BookWyrm теми, які є `*.scss` файлами, перелічені в `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). Зазвичай вам не потрібно це запускати, якщо немає помилки, яка зачищає ваші стрічки користувачів з якихось причин. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Запустити тести з `pytest`.
+
+### deactivate_2fa
+
+Деактивує двофакторну аутентифікацію для цього користувача.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/uk_UA/content/running_bookwyrm/external-storage.md b/locale/uk_UA/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/uk_UA/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/uk_UA/content/running_bookwyrm/install-prod-dockerless.md b/locale/uk_UA/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..83cd99d2
--- /dev/null
+++ b/locale/uk_UA/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. У debian це може виглядати як `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Зніміть коментар на рядках з 18 по 67 для переходу на HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+Вам потрібно буде налаштувати завдання Cron для сервісу, щоб запустити його автоматично під час перезавантаження сервера.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/uk_UA/content/running_bookwyrm/install-prod.md b/locale/uk_UA/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/uk_UA/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/uk_UA/content/running_bookwyrm/moderation.md b/locale/uk_UA/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/uk_UA/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/uk_UA/content/running_bookwyrm/monitoring-queue.md b/locale/uk_UA/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/uk_UA/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/uk_UA/content/running_bookwyrm/optional_features.md b/locale/uk_UA/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/uk_UA/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/uk_UA/content/running_bookwyrm/reverse-proxy.md b/locale/uk_UA/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/uk_UA/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/uk_UA/content/running_bookwyrm/updating.md b/locale/uk_UA/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/uk_UA/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/uk_UA/content/using_bookwyrm/adding-books.md b/locale/uk_UA/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/uk_UA/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/uk_UA/content/using_bookwyrm/posting-statuses.md b/locale/uk_UA/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/uk_UA/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/vi_VN/LC_MESSAGES/messages.po b/locale/vi_VN/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..596e3937
--- /dev/null
+++ b/locale/vi_VN/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Vietnamese\n"
+"Language: vi_VN\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: vi\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/vi_VN/content/codebase/activitypub.md b/locale/vi_VN/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/vi_VN/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/vi_VN/content/codebase/permissions.md b/locale/vi_VN/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/vi_VN/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/vi_VN/content/contributing/contributing.md b/locale/vi_VN/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/vi_VN/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/vi_VN/content/contributing/debug_toolbar.md b/locale/vi_VN/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/vi_VN/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/vi_VN/content/contributing/install-dev.md b/locale/vi_VN/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/vi_VN/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/vi_VN/content/contributing/style_guide.md b/locale/vi_VN/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/vi_VN/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/vi_VN/content/contributing/translation.md b/locale/vi_VN/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/vi_VN/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/vi_VN/content/index.md b/locale/vi_VN/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/vi_VN/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/vi_VN/content/pages/index.md b/locale/vi_VN/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/vi_VN/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/vi_VN/content/running_bookwyrm/cli.md b/locale/vi_VN/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/vi_VN/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/vi_VN/content/running_bookwyrm/external-storage.md b/locale/vi_VN/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/vi_VN/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/vi_VN/content/running_bookwyrm/install-prod-dockerless.md b/locale/vi_VN/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/vi_VN/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/vi_VN/content/running_bookwyrm/install-prod.md b/locale/vi_VN/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/vi_VN/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/vi_VN/content/running_bookwyrm/moderation.md b/locale/vi_VN/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/vi_VN/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/vi_VN/content/running_bookwyrm/monitoring-queue.md b/locale/vi_VN/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/vi_VN/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/vi_VN/content/running_bookwyrm/optional_features.md b/locale/vi_VN/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/vi_VN/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/vi_VN/content/running_bookwyrm/reverse-proxy.md b/locale/vi_VN/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/vi_VN/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/vi_VN/content/running_bookwyrm/updating.md b/locale/vi_VN/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/vi_VN/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/vi_VN/content/using_bookwyrm/adding-books.md b/locale/vi_VN/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/vi_VN/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/vi_VN/content/using_bookwyrm/posting-statuses.md b/locale/vi_VN/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/vi_VN/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/locale/zh_Hans/LC_MESSAGES/messages.po b/locale/zh_Hans/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..59edabac
--- /dev/null
+++ b/locale/zh_Hans/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-12-03 17:57\n"
+"Last-Translator: \n"
+"Language-Team: Chinese Simplified\n"
+"Language: zh_CN\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: zh-CN\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr "BookWyr 文档"
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr "有关在BookWyrm上使用和贡献的指南"
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr "如何使用和贡献"
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr "BookWyrm：社会阅读和评论"
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr "加入"
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr "参与"
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr "支持"
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr "代码"
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr "文档"
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr "<strong>BookWyrm</strong> 是协力完成的、反企业化的软件，由 <a href='https://www.mousereeve.com/'>Mouse Reeve</a> 维护。"
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr "在 <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a> 上支持 BookWyrm 。"
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr "参与"
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr "GitHub 上的 BookWyrm"
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr "给本页面贡献力量"
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr "了解更多"
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr "联系维护者"
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr "许可证"
+
diff --git a/locale/zh_Hans/content/codebase/activitypub.md b/locale/zh_Hans/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/zh_Hans/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/zh_Hans/content/codebase/permissions.md b/locale/zh_Hans/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/zh_Hans/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/zh_Hans/content/contributing/contributing.md b/locale/zh_Hans/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/zh_Hans/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/zh_Hans/content/contributing/debug_toolbar.md b/locale/zh_Hans/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/zh_Hans/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/zh_Hans/content/contributing/install-dev.md b/locale/zh_Hans/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/zh_Hans/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/zh_Hans/content/contributing/style_guide.md b/locale/zh_Hans/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/zh_Hans/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/zh_Hans/content/contributing/translation.md b/locale/zh_Hans/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/zh_Hans/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/zh_Hans/content/index.md b/locale/zh_Hans/content/index.md
new file mode 100644
index 00000000..1d8d49c5
--- /dev/null
+++ b/locale/zh_Hans/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm是一个社交网络，用于跟踪你的阅读，谈论书籍，撰写评论，并发现下一步的阅读内容。 联盟允许BookWyrm用户加入小型的、可信赖的社区，这些社区可以相互联系，并与其他ActivityPub服务（如Mastodon和Pleroma）联系。
+
+## 特点
+由于该项目仍处于早期阶段，其功能每天都在增加，而且有很多建议和想法的空间。 打开一个[Issue](https://github.com/bookwyrm-social/bookwyrm/issues)，让你的意见继续下去！
+
+- 发表关于书籍的文章
+    - 撰写评论，无论是否有评级，都会在书页中汇总。
+    - 撰写关于书籍的其他类型的状态，例如。
+        - 评论一本书
+        - 引语或摘录
+    - 回复状态
+    - 在连接的BookWyrm实例中查看一本书的汇总评论
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- 精细的隐私控制
+    - 帖子、书架和列表的私密性、仅有粉丝和公开的隐私
+    - 用户可以选择手动允许他人成为你的粉丝
+    - 允许封锁和标记，以便进行仲裁。
diff --git a/locale/zh_Hans/content/pages/index.md b/locale/zh_Hans/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/zh_Hans/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/zh_Hans/content/running_bookwyrm/cli.md b/locale/zh_Hans/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/zh_Hans/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/zh_Hans/content/running_bookwyrm/external-storage.md b/locale/zh_Hans/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/zh_Hans/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/zh_Hans/content/running_bookwyrm/install-prod-dockerless.md b/locale/zh_Hans/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/zh_Hans/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/zh_Hans/content/running_bookwyrm/install-prod.md b/locale/zh_Hans/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/zh_Hans/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/zh_Hans/content/running_bookwyrm/moderation.md b/locale/zh_Hans/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/zh_Hans/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/zh_Hans/content/running_bookwyrm/monitoring-queue.md b/locale/zh_Hans/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/zh_Hans/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/zh_Hans/content/running_bookwyrm/optional_features.md b/locale/zh_Hans/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/zh_Hans/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/zh_Hans/content/running_bookwyrm/reverse-proxy.md b/locale/zh_Hans/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/zh_Hans/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/zh_Hans/content/running_bookwyrm/updating.md b/locale/zh_Hans/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/zh_Hans/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/zh_Hans/content/using_bookwyrm/adding-books.md b/locale/zh_Hans/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/zh_Hans/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/zh_Hans/content/using_bookwyrm/posting-statuses.md b/locale/zh_Hans/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..219d77af
--- /dev/null
+++ b/locale/zh_Hans/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+在BookWyrm上发帖，要从一本书开始。 用户可以从“你的书”部分，或从一本书的登陆页面，对正在进行的或最近阅读的书籍进行评论。 从那里，用户可以对评论回复并开始对话。 BookWyrm帖子可以包括一些格式，如使用[Markdown](https://www.markdownguide.org/cheat-sheet/)的粗体、斜体和链接。
+
+如果你熟悉[在Mastodon上发帖](https://docs.joinmastodon.org/user/posting/)，你会发现BookWyrm的状态有类似的可见性设置、内容警告和提醒。 然而，目前还暂不支持投票、自定义表情符号和附件。
+
+## 状态类型
+
+### 用户评论
+
+用户可以直接对对应的书籍创建三种类型的帖子：观后感、评论和引言。 评论是针对一本书的一般方面，引言是针对具体的段落，而观后感则是针对书籍的整体。 用户还可以对状态进行回复。
+
+| 组成部分 | 观后感 | 评论 | 引言 | 回复 |
+| ---- | --- | -- | -- | -- |
+| 文本字段 | ✔   | ✔  | ✔  | ✔  |
+| 剧透警告 | ✔   | ✔  | ✔  | ✔  |
+| 页码   |     | ✔  | ✔  |    |
+| 引用   |     |    | ✔  |    |
+| 评分   | ✔   |    |    |    |
+| 标题字段 | ✔   |    |    |    |
+
+
+### 阅读状态更新
+
+当用户表示他们想要阅读、已经开始阅读或已经完成阅读一本书时，就会有对应的状态。
+
+## 文本
+文本可以包括：
+
+- 提及用户（@user）
+- URLs（`http(s)://` 不会显示）
+- 一些 [Markdown 格式](https://www.markdownguide.org/cheat-sheet/)
+  - 粗体
+  - 斜体
+  - 引用块
+  - 符号列表
+  - 链接
+
diff --git a/locale/zh_Hant/LC_MESSAGES/messages.po b/locale/zh_Hant/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..c7ab1357
--- /dev/null
+++ b/locale/zh_Hant/LC_MESSAGES/messages.po
@@ -0,0 +1,88 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: bookwyrm\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-07-08 10:16-0700\n"
+"PO-Revision-Date: 2022-07-08 17:52\n"
+"Last-Translator: \n"
+"Language-Team: Chinese Traditional\n"
+"Language: zh_TW\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+"X-Crowdin-Project: bookwyrm\n"
+"X-Crowdin-Project-ID: 479239\n"
+"X-Crowdin-Language: zh-TW\n"
+"X-Crowdin-File: /[bookwyrm-social.documentation] main/locale/en_US/LC_MESSAGES/messages.po\n"
+"X-Crowdin-File-ID: 1636\n"
+
+#: templates/index.html:5 templates/layout.html:6
+msgid "BookWyrm Documentation"
+msgstr ""
+
+#: templates/index.html:6
+msgid "Your guide to using and contributing to BookWyrm"
+msgstr ""
+
+#: templates/index.html:6
+msgid "How to Use and Contribute"
+msgstr ""
+
+#: templates/layout.html:4
+msgid "BookWyrm: Social Reading and Reviewing"
+msgstr ""
+
+#: templates/layout.html:35 templates/layout.html:39
+msgid "Join"
+msgstr ""
+
+#: templates/layout.html:38 templates/layout.html:42
+msgid "Get involved"
+msgstr ""
+
+#: templates/layout.html:41 templates/layout.html:45
+msgid "Support"
+msgstr ""
+
+#: templates/layout.html:44 templates/layout.html:48
+msgid "Code"
+msgstr ""
+
+#: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
+#: templates/layout.html:130
+msgid "Documentation"
+msgstr ""
+
+#: templates/layout.html:95 templates/layout.html:101
+msgid "<strong>BookWyrm</strong> is collaborative, anti-corporate software maintained by <a href='https://www.mousereeve.com/'>Mouse Reeve</a>."
+msgstr ""
+
+#: templates/layout.html:98 templates/layout.html:104
+msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
+msgstr ""
+
+#: templates/layout.html:102 templates/layout.html:108
+msgid "Get Involved"
+msgstr ""
+
+#: templates/layout.html:104 templates/layout.html:110
+msgid "BookWyrm on GitHub"
+msgstr ""
+
+#: templates/layout.html:107 templates/layout.html:113
+msgid "Contribute to this page"
+msgstr ""
+
+#: templates/layout.html:122 templates/layout.html:128
+msgid "Learn more"
+msgstr ""
+
+#: templates/layout.html:127 templates/layout.html:133
+msgid "Contact maintainer"
+msgstr ""
+
+#: templates/layout.html:130 templates/layout.html:136
+msgid "License"
+msgstr ""
+
diff --git a/locale/zh_Hant/content/codebase/activitypub.md b/locale/zh_Hant/content/codebase/activitypub.md
new file mode 100644
index 00000000..543ee309
--- /dev/null
+++ b/locale/zh_Hant/content/codebase/activitypub.md
@@ -0,0 +1,60 @@
+- - -
+Title: ActivityPub Date: 2021-04-20 Order: 1
+- - -
+
+BookWyrm uses the [ActivityPub](http://activitypub.rocks/) protocol to send and receive user activity between other BookWyrm instances and other services that implement ActivityPub, like [Mastodon](https://joinmastodon.org/). To handle book data, BookWyrm has a handful of extended Activity types which are not part of the standard, but are legible to other BookWyrm instances.
+
+## Activities and Objects
+
+### Users and relationships
+User relationship interactions follow the standard ActivityPub spec.
+
+- `Follow`: request to receive statuses from a user, and view their statuses that have followers-only privacy
+- `Accept`: approves a `Follow` and finalizes the relationship
+- `Reject`: denies a `Follow`
+- `Block`: prevent users from seeing one another's statuses, and prevents the blocked user from viewing the actor's profile
+- `Update`: updates a user's profile and settings
+- `Delete`: deactivates a user
+- `Undo`: reverses a `Follow` or `Block`
+
+### Statuses
+#### Object types
+
+- `Note`: On services like Mastodon, `Note`s are the primary type of status. They contain a message body, attachments, can mention users, and be replies to statuses of any type. Within BookWyrm, `Note`s can only be created as direct messages or as replies to other statuses.
+- `Review`: A review is a status in response to a book (indicated by the `inReplyToBook` field), which has a title, body, and numerical rating between 0 (not rated) and 5.
+- `Comment`: A comment on a book mentions a book and has a message body.
+- `Quotation`: A quote has a message body, an excerpt from a book, and mentions a book.
+
+
+#### Activities
+
+- `Create`: saves a new status in the database.
+
+   **Note**: BookWyrm only accepts `Create` activities if they are:
+
+   - Direct messages (i.e., `Note`s with the privacy level `direct`, which mention a local user),
+   - Related to a book (of a custom status type that includes the field `inReplyToBook`),
+   - Replies to existing statuses saved in the database
+- `Delete`: Removes a status
+- `Like`: Creates a favorite on the status
+- `Announce`: Boosts the status into the actor's timeline
+- `Undo`: Reverses a `Like` or `Announce`
+
+### Collections
+User's books and lists are represented by [`OrderedCollection`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection)
+
+#### Objects
+
+- `Shelf`: A user's book collection. By default, every user has a `to-read`, `reading`, and `read` shelf which are used to track reading progress.
+- `List`: A collection of books that may have items contributed by users other than the one who created the list.
+
+#### Activities
+
+- `Create`: Adds a shelf or list to the database.
+- `Delete`: Removes a shelf or list.
+- `Add`: Adds a book to a shelf or list.
+- `Remove`: Removes a book from a shelf or list.
+
+
+## Alternative Serialization
+Because BookWyrm uses custom object types (`Review`, `Comment`, `Quotation`) that aren't supported by ActivityPub, statuses are transformed into standard types when sent to or viewed by non-BookWyrm services. `Review`s are converted into `Article`s, and `Comment`s and `Quotation`s are converted into `Note`s, with a link to the book and the cover image attached.
diff --git a/locale/zh_Hant/content/codebase/permissions.md b/locale/zh_Hant/content/codebase/permissions.md
new file mode 100644
index 00000000..24e5896d
--- /dev/null
+++ b/locale/zh_Hant/content/codebase/permissions.md
@@ -0,0 +1,21 @@
+- - -
+Title: Permissions Date: 2021-04-18 Order: 2
+- - -
+
+User access to different features is controlled using Django's [built-in authentication system](https://docs.djangoproject.com/en/3.2/topics/auth/default/). When an instance is created, the `initdb` script creates a set of permissions, which are assinged to groups. By default, all new users are assigned the `editor` group, which allows them to edit book metadata.
+
+The instance administrator should have `superuser` status, which gives them access to Django admin (`/admin`) and confers all permissions to that user.
+
+## Permissions and groups
+This table shows the four groups (admin, moderator, editor, and user) and what permissions users in that group have:
+
+|                        | admin | moderator | editor | user |
+| ---------------------- | ----- | --------- | ------ | ---- |
+| edit instance settings | ✔️    | -         | -      | -    |
+| change user level      | ✔️    | -         | -      | -    |
+| manage federation      | ✔️    | ✔️        | -      | -    |
+| issue invites          | ✔️    | ✔️        | -      | -    |
+| deactivate users       | ✔️    | ✔️        | -      | -    |
+| delete posts           | ✔️    | ✔️        | -      | -    |
+| edit books             | ✔️    | ✔️        | ✔️     | -    |
+ upload covers            |  ✔️    |     ✔️       |   ✔️     |  ✔️
diff --git a/locale/zh_Hant/content/contributing/contributing.md b/locale/zh_Hant/content/contributing/contributing.md
new file mode 100644
index 00000000..4ea1eee9
--- /dev/null
+++ b/locale/zh_Hant/content/contributing/contributing.md
@@ -0,0 +1,19 @@
+- - -
+Title: How to Contribute Date: 2021-04-12 Order: 1
+- - -
+
+There are many ways you can contribute to this project, regardless of your level of technical expertise.
+
+## Feedback and feature requests
+Please feel encouraged and welcome to point out bugs, suggestions, feature requests, and ideas for how things ought to work using [GitHub issues](https://github.com/bookwyrm-social/bookwyrm/issues).
+
+## Code contributions
+Code contributions are gladly welcomed! If you're not sure where to start, take a look at the ["Good first issue"](https://github.com/bookwyrm-social/bookwyrm/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) tag. Because BookWyrm is a small project, there isn't a lot of formal structure, but there is a huge capacity for one-on-one support, which can look like asking questions as you go, pair programming, video chats, et cetera, so please feel free to reach out.
+
+If you have questions about the project or contributing, you can join the [BookWyrm matrix chat](https://app.element.io/#/room/#bookwyrm:matrix.org).
+
+## Translation
+Do you speak a language besides English? BookWyrm needs localization! You can add and edit translations at [translate.joinbookwyrm.com](http://translate.joinbookwyrm.com/)
+
+## Financial Support
+BookWyrm is an ad-free passion project with no intentions of seeking out venture funding or corporate financial relationships. If you want to help keep the project going, you can become a sustaining contributor via [Patreon](https://www.patreon.com/bookwyrm) or [OpenCollective](https://opencollective.com/bookwyrm), or make a one time gift via [PayPal](https://paypal.me/oulipo).
diff --git a/locale/zh_Hant/content/contributing/debug_toolbar.md b/locale/zh_Hant/content/contributing/debug_toolbar.md
new file mode 100644
index 00000000..cffc572f
--- /dev/null
+++ b/locale/zh_Hant/content/contributing/debug_toolbar.md
@@ -0,0 +1,12 @@
+- - -
+Title: Django Debug Toolbar Date: 2022-05-16 Order: 5
+- - -
+
+BookWyrm has a branch that is configured to run [Django Debug Toolbar](https://django-debug-toolbar.readthedocs.io/en/latest/). This branch will never get merged into `main` and has a few tweaks that make it work with the toolbar, but unsafe to use in anything resembling a production environment. To use this branch, you will need to go through a few steps to get it running.
+
+## Set up
+
+- Using git, checkout out the [`debug-toolbar`](https://github.com/bookwyrm-social/bookwyrm/tree/debug-toolbar) branch
+- Update the branch relative to `main` using `git merge main`. The branch is updated periodically but will likely be behind latest.
+- Re-build the Docker images using `docker-compose up --build` to ensure that the Debug Toolbar library is installed from `requirements.txt`
+- Access the application `web` image directly (instead of via `nginx`) using port `8000`
diff --git a/locale/zh_Hant/content/contributing/install-dev.md b/locale/zh_Hant/content/contributing/install-dev.md
new file mode 100644
index 00000000..4550632b
--- /dev/null
+++ b/locale/zh_Hant/content/contributing/install-dev.md
@@ -0,0 +1,50 @@
+- - -
+Title: Developer Environment Date: 2021-04-12 Order: 3
+- - -
+
+## Prerequisites
+
+These instructions assume you are developing BookWyrm using Docker. You'll need to [install Docker](https://docs.docker.com/engine/install/) and [docker-compose](https://docs.docker.com/compose/install/) to get started.
+
+## Setting up the developer environment
+
+- Get a copy of [the BookWyrm codebase from GitHub](https://github.com/bookwyrm-social/bookwyrm). You can [create a fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the repository, and then [use `git clone` to download the code](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository) to your computer.
+- Go to the directory which contains the code on your computer, you'll be working from there from here on out.
+- Set up your development environment variables file by copying the example environment file (`.env.example`) into a new file named `.env`. In the command line, you can do this with:
+``` { .sh }
+cp .env.example .env
+```
+- In `.env`, change `DEBUG` to `true`
+- Optionally, you can use a service like [ngrok](https://ngrok.com/) to set up a domain name, and set the `DOMAIN` variable in your `.env` file to the domain name generated by ngrok.
+
+- Set up nginx for development by copying the developer nginx configuration file (`nginx/development`) into a new file named `nginx/default.conf`:
+``` { .sh }
+cp nginx/development nginx/default.conf
+```
+
+- Start the application. In the command line, run:
+``` { .sh }
+./bw-dev build            # Build the docker images
+./bw-dev setup            # Initialize the database and run migrations
+./bw-dev up               # Start the docker containers
+```
+- Once the build is complete, you can access the instance at `http://localhost:1333` and create an admin user.
+
+If you're curious: the `./bw-dev` command is a simple shell script runs various other tools: above, you could skip it and run `docker-compose build` or `docker-compose up` directly if you like. `./bw-dev` just collects them into one common place for convenience. Run it without arguments to get a list of available commands, read the [documentation page](/command-line-tool.html) for it, or open it up and look around to see exactly what each command is doing!
+
+### Editing or creating Models
+
+If you change or create a model, you will probably change the database structure. For these changes to have effect you will need to run Django's `makemigrations` command to create a new [Django migrations file](https://docs.djangoproject.com/en/3.2/topics/migrations), and then `migrate` it:
+
+``` { .sh }
+./bw-dev makemigrations
+./bw-dev migrate
+```
+
+### Editing static files
+Any time you edit the CSS or JavaScript, you will need to run Django's `collectstatic` command again in order for your changes to have effect:
+``` { .sh }
+./bw-dev collectstatic
+```
+
+If you have [installed yarn](https://yarnpkg.com/getting-started/install), you can run `yarn watch:static` to automatically run the previous script every time a change occurs in `bookwyrm/static` directory.
diff --git a/locale/zh_Hant/content/contributing/style_guide.md b/locale/zh_Hant/content/contributing/style_guide.md
new file mode 100644
index 00000000..d9f41781
--- /dev/null
+++ b/locale/zh_Hant/content/contributing/style_guide.md
@@ -0,0 +1,53 @@
+- - -
+Title: Style Guide Date: 2021-10-20 Order: 4
+- - -
+
+## Pull requests
+
+So you want to contribute code to BookWyrm: that rules! If there's an open issue that you'd like to fix, it's helpful to comment on the issue so work doesn't get duplicated. Try to keep the scope of pull requests small and focused on a single topic. That way it's easier to review, and if one part needs changes, it won't hold up the other parts.
+
+If you aren't sure how to fix something, or you aren't able to get around to it, that's totally okay, just leave a comment on the pull request and we'll figure it out 💖.
+
+Pull requests have to pass all the automated checks before they can be merged - this includes style checks, global linters, a security check, and unit tests.
+
+## Linting
+
+### Global
+
+We use [EditorConfig](https://editorconfig.org) to maintain consistent indenting and line endings.
+
+### Python
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. All new pull requests are checked with GitHub actions, and you can automatically fix code style problems by running `./bw-dev black`
+
+Code is also checked with Pylint using GitHub Actions. Pylint warnings must be addressed before pull requests are merged, but it's a judgement call if the suggestion should be used, or the warning suppressed. To suppress a warning, add a comment at the end of or on the line above the warnings: `# pylint: disable=warning-name`
+
+### Templates (HTML)
+
+Your pull request will also be checked by the [curlylint](https://www.curlylint.org) linter for Django templates.
+
+### CSS
+
+We use [stylelint](https://stylelint.io) to check all CSS rules. As with Pylint [you can disable stylelint](https://stylelint.io/user-guide/ignore-code) for a particular rule, but you will need a good justification for doing so.
+
+### JavaScript
+
+[ESLint](https://eslint.org) checks any JavaScript changes you have made. If ESLint doesn't like your working JavaScript, check the linter message for the exact problem.
+
+## Inclusive Design
+
+Bookwyrm aims to be as inclusive and accessible as possible.
+
+When contributing code, check the [Inclusive Web Design Checklist](https://github.com/bookwyrm-social/bookwyrm/discussions/1354) before you file your pull request. For accessibility advice, [A11Y-101](https://www.a11y-101.com/development) is also a useful source. For information on how to make your page templates multi-lingual, see the [Translations section](/translations.html).
+
+Some particular things that Bookwyrm contributors have found useful to remember are:
+
+### Forms
+
+* Only use `input[type="checkbox"]` or `input[type="radio"]` inside `<label>`
+* If you do not place checkboxes and radio buttons inside the `<label>`, the `<label>` should be placed _after_ the element it relates to
+
+### Buttons and Links
+
+* Use a `<button>` element for anything that exists to trigger a JavaScript action (e.g. hiding or unhiding a form) or sends a `POST` request (e.g. submitting a form)
+* Use an `<a>` element for anything that triggers a `GET` request. Usually, an anchor (`<a>`) element should not be styled as a button (`class="button"`), though there are some exceptions, such as "Cancel" buttons. If in doubt, ask for advice in your pull request
diff --git a/locale/zh_Hant/content/contributing/translation.md b/locale/zh_Hant/content/contributing/translation.md
new file mode 100644
index 00000000..36662e29
--- /dev/null
+++ b/locale/zh_Hant/content/contributing/translation.md
@@ -0,0 +1,36 @@
+- - -
+Title: Translations Date: 2021-10-20 Order: 2
+- - -
+
+## Contributing to translations
+
+You can join the BookWyrm translation project at [translate.joinbookwyrm.com](https://translate.joinbookwyrm.com/).
+
+## Gender-neutral language
+
+Wherever possible, BookWyrm translations should use gender-neutral language. This applies even if a language defaults to male as a neutral gender, or if it uses something similar to "he/she". It's also important for translations to be clear, concise, and legible to a screen reader, and sometimes these goals are in conflict; there isn't a perfect, one-size-fits all answer, and the solution depends on the language.
+
+As a guiding principal, try to place a higher value on inclusive and gender-neutral language than on formal correctness or officially approved style guides. In English, for example, many formal style guides require a singular "she" or "he" pronoun to be used when referring to an individual, but it would be better in BookWyrm to use the gender-neutral singular "they" instead.
+
+If you aren't sure how best to approach a translation problem, comment on the translation or open a [discussion topic](https://translate.joinbookwyrm.com/project/bookwyrm/discussions) to address broader-scale questions.
+
+## Making templates translatable
+
+Bookwyrm takes advantage of Django's translation functionality to enable page content to change depending on the user's chosen display language. The Django documentation [provides a helpful explanation](https://docs.djangoproject.com/en/3.2/topics/i18n/translation/#internationalization-in-template-code) of how this works, but here is the short version:
+
+* all template text should include translation template tags
+* add `{% load i18n %}` at the top of your template to enable translations
+* If the text block is literal text, you can use the template tag `{% trans %}`
+* If the text block includes variables, you should use the template tag pair `{% blocktrans %}` and `{% endblocktrans %}`. If you are including padding whitespace or line breaks, use `trimmed` to automatically remove it when the locale file is generated: `{% blocktrans trimmed %}`
+
+### Examples
+
+```html
+<p>{% trans "This list is currently empty" %}</p>
+
+<p>
+    {% blocktrans trimmed with username=item.user.display_name user_path=item.user.local_path %}
+    Added by <a href="{{ user_path }}">{{ username }}</a>
+    {% endblocktrans %}
+</p>
+```
diff --git a/locale/zh_Hant/content/index.md b/locale/zh_Hant/content/index.md
new file mode 100644
index 00000000..ae203a11
--- /dev/null
+++ b/locale/zh_Hant/content/index.md
@@ -0,0 +1,33 @@
+- - -
+Title: Welcome Date: 2021-04-13
+- - -
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/zh_Hant/content/pages/index.md b/locale/zh_Hant/content/pages/index.md
new file mode 100644
index 00000000..79adfd48
--- /dev/null
+++ b/locale/zh_Hant/content/pages/index.md
@@ -0,0 +1,31 @@
+Title: Welcome Date: 2021-04-13
+
+BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
+
+## Features
+Since the project is still in its early stages, the features are growing every day, and there is plenty of room for suggestions and ideas. Open an [issue](https://github.com/bookwyrm-social/bookwyrm/issues) to get the conversation going!
+
+- Posting about books
+    - Compose reviews, with or without ratings, which are aggregated in the book page
+    - Compose other kinds of statuses about books, such as:
+        - Comments on a book
+        - Quotes or excerpts
+    - Reply to statuses
+    - View aggregate reviews of a book across connected BookWyrm instances
+    - Differentiate local and federated reviews and rating in your activity feed
+- Track reading activity
+    - Shelve books on default "to-read," "currently reading," and "read" shelves
+    - Create custom shelves
+    - Store started reading/finished reading dates, as well as progress updates along the way
+    - Update followers about reading activity (optionally, and with granular privacy controls)
+    - Create lists of books which can be open to submissions from anyone, curated, or only edited by the creator
+- Federation with ActivityPub
+    - Broadcast and receive user statuses and activity
+    - Share book data between instances to create a networked database of metadata
+    - Identify shared books across instances and aggregate related content
+    - Follow and interact with users across BookWyrm instances
+    - Inter-operate with non-BookWyrm ActivityPub services (currently, Mastodon is supported)
+- Granular privacy controls
+    - Private, followers-only, and public privacy levels for posting, shelves, and lists
+    - Option for users to manually approve followers
+    - Allow blocking and flagging for moderation
diff --git a/locale/zh_Hant/content/running_bookwyrm/cli.md b/locale/zh_Hant/content/running_bookwyrm/cli.md
new file mode 100644
index 00000000..8236c27a
--- /dev/null
+++ b/locale/zh_Hant/content/running_bookwyrm/cli.md
@@ -0,0 +1,180 @@
+- - -
+Title: Command Line Tool Date: 2021-11-11 Order: 9
+- - -
+
+Bookwyrm developers and instance managers can use the `bw-dev` script for common tasks. This can make your commands shorter, easier to remember, and harder to mess up.
+
+Once you have installed Bookwyrm [in production](installing-in-production.html) or [in development](https://docs.joinbookwyrm.com/developer-environment.html#setting_up_the_developer_environment), you can run the script from the command line with `./bw-dev` followed by the subcommand you want to run.
+
+## Docker shortcuts
+
+### bash
+
+Open an interactive `bash` session inside the docker `web` container.
+
+### build
+
+Equivalent to `docker-compose build`.
+
+### dbshell
+
+Open an interactive Postgres database shell. I hope you know what you're doing.
+
+### runweb args
+
+Run an arbitrary command (represented above by `args`) in the `web` container.
+
+Equivalent to `docker-compose run --rm web`.
+
+### service_ports_web args
+
+Run an arbitrary command in the `web` container (represented above by `args`) with ports exposed. This is useful if you want to run `pdb` tests because `runweb` will not expose the `pdb` prompt.
+
+Equivalent to `docker-compose run --rm --service-ports web`.
+
+### shell
+
+Open an interactive Django shell inside the docker `web` container. You would use this if you want to run Django shell commands directly.
+
+### up [args]
+
+Start or restart Docker containers, optionally including any arguments (represented above by `args`). Equivalent to `docker-compose up --build [args]`
+
+## Managing the database
+
+### initdb
+
+Initialize a database.
+
+### makemigrations [appname migration number]
+
+_This command is not available on the `production` branch_.
+
+Runs Django's `makemigrations` command inside your Docker container. If you have changed the database structure in a development branch you will need to run this for your changes to have effect. Optionally, you can specify a specific migration to run, e.g. `./bw-dev makemigrations bookwyrm 0108`
+
+### migrate
+
+Runs Django's `migrate` command inside your Docker container. You always need to run this after `makemigrations`.
+
+### resetdb
+
+_This command is not available on the `production` branch_.
+
+Resets the database. **This command will delete your entire Bookwyrm database**, and then initiate a fresh database and run all migrations. You should delete any recent migration files you do not want to run, _before_ running `resetdb`.
+
+## Managing a Bookwyrm instance
+
+### compile_themes
+
+Compiles all BookWyrm themes, which are `*.scss` files listed in `bookwyrm/static/css/themes`.
+
+### collectstatic
+
+Migrate static assets to either a Docker container or to an S3-compatible "bucket", depending on the context.
+
+### generate_preview_images
+
+Generate preview images for site, users, and books. This can take a while if you have a large database. See [Optional Features: Generating preview images](/optional_features.html)
+
+### remove_remote_user_preview_images
+
+Remove generated preview images for remote users. See [Optional Features: Removing preview images for remote users](/optional_features.html)
+
+### generate_thumbnails
+
+Generates thumbnail images for book covers.
+
+### populate_streams args
+
+Re-populates Redis streams (user feeds). You will not usually need to run this unless there is an error that wipes out your user feeds for some reason. You can specify which stream using the `--stream` argument.
+
+### populate_list_streams
+
+Re-populates Redis cache of lists. You will not usually need to run this unless there is an error that wipes out your users' lists for some reason.
+
+### populate_suggestions
+
+Populate suggested users for all users. You may want to run this manually to refresh suggestions.
+
+### restart_celery
+
+Restarts the `celery_worker` Docker container.
+
+### update
+
+When there are changes to the `production` branch, you can update your instance without downtime.
+
+This command `git pull`s the latest `production` branch updates, builds docker images if necessary, runs Django migrations, updates static files, and restarts all Docker containers.
+
+### admin_code
+
+Gets the secret admin code used to register the inital admin user on a new BookWyrm instance.
+
+## Setting up S3 compatible storage
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses django-storages to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+See [External Storage](/external-storage.html) for more information.
+
+### copy_media_to_s3
+
+Migrate all uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use for initial upload to an empty bucket.
+
+### sync_media_to_s3
+
+Sync new or changed uploaded media from an existing BookWyrm installation to an S3-compatible "bucket". Use to ensure all local files are uploaded to an existing bucket.
+
+### set_cors_to_s3 filename
+
+Copy a CORS rules JSON file to your S3 bucket, where `filename` is the name of your JSON file (e.g. `./bw-dev set_cors_to_s3 cors.json`)
+
+## Development and testing
+
+_These commands are not available on the `production` branch_.
+
+### black
+
+BookWyrm uses the [Black](https://github.com/psf/black) code formatter to keep the Python codebase consistent styled. Run `black` before committing your changes so the `pylint` task does not fail for your pull request and make you sad.
+
+### prettier
+
+BookWyrm uses [Prettier](https://prettier.io/) to keep the JavaScript codebase consistently styled. Run `prettier` before committing changes to scripts to automatically format your code.
+
+### stylelint
+
+BookWyrm uses [Stylelint](uhttps://stylelint.io/) to keep the CSS files consistently styled. Run `stylelintprettier` before committing changes to scripts to automatically format your code.
+
+### formatters
+
+This command runs all code formatters (`black`, `prettier`, and `stylelint`) in one go.
+
+### clean
+
+Remove all stopped Docker containers.
+
+Equivalent to:
+
+```shell
+docker-compose stop
+docker-compose rm -f
+```
+
+### makemessages
+
+Creates message files for all translation strings. After you have run `makemessages` you need to run `compilemessages` to compile the translations. See [Django's makemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#makemessages).
+
+### compilemessages
+
+Compiles translation files. See [Django's compilemessages](https://docs.djangoproject.com/en/3.2/ref/django-admin/#compilemessages).
+
+### pytest args
+
+Run tests with `pytest`.
+
+### deactivate_2fa
+
+Deactivates two factor authentication for a given user.
+
+### manual_confirm
+
+Confirms a users email, sets the user to active.
diff --git a/locale/zh_Hant/content/running_bookwyrm/external-storage.md b/locale/zh_Hant/content/running_bookwyrm/external-storage.md
new file mode 100644
index 00000000..397697db
--- /dev/null
+++ b/locale/zh_Hant/content/running_bookwyrm/external-storage.md
@@ -0,0 +1,148 @@
+- - -
+Title: External Storage Date: 2021-06-07 Order: 7
+- - -
+
+By default, BookWyrm uses local storage for static assets (favicon, default avatar, etc.), and media (user avatars, book covers, etc.), but you can use an external storage service to serve these files. BookWyrm uses `django-storages` to handle external storage, such as S3-compatible services, Apache Libcloud or SFTP.
+
+## S3-compatible Services
+
+### Setup
+
+Create a bucket at your S3-compatible service of choice, along with an Access Key ID and a Secret Access Key. These can be self hosted, like [Ceph](https://ceph.io/en/) (LGPL 2.1/3.0) or [MinIO](https://min.io/) (GNU AGPL v3.0), or commercial ([Scaleway](https://www.scaleway.com/en/docs/object-storage-feature/), [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-create-a-digitalocean-space-and-api-key)…).
+
+This guide has been tested against Scaleway Object Storage. If you use another service, please share your experience (especially if you had to take different steps) by filing an Issue on the [BookWyrm Documentation](https://github.com/bookwyrm-social/documentation) repository.
+
+### What awaits you
+
+If you are starting a new BookWyrm instance, the process will be:
+
+- Set up your external storage service
+- Enable external storage on BookWyrm
+- Start your BookWyrm instance
+- Update the instance connector
+
+If you already started your instance, and images have been uploaded to local storage, the process will be:
+
+- Set up your external storage service
+- Copy your local media to external storage
+- Enable external storage on BookWyrm
+- Restart your BookWyrm instance
+- Update the instance connector
+
+### BookWyrm Settings
+
+Edit your `.env` file by uncommenting the following lines:
+
+- `AWS_ACCESS_KEY_ID`: your access key ID
+- `AWS_SECRET_ACCESS_KEY`: your secret access key
+- `AWS_STORAGE_BUCKET_NAME`: your bucket name
+- `AWS_S3_REGION_NAME`: e.g. `"eu-west-1"` for AWS, `"fr-par"` for Scaleway or `"nyc3"` for Digital Ocean
+
+If your S3-compatible service is Amazon AWS, you should be set. If not, you’ll have to uncomment the following lines:
+
+- `AWS_S3_CUSTOM_DOMAIN`: the domain that will serve the assets, e.g. `"example-bucket-name.s3.fr-par.scw.cloud"` or `"${AWS_STORAGE_BUCKET_NAME}.${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+- `AWS_S3_ENDPOINT_URL`: the S3 API endpoint, e.g. `"https://s3.fr-par.scw.cloud"` or `"https://${AWS_S3_REGION_NAME}.digitaloceanspaces.com"`
+
+### Copying local media to external storage
+
+If your BookWyrm instance is already running and media have been uploaded (user avatars, book covers…), you will need to migrate uploaded media to your bucket.
+
+This task is done with the command:
+
+```bash
+./bw-dev copy_media_to_s3
+```
+
+### Enabling external storage for BookWyrm
+
+To enable the S3-compatible external storage, you will have to edit your `.env` file by changing the property value for `USE_S3` from `false` to `true`:
+
+```
+USE_S3=true
+```
+
+If your external storage is being served over HTTPS (which most are these days), you'll also need to make sure that `USE_HTTPS` is set to `true`, so images will be loaded over HTTPS:
+
+```
+USE_HTTPS=true
+```
+
+#### Static assets
+
+Then, you will need to run the following command, to copy the static assets to your S3 bucket:
+
+```bash
+./bw-dev collectstatic
+```
+
+#### CORS settings
+
+Once the static assets are collected, you will need to set up CORS for your bucket.
+
+Some services like Digital Ocean provide an interface to set it up, see [Digital Ocean doc: How to Configure CORS](https://docs.digitalocean.com/products/spaces/how-to/configure-cors/).
+
+If your service doesn’t provide an interface, you can still set up CORS with the command line.
+
+Create a file called `cors.json`, with the following content:
+
+```json
+{
+  "CORSRules": [
+    {
+      "AllowedOrigins": ["https://MY_DOMAIN_NAME", "https://www.MY_DOMAIN_NAME"],
+      "AllowedHeaders": ["*"],
+      "AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
+      "MaxAgeSeconds": 3000,
+      "ExposeHeaders": ["Etag"]
+    }
+  ]
+}
+```
+
+Replace `MY_DOMAIN_NAME` with the domain name(s) of your instance.
+
+Then, run the following command:
+
+```bash
+./bw-dev set_cors_to_s3 cors.json
+```
+
+No output means it should be good.
+
+If you are starting a new BookWyrm instance, you can go back to the setup instructions right now. If not, keep on reading.
+
+### Restarting your instance
+
+Once the media migration has been done and the static assets are collected, you can load the new `.env` configuration and restart your instance with:
+
+```bash
+./bw-dev up -d
+```
+
+If all goes well, your storage has been changed without server downtime. If some fonts are missing (and your browser’s JS console lights up with alerts about CORS), something went wrong [here](#cors-settings). In that case it might be good to check the headers of a HTTP request against a file on your bucket:
+
+```bash
+curl -X OPTIONS -H 'Origin: http://MY_DOMAIN_NAME' http://BUCKET_URL/static/images/logo-small.png -H "Access-Control-Request-Method: GET"
+```
+
+Replace `MY_DOMAIN_NAME` with your instance domain name, `BUCKET_URL` with the URL for your bucket, you can replace the file path with any other valid path on your bucket.
+
+If you see any message, especially a message starting with `<Error><Code>CORSForbidden</Code>`, it didn’t work. If you see no message, it worked.
+
+For an active instance, there may be a handful of files that were created locally during the time between migrating the files to external storage, and restarting the app so it uses the external storage. To ensure that any remaining files are uploaded to external storage after switching over, you can use the following command, which will upload only files that aren't already present in the external storage:
+
+```bash
+./bw-dev sync_media_to_s3
+```
+
+### Updating the instance connector
+
+*Note: You can skip this step if you're running an updated version of BookWyrm; in September 2021 the "self connector" was removed in [PR #1413](https://github.com/bookwyrm-social/bookwyrm/pull/1413)*
+
+In order for the right URL to be used when displaying local book search results, we have to modify the value for the cover images URL base.
+
+Connector data can be accessed through the Django admin interface, located at the url `http://MY_DOMAIN_NAME/admin`. The connector for your own instance is the first record in the database, so you can access the connector with this URL: `https://MY_DOMAIN_NAME/admin/bookwyrm/connector/1/change/`.
+
+The field _Covers url_ is defined by default as `https://MY_DOMAIN_NAME/images`, you have to change it to `https://S3_STORAGE_URL/images`. Then, click the _Save_ button, and voilà!
+
+You will have to update the value for _Covers url_ every time you change the URL for your storage.
diff --git a/locale/zh_Hant/content/running_bookwyrm/install-prod-dockerless.md b/locale/zh_Hant/content/running_bookwyrm/install-prod-dockerless.md
new file mode 100644
index 00000000..1b31e188
--- /dev/null
+++ b/locale/zh_Hant/content/running_bookwyrm/install-prod-dockerless.md
@@ -0,0 +1,134 @@
+---
+Title: Installing Without Docker
+Date: 2022-10-02
+Order: 2
+---
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production. This method of installation is more involved, and therefore is for more experienced admins. Docker install is recommended This install method assumes you already have ssl configured with certificates available
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- Install dependencies. On debian this could look like `apt install postgresql redis nginx python3-venv python3-pip python3-dev libpq-dev`
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups. Not all of these changes effect the dockerless install, however the `production` branch is still recommended
+
+Instructions for running BookWyrm in production without Docker:
+
+- Make and enter directory you want to install bookwyrm too. For example `/opt/bookwyrm`: `mkdir /opt/bookwyrm && cd /opt/bookwyrm`
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git ./`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `POSTGRES_HOST` | Set to `localhost` (the machine running your db)
+    - `POSTGRES_USER` | Set to `bookwyrm` (recommended) or something custom (configured later)
+    - `POSTGRES_DB` | Set to `bookwyrm`
+    - `REDIS_ACTIVITY_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_ACTIVITY_HOST` | Set to `localhost` (the machine running redis)
+    - `REDIS_BROKER_PASSWORD` | Set to nothing (fine on a local machine with a firewall)
+    - `REDIS_BROKER_HOST` | Set to `localhost` (the machine running redis)
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Copy the server_config to nginx's conf.d: `cp nginx/server_config /etc/nginx/conf.d/server_config`
+    - Make a copy of the production template config and set it for use in nginx: `cp nginx/production /etc/nginx/sites-available/bookwyrm.conf`
+    - Update nginx `bookwyrm.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - Replace `/app/` with your install directory `/opt/bookwyrm/` everywhere in the file (including commented out)
+        - Uncomment lines 18 to 67 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+        - Change the `ssl_certificate` and `ssl_certificate_key` paths to your fullchain and privkey locations
+        - Change line 4 so that it says `server localhost:8000`. You may choose a different port here if you wish
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+    - Enable the nginx config: `ln -s /etc/nginx/sites-available/bookwyrm.conf /etc/nginx/sites-enabled/bookwyrm.conf`
+     - Reload nginx: `systemctl reload nginx`
+- Setup the python virtual enviroment
+    - Make the python venv directory in your install dir: `mkdir venv` `python3 -m venv ./venv`
+    - Install bookwyrm python dependencies with pip: `./venv/bin/pip3 install -r requirements.txt`
+- Make the bookwyrm postgresql database. Make sure to change the password to what you set in the `.env` config:
+
+    `sudo -i -u postgres psql`
+
+```
+CREATE USER bookwyrm WITH PASSWORD 'securedbypassword123';
+
+CREATE DATABASE bookwyrm TEMPLATE template0 ENCODING 'UNICODE';
+
+ALTER DATABASE bookwyrm OWNER TO bookwyrm;
+
+GRANT ALL PRIVILEGES ON DATABASE bookwyrm TO bookwyrm;
+
+\q
+```
+
+- Migrate the database schema by running `venv/bin/python3 manage.py migrate`
+- Initialize the database by running `venv/bin/python3 manage.py initdb`
+- Create the static by running `venv/bin/python3 manage.py collectstatic --no-input`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Create and setup your `bookwyrm` user
+    - Make the system bookwyrm user: `useradd bookwyrm -r`
+    - Change the owner of your install directory to bookwyrm: `chown -R bookwyrm:bookwyrm /opt/bookwyrm`
+    - You should now run bookwyrm related commands as the bookwyrm user: `sudo -u bookwyrm echo I am the $(whoami) user`
+
+- Generate the admin code with `sudo -u bookwyrm venv/bin/python3 manage.py admin_code`, and copy the admin code to use when you create your admin account.
+- You can get your code at any time by re-running that command. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Make and configure the run script
+    - Make a file called dockerless-run.sh and fill it with the following contents
+
+``` { .sh }
+#!/bin/bash
+
+# stop if one process fails
+set -e
+
+# bookwyrm
+/opt/bookwyrm/venv/bin/gunicorn bookwyrm.wsgi:application --bind 0.0.0.0:8000 &
+
+# celery
+/opt/bookwyrm/venv/bin/celery -A celerywyrm worker -l info -Q high_priority,medium_priority,low_priority &
+/opt/bookwyrm/venv/bin/celery -A celerywyrm beat -l INFO --scheduler django_celery_beat.schedulers:DatabaseScheduler &
+# /opt/bookwyrm/venv/bin/celery -A celerywyrm flower &
+```
+    - Replace `/opt/bookwyrm` with your install dir
+    - Change `8000` to your custom port number
+    - Flower has been disabled here because it is not autoconfigured with the password set in the `.env` file
+- You can now run BookWyrm with: `sudo -u bookwyrm bash /opt/bookwyrm/dockerless-run.sh`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+- You may want to configure BookWyrm to autorun with a systemd service. Here is an example:
+```
+# /etc/systemd/system/bookwyrm.service
+[Unit]
+Description=Bookwyrm Server
+After=network.target
+After=systemd-user-sessions.service
+After=network-online.target
+
+[Service]
+User=bookwyrm
+Type=simple
+Restart=always
+ExecStart=/bin/bash /opt/bookwyrm/dockerless-run.sh
+WorkingDirectory=/opt/bookwyrm/
+
+[Install]
+WantedBy=multi-user.target
+```
+You will need to set up a Cron job for the service to start automatically on a server restart.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+## Get Involved
+
+See [Get Involved](https://joinbookwyrm.com/get-involved/) for details.
diff --git a/locale/zh_Hant/content/running_bookwyrm/install-prod.md b/locale/zh_Hant/content/running_bookwyrm/install-prod.md
new file mode 100644
index 00000000..acb1f813
--- /dev/null
+++ b/locale/zh_Hant/content/running_bookwyrm/install-prod.md
@@ -0,0 +1,97 @@
+- - -
+Title: Installing in Production Date: 2021-05-18 Order: 1
+- - -
+
+This project is still young and isn't, at the moment, very stable, so please proceed with caution when running in production.
+
+## Server setup
+- Get a domain name and set up DNS for your server. You'll need to point the nameservers of your domain on your DNS provider to the server where you'll be hosting BookWyrm. Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars)
+- Set your server up with appropriate firewalls for running a web application (this instruction set is tested against Ubuntu 20.04). Here are instructions for [DigitalOcean](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04)
+- Set up an email service (such as [Mailgun](https://documentation.mailgun.com/en/latest/quickstart.html)) and the appropriate SMTP/DNS settings. Use the service's documentation for configuring your DNS
+- [Install Docker and docker-compose](https://docs.docker.com/compose/install/)
+
+## Install and configure BookWyrm
+
+The `production` branch of BookWyrm contains a number of tools not on the `main` branch that are suited for running in production, such as `docker-compose` changes to update the default commands or configuration of containers, and individual changes to container config to enable things like SSL or regular backups.
+
+Instructions for running BookWyrm in production:
+
+- Get the application code: `git clone git@github.com:bookwyrm-social/bookwyrm.git`
+- Switch to the `production` branch: `git checkout production`
+- Create your environment variables file, `cp .env.example .env`, and update the following:
+    - `SECRET_KEY` | A difficult to guess, secret string of characters
+    - `DOMAIN` | Your web domain
+    - `EMAIL` | Email address to be used for certbot domain verification
+    - `POSTGRES_PASSWORD` | Set a secure password for the database
+    - `REDIS_ACTIVITY_PASSWORD` | Set a secure password for Redis Activity subsystem
+    - `REDIS_BROKER_PASSWORD` | Set a secure password for Redis queue broker subsystem
+    - `FLOWER_USER` | Your own username for accessing Flower queue monitor
+    - `FLOWER_PASSWORD` | Your own secure password for accessing Flower queue monitor
+    - `EMAIL_HOST_USER` | The "from" address that your app will use when sending email
+    - `EMAIL_HOST_PASSWORD` | The password provided by your email service
+- Configure nginx
+    - Make a copy of the production template config and set it for use in nginx `cp nginx/production nginx/default.conf`
+    - Update `nginx/default.conf`:
+        - Replace `your-domain.com` with your domain name everywhere in the file (including the lines that are currently commented out)
+        - If you aren't using the `www` subdomain, remove the www.your-domain.com version of the domain from the `server_name` in the first server block in `nginx/default.conf` and remove the `-d www.${DOMAIN}` flag at the end of the `certbot` command in `docker-compose.yml`.
+        - If you are running another web-server on your host machine, you will need to follow the [reverse-proxy instructions](/reverse-proxy.html)
+- Initialize the database by running `./bw-dev migrate`
+- Run the application (this should also set up a Certbot ssl cert for your domain) with `docker-compose up --build`, and make sure all the images build successfully
+    - If you are running other services on your host machine, you may run into errors where services fail when attempting to bind to a port. See the [troubleshooting guide](#port_conflicts) for advice on resolving this.
+- When docker has built successfully, stop the process with `CTRL-C`
+- Set up HTTPS redirect
+    - In `docker-compose.yml`, comment out the active certbot command, which installs the certificate, and uncomment the line below, which sets up automatically renewals.
+    - In `nginx/default.conf`, uncomment lines 18 through 50 to enable forwarding to HTTPS. You should have two `server` blocks enabled
+- Set up a `cron` job to keep your certificates up to date (Lets Encrypt certificates expire after 90 days)
+    - Type `crontab -e` to edit your cron file in the host machine
+    - add a line to try renewing once a day: `5 0 * * * cd /path/to/your/bookwyrm && docker-compose run --rm certbot`
+- If you wish to use an external storage for static assets and media files (such as an S3-compatible service), [follow the instructions](/external-storage.html) until it tells you to come back here
+- Initialize the application with `./bw-dev setup`, and copy the admin code to use when you create your admin account.
+    - The output of `./bw-dev setup` should conclude with your admin code. You can get your code at any time by running `./bw-dev admin_code` from the command line. Here's an example output:
+
+``` { .sh }
+*******************************************
+Use this code to create your admin account:
+c6c35779-af3a-4091-b330-c026610920d6
+*******************************************
+```
+
+- Run docker-compose in the background with: `docker-compose up -d`
+- The application should be running at your domain. When you load the domain, you should get a configuration page which confirms your instance settings, and a form to create an admin account. Use your admin code to register.
+
+Congrats! You did it!! Configure your instance however you'd like.
+
+
+## Backups
+
+BookWyrm's db service dumps a backup copy of its database to its `/backups` directory daily at midnight UTC. Backups are named `backup__%Y-%m-%d.sql`.
+
+The db service has an optional script for periodically pruning the backups directory so that all recent daily backups are kept, but for older backups, only weekly or monthly backups are kept. To enable this script:
+
+- Uncomment the final line in `postgres-docker/cronfile`
+- rebuild your instance `docker-compose up --build`
+
+You can copy backups from the backups volume to your host machine with `docker cp`:
+
+- Run `docker-compose ps` to confirm the db service's full name (it's probably `bookwyrm_db_1`.
+- Run `docker cp <container_name>:/backups <host machine path>`
+
+## Port Conflicts
+
+BookWyrm has multiple services that run on their default ports. This means that, depending on what else you are running on your host machine, you may run into errors when building or running BookWyrm when attempts to bind to those ports fail.
+
+If this occurs, you will need to change your configuration to run services on different ports. This may require one or more changes the following files:
+
+- `docker-compose.yml`
+- `nginx/default.conf`
+- `.env` (You create this file yourself during setup)
+
+If you are already running a web-server on your machine, you will need to set up a reverse-proxy.
+
+## Get Connected
+
+Because BookWyrm is a young project, we're still working towards a stable release schedule, and there are a lot of bugs and breaking changes. There is a GitHub team which can be tagged when there's something important to know about an update, which you can join by sharing your GitHub username. There are a few ways in get in touch:
+
+ - Open an issue or pull request to add your instance to the [official list](https://github.com/bookwyrm-social/documentation/blob/main/content/using_bookwyrm/instances.md)
+ - Reach out to the project on [Mastodon](https://tech.lgbt/@bookwyrm) or [email the maintainer](mailto:mousereeve@riseup.net) directly with your GitHub username
+ - Join the [Matrix](https://matrix.to/#/#bookwyrm:matrix.org) chat room
diff --git a/locale/zh_Hant/content/running_bookwyrm/moderation.md b/locale/zh_Hant/content/running_bookwyrm/moderation.md
new file mode 100644
index 00000000..e9d8cc0e
--- /dev/null
+++ b/locale/zh_Hant/content/running_bookwyrm/moderation.md
@@ -0,0 +1,21 @@
+- - -
+Title: Moderation Date: 2021-04-18 Order: 5
+- - -
+
+## Blocking
+Users have the option to block other users on their own, without a moderator intervening. From the "Federated Servers" admin view, administrators can see how many users from an instance have been blocked by local users.
+
+## Reports
+Users can report statuses or users from the "more options" menu in the footer of posts and the follow/unfollow buttons for users. When a report is made, all users with admin permissions will receive a notification.
+
+When a report is made, there are a few options how the moderator can respond.
+- Send a direct message to the reported user.
+- Delete the reported status.
+- Deactivate the user. For local users, this will make them unable to log in, and their account will not be shown in the application. For remote users, the server will reject any incoming activities from this user, and they will not be shown in searches.
+
+## Instance-level moderation
+Moderators can block entire instances. This will prevent any activities from coming in from that instance, and deactivate all accounts from that instance locally.
+
+If the instance is un-blocked, all the users who were deactivated by the block will be re-activated.
+
+Moderators can also upload blocklists to block servers in bulk.
diff --git a/locale/zh_Hant/content/running_bookwyrm/monitoring-queue.md b/locale/zh_Hant/content/running_bookwyrm/monitoring-queue.md
new file mode 100644
index 00000000..8cc18339
--- /dev/null
+++ b/locale/zh_Hant/content/running_bookwyrm/monitoring-queue.md
@@ -0,0 +1,21 @@
+---
+Title: Monitoring Queue
+Date: 2022-11-23
+Order: 6
+---
+
+There might be occurences where your instances behaves slowly. One option would be to inspect the queue to see, whether some jobs hang. Read on to learn how.
+
+## Celery
+
+BookWyrm is using [Celery](https://docs.celeryq.dev/en/stable/) to manage background jobs.
+
+## Flower
+
+To watch Celery jobs in real-time BookWyrm uses [Flower](https://flower.readthedocs.io/en/latest/).
+
+In case you haven't tweaked the [`docker-compose.yml`](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/docker-compose.yml#L87-L100) you can find the service on [port 8888](https://github.com/bookwyrm-social/bookwyrm/blob/dc14670a2ca7553317528d3384146d79df1f7413/.env.example#L42-L45). That is: `https://MY_DOMAIN_NAME:8888/`.
+
+### Tasks
+
+You can find [`@app.task` annotated](https://github.com/bookwyrm-social/bookwyrm/search?q=%40app.task) tasks in the codebase.
diff --git a/locale/zh_Hant/content/running_bookwyrm/optional_features.md b/locale/zh_Hant/content/running_bookwyrm/optional_features.md
new file mode 100644
index 00000000..cf0b858f
--- /dev/null
+++ b/locale/zh_Hant/content/running_bookwyrm/optional_features.md
@@ -0,0 +1,54 @@
+- - -
+Title: Optional features Date: 2021-08-02 Order: 8
+- - -
+
+Some features of BookWyrm have to be enabled to work.
+
+## Preview image generation
+
+By default, BookWyrm uses the instance's logo (or the default logo) as an OpenGraph preview image. As an alternative, you can enable the generation of preview images for books, users, and the website.
+
+The preview images will be sized for large OpenGraph images (used by Twitter under the name of `summary_large_image`). Depending on the type of image, the contents will be:
+
+- the default instance image will display the big logo, along with the name of the instance and its url
+- the user image will display their avatar, display name, handle (in the form of username@instance)
+- the book image will display their cover, title, subtitle (if present), author and rating (if present)
+
+These images will be updated at various points:
+
+- instance image: when the instance name or big logo are changed
+- user image: when the display name or avatar are changed
+- book image: when the title(s), author(s) or cover are changed, or when a new rating is added
+
+### Enabling preview images
+
+In order to enable the feature with default settings, you have to uncomment (remove the `#` in front of) the line `ENABLE_PREVIEW_IMAGES=true` in your `.env` file. All the new updating events aforementioned will cause the generation of the corresponding image.
+
+Examples for these images can be viewed on the [feature’s pull request’s description](https://github.com/bookwyrm-social/bookwyrm/pull/1142#pullrequest-651683886-permalink).
+
+### Generating preview images
+
+If you enable this setting after your instance has been started, some images may not have been generated. A command has been added to automate the image generation. In order to prevent a ressource hog by generating **A LOT** of images, you have to pass the argument `--all` (or `-a`) to start the generation of the preview images for all users and books. Without this argument, only the site preview will be generated.
+
+User and book preview images will be generated asynchroneously: the task will be sent to Flower. Some time may be needed before all the books and users have a working preview image. If you have a good book 📖, a kitten 🐱 or a cake 🍰, this is the perfect time to show them some attention 💖.
+
+### Optional settings
+
+So you want to customize your preview images? Here are the options:
+
+- `PREVIEW_BG_COLOR` will set the color for the preview image background. You can supply a color value, like `#b00cc0`, or the following values `use_dominant_color_light` or `use_dominant_color_dark`. These will extract a dominant color from the book cover and use it, in a light or a dark theme respectively.
+- `PREVIEW_TEXT_COLOR` will set the color for the text. Depending on the choice for the background color, you should find a value that will have a sufficient contrast for the image to be accessible. A contrast ratio of 1:4.5 is recommended.
+- `PREVIEW_IMG_WIDTH` and `PREVIEW_IMG_HEIGHT` will set the dimensions of the image. Currently, the system will work best on images with a landscape (horizontal) orientation.
+- `PREVIEW_DEFAULT_COVER_COLOR` will set the color for books without covers.
+
+All the color variables accept values that can be recognized as colors by Pillow’s `ImageColor` module: [Learn more about Pillow color names](https://pillow.readthedocs.io/en/stable/reference/ImageColor.html#color-names).
+
+### Removing preview images for remote users
+
+Prior to BookWyrm 0.5.4, preview images were generated for remote users. As it was wasteful in terms of disk space and computing power, that generation has been stopped. If you wish to delete in bulk all the images that were previously generated for remote users, a new command was added:
+
+```sh
+./bw-dev remove_remote_user_preview_images
+```
+
+That command will empty the `user.preview_image` property in the database for remote users, and delete the file in storage.
diff --git a/locale/zh_Hant/content/running_bookwyrm/reverse-proxy.md b/locale/zh_Hant/content/running_bookwyrm/reverse-proxy.md
new file mode 100644
index 00000000..2903028a
--- /dev/null
+++ b/locale/zh_Hant/content/running_bookwyrm/reverse-proxy.md
@@ -0,0 +1,110 @@
+- - -
+Title: Using a Reverse-Proxy Date: 2021-05-11 Order: 4
+- - -
+
+## Running BookWyrm Behind a Reverse-Proxy
+If you are running another web-server on your machine, you should have it handle proxying web requests to BookWyrm.
+
+The default BookWyrm configuration already has an nginx server that proxies requests to the django app that handles SSL and directly serves static files. The static files are stored in a Docker volume that several BookWyrm services access, so it is not recommended to remove this server completely.
+
+To run BookWyrm behind a reverse-proxy, make the following changes:
+
+- In `nginx/default.conf`:
+    - Comment out the two default servers
+    - Uncomment the server labeled Reverse-Proxy server
+    - Replace `your-domain.com` with your domain name
+- In `docker-compose.yml`:
+    - In `services` -> `nginx` -> `ports`, comment out the default ports and add `- 8001:8001`
+    - In `services` -> `nginx` -> `volumes`, comment out the two volumes that begin `./certbot/`
+    - In `services`, comment out the `certbot` service
+
+At this point, you can follow, the [setup](#server-setup) instructions as listed. Once docker is running, you can access your BookWyrm instance at `http://localhost:8001` (**NOTE:** your server is not accessible over `https`).
+
+Steps for setting up a reverse-proxy are server dependent.
+
+#### Nginx
+
+Before you can set up nginx, you will need to locate your nginx configuration directory, which is dependent on your platform and how you installed nginx. See [nginx's guide](http://nginx.org/en/docs/beginners_guide.html) for details.
+
+To set up your server:
+
+- In you `nginx.conf` file, ensure that `include servers/*;` isn't commented out.
+- In your nginx `servers` directory, create a new file named after your domain containing the following information:
+
+``` { .nginx }
+server {
+    server_name your-domain.com www.your-domain.com;
+
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    listen [::]:80 ssl;
+    listen 80 ssl;
+}
+```
+
+To set up with an ssl block:
+``` { .nginx }
+server {
+    server_name your.domain;
+
+    listen [::]:80;
+    listen 80;
+    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains" always;
+    rewrite ^ https://$server_name$request_uri;
+    location / { return 301 https://$host$request_uri; }
+}
+
+# SSL code
+ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem;
+ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem;
+
+server {
+    listen [::]:443 ssl http2;
+    listen 443 ssl http2;
+
+    server_name your.domain;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /images/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+
+    location /static/ {
+        proxy_pass http://localhost:8001;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header Host $host;
+    }
+}
+```
+- run `sudo certbot run --nginx --email YOUR_EMAIL -d your-domain.com -d www.your-domain.com`
+- restart nginx
+
+If everything worked correctly, your BookWyrm instance should now be externally accessible.
+
+*Note: the `proxy_set_header Host $host;` is essential; if you do not include it, incoming messages from federated servers will be rejected.*
+
+*Note: the location of the ssl certificates may vary depending on the OS of your server*
+
diff --git a/locale/zh_Hant/content/running_bookwyrm/updating.md b/locale/zh_Hant/content/running_bookwyrm/updating.md
new file mode 100644
index 00000000..6dceee3b
--- /dev/null
+++ b/locale/zh_Hant/content/running_bookwyrm/updating.md
@@ -0,0 +1,27 @@
+- - -
+Title: Updating Your Instance Date: 2022-11-17 Order: 3
+- - -
+
+When there are changes available in the production branch, you can install and get them running on your instance using the command `./bw-dev update`. This does a number of things:
+
+- `git pull` gets the updated code from the git repository. If there are conflicts, you may need to run `git pull` separately and resolve the conflicts before trying the `./bw-dev update` script again.
+- `docker-compose build` rebuilds the images, which ensures that the correct packages are installed. This step takes a long time and is only needed when the dependencies (including pip `requirements.txt` packages) have changed, so you can comment it out if you want a quicker update path and don't mind un-commenting it as needed.
+- `docker-compose run --rm web python manage.py migrate` runs the database migrations in Django using the newly built Docker images
+- `docker-compose run --rm web python manage.py collectstatic --no-input` loads any updated static files (such as the JavaScript and CSS)
+- `docker-compose down; docker-compose up -d` will restart all the docker containers and make use of the newly built images (Attention: downtime during the restart)
+
+## Re-building activity streams
+
+Feeds for each user are stored in Redis. To re-populate a stream, use the management command:
+
+``` { .sh }
+./bw-dev populate_streams
+# Or use docker-compose directly
+docker-compose run --rm web python manage.py populate_streams
+```
+
+If something has gone terribly awry, the stream data can be deleted.
+
+``` { .sh }
+docker-compose run --rm web python manage.py erase_streams
+```
diff --git a/locale/zh_Hant/content/using_bookwyrm/adding-books.md b/locale/zh_Hant/content/using_bookwyrm/adding-books.md
new file mode 100644
index 00000000..d27984ce
--- /dev/null
+++ b/locale/zh_Hant/content/using_bookwyrm/adding-books.md
@@ -0,0 +1,20 @@
+---
+Title: Adding Books
+Date: 2022-07-29
+Order: 2
+---
+
+There are a few different ways to add books to your BookWyrm instance! When you can't find the book you're looking for, try these options in order -- it's better to import a book than to create one from scratch.
+
+## Loading books from other catalogs
+
+If the book you're looking for isn't available on your instance, there are a few different ways to add it. The best way is to import it from an outside source -- your instance can load books from other BookWyrm instances, as well as [OpenLibrary](http://openlibrary.org/) and [Inventaire](http://inventaire.io/). If there are no search results for your query, these sources will automatically be queried, and will show up with a button to "**Import book**". If there are local search results that aren't what you're looking for, you can click the "**Load results from other catalogues**" link to load more results.
+
+
+## Adding another edition
+
+If you found the book you want, but not the right edition, you can add another edition to the work from the list of editions. Click the link below the description that tells you how many editions there are (for example, "**4 editions**"). At the bottom of the editions list, there is a button to "**Add another edition**".
+
+## Add a completely new book
+
+Once you've tried searching for your book, importing it from another catalog, and finding other editions of the book, you can add a new book manually. The link to manually add a book is at the bottom of the search page when external catalogs are shown. You can also navigate direclty to `/create-book` on your instance.
diff --git a/locale/zh_Hant/content/using_bookwyrm/posting-statuses.md b/locale/zh_Hant/content/using_bookwyrm/posting-statuses.md
new file mode 100644
index 00000000..a92845c8
--- /dev/null
+++ b/locale/zh_Hant/content/using_bookwyrm/posting-statuses.md
@@ -0,0 +1,40 @@
+- - -
+Title: Posting statuses Date: 2022-04-30 Order: 1
+- - -
+
+Posting on BookWyrm starts with a book. Users can comment on in-progress or recently read books from the "Your books" section, or from a book's landing page. From there, users can reply and start a conversation. BookWyrm posts can include formatting like bold, italics and links using [Markdown](https://www.markdownguide.org/cheat-sheet/).
+
+If you're familiar with [posting on Mastodon](https://docs.joinmastodon.org/user/posting/), you'll find that BookWyrm statuses have analogous visibility settings, content warnings, and mentions. However, polls, custom emoji, and attachments are not supported yet.
+
+## Types of statuses
+
+### User commentary
+
+There are three types of posts users can create directly in response to books: reviews, comments, and quotes. Comments respond to general aspects of a book, quotes pertain to specific passages, and reviews deal with books overall. Users can also reply to statuses.
+
+| Component     | Review | Comment | Quote | Reply |
+| ------------- | ------ | ------- | ----- | ----- |
+| Text field    | ✔      | ✔       | ✔     | ✔     |
+| Spoiler alert | ✔      | ✔       | ✔     | ✔     |
+| Page number   |        | ✔       | ✔     |       |
+| Quote         |        |         | ✔     |       |
+| Rating        | ✔      |         |       |       |
+| Title field   | ✔      |         |       |       |
+
+
+### Reading status updates
+
+Statuses are generated when a user indicates that they want to read, have started reading, or have finished reading a book.
+
+## Text
+Text can include:
+
+- Mentions (@user)
+- URLs (`http(s)://` is not displayed)
+- Some [Markdown formatting](https://www.markdownguide.org/cheat-sheet/)
+  - bold
+  - italics
+  - block quotes
+  - bullet lists
+  - links
+
diff --git a/lt/locale/lt_LT/content/codebase/_meta.yml b/lt/locale/lt_LT/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/lt/locale/lt_LT/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/lt/locale/lt_LT/content/contributing/_meta.yml b/lt/locale/lt_LT/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/lt/locale/lt_LT/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/lt/locale/lt_LT/content/running_bookwyrm/_meta.yml b/lt/locale/lt_LT/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/lt/locale/lt_LT/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/lt/locale/lt_LT/content/using_bookwyrm/_meta.yml b/lt/locale/lt_LT/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/lt/locale/lt_LT/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/nl/locale/nl_NL/content/codebase/_meta.yml b/nl/locale/nl_NL/content/codebase/_meta.yml
new file mode 100644
index 00000000..6a37fcd6
--- /dev/null
+++ b/nl/locale/nl_NL/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Broncode
+order: 4
diff --git a/nl/locale/nl_NL/content/contributing/_meta.yml b/nl/locale/nl_NL/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/nl/locale/nl_NL/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/nl/locale/nl_NL/content/running_bookwyrm/_meta.yml b/nl/locale/nl_NL/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/nl/locale/nl_NL/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/nl/locale/nl_NL/content/using_bookwyrm/_meta.yml b/nl/locale/nl_NL/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..8f8a10d7
--- /dev/null
+++ b/nl/locale/nl_NL/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: BookWyrm gebruiken
+order: 1
diff --git a/no/locale/no_NO/content/codebase/_meta.yml b/no/locale/no_NO/content/codebase/_meta.yml
new file mode 100644
index 00000000..8bb78265
--- /dev/null
+++ b/no/locale/no_NO/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Kodebase
+order: 4
diff --git a/no/locale/no_NO/content/contributing/_meta.yml b/no/locale/no_NO/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/no/locale/no_NO/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/no/locale/no_NO/content/running_bookwyrm/_meta.yml b/no/locale/no_NO/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/no/locale/no_NO/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/no/locale/no_NO/content/using_bookwyrm/_meta.yml b/no/locale/no_NO/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/no/locale/no_NO/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/ou/locale/en_Oulipo/content/codebase/_meta.yml b/ou/locale/en_Oulipo/content/codebase/_meta.yml
new file mode 100644
index 00000000..fef34ba3
--- /dev/null
+++ b/ou/locale/en_Oulipo/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Programming
+order: 4
diff --git a/ou/locale/en_Oulipo/content/contributing/_meta.yml b/ou/locale/en_Oulipo/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/ou/locale/en_Oulipo/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/ou/locale/en_Oulipo/content/running_bookwyrm/_meta.yml b/ou/locale/en_Oulipo/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/ou/locale/en_Oulipo/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/ou/locale/en_Oulipo/content/using_bookwyrm/_meta.yml b/ou/locale/en_Oulipo/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/ou/locale/en_Oulipo/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/pl/locale/pl_PL/content/codebase/_meta.yml b/pl/locale/pl_PL/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/pl/locale/pl_PL/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/pl/locale/pl_PL/content/contributing/_meta.yml b/pl/locale/pl_PL/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/pl/locale/pl_PL/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/pl/locale/pl_PL/content/running_bookwyrm/_meta.yml b/pl/locale/pl_PL/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/pl/locale/pl_PL/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/pl/locale/pl_PL/content/using_bookwyrm/_meta.yml b/pl/locale/pl_PL/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..c6d571b5
--- /dev/null
+++ b/pl/locale/pl_PL/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Korzystanie z BookWyrm
+order: 1
diff --git a/pt-BR/locale/pt_BR/content/codebase/_meta.yml b/pt-BR/locale/pt_BR/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/pt-BR/locale/pt_BR/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/pt-BR/locale/pt_BR/content/contributing/_meta.yml b/pt-BR/locale/pt_BR/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/pt-BR/locale/pt_BR/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/pt-BR/locale/pt_BR/content/running_bookwyrm/_meta.yml b/pt-BR/locale/pt_BR/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/pt-BR/locale/pt_BR/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/pt-BR/locale/pt_BR/content/using_bookwyrm/_meta.yml b/pt-BR/locale/pt_BR/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/pt-BR/locale/pt_BR/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/pt-PT/locale/pt_PT/content/codebase/_meta.yml b/pt-PT/locale/pt_PT/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/pt-PT/locale/pt_PT/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/pt-PT/locale/pt_PT/content/contributing/_meta.yml b/pt-PT/locale/pt_PT/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/pt-PT/locale/pt_PT/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/pt-PT/locale/pt_PT/content/running_bookwyrm/_meta.yml b/pt-PT/locale/pt_PT/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/pt-PT/locale/pt_PT/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/pt-PT/locale/pt_PT/content/using_bookwyrm/_meta.yml b/pt-PT/locale/pt_PT/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/pt-PT/locale/pt_PT/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/ro/locale/ro_RO/content/codebase/_meta.yml b/ro/locale/ro_RO/content/codebase/_meta.yml
new file mode 100644
index 00000000..f1b7a161
--- /dev/null
+++ b/ro/locale/ro_RO/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Bază de cod
+order: 4
diff --git a/ro/locale/ro_RO/content/contributing/_meta.yml b/ro/locale/ro_RO/content/contributing/_meta.yml
new file mode 100644
index 00000000..0d7fa8c3
--- /dev/null
+++ b/ro/locale/ro_RO/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contribuiți
+order: 3
diff --git a/ro/locale/ro_RO/content/running_bookwyrm/_meta.yml b/ro/locale/ro_RO/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b2b6d76f
--- /dev/null
+++ b/ro/locale/ro_RO/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Rulați BookWyrm
+order: 2
diff --git a/ro/locale/ro_RO/content/using_bookwyrm/_meta.yml b/ro/locale/ro_RO/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..4c47e8fe
--- /dev/null
+++ b/ro/locale/ro_RO/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Folosiți BookWyrm
+order: 1
diff --git a/ru/locale/ru_RU/content/codebase/_meta.yml b/ru/locale/ru_RU/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/ru/locale/ru_RU/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/ru/locale/ru_RU/content/contributing/_meta.yml b/ru/locale/ru_RU/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/ru/locale/ru_RU/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/ru/locale/ru_RU/content/running_bookwyrm/_meta.yml b/ru/locale/ru_RU/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/ru/locale/ru_RU/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/ru/locale/ru_RU/content/using_bookwyrm/_meta.yml b/ru/locale/ru_RU/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/ru/locale/ru_RU/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/sl/locale/sl_SI/content/codebase/_meta.yml b/sl/locale/sl_SI/content/codebase/_meta.yml
new file mode 100644
index 00000000..4c384159
--- /dev/null
+++ b/sl/locale/sl_SI/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Kodna baza
+order: 4
diff --git a/sl/locale/sl_SI/content/contributing/_meta.yml b/sl/locale/sl_SI/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/sl/locale/sl_SI/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/sl/locale/sl_SI/content/running_bookwyrm/_meta.yml b/sl/locale/sl_SI/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/sl/locale/sl_SI/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/sl/locale/sl_SI/content/using_bookwyrm/_meta.yml b/sl/locale/sl_SI/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/sl/locale/sl_SI/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/sr/locale/sr_SP/content/codebase/_meta.yml b/sr/locale/sr_SP/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/sr/locale/sr_SP/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/sr/locale/sr_SP/content/contributing/_meta.yml b/sr/locale/sr_SP/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/sr/locale/sr_SP/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/sr/locale/sr_SP/content/running_bookwyrm/_meta.yml b/sr/locale/sr_SP/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/sr/locale/sr_SP/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/sr/locale/sr_SP/content/using_bookwyrm/_meta.yml b/sr/locale/sr_SP/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/sr/locale/sr_SP/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/sv-SE/locale/sv_SE/content/codebase/_meta.yml b/sv-SE/locale/sv_SE/content/codebase/_meta.yml
new file mode 100644
index 00000000..d5ec5864
--- /dev/null
+++ b/sv-SE/locale/sv_SE/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Kodbas
+order: 4
diff --git a/sv-SE/locale/sv_SE/content/contributing/_meta.yml b/sv-SE/locale/sv_SE/content/contributing/_meta.yml
new file mode 100644
index 00000000..5335b1c9
--- /dev/null
+++ b/sv-SE/locale/sv_SE/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Bidra
+order: 3
diff --git a/sv-SE/locale/sv_SE/content/running_bookwyrm/_meta.yml b/sv-SE/locale/sv_SE/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..9bb0b8f6
--- /dev/null
+++ b/sv-SE/locale/sv_SE/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Köra BookWyrm
+order: 2
diff --git a/sv-SE/locale/sv_SE/content/using_bookwyrm/_meta.yml b/sv-SE/locale/sv_SE/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..25c9a8bc
--- /dev/null
+++ b/sv-SE/locale/sv_SE/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Använda BookWyrm
+order: 1
diff --git a/tr/locale/tr_TR/content/codebase/_meta.yml b/tr/locale/tr_TR/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/tr/locale/tr_TR/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/tr/locale/tr_TR/content/contributing/_meta.yml b/tr/locale/tr_TR/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/tr/locale/tr_TR/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/tr/locale/tr_TR/content/running_bookwyrm/_meta.yml b/tr/locale/tr_TR/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/tr/locale/tr_TR/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/tr/locale/tr_TR/content/using_bookwyrm/_meta.yml b/tr/locale/tr_TR/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/tr/locale/tr_TR/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/uk/locale/uk_UA/content/codebase/_meta.yml b/uk/locale/uk_UA/content/codebase/_meta.yml
new file mode 100644
index 00000000..3b77f45d
--- /dev/null
+++ b/uk/locale/uk_UA/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Кодова база
+order: 4
diff --git a/uk/locale/uk_UA/content/contributing/_meta.yml b/uk/locale/uk_UA/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/uk/locale/uk_UA/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/uk/locale/uk_UA/content/running_bookwyrm/_meta.yml b/uk/locale/uk_UA/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/uk/locale/uk_UA/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/uk/locale/uk_UA/content/using_bookwyrm/_meta.yml b/uk/locale/uk_UA/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/uk/locale/uk_UA/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/vi/locale/vi_VN/content/codebase/_meta.yml b/vi/locale/vi_VN/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/vi/locale/vi_VN/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/vi/locale/vi_VN/content/contributing/_meta.yml b/vi/locale/vi_VN/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/vi/locale/vi_VN/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/vi/locale/vi_VN/content/running_bookwyrm/_meta.yml b/vi/locale/vi_VN/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/vi/locale/vi_VN/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/vi/locale/vi_VN/content/using_bookwyrm/_meta.yml b/vi/locale/vi_VN/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/vi/locale/vi_VN/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1
diff --git a/zh-CN/locale/zh_Hans/content/codebase/_meta.yml b/zh-CN/locale/zh_Hans/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/zh-CN/locale/zh_Hans/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/zh-CN/locale/zh_Hans/content/contributing/_meta.yml b/zh-CN/locale/zh_Hans/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/zh-CN/locale/zh_Hans/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/zh-CN/locale/zh_Hans/content/running_bookwyrm/_meta.yml b/zh-CN/locale/zh_Hans/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/zh-CN/locale/zh_Hans/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/zh-CN/locale/zh_Hans/content/using_bookwyrm/_meta.yml b/zh-CN/locale/zh_Hans/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..c5b04260
--- /dev/null
+++ b/zh-CN/locale/zh_Hans/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: 使用 BookWrym
+order: 1
diff --git a/zh-TW/locale/zh_Hant/content/codebase/_meta.yml b/zh-TW/locale/zh_Hant/content/codebase/_meta.yml
new file mode 100644
index 00000000..e06a4d84
--- /dev/null
+++ b/zh-TW/locale/zh_Hant/content/codebase/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Codebase
+order: 4
diff --git a/zh-TW/locale/zh_Hant/content/contributing/_meta.yml b/zh-TW/locale/zh_Hant/content/contributing/_meta.yml
new file mode 100644
index 00000000..314fa661
--- /dev/null
+++ b/zh-TW/locale/zh_Hant/content/contributing/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Contributing
+order: 3
diff --git a/zh-TW/locale/zh_Hant/content/running_bookwyrm/_meta.yml b/zh-TW/locale/zh_Hant/content/running_bookwyrm/_meta.yml
new file mode 100644
index 00000000..ae2b301e
--- /dev/null
+++ b/zh-TW/locale/zh_Hant/content/running_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Running BookWyrm
+order: 2
diff --git a/zh-TW/locale/zh_Hant/content/using_bookwyrm/_meta.yml b/zh-TW/locale/zh_Hant/content/using_bookwyrm/_meta.yml
new file mode 100644
index 00000000..b05d2b24
--- /dev/null
+++ b/zh-TW/locale/zh_Hant/content/using_bookwyrm/_meta.yml
@@ -0,0 +1,3 @@
+---
+title: Using BookWyrm
+order: 1