Rename files to spinal case

Add missing files and images

Author: stevepiercy

docs/backend/upgrading/add-on-upgrade.md

@@ -0,0 +1,28 @@
+# Upgrade add-on products
+
+```{admonition} Description
+The steps to take to migrate your third party products
+```
+
+- Shut down your Plone server instance.
+- If you specified concrete versions of the third-party products in your *buildout.cfg* file (so-called "pinning", and a recommended practice), like *Products.PloneFormGen* = 1.7.17, update these references to point to the new versions.
+
+```{note}
+Without pinning, i.e. specifying only, for example, *Products.PloneFormGen* and no version, buildout will pick the newest version of the products by default.
+```
+
+- Run *bin/buildout*. Wait until all new software is downloaded and installed.
+- Start Plone again - your site may look weird, or even be inaccessible until you have performed the next step
+- Navigate to the Add-on screen (add `/prefs_install_products_form` to your site URL, and upgrade products if you can (products that support both your current and new version of Plone).
+  : - Perform product-specific upgrade procedures (if any).
+    - You will find these in the documentation of each product.
+
+Should the `/prefs_install_products_form` be unreachable, you should try doing the add-on upgrades from the Management Interface.
+Navigate to the quickinstaller in the Management Interface, and reinstall or upgrade products that are shown to be outdated.
+
+```{note}
+Be careful when updating add-ons through the Management Interface.
+It may show outdated themes as well with a hint to update.
+If you do that, the updated theme will activate itself, overriding your current theme.
+If this happens, re-enable your theme in the theming panel.
+```

docs/backend/upgrading/index.md

@@ -24,7 +24,7 @@ though the stack discussion may be useful to everyone.
 
 intro
 preparations
-addon_upgrade
+add-on-upgrade
 troubleshooting
-version_specific_migration/index
+version-specific-migration/index
 ```

…/images/portal_actions_control_panel.png …/images/portal-actions-control-panel.pngdocs/backend/upgrading/version_specific_migration/images/portal_actions_control_panel.png renamed to docs/backend/upgrading/version-specific-migration/images/portal-actions-control-panel.png docs/backend/upgrading/version_specific_migration/images/portal_actions_control_panel.png renamed to docs/backend/upgrading/version-specific-migration/images/portal-actions-control-panel.png

@@ -8,12 +8,12 @@ If your migration does not involve a version pair specified here, then you may f
 ```{toctree}
 :maxdepth: 2
 
-p4x_to_p5x_upgrade
-plone5_minor_upgrade
-upgrade_to_51
-upgrade_to_52
-upgrade_to_python3
-upgrade_zodb_to_python3
-upgrade_to_60
+p4x-to-p5x-upgrade
+plone5-minor-upgrade
+upgrade-to-51
+upgrade-to-52
+upgrade-to-python3
+upgrade-zodb-to-python3
+upgrade-to-60
 migrate-to-volto
 ```

…_migration/images/sharing_group_link.png …-migration/images/sharing-group-link.pngdocs/backend/upgrading/version_specific_migration/images/sharing_group_link.png renamed to docs/backend/upgrading/version-specific-migration/images/sharing-group-link.png docs/backend/upgrading/version_specific_migration/images/sharing_group_link.png renamed to docs/backend/upgrading/version-specific-migration/images/sharing-group-link.png

@@ -5,7 +5,7 @@ Instructions and tips for upgrading to a newer Plone version.
 ```
 
 ```{note}
-If you want to upgrade add-ons to Plone 5, also see {doc}`/develop/addons/upgrade_to_50`
+If you want to upgrade add-ons to Plone 5, also see {doc}`/develop/addons/upgrade-to-50`
 ```
 
 ## General Information

…ding/version_specific_migration/index.md …ding/version-specific-migration/index.mddocs/backend/upgrading/version_specific_migration/index.md renamed to docs/backend/upgrading/version-specific-migration/index.md docs/backend/upgrading/version_specific_migration/index.md renamed to docs/backend/upgrading/version-specific-migration/index.md

@@ -14,7 +14,7 @@ Instructions and tips for upgrading to Plone 5.1
 ```
 
 ```{note}
-If you want to upgrade add-ons to Plone 5.1, please see {doc}`/develop/addons/upgrade_to_51`
+If you want to upgrade add-ons to Plone 5.1, please see {doc}`/develop/addons/upgrade-to-51`
 ```
 
 ## General Information
@@ -71,7 +71,7 @@ These are for example site menus, user menus, footer links, etcetera.
 It also allows to add custom ones.
 Actions can be re-ordered, and can be hidden or displayed.
 
-```{image} images/portal_actions_control_panel.png
+```{image} images/portal-actions-control-panel.png
 ```
 
 See {ref}`Creating actions through-the-web <create_actions_ttw>`.
@@ -88,7 +88,7 @@ This is [PLIP 1310](https://github.com/plone/Products.CMFPlone/issues/1310).
 
 When a Group is shown on the Sharing page, you can click on the group name to go to the list of members of that group.
 
-```{image} images/sharing_group_link.png
+```{image} images/sharing-group-link.png
 ```
 
 #### For Developers
@@ -309,14 +309,14 @@ The monitor of the visitor will show the best available density.
 
 Compare this low resolution image:
 
-```{image} /_static/plip_hidpi_low_resolution.png
+```{image} /_static/plip-hidpi-low-resolution.png
 :align: center
 :alt: 'Example: low resolution'
 ```
 
 with this high resolution image:
 
-```{image} /_static/plip_hidpi_high_resolution.png
+```{image} /_static/plip-hidpi-high-resolution.png
 :align: center
 :alt: 'Example: low resolution'
 ```

…n_specific_migration/migrate-to-volto.md …n-specific-migration/migrate-to-volto.mddocs/backend/upgrading/version_specific_migration/migrate-to-volto.md renamed to docs/backend/upgrading/version-specific-migration/migrate-to-volto.md docs/backend/upgrading/version_specific_migration/migrate-to-volto.md renamed to docs/backend/upgrading/version-specific-migration/migrate-to-volto.md

@@ -59,7 +59,7 @@ The migration to Python 3 follows these steps:
 4. Port add-ons and custom code to Python 3 without the existing database.
 5. Migrate the database using `zodbupdate`. If you are working on a new project (i.e. without a existing database) you can skip the last step.
 
-See {doc}`/manage/version-specific-migration/upgrade_to_python3` for details about porting code and database to Python 3.
+See {doc}`/manage/version-specific-migration/upgrade-to-python3` for details about porting code and database to Python 3.
 
 ### Zope 4.0