website: re-generate commons

Author: ilg-ul

website/blog/_templates/blog-post-release-part-1-liquid.mdx

@@ -2,7 +2,7 @@
 
 title: xPack {{packageConfig.descriptiveName}} v{{xpackVersion}} released
 seo_title: Version {{xpackVersion}} released
-description: Version {{xpackVersion}} is a TODO new/maintenance release.
+description: Version {{xpackVersion}} is a TODO maintenance/new release.
 keywords:
   - xpack
   - {{packageConfig.permalinkName}}
@@ -34,6 +34,10 @@ download_url: https://github.com/xpack-dev-tools/windows-build-tools-xpack/relea
 import {PageMetadata} from '@docusaurus/theme-common';
 import Image from '@theme/IdealImage';
 import CodeBlock from '@theme/CodeBlock';
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+import customField from '@site/src/libs/customField';
 
 import Prerequisites from './_common/_prerequisites-glib-2.28.mdx';
 import DeprecationNotices from './_common/_deprecation-notices-glib-2.28.mdx';
@@ -128,7 +132,7 @@ set of platforms. The results are available from:
 
 ## Tests
 
-The binaries were testes on Windows 10 Pro 32/64-bit.
+The binaries were testes on x64 Windows.
 
 Install the package with xpm.
 

website/blog/_templates/blog-post-release-part-2-liquid.mdx

@@ -1,4 +1,78 @@
 
+## Folders hierarchy
+
+After install, the package creates a hierarchy of folders like the following
+(only the first two depth levels are shown):
+
+{%- assign platforms_array = platforms | split: "," %}
+
+{%- assign names_array = "" | split: "" %}
+
+{%- for platform in platforms_array %}
+{%- case platform %}
+{%- when "win32-x64" %}
+{%- assign names_array = names_array | concat: "Windows" %}
+{%- when "darwin-x64", "darwin-arm64" %}
+{%- assign names_array = names_array | concat: "macOS" %}
+{%- when "linux-x64", "linux-arm64", "linux-arm" %}
+{%- assign names_array = names_array | concat: "GNU/Linux" %}
+{%- endcase %}
+{%- endfor %}
+
+{%- assign names_array = names_array | uniq %}
+
+<Tabs groupId="operating-systems">
+
+{%- for name in names_array %}
+{%- case name %}
+{%- when "Windows" %}
+
+<TabItem value="windows" label="Windows" default>
+
+<CodeBlock language="console"> {
+`C:\> tree /f %USERPROFILE%\\AppData\\Roaming\\xPacks\\@{{packageScope}}\\{{packageName}}\\${frontMatter.version}.${frontMatter.npm_subversion}\\.content
+Folder PATH listing
+Volume serial number is B02D-925C
+├── README.md
+├── bin
+TODO
+`} </CodeBlock>
+
+</TabItem>
+
+{%- when "macOS" %}
+
+<TabItem value="macos" label="macOS">
+
+<CodeBlock language="console"> {
+`$ tree -L 2 ~/Library/xPacks/\{{packageScopedName}}/${frontMatter.version}.${frontMatter.npm_subversion}/.content/
+/Users/ilg/Library/xPacks/\{{packageScopedName}}/${frontMatter.version}.${frontMatter.npm_subversion}/.content/
+├── README.md
+├── bin
+TODO
+`} </CodeBlock>
+
+</TabItem>
+
+{%- when "GNU/Linux" %}
+
+<TabItem value="linux" label="GNU/Linux">
+
+<CodeBlock language="console"> {
+`$ tree -L 2 ~/.local/xPacks/\{{packageScopedName}}/${frontMatter.version}.${frontMatter.npm_subversion}/.content/
+/home/ilg/.local/xPacks/\{{packageScopedName}}/${frontMatter.version}.${frontMatter.npm_subversion}/.content/
+├── README.md
+├── bin
+TODO
+`} </CodeBlock>
+
+</TabItem>
+
+{%- endcase %}
+{%- endfor %}
+
+</Tabs>
+
 <DeprecationNotices/>
 
 <DownloadAnalytics version={frontMatter.version}/>

website/docs/_common/_publish-website.mdx

