deploy versions

Author: BookWyrm Bot

locale/de_DE/LC_MESSAGES/messages.mo

@@ -144,10 +144,7 @@ Locales for the language dropdown are listed in `i18n.py`. Generally we wait for
 
 When a new version of BookWyrm is released we need to create a new version of the docs:
 
-1. Add a new branch with a name exactly matching the new version tag in BookWyrm. e.g. `v0.8.0`.
-
-2. Add that branch name to the list of versions in `generate.py` in the `main` branch of the docs
-
-3. Check out every other version in turn, and merge the updated generation file into it so they all have the new branch listed: `git checkout main generate.py`. Then commit this change, create a PR to merge this change into the version's branch in the docs, and merge it. This will ensure that all pages in all versions of the docs have every other version listed in the dropdown menu.
-
-4. Merge the change in the `main` branch last - only merges into `main` trigger the GitHub action to deploy to the docs web server so if you do this first, the changes in other branches will have no effect.
+1. Add a new branch with a name exactly matching the new version tag in BookWyrm. e.g. `v0.x.y`.
+2. Add that branch name to the list of versions in `generate.py`, and push your new branch to the repository.
+3. Check out every other version in turn, and merge the updated `generate.py` file into it so they all have the new branch listed: `git checkout v0.x.y generate.py`. Then commit this change, create a PR to merge this change into the version's branch in the docs, and merge it. This will ensure that all pages in all versions of the docs have every other version listed in the dropdown menu.
+4. Merge the new `generate.py` in the `main` branch last - only merges into `main` trigger the GitHub action to deploy to the docs web server so if you do this first, the changes in other branches will have no effect until next time you update `main`.

locale/de_DE/content/contributing/documentation.md

@@ -0,0 +1,51 @@
+---
+Title: Management Commands
+Date: 2023-04-26
+Order: 11
+---
+
+In the `bookwyrm/management/commands` directory there are some commands to manipulate the instance’s database. Some of them are documented here.
+
+## Merging objects
+
+Quite often an instance will end up with duplicate books and authors or editions that appear as separate books when they are actually just different editions of the same work. This can happen because of importing editions that don’t have shared identifiers or from user mistakes. There also was a bug prior to version 0.7.5 which created a large number of duplicate books, editions, and authors. Sadly there’s no user interface to correct this for the time being, but in cases where the books are important for your instance you can use these management commands to fix some of the problems if you are using at least version 0.6.2.
+
+Please take extra care when using these commands because if you make a mistake there’s no way to undo it.
+
+### Merging editions
+
+If an edition of a book appears twice in the database and you are sure they are actually both referring to same edition, you can combine them into one with a command like this:
+
+```
+./bw-dev runweb python manage.py merge_editions --canonical=27 --other=38
+```
+
+This will copy any missing information from edition 38 (the “other” edition) over to edition 27 (the “canonical” edition) and then delete the other edition. If any field of information is in both editions then the data from the canonical edition will be kept. If the other edition is in any lists or has any comments or reviews etc then these will all be updated to point to the canonical edition instead.
+
+You can find the numbers to use in the command by visiting the page for a book and looking at the number in the URL.
+
+### Merging authors
+
+You can identify potential duplicate authors with `show_duplicate_authors`:
+
+```sh
+./bw-dev runweb python manage.py show_duplicate_authors
+```
+
+This will list all your _potential_ duplicate author records, based purely on their name, showing their birth and death dates if available, the count of books for each author, and a link to their page on your instance. Note that **you must check that these are actually duplicates** before merging them as they may be different authors with the same name.
+
+Once confirmed, if an author is duplicated you can combine the two authors into one with a command like this:
+
+```sh
+./bw-dev runweb python manage.py merge_authors --canonical=7 --other=46
+```
+
+As for the editions, any extra information from the other author will be copied over to the canonical author and then the other author will be deleted. Any books written by the other author will be changed to be written by the canonical author. You can find the numbers to use in the command by visiting the page for an author and looking at the number in the URL.
+
+## Fixing ISBNs
+
+There was a bug in `v0.8.0` which erroneously created 11-digit ISBN10 entries in some circumstances. This was fixed in a data migration in `v0.8.1`, however for various reasons you may need to manually run a cleanup command to fix any incorrect ISBNs in your local database:
+
+```sh
+./bw-dev runweb python manage.py fix_isbn10_entries
+```

