website: re-generate commons

Author: ilg-ul

website/blog/2025-10-14-gcc-v12-5-0-1-released.mdx

@@ -36,6 +36,8 @@ 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';
 import DownloadAnalytics from './_common/_download-analytics.mdx';

website/blog/2025-10-14-gcc-v13-4-0-1-released.mdx

@@ -36,6 +36,8 @@ 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';
 import DownloadAnalytics from './_common/_download-analytics.mdx';

website/blog/2025-10-14-gcc-v14-3-0-1-released.mdx

@@ -36,6 +36,8 @@ 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';
 import DownloadAnalytics from './_common/_download-analytics.mdx';

website/blog/2025-10-14-gcc-v15-2-0-1-released.mdx

@@ -36,6 +36,8 @@ 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';
 import DownloadAnalytics from './_common/_download-analytics.mdx';

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

@@ -36,6 +36,8 @@ 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';
 import DownloadAnalytics from './_common/_download-analytics.mdx';

website/docs/install/_common/_content.mdx

@@ -303,7 +303,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/gcc/15.2.0-1.1/.content/bin:$PATH
+`export PATH=$HOME/AppData/Roaming/xPacks/@xpack-dev-tools/gcc/15.2.0-1.1/.content/bin:$PATH
 `} </CodeBlock>
 
 :::tip
@@ -318,7 +318,7 @@ corresponding shell.
 <TabItem value="linux" label="GNU/Linux">
 
 <CodeBlock language="sh"> {
-`export PATH=$HOME/.local/xPacks/xpack-dev-tools/gcc/15.2.0-1.1/.content/bin:$PATH
+`export PATH=$HOME/.local/xPacks/@xpack-dev-tools/gcc/15.2.0-1.1/.content/bin:$PATH
 `} </CodeBlock>
 
 </TabItem>

website/docs/maintainer/_common/_content.mdx

@@ -414,13 +414,6 @@ watching the gcc-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

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/gcc-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/gcc-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 15.2.0-1.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: [