@@ -10,16 +10,16 @@ The website deployment is performed automatically when pushing to the
 [GitHub Actions](https://github.com/xpack-dev-tools/windows-build-tools-xpack/actions/workflows/publish-github-pages.yml).
 
 - Open https://xpack-dev-tools.github.io/windows-build-tools-xpack/docs/maintainer/#publish-the-website in a separate window
-- Stop the local web server
+- **Stop** the local web server
 - Switch to the `website` branch
 - **Merge** the `xpack-development` branch into the `website` branch
 - **Push** the `website` branch to GitHub
   :::info
   At this point, an automated GitHub Action will generate and publish the website.
   :::
 - Check out the `xpack-development` branch
-- Wait for the publication to complete
-- Refresh the web page
+- **Wait** for the publication to complete
+- **Refresh** the web page
 - The new release blog post is available
 at https://xpack-dev-tools.github.io/windows-build-tools-xpack/blog/
 - Record the post URL, as it must be used to update the release page

website/docs/install/_common/_content.mdx

@@ -280,7 +280,7 @@ the project build configurations need a PATH adjustment:
 <TabItem value="windows" label="Windows" default>
 
 <CodeBlock language="sh"> {
-`export PATH=$HOME/AppData/Roaming/xPacks/xpack-dev-tools/windows-build-tools/4.4.1-3.1/.content/bin:$PATH
+`export PATH=$HOME/AppData/Roaming/xPacks/@xpack-dev-tools/windows-build-tools/4.4.1-3.1/.content/bin:$PATH
 `} </CodeBlock>
 
 :::tip

website/docs/maintainer/_common/_content.mdx

@@ -154,19 +154,6 @@ triggered via the VS Code graphical interface, utilising the
 
 <ProjectPatches/>
 
-### Restart the Docker daemons
-
-If, for any reason, the Docker builds need to be cancelled, it is very
-likely that some processes will continue to execute in the background.
-
-To completely terminate them, and ensure that Docker executes
-from a clean slate, restart the Docker daemons on all GNU/Linux
-machines:
-
-```sh
-sudo systemctl restart docker
-```
-
 ### Verify if both projects are pushed
 
 Verify that both the **current project** and the **helper** are
@@ -203,9 +190,11 @@ Commit with the message _**website: update development durations**_
 Copy the trees displayed at the end of the test builds and paste to the
 **Folder hierarchy** section within the web file:
 
+<ul>
 
 
-- `website/docs/_project/_folders-hierarchies-windows.mdx`
+<li> <code>website/docs/_project/_folders-hierarchies-windows.mdx</code></li>
+</ul>
 
 If present, replace the actual version
 (such as **4.4.1-3.1**) with the following expression:
@@ -251,7 +240,7 @@ place them in the XBB cache (`Work/cache`) and restart the build.
 
 ## Execute the production builds
 
-The automation is provided by GitHub Actions.
+The automation is provided by GitHub Actions on GitHub-hosted runners.
 
 ### Publish the helper
 
@@ -316,7 +305,7 @@ The resulting binaries are available for testing from
 
 ### Automated tests
 
-The automation is provided by GitHub Actions.
+The automation is provided by GitHub Actions on GitHub-hosted runners.
 
 To trigger the GitHub Actions tests, execute the xpm actions:
 
@@ -352,11 +341,6 @@ xpm run install -C ~/Work/xpack-dev-tools/windows-build-tools-xpack.git/build-as
 xpm run test-pre-release -C ~/Work/xpack-dev-tools/windows-build-tools-xpack.git/build-assets
 ```
 
-:::caution
-Since the builds were performed on the latest GitHub macOS runners,
-it is strongly recommended to also execute the tests on an older macOS 11 machine.
-:::
-
 For additional tests, on each platform,
 download the archive from
 [pre-releases/test](https://github.com/xpack-dev-tools/pre-releases/releases/tag/test/)
@@ -402,17 +386,10 @@ watching the windows-build-tools-xpack project.
 
 <CommonPrepareNewBlogPost />
 
-### Update the web install page
-
-- Check and possibly update the output of the `--version` runs in
-  - `website/docs/install/_project/_automatic-install-quick-test.mdx`
-  - `website/docs/install/_project/_manual-install-quick-test.mdx`
-- **Commit** with the message _**website: update quick tests**_
-
 ### Check the list of links in top package.json
 
 - Open the top `package.json` file
-- Check if the links in the `bin` property cover the actual binaries
+- Check if the links in the `xpack.executables` property cover the actual binaries
 - If necessary, also check on Windows
 
 ### Update the package.json list of binaries
@@ -446,7 +423,7 @@ Execute the **trigger-workflow-test-xpm** xpm action:
 xpm run trigger-workflow-test-xpm -C ~/Work/xpack-dev-tools/windows-build-tools-xpack.git/build-assets
 ```
 
-This will install the package via `xpm install` on all supported platforms.
+This will test if the package can be installed via `xpm install` on all supported platforms.
 
 The test results are available from the
 [GitHub Actions](https://github.com/xpack-dev-tools/windows-build-tools-xpack/actions) page.

website/docs/maintainer/_common/_first-development-run-gcc.mdx

@@ -0,0 +1,17 @@
+
+import versionMajor from '@site/src/libs/versionMajor';
+
+{/* ------------------------------------------------------------------------ */}
+
+The strategy with the development builds is to run them in descending order
+({versionMajor()}.2, {versionMajor() - 1}.3, {versionMajor() - 2}.4, {versionMajor() - 3}.5).
+
+For this update the top `package.json` and `build-assets/scripts/VERSION` files
+and run the build scripts.
+
+After each build, save the folder hierarchies and executables, to be used
+in the blog posts.
+
+Then perform the steps to make the production builds in ascending order
+({versionMajor() - 3}.5, {versionMajor() - 2}.4, {versionMajor() - 1}.3, {versionMajor()}.2),
+with full tests and website updates.

website/docs/maintainer/_common/_prepare-new-blog-post.mdx

@@ -10,11 +10,11 @@
   ```sh
   npm run generate-website-blog-post -C ~/Work/xpack-dev-tools/windows-build-tools-xpack.git/website
   ```
-- Edit the front matter properties (the `description` property)
-- Select the correct summary (maintenance vs. new release)
+- Fix the TODO in the front matter `description` property (select maintenance vs. new release)
+- Fix the TODO in the summary (select maintenance vs. new release)
 - Add entries in the **Bug fixes**; utilise the following syntax
   ```
   - [[#N](https://github.com/xpack-dev-tools/windows-build-tools-xpack/issues/N)]:
   ```
-- Copy/paste the folder structures from the installation guide
+- Copy/paste the **folder hierarchies** from the `website/docs/_project/_folders-hierarchies-*.mdx` files
 - **Commit** with the message _**website: blog post release 4.4.1-3.1 published**_

website/docusaurus.config.ts

@@ -47,7 +47,6 @@ const config: Config = {
 
   onBrokenAnchors: 'throw',
   onBrokenLinks: 'throw',
-  onBrokenMarkdownLinks: 'throw',
 
   onDuplicateRoutes: 'throw',
 
@@ -64,7 +63,10 @@ const config: Config = {
   },
 
   markdown: {
-    format: 'detect'
+    format: 'detect',
+    hooks: {
+        onBrokenMarkdownLinks: 'throw'
+    }
   },
 
   plugins: [