locale/de_DE/content/running_bookwyrm/management-commands.md

@@ -144,10 +144,7 @@ Locales for the language dropdown are listed in `i18n.py`. Generally we wait for
 
 When a new version of BookWyrm is released we need to create a new version of the docs:
 
-1. Add a new branch with a name exactly matching the new version tag in BookWyrm. e.g. `v0.8.0`.
-
-2. Add that branch name to the list of versions in `generate.py` in the `main` branch of the docs
-
-3. Check out every other version in turn, and merge the updated generation file into it so they all have the new branch listed: `git checkout main generate.py`. Then commit this change, create a PR to merge this change into the version's branch in the docs, and merge it. This will ensure that all pages in all versions of the docs have every other version listed in the dropdown menu.
-
-4. Merge the change in the `main` branch last - only merges into `main` trigger the GitHub action to deploy to the docs web server so if you do this first, the changes in other branches will have no effect.
+1. Add a new branch with a name exactly matching the new version tag in BookWyrm. e.g. `v0.x.y`.
+2. Add that branch name to the list of versions in `generate.py`, and push your new branch to the repository.
+3. Check out every other version in turn, and merge the updated `generate.py` file into it so they all have the new branch listed: `git checkout v0.x.y generate.py`. Then commit this change, create a PR to merge this change into the version's branch in the docs, and merge it. This will ensure that all pages in all versions of the docs have every other version listed in the dropdown menu.
+4. Merge the new `generate.py` in the `main` branch last - only merges into `main` trigger the GitHub action to deploy to the docs web server so if you do this first, the changes in other branches will have no effect until next time you update `main`.

locale/en_Oulipo/LC_MESSAGES/messages.mo

@@ -0,0 +1,51 @@
+---
+Title: Management Commands
+Date: 2023-04-26
+Order: 11
+---
+
+In the `bookwyrm/management/commands` directory there are some commands to manipulate the instance’s database. Some of them are documented here.
+
+## Merging objects
+
+Quite often an instance will end up with duplicate books and authors or editions that appear as separate books when they are actually just different editions of the same work. This can happen because of importing editions that don’t have shared identifiers or from user mistakes. There also was a bug prior to version 0.7.5 which created a large number of duplicate books, editions, and authors. Sadly there’s no user interface to correct this for the time being, but in cases where the books are important for your instance you can use these management commands to fix some of the problems if you are using at least version 0.6.2.
+
+Please take extra care when using these commands because if you make a mistake there’s no way to undo it.
+
+### Merging editions
+
+If an edition of a book appears twice in the database and you are sure they are actually both referring to same edition, you can combine them into one with a command like this:
+
+```
+./bw-dev runweb python manage.py merge_editions --canonical=27 --other=38
+```
+
+This will copy any missing information from edition 38 (the “other” edition) over to edition 27 (the “canonical” edition) and then delete the other edition. If any field of information is in both editions then the data from the canonical edition will be kept. If the other edition is in any lists or has any comments or reviews etc then these will all be updated to point to the canonical edition instead.
+
+You can find the numbers to use in the command by visiting the page for a book and looking at the number in the URL.
+
+### Merging authors
+
+You can identify potential duplicate authors with `show_duplicate_authors`:
+
+```sh
+./bw-dev runweb python manage.py show_duplicate_authors
+```
+
+This will list all your _potential_ duplicate author records, based purely on their name, showing their birth and death dates if available, the count of books for each author, and a link to their page on your instance. Note that **you must check that these are actually duplicates** before merging them as they may be different authors with the same name.
+
+Once confirmed, if an author is duplicated you can combine the two authors into one with a command like this:
+
+```sh
+./bw-dev runweb python manage.py merge_authors --canonical=7 --other=46
+```
+
+As for the editions, any extra information from the other author will be copied over to the canonical author and then the other author will be deleted. Any books written by the other author will be changed to be written by the canonical author. You can find the numbers to use in the command by visiting the page for an author and looking at the number in the URL.
+
+## Fixing ISBNs
+
+There was a bug in `v0.8.0` which erroneously created 11-digit ISBN10 entries in some circumstances. This was fixed in a data migration in `v0.8.1`, however for various reasons you may need to manually run a cleanup command to fix any incorrect ISBNs in your local database:
+
+```sh
+./bw-dev runweb python manage.py fix_isbn10_entries
+```

