Limit PR scope based on title; keep only intended doc(s); revert unrelated files

Author: web-flow

docusaurus/docs/cms/admin-panel-customization/bundlers.md

@@ -80,15 +80,10 @@ strapi develop --bundler=webpack
 ```
 
 :::prerequisites
-If you plan to customize webpack, start from the example file in your project root. Rename:
-
-- `webpack.config.example.js` → `webpack.config.js` (JavaScript)
-- or `webpack.config.example.ts` → `webpack.config.ts` (TypeScript)
-
-Strapi will pick up `webpack.config.js` or `webpack.config.ts` automatically when you run `strapi develop --bundler=webpack`.
+Make sure to rename the default `webpack.config.example.js` file into `webpack.config.` before customizing webpack.
 :::
 
-To extend webpack v5, define a function that returns a modified config in `/src/admin/webpack.config.js` or `/src/admin/webpack.config.ts`:
+In order to extend the usage of webpack v5, define a function that extends its configuration inside `/src/admin/webpack.config.`:
 
 <Tabs groupId="js-ts">
 <TabItem value="js" label="JavaScript">
@@ -123,3 +118,4 @@ export default (config, webpack) => {
 
 </TabItem>
 </Tabs>
+

docusaurus/docs/cms/admin-panel-customization/host-port-path.md

@@ -95,7 +95,3 @@ export default ({ env }) => ({
 :::strapi Other admin panel configurations
 The `/config/admin.[ts|js]` file can be used to configure many other aspects. Please refer to the [admin panel configuration](/cms/configurations/admin-panel) documentation for details.
 :::
-
-:::tip Behind a reverse proxy
-When serving the admin from a different public origin (domain, host, or port) than the API, set `host`/`port` accordingly and ensure your proxy forwards headers (e.g., `X-Forwarded-*`). If the admin is reachable at a different origin, prefer configuring that origin explicitly.
-:::

docusaurus/docs/cms/admin-panel-customization/logos.md

@@ -11,10 +11,6 @@ tags:
 
 # Logos
 
-<Tldr>
-Update login and navigation logos by extending the admin app. Prefer SVG for crisp rendering; provide light/dark variants when possible for contrast.
-</Tldr>
-
 Strapi's [admin panel](/cms/admin-panel-customization) displays its branding on both the login screen and in the main navigation. Replacing these images allows you to match the interface to your identity. The present page shows how to override the two logo files via the admin panel configuration. If you prefer uploading them directly in the UI, see [Customizing the logo](/cms/features/admin-panel#customizing-the-logo).
 
 The Strapi admin panel displays a logo in 2 different locations, represented by 2 different keys in the admin panel configuration:

docusaurus/docs/cms/admin-panel-customization/theme-extension.md

@@ -21,25 +21,3 @@ To extend the theme, use either:
 :::strapi Strapi Design System
 The default <ExternalLink to="https://github.com/strapi/design-system/tree/main/packages/design-system/src/themes" text="Strapi theme"/> defines various theme-related keys (shadows, colors…) that can be updated through the `config.theme.light` and `config.theme.dark` keys in `./admin/src/app.js`. The <ExternalLink to="https://design-system.strapi.io/" text="Strapi Design System"/> is fully customizable and has a dedicated <ExternalLink to="https://design-system-git-main-strapijs.vercel.app" text="StoryBook"/> documentation.
 :::
-
-### Example (TypeScript)
-
-```ts title="/src/admin/app.ts"
-export default {
-  config: {
-    theme: {
-      light: {
-        colors: {
-          primary600: '#4A6EFF',
-        },
-      },
-      dark: {
-        colors: {
-          primary600: '#9DB2FF',
-        },
-      },
-    },
-  },
-  bootstrap() {},
-}
-```

docusaurus/docs/cms/admin-panel-customization/wysiwyg-editor.md

@@ -15,7 +15,3 @@ Strapi's [admin panel](/cms/admin-panel-customization) comes with a built-in ric
 
 - You can install a third-party plugin, such as one for CKEditor, by visiting <ExternalLink to="https://market.strapi.io/" text="Strapi's Marketplace"/>.
 - You can create your own plugin to create and register a fully custom WYSIWYG field (see [custom fields documentation](/cms/features/custom-fields)).
-
-:::tip Next steps
-When evaluating editors, start with a plugin from the Marketplace for a quick trial, then consider a custom field if you need deeper integration (schema, validation, or custom toolbar behavior).
-:::

docusaurus/docs/cms/backend-customization/controllers.md

@@ -29,10 +29,6 @@ In most cases, the controllers will contain the bulk of a project's business log
   <em><figcaption style={{fontSize: '12px'}}>The diagram represents a simplified version of how a request travels through the Strapi back end, with controllers highlighted. The backend customization introduction page includes a complete, <a href="/cms/backend-customization#interactive-diagram">interactive diagram</a>.</figcaption></em>
 </figure>
 
-:::caution Sanitize inputs and outputs
-When overriding core actions, always validate and sanitize queries and responses to avoid leaking private fields or bypassing access rules. Use `validateQuery` (optional), `sanitizeQuery` (recommended), and `sanitizeOutput` before returning data from custom actions. See the example below for a safe `find` override.
-:::
-
 ## Implementation
 
 Controllers can be [generated or added manually](#adding-a-new-controller). Strapi provides a `createCoreController` factory function that automatically generates core controllers and allows building custom ones or [extend or replace the generated controllers](#extending-core-controllers).
@@ -99,7 +95,7 @@ module.exports = createCoreController('api::restaurant.restaurant', ({ strapi })
 
 <TabItem value="ts" label="TypeScript">
 
-```ts title="./src/api/restaurant/controllers/restaurant.ts"
+```js title="./src/api/restaurant/controllers/restaurant.ts"
 
 import { factories } from '@strapi/strapi';
 

docusaurus/docs/cms/backend-customization/middlewares.md

@@ -108,7 +108,7 @@ module.exports = () => {
 
 <TabItem value="ts" label="TypeScript">
 
-```ts title="/config/middlewares.ts"
+```js title="/config/middlewares.ts"
 
 export default () => {
   return async (ctx, next) => {
@@ -129,10 +129,6 @@ export default () => {
 
 The GraphQL plugin also allows [implementing custom middlewares](/cms/plugins/graphql#middlewares), with a different syntax.
 
-:::tip Discover loaded middlewares
-Run `yarn strapi middlewares:list` to list all registered middlewares and double‑check naming when wiring them in routers.
-:::
-
 ## Usage
 
 Middlewares are called different ways depending on their scope:

docusaurus/docs/cms/backend-customization/models.md

@@ -16,10 +16,6 @@ tags:
 
 # Models
 
-<Tldr>
-Models define your content types’ shape and drive generated controllers and routes. Use the Document Service API to query/create/update data and keep controllers thin.
-</Tldr>
-
 <Tldr>
 Models define Strapi’s content structure via content-types and reusable components. This documentation walks through creating these models in the Content-type Builder or CLI and managing schema files with optional lifecycle hooks.
 </Tldr>

docusaurus/docs/cms/backend-customization/policies.md

@@ -24,7 +24,7 @@ Policies are functions that execute specific logic on each request before it rea
 
 Each [route](/cms/backend-customization/routes) of a Strapi project can be associated to an array of policies. For example, a policy named `is-admin` could check that the request is sent by an admin user, and restrict access to critical routes.
 
-Policies can be global or scoped. [Global policies](#global-policies) can be associated to any route in the project. Scoped policies only apply to a specific [API](#api-policies) or [plugin](#plugin-policies) and should live under the corresponding `./src/api/<api-name>/policies/` or `./src/plugins/<plugin-name>/policies/` folder.
+Policies can be global or scoped. [Global policies](#global-policies) can be associated to any route in the project. Scoped policies only apply to a specific [API](#api-policies) or [plugin](#plugin-policies).
 
 <figure style={{width: '100%', margin: '0'}}>
   <img src="/img/assets/backend-customization/diagram-routes.png" alt="Simplified Strapi backend diagram with routes and policies highlighted" />
@@ -89,7 +89,7 @@ Policies can be configured using a `config` object:
 <Tabs groupId="js-ts">
 <TabItem value="js" label="JavaScript">
 
-```js title="./src/api/[api-name]/policies/my-policy.js"
+```js title=".src/api/[api-name]/policies/my-policy.js"
 
 module.exports = (policyContext, config, { strapi }) => {
     if (policyContext.state.user.role.code === config.role) { // if user's role is the same as the one described in configuration

docusaurus/docs/cms/backend-customization/routes.md

@@ -97,7 +97,7 @@ module.exports = createCoreRouter('api::restaurant.restaurant', {
 
 <TabItem value="ts" label="TypeScript">
 
-```ts title="./src/api/[apiName]/routes/[routerName].ts (e.g './src/api/restaurant/routes/restaurant.ts')"
+```js title="./src/api/[apiName]/routes/[routerName].ts (e.g './src/api/restaurant/routes/restaurant.ts')"
 
 import { factories } from '@strapi/strapi'; 
 
@@ -149,7 +149,7 @@ module.exports = createCoreRouter('api::restaurant.restaurant', {
 
 <TabItem value="ts" label="TypeScript">
 
-```ts title="./src/api/restaurant/routes/restaurant.ts"
+```js title="./src/api/restaurant/routes/restaurant.ts"
 
 import { factories } from '@strapi/strapi'; 
 
@@ -168,7 +168,7 @@ export default factories.createCoreRouter('api::restaurant.restaurant', {
 </TabItem>
 </Tabs>
 
-This only allows a `GET` request on the `/restaurants` path from the core `find` [controller](/cms/backend-customization/controllers) without authentication. When you reference custom controller actions in custom routers, prefer the fully‑qualified `api::<api-name>.<controllerName>.<actionName>` form for clarity (e.g., `api::restaurant.restaurant.review`).
+This only allows a `GET` request on the `/restaurants` path from the core `find` [controller](/cms/backend-customization/controllers) without authentication.
 
 ### Creating custom routers