Use markdown syntax in mdx where possible
Closes #788
Luke Karrys committed
Oct 23, 2023 at 11:28 UTC
56006098185f25bc10309ccbdbce59c19948fc42
27 files changed
+45
-101
.eslintrc.js
-2
@@ -43,8 +43,6 @@ module.exports = {
43
},
44
rules: {
45
'no-irregular-whitespace': 'off',
46
- 'jsx-a11y/anchor-has-content': 'off',
47
- 'react/jsx-no-target-blank': 'off',
46
},
47
},
48
],
cli/lib/extract.js
+6
@@ -37,6 +37,12 @@ const unpackTarball = async ({release, cwd, dir}) => {
37
// the v6 version of the funding page has json not inside a code
38
.replace(/(:\n\n)(\s{4}"funding": {)/g, '$1```json\n$2')
39
.replace(/^(\s{4}]$)(\n\n)/gm, '$1\n```$2')
40
+ // anchor links to markdown. this regex does need to match spaces and newlines since the source markdown
41
+ // already has some links where attributes are separated by newlines
42
+ .replace(
43
+ /<a[\s\n]href="(.*?)"(?:[\s\n]target="_blank")?(?:[\s\n]rel="[a-z\s]+")?>(.*?)<\/a>/g,
44
+ (_, href, text) => `[${href}](${text.trim()})`,
45
+ )
46
)
47
}
48
content/cli/v10/commands/npm-audit.mdx
+2
-2
@@ -99,13 +99,13 @@ The `sig` is generated using the following template: `${package.name}@${package.
99
100
Keys response:
101
102
-- `expires`: null or a simplified extended <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 format</a>: `YYYY-MM-DDTHH:mm:ss.sssZ`
102
+- `expires`: null or a simplified extended [https://en.wikipedia.org/wiki/ISO_8601](ISO 8601 format): `YYYY-MM-DDTHH:mm:ss.sssZ`
103
- `keydid`: sha256 fingerprint of the public key
104
- `keytype`: only `ecdsa-sha2-nistp256` is currently supported by the npm CLI
105
- `scheme`: only `ecdsa-sha2-nistp256` is currently supported by the npm CLI
106
- `key`: base64 encoded public key
107
108
-See this <a href="https://registry.npmjs.org/-/npm/v1/keys" target="_blank">example key's response from the public npm registry</a>.
108
+See this [https://registry.npmjs.org/-/npm/v1/keys](example key's response from the public npm registry).
109
110
### Audit Endpoints
111
content/cli/v10/commands/npm-team.mdx
+1
-1
@@ -55,7 +55,7 @@ Teams must always be fully qualified with the organization/scope they belong to
55
56
If you have two-factor authentication enabled in `auth-and-writes` mode, then you can provide a code from your authenticator with `[--otp <otpcode>]`. If you don't include this then you will be taken through a second factor flow based on your `authtype`.
57
58
-- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, <a href="https://docs.npmjs.com/about-developers-team" target="_blank">learn more.</a>
58
+- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, [https://docs.npmjs.com/about-developers-team](learn more.)
59
60
Here's how to create a new team `newteam` under the `org` org:
61
content/cli/v10/commands/npm-unpublish.mdx
+1
-3
@@ -41,9 +41,7 @@ redirect_from:
41
npm unpublish [<package-spec>]
42
```
43
44
-To learn more about how the npm registry treats unpublish, see our <a
45
-href="https://docs.npmjs.com/policies/unpublish" target="_blank"
46
-rel="noopener noreferrer"> unpublish policies</a>
44
+To learn more about how the npm registry treats unpublish, see our [https://docs.npmjs.com/policies/unpublish](unpublish policies)
45
46
### Warning
47
content/cli/v6/commands/npm-team.mdx
+1
-1
@@ -41,7 +41,7 @@ Teams must always be fully qualified with the organization/scope they belong to
41
42
If you have two-factor authentication enabled in `auth-and-writes` mode, then you can provide a code from your authenticator with `[--otp <otpcode>]`. If you don't include this then you will be prompted.
43
44
-- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, <a href="https://docs.npmjs.com/about-developers-team" target="_blank">learn more.</a>
44
+- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, [https://docs.npmjs.com/about-developers-team](learn more.)
45
- add / rm: Add a user to an existing team, or remove a user from a team they belong to.
46
47
- ls: If performed on an organization name, will return a list of existing teams under that organization. If performed on a team, it will instead return a list of all users belonging to that particular team.
content/cli/v6/commands/npm-unpublish.mdx
+1
-1
@@ -45,7 +45,7 @@ If no version is specified, or if all versions are removed then the root package
45
46
Even if a package version is unpublished, that specific name and version combination can never be reused. In order to publish the package again, a new version number must be used. If you unpublish the entire package, you may not publish any new versions of that package until 24 hours have passed.
47
48
-To learn more about how unpublish is treated on the npm registry, see our <a href="https://www.npmjs.com/policies/unpublish" target="_blank" rel="noopener noreferrer"> unpublish policies</a>.
48
+To learn more about how unpublish is treated on the npm registry, see our [https://www.npmjs.com/policies/unpublish](unpublish policies).
49
50
### See Also
51
content/cli/v7/commands/npm-team.mdx
+1
-1
@@ -41,7 +41,7 @@ Teams must always be fully qualified with the organization/scope they belong to
41
42
If you have two-factor authentication enabled in `auth-and-writes` mode, then you can provide a code from your authenticator with `[--otp <otpcode>]`. If you don't include this then you will be prompted.
43
44
-- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, <a href="https://docs.npmjs.com/about-developers-team" target="_blank">learn more.</a>
44
+- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, [https://docs.npmjs.com/about-developers-team](learn more.)
45
46
Here's how to create a new team `newteam` under the `org` org:
47
content/cli/v7/commands/npm-unpublish.mdx
+1
-3
@@ -21,9 +21,7 @@ redirect_from:
21
22
### Synopsis
23
24
-To learn more about how the npm registry treats unpublish, see our <a
25
-href="https://docs.npmjs.com/policies/unpublish" target="_blank"
26
-rel="noopener noreferrer"> unpublish policies</a>
24
+To learn more about how the npm registry treats unpublish, see our [https://docs.npmjs.com/policies/unpublish](unpublish policies)
25
26
#### Unpublishing a single version of a package
27
content/cli/v8/commands/npm-audit.mdx
+2
-2
@@ -79,13 +79,13 @@ The `sig` is generated using the following template: `${package.name}@${package.
79
80
Keys response:
81
82
-- `expires`: null or a simplified extended <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 format</a>: `YYYY-MM-DDTHH:mm:ss.sssZ`
82
+- `expires`: null or a simplified extended [https://en.wikipedia.org/wiki/ISO_8601](ISO 8601 format): `YYYY-MM-DDTHH:mm:ss.sssZ`
83
- `keydid`: sha256 fingerprint of the public key
84
- `keytype`: only `ecdsa-sha2-nistp256` is currently supported by the npm CLI
85
- `scheme`: only `ecdsa-sha2-nistp256` is currently supported by the npm CLI
86
- `key`: base64 encoded public key
87
88
-See this <a href="https://registry.npmjs.org/-/npm/v1/keys" target="_blank">example key's response from the public npm registry</a>.
88
+See this [https://registry.npmjs.org/-/npm/v1/keys](example key's response from the public npm registry).
89
90
### Audit Endpoints
91
content/cli/v8/commands/npm-team.mdx
+1
-1
@@ -39,7 +39,7 @@ Teams must always be fully qualified with the organization/scope they belong to
39
40
If you have two-factor authentication enabled in `auth-and-writes` mode, then you can provide a code from your authenticator with `[--otp <otpcode>]`. If you don't include this then you will be prompted.
41
42
-- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, <a href="https://docs.npmjs.com/about-developers-team" target="_blank">learn more.</a>
42
+- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, [https://docs.npmjs.com/about-developers-team](learn more.)
43
44
Here's how to create a new team `newteam` under the `org` org:
45
content/cli/v8/commands/npm-unpublish.mdx
+1
-3
@@ -25,9 +25,7 @@ redirect_from:
25
npm unpublish [<package-spec>]
26
```
27
28
-To learn more about how the npm registry treats unpublish, see our <a
29
-href="https://docs.npmjs.com/policies/unpublish" target="_blank"
30
-rel="noopener noreferrer"> unpublish policies</a>
28
+To learn more about how the npm registry treats unpublish, see our [https://docs.npmjs.com/policies/unpublish](unpublish policies)
29
30
### Warning
31
content/cli/v9/commands/npm-audit.mdx
+2
-2
@@ -83,13 +83,13 @@ The `sig` is generated using the following template: `${package.name}@${package.
83
84
Keys response:
85
86
-- `expires`: null or a simplified extended <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 format</a>: `YYYY-MM-DDTHH:mm:ss.sssZ`
86
+- `expires`: null or a simplified extended [https://en.wikipedia.org/wiki/ISO_8601](ISO 8601 format): `YYYY-MM-DDTHH:mm:ss.sssZ`
87
- `keydid`: sha256 fingerprint of the public key
88
- `keytype`: only `ecdsa-sha2-nistp256` is currently supported by the npm CLI
89
- `scheme`: only `ecdsa-sha2-nistp256` is currently supported by the npm CLI
90
- `key`: base64 encoded public key
91
92
-See this <a href="https://registry.npmjs.org/-/npm/v1/keys" target="_blank">example key's response from the public npm registry</a>.
92
+See this [https://registry.npmjs.org/-/npm/v1/keys](example key's response from the public npm registry).
93
94
### Audit Endpoints
95
content/cli/v9/commands/npm-team.mdx
+1
-1
@@ -39,7 +39,7 @@ Teams must always be fully qualified with the organization/scope they belong to
39
40
If you have two-factor authentication enabled in `auth-and-writes` mode, then you can provide a code from your authenticator with `[--otp <otpcode>]`. If you don't include this then you will be taken through a second factor flow based on your `authtype`.
41
42
-- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, <a href="https://docs.npmjs.com/about-developers-team" target="_blank">learn more.</a>
42
+- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, [https://docs.npmjs.com/about-developers-team](learn more.)
43
44
Here's how to create a new team `newteam` under the `org` org:
45
content/cli/v9/commands/npm-unpublish.mdx
+1
-3
@@ -25,9 +25,7 @@ redirect_from:
25
npm unpublish [<package-spec>]
26
```
27
28
-To learn more about how the npm registry treats unpublish, see our <a
29
-href="https://docs.npmjs.com/policies/unpublish" target="_blank"
30
-rel="noopener noreferrer"> unpublish policies</a>
28
+To learn more about how the npm registry treats unpublish, see our [https://docs.npmjs.com/policies/unpublish](unpublish policies)
29
30
### Warning
31
content/getting-started/setting-up-your-npm-user-account/creating-a-new-npm-user-account.mdx
+2
-2
@@ -32,11 +32,11 @@ If you do not already have an npm user account, you can create an account in ord
32
33
## Testing your new account with npm login
34
35
-Use the <a href="https://docs.npmjs.com/cli/adduser">`npm login`</a> command to test logging in to your new account.
35
+Use the [`npm login`](https://docs.npmjs.com/cli/adduser) command to test logging in to your new account.
36
37
<Note>
38
39
-**Note:** If you misspell your existing account username when you log in with the `npm login` command, you will create a new account with the misspelled name. For help with accidentally-created accounts, <a href="https://www.npmjs.com/support">contact npm Support</a>.
39
+**Note:** If you misspell your existing account username when you log in with the `npm login` command, you will create a new account with the misspelled name. For help with accidentally-created accounts, [contact npm Support](https://www.npmjs.com/support).
40
41
</Note>
42
content/packages-and-modules/contributing-packages-to-the-registry/about-package-readme-files.mdx
+1
-1
@@ -14,7 +14,7 @@ An npm package README file must be in the root-level directory of the package.
14
15
<Note>
16
17
-**Note:** The file extension `.md` indicates a Markdown file. For more information about Markdown, see the GitHub Guide "<a href="https://guides.github.com/features/mastering-markdown/#what">Mastering Markdown</a>".
17
+**Note:** The file extension `.md` indicates a Markdown file. For more information about Markdown, see the GitHub Guide "[Mastering Markdown](https://guides.github.com/features/mastering-markdown/#what)".
18
19
</Note>
20
content/packages-and-modules/contributing-packages-to-the-registry/creating-and-publishing-private-packages.mdx
+3
-3
@@ -12,9 +12,9 @@ For more information on scopes and private packages, see "[About scopes][scopes]
12
13
<Note>
14
15
-**Note:** Before you can publish private user-scoped npm packages, you must <a href="https://npmjs.com/signup">sign up</a> for a paid npm user account.
15
+**Note:** Before you can publish private user-scoped npm packages, you must [sign up](https://npmjs.com/signup) for a paid npm user account.
16
17
-Additionally, to publish private organization-scoped packages, you must <a href="https://npmjs.com/signup">create an npm user account</a>, then <a href="https://www.npmjs.com/signup?next=/org/create"> create a paid npm organization</a>.
17
+Additionally, to publish private organization-scoped packages, you must [create an npm user account](https://npmjs.com/signup), then [ create a paid npm organization](https://www.npmjs.com/signup?next=/org/create).
18
19
</Note>
20
@@ -58,7 +58,7 @@ Additionally, to publish private organization-scoped packages, you must <a href=
58
npm init --scope=@my-username
59
```
60
61
-6. Respond to the prompts to generate a <a href="https://docs.npmjs.com/about-package-json-and-package-lock-json-files">`package.json`</a> file. For help naming your package, see "[Package name guidelines][pkg-name]".
61
+6. Respond to the prompts to generate a [`package.json`](https://docs.npmjs.com/about-package-json-and-package-lock-json-files) file. For help naming your package, see "[Package name guidelines][pkg-name]".
62
63
7. Create a [README file][readme-file] that explains what your package code is and how to use it.
64
content/packages-and-modules/contributing-packages-to-the-registry/creating-and-publishing-scoped-public-packages.mdx
+3
-3
@@ -10,9 +10,9 @@ For more information on scopes, see "[About scopes][scopes]".
10
11
<Note>
12
13
-**Note:** Before you can publish user-scoped npm packages, you must <a href="https://www.npmjs.com/signup">sign up</a> for an npm user account.
13
+**Note:** Before you can publish user-scoped npm packages, you must [sign up](https://www.npmjs.com/signup) for an npm user account.
14
15
-Additionally, to publish organization-scoped packages, you must <a href="https://www.npmjs.com/signup">create an npm user account</a>, then <a href="https://www.npmjs.com/signup?next=/org/create">create an npm organization</a>.
15
+Additionally, to publish organization-scoped packages, you must [create an npm user account](https://www.npmjs.com/signup), then [create an npm organization](https://www.npmjs.com/signup?next=/org/create).
16
17
</Note>
18
@@ -56,7 +56,7 @@ Additionally, to publish organization-scoped packages, you must <a href="https:/
56
npm init --scope=@my-username
57
```
58
59
-6. Respond to the prompts to generate a <a href="https://docs.npmjs.com/about-package-json-and-package-lock-json-files">`package.json`</a> file. For help naming your package, see "[Package name guidelines][pkg-name]".
59
+6. Respond to the prompts to generate a [`package.json`](https://docs.npmjs.com/about-package-json-and-package-lock-json-files) file. For help naming your package, see "[Package name guidelines][pkg-name]".
60
7. Create a [README file][readme-file] that explains what your package code is and how to use it.
61
8. In your preferred text editor, write the code for your package.
62
content/packages-and-modules/contributing-packages-to-the-registry/creating-and-publishing-unscoped-public-packages.mdx
+2
-2
@@ -12,7 +12,7 @@ For more information on package scope, access, and visibility, see "[Package sco
12
13
<Note>
14
15
-**Note:** Before you can publish public unscoped npm packages, you must <a href="https://www.npmjs.com/signup">sign up</a> for an npm user account.
15
+**Note:** Before you can publish public unscoped npm packages, you must [sign up](https://www.npmjs.com/signup) for an npm user account.
16
17
</Note>
18
@@ -38,7 +38,7 @@ For more information on package scope, access, and visibility, see "[Package sco
38
```
39
40
4. In the package root directory, run the `npm init` command.
41
-5. Respond to the prompts to generate a <a href="https://docs.npmjs.com/about-package-json-and-package-lock-json-files">`package.json`</a> file. For help naming your package, see "[Package name guidelines][pkg-name]".
41
+5. Respond to the prompts to generate a [`package.json`](https://docs.npmjs.com/about-package-json-and-package-lock-json-files) file. For help naming your package, see "[Package name guidelines][pkg-name]".
42
6. Create a [README file][readme-file] that explains what your package code is and how to use it.
43
7. In your preferred text editor, write the code for your package.
44
content/packages-and-modules/introduction-to-packages-and-modules/package-scope-access-level-and-visibility.mdx
+1
-1
@@ -6,7 +6,7 @@ Visibility of npm packages depends on the scope (namespace) in which the package
6
7
<Note>
8
9
-**Note:** To create organization-scoped packages, you must first create an organization. For more information, see "<a href="https://docs.npmjs.com/creating-an-organization">Creating an organization</a>".
9
+**Note:** To create organization-scoped packages, you must first create an organization. For more information, see "[Creating an organization](https://docs.npmjs.com/creating-an-organization)".
10
11
</Note>
12
content/packages-and-modules/securing-your-code/about-registry-signatures.mdx
+5
-5
@@ -18,7 +18,7 @@ The public npm registry is migrating away from the existing PGP signatures to EC
18
19
Signature verification was previously a multi-step process involving the Keybase CLI, as well as manually retrieving and parsing the signature from the package metadata.
20
21
-Read more about <a href="/verifying-registry-signatures">migrating and verifying signatures</a> using the npm CLI.
21
+Read more about [migrating and verifying signatures](/verifying-registry-signatures) using the npm CLI.
22
23
## Supporting signatures on third-party registries
24
@@ -35,11 +35,11 @@ The npm CLI supports registry signatures and signing keys provided by any regist
35
}],
36
```
37
38
-See this <a href="https://registry.npmjs.org/light-cycle/1.4.3" target="_blank">example of a signed package from the public npm registry</a>.
38
+See this [example of a signed package from the public npm registry](https://registry.npmjs.org/light-cycle/1.4.3).
39
40
To generate the signature, sign the package name, version and tarball sha integrity: `${package.name}@${package.version}:${package.dist.integrity}`.
41
42
-The current best practice is to use a <a href="https://en.wikipedia.org/wiki/Key_management#Key_management_system" target="_blank">Key Management System</a> that does the signing operation on a <a href="https://en.wikipedia.org/wiki/Hardware_security_module" target="_blank">Hardware Security Module (HSM)</a> in order to not directly handle the private key part, which reduces the attack surface.
42
+The current best practice is to use a [Key Management System](https://en.wikipedia.org/wiki/Key_management#Key_management_system) that does the signing operation on a [Hardware Security Module (HSM)](https://en.wikipedia.org/wiki/Hardware_security_module) in order to not directly handle the private key part, which reduces the attack surface.
43
44
The `keyid` must match one of the public signing keys below.
45
@@ -59,10 +59,10 @@ The `keyid` must match one of the public signing keys below.
59
60
Keys response:
61
62
-- `expires`: null or a simplified extended <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 format</a>: `YYYY-MM-DDTHH:mm:ss.sssZ`
62
+- `expires`: null or a simplified extended [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601): `YYYY-MM-DDTHH:mm:ss.sssZ`
63
- `keydid`: sha256 fingerprint of the public key
64
- `keytype`: only `ecdsa-sha2-nistp256` is currently supported by the npm CLI
65
- `scheme`: only `ecdsa-sha2-nistp256` is currently supported by the npm CLI
66
- `key`: base64 encoded public key
67
68
-See this <a href="https://registry.npmjs.org/-/npm/v1/keys" target="_blank">example key's response from the public npm registry</a>.
68
+See this [example key's response from the public npm registry](https://registry.npmjs.org/-/npm/v1/keys).
content/packages-and-modules/securing-your-code/auditing-package-dependencies-for-security-vulnerabilities.mdx
+1
-1
@@ -16,7 +16,7 @@ A security audit is an assessment of package dependencies for security vulnerabi
16
17
</Note>
18
19
-The <a href="https://docs.npmjs.com/cli/audit">`npm audit` command</a> submits a description of the dependencies configured in your package to your default registry and asks for a report of known vulnerabilities. `npm audit` checks direct dependencies, devDependencies, bundledDependencies, and optionalDependencies, but does not check peerDependencies.
19
+The [`npm audit` command](https://docs.npmjs.com/cli/audit) submits a description of the dependencies configured in your package to your default registry and asks for a report of known vulnerabilities. `npm audit` checks direct dependencies, devDependencies, bundledDependencies, and optionalDependencies, but does not check peerDependencies.
20
21
`npm audit` automatically runs when you install a package with `npm install`. You can also run `npm audit` manually on your [locally installed packages](downloading-and-installing-packages-locally) to conduct a security audit of the package and produce a report of dependency vulnerabilities and, if available, suggested patches.
22
content/packages-and-modules/updating-and-managing-your-published-packages/changing-package-visibility.mdx
+1
-1
@@ -39,7 +39,7 @@ To make a public package private on the command line, run the following command,
39
npm access restricted <package-name>
40
```
41
42
-For more information, see the <a href="https://docs.npmjs.com/cli-documentation/access">`npm access`</a> documentation.
42
+For more information, see the [`npm access`](https://docs.npmjs.com/cli-documentation/access) documentation.
43
44
## Making a private package public
45
content/packages-and-modules/updating-and-managing-your-published-packages/deprecating-and-undeprecating-packages-or-package-versions.mdx
+1
-1
@@ -10,7 +10,7 @@ A deprecation warning or message can say anything. You may wish to include a mes
10
11
<Note>
12
13
-**Note:** We strongly recommend deprecating packages or package versions instead of <a href="/unpublishing-packages-from-the-registry">unpublishing</a> them, because unpublishing removes a package from the registry entirely, meaning anyone who relied on it will no longer be able to use it, with no warning.
13
+**Note:** We strongly recommend deprecating packages or package versions instead of [unpublishing](/unpublishing-packages-from-the-registry) them, because unpublishing removes a package from the registry entirely, meaning anyone who relied on it will no longer be able to use it, with no warning.
14
15
</Note>
16
src/shared.js
+3
-55
@@ -1,5 +1,5 @@
1
import React from 'react'
2
-import {Link, Note, Screenshot, ul as Ul} from './mdx'
2
+import {Link, Screenshot, ul as Ul} from './mdx'
3
4
const shared = {
5
/* User login */
@@ -109,11 +109,11 @@ const shared = {
109
text: (
110
<>
111
In the credit card information dialog box, enter your credit card information:
112
- <ul>
112
+ <Ul>
113
<li>Card number</li>
114
<li>MM / YY: the month and year of the card expiration date</li>
115
<li>CVC: the three-digit code on the credit card</li>
116
- </ul>
116
+ </Ul>
117
</>
118
),
119
image: <Screenshot src="/shared/billing-creditcard-form.png" alt="Screenshot of the credit card form" />,
@@ -340,58 +340,6 @@ const shared = {
340
),
341
image: <Screenshot src="/shared/organization-teams-tab.png" alt="Screenshot of the organization teams tab" />,
342
},
343
-
344
- /* Enterprise */
345
- 'enterprise-admin-panel': {
346
- text: (
347
- <>
348
- In the upper right corner of the page, click your profile picture, then click{' '}
349
- <strong>Site Administration</strong>.
350
- </>
351
- ),
352
- image: <Screenshot src="/shared/enterprise-admin-panel.png" alt="Screenshot of the admin panel" />,
353
- },
354
- 'enterprise-admin-panel-settings': {
355
- image: (
356
- <Screenshot
357
- src="/shared/enterprise-admin-panel-settings.png"
358
- alt="Screenshot of the admin panel settings button"
359
- />
360
- ),
361
- },
362
- 'enterprise-choose-security-policy': {
363
- image: (
364
- <Screenshot src="/shared/enterprise-choose-security-policy.png" alt="Screenshot of the choose security policy" />
365
- ),
366
- },
367
- 'enterprise-custom-blocking-message': {
368
- image: (
369
- <Screenshot
370
- src="/shared/enterprise-custom-blocking-message.png"
371
- alt="Screenshot of the custom blocking message option"
372
- />
373
- ),
374
- },
375
- 'enterprise-instance-login': {
376
- text: <>Log in to your Enterprise instance.</>,
377
- },
378
- 'enterprise-migration-requirements': {
379
- text: (
380
- <Note>
381
- <strong>Note:</strong> Using{' '}
382
- <code>
383
- <a href="https://www.npmjs.com/package/pneumatic-tubes">pneumatic-tubes</a>
384
- </code>{' '}
385
- for migration requires{' '}
386
- <ul>
387
- <li>Node 8+</li>
388
- <li>
389
- npm 5+ (to install or upgrade, run <code>npm install npm@latest -g</code>)
390
- </li>
391
- </ul>
392
- </Note>
393
- ),
394
- },
343
}
344
345
export default shared
static/shared/enterprise-custom-blocking-message
Binary files a/static/shared/enterprise-custom-blocking-message and /dev/null differ