locale/en_Oulipo/content/contributing/documentation.md

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-07-05 04:19+0000\n"
+"POT-Creation-Date: 2026-01-18 03:41+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -56,51 +56,66 @@ msgstr ""
 #: templates/layout.html:47 templates/layout.html:124 templates/layout.html:51
 #: templates/layout.html:130 templates/layout.html:52 templates/layout.html:131
 #: templates/layout.html:137 templates/layout.html:35 templates/layout.html:138
+#: templates/layout.html:149
 msgid "Documentation"
 msgstr ""
 
 #: templates/layout.html:95 templates/layout.html:101 templates/layout.html:102
 #: templates/layout.html:108 templates/layout.html:109
+#: templates/layout.html:120
 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 templates/layout.html:105
 #: templates/layout.html:111 templates/layout.html:112
+#: templates/layout.html:123
 msgid "Support BookWyrm on <a href='https://www.patreon.com/bookwyrm' target='_blank'>Patreon</a>."
 msgstr ""
 
 #: templates/layout.html:102 templates/layout.html:108
 #: templates/layout.html:109 templates/layout.html:115
-#: templates/layout.html:116
+#: templates/layout.html:116 templates/layout.html:127
 msgid "Get Involved"
 msgstr ""
 
 #: templates/layout.html:104 templates/layout.html:110
 #: templates/layout.html:111 templates/layout.html:117
-#: templates/layout.html:118
+#: templates/layout.html:118 templates/layout.html:129
 msgid "BookWyrm on GitHub"
 msgstr ""
 
 #: templates/layout.html:107 templates/layout.html:113
 #: templates/layout.html:114 templates/layout.html:120
-#: templates/layout.html:121
+#: templates/layout.html:121 templates/layout.html:132
 msgid "Contribute to this page"
 msgstr ""
 
 #: templates/layout.html:122 templates/layout.html:128
 #: templates/layout.html:129 templates/layout.html:135
-#: templates/layout.html:136
+#: templates/layout.html:136 templates/layout.html:147
 msgid "Learn more"
 msgstr ""
 
 #: templates/layout.html:127 templates/layout.html:133
 #: templates/layout.html:134 templates/layout.html:140
-#: templates/layout.html:141
+#: templates/layout.html:141 templates/layout.html:152
 msgid "Contact maintainer"
 msgstr ""
 
 #: templates/layout.html:130 templates/layout.html:136
 #: templates/layout.html:137 templates/layout.html:143
-#: templates/layout.html:144
+#: templates/layout.html:144 templates/layout.html:155
 msgid "License"
 msgstr ""
+
+#: templates/layout.html:65
+msgid "This is the documentation for the current development code. Choose a version from the menu to see documentation for released versions since"
+msgstr ""
+
+#: templates/layout.html:115
+msgid "Can't find what you are looking for, or see something wrong? <a href='https://github.com/bookwyrm-social/documentation/issues'>Log an Issue to help us improve this documentation!</a>"
+msgstr ""
+
+#: templates/page.html:16
+msgid "Page Contents"
+msgstr ""

locale/en_Oulipo/content/running_bookwyrm/management-commands.md

@@ -144,10 +144,7 @@ Locales for the language dropdown are listed in `i18n.py`. Generally we wait for
 
 When a new version of BookWyrm is released we need to create a new version of the docs:
 
