@atlassian/clientside-extensions-docs 2.4.0-dd1c430-kra20i84 → 2.4.1-docs-1

package/README.md

@@ -8,11 +8,8 @@ These docs will be published at:
 
 ## Preview
 
-`yarn preview`
-
-This will first install the Docker image needed to run the Atlassian Docs locally, and then start the server with the content locally at:
-
-[http://localhost:8080/server/framework/clientside-extensions](http://localhost:8080/server/framework/clientside-extensions)
+1. Install [Atlas CLI](https://developer.atlassian.com/platform/atlas-cli/users/install/) and DAC plugin `atlas plugin install -n dac`.
+2. Run `yarn start` to start the server with the content locally at : [http://localhost:8080/server/framework/clientside-extensions](http://localhost:8080/server/framework/clientside-extensions)
 
 ## Validation
 

package/content/server/framework/clientside-extensions/get-help.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: help
 subcategory: get-help
-date: '2021-07-19'
+date: '2021-10-12'
 ---
 
 # Get help
@@ -33,4 +33,4 @@ At the bottom of the page, there should be a green “Contact Support” button
 
 ## Additional links
 
--   Check the [Debugging and troubleshooting an extension guide](/server/framework/clientside-extensions/guides/how-to/debugging-and-troubleshooting-an-extension/debugging-and-troubleshooting-an-extension)
+-   Check the [Debugging and troubleshooting an extension guide](/server/framework/clientside-extensions/guides/how-to/debugging-and-troubleshooting-an-extension)

package/content/server/framework/clientside-extensions/guides/extension-points/creating-an-extension-point.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: extension-points
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Creating an extension point

package/content/server/framework/clientside-extensions/guides/extension-points/extension-point-documentation.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: extension-points
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Extension point documentation

package/content/server/framework/clientside-extensions/guides/extension-points/index.md

@@ -4,22 +4,25 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: extension-points
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Getting started
 
 {{% warning %}}
-The APIs for creating extension points are based on the React framework and Atlaskit, meaning you can only use them if you're developing with React.
+The APIs for creating extension points are based on the React framework and Atlaskit, meaning you can
+only use them if you're developing with React.
 
 A framework agnostic solution is being designed and will be available on a future release.
 {{% /warning %}}
 
 For this tutorial, you will be creating an extension point on a page in Bitbucket Server 7.x.
 
-The Bitbucket Server team provides a template to create a Bitbucket Plugin with all the tools already configured for you, including Client-side Extensions (CSE).
+The Bitbucket Server team provides a template to create a Bitbucket Plugin with all the tools already configured for
+you, including Client-side Extensions (CSE).
 
-You can grab a copy by cloning the [Bitbucket CSE template](https://bitbucket.org/atlassianlabs/bitbucket-client-side-extensions-template):
+You can grab a copy by cloning
+the [Bitbucket CSE template](https://bitbucket.org/atlassianlabs/bitbucket-client-side-extensions-template):
 
 ```
 git clone git@bitbucket.org:atlassianlabs/bitbucket-client-side-extensions-template.git
@@ -27,7 +30,8 @@ git clone git@bitbucket.org:atlassianlabs/bitbucket-client-side-extensions-templ
 
 {{% note %}}
 If you want to create extension points on your own project, follow the guide on
-[how to setup CSE schema-loader](/server/framework/clientside-extensions/guides/how-to/setup-schema-loader/) before you get started.
+[how to setup CSE schema-loader](/server/framework/clientside-extensions/guides/how-to/setup-schema-loader/) before you
+get started.
 {{% /note %}}
 
 ## Installing the requirements
@@ -53,9 +57,25 @@ To start Bitbucket from your project, run:
 atlas-run -DskipTests
 ```
 
+Once the Bitbucket starts, you should see this message in the terminal:
+
+```
+bitbucket started successfully in XYZs at http://localhost:7990/bitbucket
+```
+
+Now, you can open the browser and navigate to http://localhost:7990/bitbucket
+
+### Default credentials
+
+The local instance of Bitbucket requires you to log in using those credentials:
+
+-   username: `admin`
+-   password: `admin`
+
 ## Developing
 
-The template comes with watchmode and hot reload configured for your front-end code. You can run the CSE watch server by executing:
+The template comes with watchmode and hot reload configured for your front-end code. You can run the CSE watch server by
+executing:
 
 ```
 npm start
@@ -63,12 +83,14 @@ npm start
 
 ## Working directory
 
-You will be working on a blank page created with [CSE page extensions](/server/framework/clientside-extensions/reference/api/extension-factories/page/),
-and will create an extension point named `extension.points.tutorial`.
+You will be working on a blank page created
+with [CSE page extensions](/server/framework/clientside-extensions/reference/api/extension-factories/page/), and will
+create an extension point named `extension.points.tutorial`.
 
 {{% note %}}
-It is not necessary to use [CSE page extensions](/server/framework/clientside-extensions/reference/api/extension-factories/page/) to create an extension point. This guide uses them
-to provide a clean environment for working with extension point APIs.
+It is not necessary to
+use [CSE page extensions](/server/framework/clientside-extensions/reference/api/extension-factories/page/) to create an
+extension point. This guide uses them to provide a clean environment for working with extension point APIs.
 {{% /note %}}
 
 All the exercises are going to be developed inside this directory:
@@ -77,14 +99,16 @@ All the exercises are going to be developed inside this directory:
 
 There you will find:
 
--   `./extension-points-page.jsx`: the blank page where you are going to create your extension point and render the extensions
+-   `./extension-points-page.jsx`: the blank page where you are going to create your extension point and render the
+    extensions
 -   `./extensions/`: a set of extensions that you're going fetch and render throughout the guides.
 
-Once you install and start Bitbucket Server from the template, you can head to the tutorial page
-and should see the title `extension.points.tutorial`
+Once you install and start Bitbucket Server from the template, you can head to the tutorial page and should see the
+title `extension.points.tutorial`
 
 -   http://localhost:7990/bitbucket/plugins/servlet/extension-points
 
 ## You're ready!
 
-You're now ready to [create your first extension point](/server/framework/clientside-extensions/guides/extension-points/creating-an-extension-point/)!
+You're now ready
+to [create your first extension point](/server/framework/clientside-extensions/guides/extension-points/creating-an-extension-point/)!

package/content/server/framework/clientside-extensions/guides/extension-points/providing-context.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: extension-points
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Providing context

package/content/server/framework/clientside-extensions/guides/extension-points/rendering-extensions.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: extension-points
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Rendering extensions

package/content/server/framework/clientside-extensions/guides/how-to/debugging-and-troubleshooting-an-extension.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: how-to
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Debugging and troubleshooting an extension
@@ -32,13 +32,14 @@ Before you start troubleshooting the extension code, first, you should first ens
 
 ### Check if your plugin was loaded
 
-1. First, you need to start the application, open the web browser, and navigate to the administration panel.
-2. Next, find and navigate to the **Manage Apps** page.
-3. On the list of all installed plugins, locate your plugin using **App key** (**plugin key**), and check whether all the plugin's modules are enabled:
+1. First, you need to start the application, open the web browser, and navigate to the administration panel of your application.
+1. If you are using a local instance of Bitbucket or [Bitbucket CSE Template](https://bitbucket.org/atlassianlabs/bitbucket-client-side-extensions-template) project to develop the plugin, then use `admin` as the user and `admin` as the password to log in into the administration panel.
+1. Next, find and navigate to the **Manage Apps** page.
+1. On the list of all installed plugins, locate your plugin using **App key** (**plugin key**), and check whether all the plugin's modules are enabled:
 
     ![Manage Apps](/server/framework/clientside-extensions/guides/how-to/debugging-and-troubleshooting-an-extension/plugin-troubleshooting.png)
 
-4. If your plugin is on the list and all the modules are enabled, you can proceed to the next step.
+1. If your plugin is on the list and all the modules are enabled, you can proceed to the next step.
 
 {{% tip %}}
 

package/content/server/framework/clientside-extensions/guides/how-to/setup-page-bootstrapper.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: how-to
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Setting up the CSE page bootstrapper

package/content/server/framework/clientside-extensions/guides/how-to/setup-schema-loader.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: how-to
-date: '2021-06-29'
+date: '2021-11-29'
 ---
 
 # Setting up the CSE schema-loader
@@ -36,10 +36,16 @@ In your webpack configuration, configure the loader to match `.cse.graphql` file
 
 module.exports = {
     // your webpack config
-    entry: { /**/ },
-    output: {/**/},
-    plugins: [/**/],
-    ...
+    entry: {
+        /**/
+    },
+    output: {
+        /**/
+    },
+    plugins: [
+        /**/
+    ],
+    // ...
 
     module: {
         rules: [
@@ -52,13 +58,13 @@ module.exports = {
                     cwd: path.resolve(__dirname, 'src', 'schemas'),
                 },
             },
-        ]
-    }
+        ],
+    },
 };
 ```
 
 After configuring the loader, you will be able to import the [hooks and components](/server/framework/clientside-extensions/reference/api/extension-points/hooks-and-components/)
-directly from the schema as follow:
+directly from the schema as follows:
 
 `schema.cse.graphql`
 
@@ -97,7 +103,7 @@ const ExampleExtensionPoint = ({ context }) => {
 
     return (
         <>
-            {extensions.map(({attributes}) => <a href={attributes.url}>{attributes.label}</a>}
+            {extensions.map(({attributes}) => (<a href={attributes.url}>{attributes.label}</a>)}
         </>
     )
 }
@@ -105,65 +111,29 @@ const ExampleExtensionPoint = ({ context }) => {
 export default ExampleExtensionPoint;
 ```
 
-## 3. Generic code
-
-If you do not use React, there is a way to instead generate plain vanilla JavaScript code.
-For this to happen, set the _generic_ option to `true`.
-
-```js
-// #webpack.config.js
-
-module.exports = {
-    // your webpack config
-    entry: { /**/ },
-    output: {/**/},
-    plugins: [/**/],
-    ...
-
-    module: {
-        rules: [
-            // Add a rule entry to the list of loaders
-            {
-                test: /\.cse.graphql$/,
-                loader: '@atlassian/clientside-extensions-schema/loader',
-                options: {
-                    // You can specify a working dir
-                    cwd: path.resolve(__dirname, 'src', 'schemas'),
-                },
-            },
-            // Rule to handle non-react extensions
-            {
-                test: /\.cse.generic.graphql$/,
-                loader: '@atlassian/clientside-extensions-schema/loader',
-                options: {
-                    cwd: path.resolve(__dirname, 'src', 'schemas'),
-                    // Enables vanilla javascript code generation
-                    generic: true
-                },
-            },
-        ]
-    }
-};
-```
-
-## 4. Sharing scalars and types
+## 3. Sharing scalars and types
 
 CSE provides a set of default [scalars and types](/server/framework/clientside-extensions/reference/api/extension-points/schemas/#provided-scalars)
 that you will be using very often, but there are cases where you would like to share your own types and scalars
 between schema definitions.
 
-To do so, you can declare files with a name like `*.type.graphql` and configure the loader to include those
-definition for all your schemas as follow:
+To do so, you can declare files with a name like `*.type.graphql` and configure the loader to include those definitions for all your schemas as follows:
 
 ```js
 // #webpack.config.js
 
 module.exports = {
     // your webpack config
-    entry: { /**/ },
-    output: {/**/},
-    plugins: [/**/],
-    ...
+    entry: {
+        /**/
+    },
+    output: {
+        /**/
+    },
+    plugins: [
+        /**/
+    ],
+    // ...
 
     module: {
         rules: [
@@ -173,11 +143,11 @@ module.exports = {
                 options: {
                     cwd: path.resolve(__dirname, 'src', 'schemas'),
                     // configure a pattern for your own shared types
-                    providedTypes: '**/*.type.graphql'
+                    providedTypes: '**/*.type.graphql',
                 },
             },
-        ]
-    }
+        ],
+    },
 };
 ```
 
@@ -237,13 +207,15 @@ When using `webpack` to load your extensions with the schema-loader at `@atlassi
 you need to tell your test-runner how to interpret those imports. This `jest-transformer` will do exactly this, if you
 run your tests using jest.
 
-To use it add the following to your `jest`config:
+To use it, add the following entry to your Jest `jest.config.js` config file:
 
 ```js
-transform: {
-  // A custom GraphQL transformer that provides React hooks and components for CSE
-  '^.+\\.extension\\.graphql$': require.resolve('@atlassian/clientside-extensions-schema/jest-graphql-transformer.js'),
-},
+module.exports = {
+    transform: {
+        // A custom GraphQL transformer that provides React hooks and components for CSE
+        '^.+\\.extension\\.graphql$': require.resolve('@atlassian/clientside-extensions-schema/jest-graphql-transformer.js'),
+    },
+};
 ```
 
 {{% note %}}

package/content/server/framework/clientside-extensions/guides/how-to/setup-webpack-plugin.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: how-to
-date: '2021-06-29'
+date: '2021-11-29'
 ---
 
 # Setting up the CSE webpack plugin
@@ -64,7 +64,7 @@ module.exports = {
 
 ## 3. Configuring WRM webpack plugin
 
-CSE webpack plugin makes use of [WRM webpack plugin](https://bitbucket.org/atlassianlabs/atlassian-webresource-webpack-plugin/src) to generate the
+CSE webpack plugin makes use of [WRM webpack plugin](https://www.npmjs.com/package/atlassian-webresource-webpack-plugin) to generate the
 resource definitions for your extensions, so you also need to configure it.
 
 In your webpack configuration, import `atlassian-webresource-webpack-plugin` and use as follows:
@@ -168,3 +168,17 @@ module.exports = {
     },
 };
 ```
+
+## 5. Self troubleshooting tool
+
+We provide a tool that helps troubleshoot the configuration of webpack and Atlassian P2 projects.
+
+To check if your project was configured correctly, open a terminal and navigate to the root directory of your project. Next, run the troubleshooting command:
+
+```shell
+npx @atlassian/wrm-troubleshooting
+```
+
+The tool will ask you a few questions and guide you if it finds issues with your projects' configuration.
+
+You can read more about the troubleshooting tool on the [NPM page for the `@atlassian/wrm-troubleshooting` package](https://www.npmjs.com/package/@atlassian/wrm-troubleshooting).

package/content/server/framework/clientside-extensions/guides/introduction/creating-a-modal.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: introduction
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Creating a modal

package/content/server/framework/clientside-extensions/guides/introduction/creating-a-page.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: introduction
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Creating a page

package/content/server/framework/clientside-extensions/guides/introduction/creating-an-extension.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: introduction
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Creating an Extension

package/content/server/framework/clientside-extensions/guides/introduction/custom-HTML-content.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: introduction
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Custom HTML content

package/content/server/framework/clientside-extensions/guides/introduction/discovering-extension-points.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: introduction
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Discovering extension points

package/content/server/framework/clientside-extensions/guides/introduction/index.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: introduction
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Getting started
@@ -49,9 +49,24 @@ To start Bitbucket from your project, run:
 atlas-run -DskipTests
 ```
 
+Once the Bitbucket starts, you should see this message in the terminal:
+
+```
+bitbucket started successfully in XYZs at http://localhost:7990/bitbucket
+```
+
+Now, you can open the browser and navigate to http://localhost:7990/bitbucket
+
+### Default credentials
+
+The local instance of Bitbucket requires you to log in using those credentials:
+
+-   username: `admin`
+-   password: `admin`
+
 ## Developing
 
-The template comes with watchmode and hot reload configured for your front-end code. You can run the CSE watch server executing:
+The template comes with watchmode and hot reload configured for your front-end code. You can run the CSE watch server by executing:
 
 ```
 npm start

package/content/server/framework/clientside-extensions/guides/introduction/using-extension-api.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: introduction
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Using the extensions API

package/content/server/framework/clientside-extensions/index.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: index
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # About Client-side Extensions

package/content/server/framework/clientside-extensions/reference/api/extension-api/async-panel-api.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # AsyncPanel API

package/content/server/framework/clientside-extensions/reference/api/extension-api/index.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Extension API

package/content/server/framework/clientside-extensions/reference/api/extension-api/modal-api.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Modal API

package/content/server/framework/clientside-extensions/reference/api/extension-api/panel-api.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Panel API

package/content/server/framework/clientside-extensions/reference/api/extension-api/render-element-as-react.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Render element as React

package/content/server/framework/clientside-extensions/reference/api/extension-factories/async-panel.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # AsyncPanel

package/content/server/framework/clientside-extensions/reference/api/extension-factories/button.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Button

package/content/server/framework/clientside-extensions/reference/api/extension-factories/index.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Extension Factories

package/content/server/framework/clientside-extensions/reference/api/extension-factories/link.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Link

package/content/server/framework/clientside-extensions/reference/api/extension-factories/modal.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Modal

package/content/server/framework/clientside-extensions/reference/api/extension-factories/page.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Page

package/content/server/framework/clientside-extensions/reference/api/extension-factories/panel.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Panel

package/content/server/framework/clientside-extensions/reference/api/extension-points/extension-handlers.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Extension Handlers

package/content/server/framework/clientside-extensions/reference/api/extension-points/hooks-and-components.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Hooks and Components

package/content/server/framework/clientside-extensions/reference/api/extension-points/index.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Extension Points
@@ -82,7 +82,7 @@ import { useExtensions } from './schema.cse.graphql';
 ```
 
 {{% tip %}}
-Follow the [How to setup CSE schema-loader](/server/framework/clientside-extensions/reference/guides/how-to/setup-schema-loader)
+Follow the [How to setup CSE schema-loader](/server/framework/clientside-extensions/guides/how-to/setup-schema-loader)
 to learn how to install and configure the loader.
 {{% /tip %}}
 

package/content/server/framework/clientside-extensions/reference/api/extension-points/schemas.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Schemas

package/content/server/framework/clientside-extensions/reference/api/extension-points-v1-deprecated.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: api
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Extension Points v1 (deprecated)
@@ -18,7 +18,7 @@ guide for the latest API.
 
 This is a guide for product developers or extension point owners.
 
-First, make sure to install and provide Client-side Extensions in your Product as described in the [Installation Guide](https://bitbucket.org/atlassian/atlassian-clientside-extensions/src/master/INSTALLATION.md).
+First, make sure to install and provide Client-side Extensions in your Product as described in the [Installation Guide for v1](https://bitbucket.org/atlassian/atlassian-clientside-extensions/src/v1.2.9/INSTALLATION.md).
 
 Next, add `@atlassian/clientside-extensions-components` to your project.
 These are a set of React components and hooks that will help you use the APIs when your code is written in React. As of this point no other framework is supported.
@@ -310,8 +310,8 @@ dropdown (place it in the dropdown trigger), or part of a Grid (place it in the
 
 ## Default extension types and handlers
 
-Handlers continue to work the same on the recent version of CSE. Refer to the [extension handlers](/server/framework/clientside-extensions/reference/api/extension-handlers/) guide to learn how to use them.
+Handlers continue to work the same on the recent version of CSE. Refer to the [extension handlers](/server/framework/clientside-extensions/reference/api/extension-points/extension-handlers/) guide to learn how to use them.
 
 {{% warning %}}
-Refer to the [extension handlers](/server/framework/clientside-extensions/reference/api/extension-handlers/) guide.
+Refer to the [extension handlers](/server/framework/clientside-extensions/reference/api/extension-points/extension-handlers/) guide.
 {{% /warning %}}

package/content/server/framework/clientside-extensions/reference/glossary/index.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: glossary
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Glossary

package/content/server/framework/clientside-extensions/reference/webpack-plugin/annotations.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: webpack
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Annotations

package/content/server/framework/clientside-extensions/reference/webpack-plugin/webpack-plugin.md

@@ -4,12 +4,12 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: webpack
-date: '2021-06-29'
+date: '2021-10-12'
 ---
 
 # Webpack plugin
 
-Client-side Extensions webpack plugin depends on [WRM webpack plugin](https://bitbucket.org/atlassianlabs/atlassian-webresource-webpack-plugin/src).
+Client-side Extensions webpack plugin depends on [WRM webpack plugin](https://www.npmjs.com/package/atlassian-webresource-webpack-plugin).
 
 Refer to the [setup guide](/server/framework/clientside-extensions/guides/how-to/setup-webpack-plugin/) to check how to install and configure the webpack plugin.
 
@@ -62,3 +62,17 @@ module.exports = {
     /*...*/
 };
 ```
+
+## Self troubleshooting tool
+
+We provide a tool that helps troubleshoot the configuration of webpack and Atlassian P2 projects.
+
+To check if your project was configured correctly, open a terminal and navigate to the root directory of your project. Next, run the troubleshooting command:
+
+```shell
+npx @atlassian/wrm-troubleshooting
+```
+
+The tool will ask you a few questions and guide you if it finds issues with your projects' configuration.
+
+You can read more about the troubleshooting tool on the [NPM page for the `@atlassian/wrm-troubleshooting` package][https://www.npmjs.com/package/@atlassian/wrm-troubleshooting].

package/data/clientside-extensions.json

@@ -247,6 +247,10 @@
         {
             "from": "/reference/api/render-element-as-react/",
             "to": "/reference/api/extension-api/render-element-as-react/"
+        },
+        {
+            "from": "/reference/api/extension-handlers/",
+            "to": "/reference/api/extension-points/extension-handlers/"
         }
     ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@atlassian/clientside-extensions-docs",
-    "version": "2.4.0-dd1c430-kra20i84",
+    "version": "2.4.1-docs-1",
     "description": "Holds the official documentation for Altassian Server client-side extensions API.",
     "license": "BSD-3-Clause",
     "homepage": "https://bitbucket.org/atlassian/atlassian-clientside-extensions#readme",
@@ -63,9 +63,9 @@
         }
     ],
     "scripts": {
-        "start": "npm run preview",
+        "start": "atlas dac watch",
         "usage": "doc-scripts usage",
-        "preview": "doc-scripts preview",
+        "preview": "atlas dac watch",
         "lint": "yarn spellcheck && yarn prettier",
         "prettier": "prettier --check '**/*.{json,md}'",
         "spellcheck": "doc-scripts spellcheck",
@@ -77,7 +77,7 @@
         "doc-scripts": "doc-scripts"
     },
     "optionalDependencies": {
-        "@atlassian/doc-scripts": "^4.0.4"
+        "@atlassian/doc-scripts": "^5.0.0"
     },
-    "gitHead": "dd1c430a335d83e079c7bf0bc39ffb23147dff9b"
+    "gitHead": "4c98bad371a4fff8afcef318bb67ed86727fb877"
 }