website: re-generate commons

website/docs/maintainer/_common/_content.mdx

@@ -169,7 +169,7 @@ or run the following in a terminal:
 ```
 
 Navigate to the **Maintainer Info** page,
-the **Increase the version and update VERSION** section.
+the **Update the version specific code** section.
 
 <UpdateVersionSpecific/>
 
@@ -282,7 +282,7 @@ caffeinate ssh xbbli
 
 ### Update the durations of the development builds
 
-In `website/docs/maintainer/_shared/_development-durations.mdx`, update
+In `website/docs/_shared/_development-durations.mdx`, update
 the durations of the builds.
 
 Commit with the message _**website: update development durations**_.
@@ -345,7 +345,9 @@ The automation is provided by GitHub Actions and three self-hosted runners.
 ### Start the self-hosted runners
 
 If the runners expired (more than 2 weeks since last use), run the
-`github-runner-configure.sh` script to reconfigure them
+`github-runner-configure.sh` script to reconfigure them. This scripts
+is available in the `xbb-helper` and
+requires `GITHUB_API_XPACK_DEV_TOOLS_RUNNERS_TOKEN` to be present.
 
 - on the development machine (`wksi`) open
 a ssh session to the build machine `xbbli`:
@@ -390,14 +392,23 @@ The status of all self-hosted runners is available at the [GitHub Runners](https
 
 Publish a new release of the helper on **npmjs**.
 
-### In `npm-packages-helper.git`, update the dependency to the new helper
+### In the npm packages helper, update the dependency to the new helper
 
 In `templates/_xpack-dev-tools/build-assets/package-merge-liquid.json`, update the reference
-to `"@@xpack-dev-tools/xbb-helper":`.
+to `"@xpack-dev-tools/xbb-helper":`.
 
-### Commit the changes to `build-assets/package.json`
+### Generate the top commons
 
-Commit with the message _**template: build-assets/package-merge-liquid.json: bump deps**_.
+Run the top **generate-top-commons** npm script to update the
+`build-assets/package.json` and the GitHub workflow files.
+
+```sh
+npm run generate-top-commons -C ~/Work/xpack-dev-tools/wine-xpack.git
+```
+
+### Commit the changes
+
+Commit with the message _**re-generate top commons**_.
 
 ### Check for disk space
 
@@ -434,15 +445,6 @@ This is equivalent to running a wide `rm` to remove the `build` folders:
 rm -rf ~/Work/xpack-dev-tools/*/build-assets/build
 ```
 
-### Generate the GitHub workflows
-
-Run the top **generate-top-commons** npm script to update the
-GitHub workflow files.
-
-```sh
-npm run generate-workflows -C ~/Work/xpack-dev-tools/wine-xpack.git
-```
-
 ### Commit and push
 
 - commit with the message **re-generate workflows**
@@ -702,13 +704,15 @@ npm run build -C website
 
 ### Publish the website
 
+- open https://xpack-dev-tools.github.io/wine-xpack/docs/maintainer/#publish-the-website in a separate window
 - stop the local web server
 - select the `website` branch
 - merge `xpack-development` into `website`
 - push the `website` branch to GitHub
   :::info
   At this moment an automated GitHub Action will generate and publish the website.
   :::
+- add a new tag like `web-YYYYMMDD`
 - the new release blog post is
 in https://xpack-dev-tools.github.io/wine-xpack/blog/
 - remember the post URL, since it must be used to update the release page