-1. Add a new branch with a name exactly matching the new version tag in BookWyrm. e.g. `v0.8.0`.
-
-2. Add that branch name to the list of versions in `generate.py` in the `main` branch of the docs
-
-3. Check out every other version in turn, and merge the updated generation file into it so they all have the new branch listed: `git checkout main generate.py`. Then commit this change, create a PR to merge this change into the version's branch in the docs, and merge it. This will ensure that all pages in all versions of the docs have every other version listed in the dropdown menu.
-
-4. Merge the change in the `main` branch last - only merges into `main` trigger the GitHub action to deploy to the docs web server so if you do this first, the changes in other branches will have no effect.
+1. Add a new branch with a name exactly matching the new version tag in BookWyrm. e.g. `v0.x.y`.
+2. Add that branch name to the list of versions in `generate.py`, and push your new branch to the repository.
+3. Check out every other version in turn, and merge the updated `generate.py` file into it so they all have the new branch listed: `git checkout v0.x.y generate.py`. Then commit this change, create a PR to merge this change into the version's branch in the docs, and merge it. This will ensure that all pages in all versions of the docs have every other version listed in the dropdown menu.
+4. Merge the new `generate.py` in the `main` branch last - only merges into `main` trigger the GitHub action to deploy to the docs web server so if you do this first, the changes in other branches will have no effect until next time you update `main`.

locale/en_US/LC_MESSAGES/messages.po

@@ -0,0 +1,51 @@
+---
+Title: Management Commands
+Date: 2023-04-26
+Order: 11
+---
+
+In the `bookwyrm/management/commands` directory there are some commands to manipulate the instance’s database. Some of them are documented here.
+
+## Merging objects
+
+Quite often an instance will end up with duplicate books and authors or editions that appear as separate books when they are actually just different editions of the same work. This can happen because of importing editions that don’t have shared identifiers or from user mistakes. There also was a bug prior to version 0.7.5 which created a large number of duplicate books, editions, and authors. Sadly there’s no user interface to correct this for the time being, but in cases where the books are important for your instance you can use these management commands to fix some of the problems if you are using at least version 0.6.2.
+
+Please take extra care when using these commands because if you make a mistake there’s no way to undo it.
+
+### Merging editions
+
+If an edition of a book appears twice in the database and you are sure they are actually both referring to same edition, you can combine them into one with a command like this:
+
+```
+./bw-dev runweb python manage.py merge_editions --canonical=27 --other=38
+```
+
+This will copy any missing information from edition 38 (the “other” edition) over to edition 27 (the “canonical” edition) and then delete the other edition. If any field of information is in both editions then the data from the canonical edition will be kept. If the other edition is in any lists or has any comments or reviews etc then these will all be updated to point to the canonical edition instead.
+
+You can find the numbers to use in the command by visiting the page for a book and looking at the number in the URL.
+
+### Merging authors
+
+You can identify potential duplicate authors with `show_duplicate_authors`:
+
+```sh
+./bw-dev runweb python manage.py show_duplicate_authors
+```
+
+This will list all your _potential_ duplicate author records, based purely on their name, showing their birth and death dates if available, the count of books for each author, and a link to their page on your instance. Note that **you must check that these are actually duplicates** before merging them as they may be different authors with the same name.
+
+Once confirmed, if an author is duplicated you can combine the two authors into one with a command like this:
+
+```sh
+./bw-dev runweb python manage.py merge_authors --canonical=7 --other=46
+```
+
+As for the editions, any extra information from the other author will be copied over to the canonical author and then the other author will be deleted. Any books written by the other author will be changed to be written by the canonical author. You can find the numbers to use in the command by visiting the page for an author and looking at the number in the URL.
+
+## Fixing ISBNs
+
+There was a bug in `v0.8.0` which erroneously created 11-digit ISBN10 entries in some circumstances. This was fixed in a data migration in `v0.8.1`, however for various reasons you may need to manually run a cleanup command to fix any incorrect ISBNs in your local database:
+
+```sh
+./bw-dev runweb python manage.py fix_isbn10_entries
+```