docs: support MDX props injection for brand name customization (module-federation#4552)

Author: 2heal1

apps/website-new/docs/en/blog/error-load-remote.mdx

@@ -5,10 +5,6 @@ title: Error handling for remote module rendering in Module Federation.
 # Error handling for remote module rendering in Module Federation.
 import BlogGifGrid from '@components/BlogGifGrid.tsx';
 
-:::tip Version Requirements
-This solution requires upgrading the `@module-federation/runtime` version to 0.8.10 or higher.
-:::
-
 
 ## Background
 Remote module loading process may fail due to network resource loading failure or business logic rendering failure.
@@ -50,7 +46,7 @@ These three solutions are for different scenarios, can be used separately, or co
 
 For weak network environment or producer has not started the service, we can add retry mechanism to request resources multiple times, which will increase the probability of resource loading success.
 
-Module Federation official provides retry plugin [@module-federation/retry-plugin](https://module-federation.io/zh/plugin/plugins/retry-plugin.html) to support retry mechanism for resources, support fetch and script resources retry.    
+Module Federation official provides retry plugin [@module-federation/retry-plugin](https://module-federation.io/zh/plugin/plugins/retry-plugin.html) to support retry mechanism for resources, support fetch and script resources retry.
 
 #### Pure runtime registration
 
@@ -313,7 +309,7 @@ export default defineConfig({
 ```
 
 :::info Tips
-The following example shows how to handle errors in different lifecycle stages. 
+The following example shows how to handle errors in different lifecycle stages.
 
 If your application scenario is simple, you can refer to the **simplified version** below, which provides a unified error handling solution.
 

apps/website-new/docs/en/configure/dts.mdx

@@ -3,7 +3,7 @@
 - Type: `boolean | PluginDtsOptions`
 - Required: No
 - Default value: `true`
-- Usage scenario: used to control `Module Federation` generation/consumption type behavior
+- Usage scenario: used to control <code>{props.brandName || props.name || 'Module Federation'}</code> generation/consumption type behavior
 
 After configuration, the producer will automatically generate a compressed type file `@mf-types.zip` (default name) during build, and the consumer will automatically pull the type file of `remotes` and decompress it to `@mf-types` (default name).
 

apps/website-new/docs/en/configure/exposes.mdx

@@ -3,7 +3,7 @@
 - Type: `PluginExposesOptions`
 - Required: No
 - Default value: `undefined`
-- Usage: Determines the modules and file entries exposed by `Module Federation`.
+- Usage: Determines the modules and file entries exposed by <code>{props.brandName || props.name || 'Module Federation'}</code>.
 
 :::tip
 A producer-specific parameter, setting `exposes` indicates that this is a producer.

apps/website-new/docs/en/configure/manifest.mdx

@@ -3,10 +3,10 @@
 - Type: `boolean | PluginManifestOptions`
 - Default value: `undefined`
 
-Controls whether the plugin generates manifest artifacts and how they are produced. When enabled, the plugin emits `mf-manifest.json` and `mf-stats.json` (names can be customized via `fileName`) on every build so that other tools can consume them directly through `processAssets` or from the final build output.
+Controls whether the plugin generates manifest artifacts and how they are produced. When enabled, the plugin emits  <code>{props.manifest || 'mf-manifest.json' }</code> and <code>{props.stats || 'mf-stats.json' }</code> (names can be customized via `fileName`) on every build so that other tools can consume them directly through `processAssets` or from the final build output.
 
-- `mf-stats.json`: captures the full build statistics, including the assets for exposes/shared/remotes, `metaData` (plugin version, build info, `remoteEntry`, etc.), and any additional asset analysis. Ideal for debugging or merging stats across environments.
-- `mf-manifest.json`: a runtime-oriented manifest distilled from the stats. It keeps the stable structure that Module Federation consumers read when loading remote modules. The exposes/shared/remotes entries describe what is actually available to consumers.
+- <code>{props.stats || 'mf-stats.json'}</code>: captures the full build statistics, including the assets for exposes/shared/remotes, `metaData` (plugin version, build info, `remoteEntry`, etc.), and any additional asset analysis. Ideal for debugging or merging stats across environments.
+- <code>{props.manifest || 'mf-manifest.json'}</code>: a runtime-oriented manifest distilled from the stats. It keeps the stable structure that {props.brandName  || 'Module Federation'} consumers read when loading remote modules. The exposes/shared/remotes entries describe what is actually available to consumers.
 
 The `PluginManifestOptions` types are as follows:
 

apps/website-new/docs/en/configure/shared.mdx

@@ -168,11 +168,11 @@ At this point, you can add the corresponding dependencies to the `shared` config
 
 ### How to use shared dependencies
 
-Depending on the use case, {props.name || 'Module Federation'} supports two forms of shared dependency configuration: array and object. The former is suitable for most scenarios, while the latter is suitable for complex customization needs.
+Depending on the use case, {props.brandName || props.name || 'Module Federation'} supports two forms of shared dependency configuration: array and object. The former is suitable for most scenarios, while the latter is suitable for complex customization needs.
 
 **Array Format (General Scenario)**
 
-Simply add the corresponding dependencies to the `shared` configuration in the {props.name || 'Module Federation'} build configuration, for example:
+Simply add the corresponding dependencies to the `shared` configuration in the {props.brandName || props.name || 'Module Federation'} build configuration, for example:
 
 import ArrayShared from '@components/common/configure/array-shared';
 import React from 'react';
@@ -181,7 +181,7 @@ import React from 'react';
 
 **Object Format (Customized Configuration)**
 
-Add the shared dependencies in the `shared` configuration of the {props.name || 'Module Federation'}, with the `key` being the dependency name and the `value` being the provided configuration.
+Add the shared dependencies in the `shared` configuration of the {props.brandName || props.name || 'Module Federation'}, with the `key` being the dependency name and the `value` being the provided configuration.
 
 import ObjectShared from '@components/common/configure/object-shared'
 

apps/website-new/docs/en/configure/treeShakingDir.mdx

@@ -6,4 +6,4 @@ The directory used to output tree-shaking shared fallback assets.
 - Required: No
 - Default: `undefined`
 
-When shared dependency tree shaking is enabled, Module Federation will extract the exports of unused shared modules. This option specifies the output directory for those fallback assets.
+When shared dependency tree shaking is enabled, {props.brandName || props.name || 'Module Federation'} will extract the exports of unused shared modules. This option specifies the output directory for those fallback assets.

apps/website-new/docs/en/guide/build-plugins/plugins-rspack.mdx

@@ -1,7 +1,7 @@
 # Rspack
 
-- Capable of building modules that meet the `Module Federation` loading specifications.
-- Can consume modules that adhere to the `Module Federation` specifications using aliases.
+- Capable of building modules that meet the <code>{props.brandName || props.name || 'Module Federation'}</code> loading specifications.
+- Can consume modules that adhere to the <code>{props.brandName || props.name || 'Module Federation'}</code> specifications using aliases.
 - Can set shared dependency configurations for modules, so that when the host environment of the loaded module already has the corresponding dependency, it will not be loaded again.
 - When a module has remote types, it will automatically download and consume the types of the remote modules.
 - Consuming remote modules will have hot update capabilities.
@@ -18,10 +18,10 @@ import { PackageManagerTabs } from '@theme';
 
 <PackageManagerTabs
   command={{
-    npm: `npm add ${props.pkgName || '@module-federation/enhanced'}`,
-    yarn: `yarn add ${props.pkgName || '@module-federation/enhanced'}`,
-    pnpm: `pnpm add ${props.pkgName || '@module-federation/enhanced'}`,
-    bun: `bun add ${props.pkgName || '@module-federation/enhanced'}`,
+    npm: `npm add ${props.rspackPackage || props.pkgName || '@module-federation/enhanced'}`,
+    yarn: `yarn add ${props.rspackPackage || props.pkgName || '@module-federation/enhanced'}`,
+    pnpm: `pnpm add ${props.rspackPackage || props.pkgName || '@module-federation/enhanced'}`,
+    bun: `bun add ${props.rspackPackage || props.pkgName || '@module-federation/enhanced'}`,
   }}
 />
 

apps/website-new/docs/en/guide/build-plugins/plugins-rspress.mdx

@@ -4,7 +4,7 @@
 Requires [Rspress version 2.0.0-beta.16](https://v2.rspress.rs/plugin/system/introduction) or higher.
 :::
 
-Helps users build and consume {props.name || 'Module Federation'} products in **Rspress**.
+Helps users build and consume {props.brandName || props.name || 'Module Federation'} products in **Rspress**.
 
 ## Quick Start
 
@@ -64,7 +64,7 @@ import ConfigType from '@components/common/rspress/config-type';
 
 ### {props.pluginOptionName || 'moduleFederationOptions'}
 
-[{props.name || 'Module Federation'} Configuration](../../../configure/index)
+[{props.brandName || props.name || 'Module Federation'} Configuration](../../../configure/index)
 
 ### rspressOptions
 

apps/website-new/docs/en/guide/build-plugins/plugins-webpack.mdx

@@ -1,7 +1,7 @@
 # Webpack
 
-- Capable of building modules that meet the {props.name || 'Module Federation'} loading specification.
-- Capable of consuming modules of the {props.name || 'Module Federation'} specification using aliases.
+- Capable of building modules that meet the {props.brandName || props.name || 'Module Federation'} loading specification.
+- Capable of consuming modules of the {props.brandName || props.name || 'Module Federation'} specification using aliases.
 - Capable of setting the shared dependency configuration for modules. When the host environment where the module is loaded already has the corresponding dependency, it will not be loaded repeatedly.
 - When a module has a remote type, the type of the remote module will be automatically downloaded for consumption.
 - Hot-reloading capability when consuming remote modules.
@@ -19,7 +19,7 @@ You can install the plugin with the following command:
 import InstallKit from '@components/common/install-kit';
 
 <InstallKit
-  pkgName={props.pkgName}
+  pkgName={props.enhancedPackage || props.pkgName}
 />
 
 ### Create {props.configName || 'module-federation.config.js'}

apps/website-new/docs/en/plugin/dev/index.mdx

@@ -1,12 +1,12 @@
 # Plugin System
 
-Module Federation provides a lightweight runtime plugin system for implementing most of its features and allowing users to extend functionalities.
+{props.brandName || props.name || 'Module Federation'} provides a lightweight runtime plugin system for implementing most of its features and allowing users to extend functionalities.
 
-Plugins developed by developers can modify the default behavior of `Module Federation` and add various additional features, including but not limited to:
+Plugins developed by developers can modify the default behavior of <code>{props.brandName || props.name || 'Module Federation'}</code> and add various additional features, including but not limited to:
 
 - Obtaining context information
 - Registering lifecycle hooks
-- Modifying Module Federation configurations
+- Modifying {props.brandName || props.name || 'Module Federation'} configurations
 - ...
 
 ## Developing Plugins