Fix more broken links and redirects

docs/effective-volto/addons/semanticui.md

@@ -46,7 +46,7 @@ path).
 
 Volto's theme is called Pastanaga. It's a typical Semantic-UI theme. For
 the new elements and components that don't exist in Semantic-UI, the Pastanaga
-theme uses the [extras](https://github.com/plone/volto/tree/master/theme/themes/pastanaga/extras) folder. The downside is that they aren't fully using the Semantic-UI theming engine.
+theme uses the [extras](https://github.com/plone/volto/tree/main/packages/volto/theme/themes/pastanaga/extras) folder. The downside is that they aren't fully using the Semantic-UI theming engine.
 
 The key to success in Volto theming is to understand how Semantic-UI's theming
 engine works and how to manipulate it. Reading the `theme.less` and

docs/effective-volto/deployment/docker.md

@@ -16,7 +16,7 @@ It is recommended that you follow the best practices explained in the "Installin
 
 You'll find in the Volto repository a simple `docker-compose` example:
 
-https://github.com/plone/volto/blob/main/docker-compose.yml
+https://github.com/plone/volto/blob/main/packages/volto/docker-compose.yml
 
 ```shell
 docker-compose -f <following_snippet.yml> up

docs/effective-volto/development/debugging.md

@@ -18,4 +18,4 @@ component hierarchy, inspect props, hooks, HOCs, etc.
 Redux Dev Tools allows you to observe the Redux actions and inspect the store
 state.
 
-You can add `debugger` lines in your code, to trigger breakpoints in the browser. To debug the server, you need to hook the [Chrome DevTools](https://nodejs.org/en/docs/guides/debugging-getting-started). Note that there's multiple threads hooked into the inspector (server, client, hotreload process), so you'll have to find the one that coresponds to the server.
+You can add `debugger` lines in your code, to trigger breakpoints in the browser. To debug the server, you need to hook the [Chrome DevTools](https://nodejs.org/docs/latest/api/debugger.html). Note that there's multiple threads hooked into the inspector (server, client, hotreload process), so you'll have to find the one that coresponds to the server.

docs/effective-volto/development/icons.md

@@ -9,7 +9,7 @@ myst:
 
 # Icons
 
-Volto has a pre-defined set of SVG icons from the Pastanaga UI icon system. You can find them in the code repo in [here](https://github.com/plone/volto/tree/master/src/icons). They are also browseable in https://pastanaga.io/icons/.
+Volto has a pre-defined set of SVG icons from the Pastanaga UI icon system. You can find them in the code repo in [here](https://github.com/plone/volto/tree/main/packages/volto/src/icons). They are also browseable in https://pastanaga.io/icons/.
 
 The following example shows how to display one of these icons.
 

docs/mastering-plone/volto_testing.md

@@ -41,7 +41,7 @@ We already added a content type `talk`. Let's write a test 'An editor can add a
    >   },
    > ```
 
-3. Get some helper functions for an autologin, etc. from [Volto](https://github.com/plone/volto/tree/master/cypress/support).
+3. Get some helper functions for an autologin, etc. from [Volto](https://github.com/plone/volto/tree/main/packages/volto/cypress/support).
 
 4. Create a folder {file}`cypress/integration/` with a file {file}`content.js`
 

docs/mastering-plone/what_is_plone.md

@@ -142,7 +142,7 @@ Plone creates forms for all these schemata to add and edit content.
 
 ```{seealso}
 - [Zope Component Architecture](https://zopecomponent.readthedocs.io/en/latest/narr.html)
-- The [Keynote](https://youtu.be/eGRJbBI_H2w?t=1308) by Cris Ewing at PyCon 2016
+- The [Keynote](https://www.youtube.com/watch?t=1308&v=eGRJbBI_H2w) by Cris Ewing at PyCon 2016
 ```
 
 

docs/volto_customization/voltosettings.md

@@ -78,7 +78,7 @@ Here are some more setting you might use in your projects:
 - `maxFileUploadSize` - Limit the size of uploads
 - `nonContentRoutes` - A list of path strings which are considered to be outside of plone-restapi's content serialization. For example: `/controlpanel, /login,/sitemap,/personal-information` are all nonContentRoutes.
 
-You can find all existing options in the file <a target="_blank" href="https://github.com/plone/volto/blob/main/src/config/index.js#L73">config/index.js</a> of Volto itself which is available in your projects in `frontend/omelette/src/config/index.js`.
+You can find all existing options in the file <a target="_blank" href="https://github.com/plone/volto/blob/main/packages/volto/src/config/index.js#L73">config/index.js</a> of Volto itself which is available in your projects in `frontend/omelette/src/config/index.js`.
 
 ```{seealso}
 Many options are explained in the {doc}`plone6docs:volto/configuration/settings-reference`

docs/voltoaddons/02-block-edit.md

@@ -260,7 +260,7 @@ The reducer code looks scary, but it shouldn't be. To understand it, you need
 to know:
 
 - In Volto, all actions that have a `request` field are treated as network
-  requests, and they will be processed by the [API middleware](https://github.com/plone/volto/blob/main/src/middleware/api.js).
+  requests, and they will be processed by the [API middleware](https://github.com/plone/volto/blob/main/packages/volto/src/middleware/api.js).
 - That middleware will then trigger several new actions, derived from the main
   function and prefixed with its name, either `PENDING`, `SUCCESS`, or `FAIL`.
 - For each of these new actions, we will reduce the state of the store to

docs/voltoaddons/04-block-edit-options.md

@@ -438,5 +438,5 @@ export default withBlockDataSource({
 })(DataTableEdit);
 ```
 
-[field.jsx]: https://github.com/plone/volto/blob/main/src/components/manage/Form/Field.jsx
-[Volto's widget documentation]: https://github.com/plone/volto/blob/main/docs/source/recipes/widget.md
+[field.jsx]: https://github.com/plone/volto/blob/main/packages/volto/src/components/manage/Form/Field.jsx
+[Volto's widget documentation]: https://github.com/plone/volto/blob/main/docs/source/development/widget.md