2021-06-04 11:17:15 +02:00
|
|
|
/**
|
|
|
|
|
* Creating a sidebar enables you to:
|
|
|
|
|
- create an ordered group of docs
|
|
|
|
|
- render a sidebar for each doc of that group
|
|
|
|
|
- provide next/previous navigation
|
|
|
|
|
|
|
|
|
|
The sidebars can be generated from the filesystem, or explicitly defined here.
|
|
|
|
|
|
|
|
|
|
Create as many sidebars as you want.
|
|
|
|
|
*/
|
|
|
|
|
|
2024-01-18 17:39:25 +01:00
|
|
|
// TODO: Add warning to legacy API docs - but generated items
|
|
|
|
|
// TODO: Continue to clean URLs & redirects - but wait for SEO results first
|
2023-10-31 15:38:03 +01:00
|
|
|
|
|
|
|
|
|
2021-06-04 11:17:15 +02:00
|
|
|
module.exports = {
|
2024-01-29 19:30:18 +01:00
|
|
|
academy: [
|
2022-01-12 11:44:14 +01:00
|
|
|
{
|
2023-10-31 15:38:03 +01:00
|
|
|
label: 'Unleash Academy',
|
|
|
|
|
collapsed: true,
|
2022-01-24 13:41:29 +01:00
|
|
|
type: 'category',
|
|
|
|
|
link: {
|
2023-10-10 23:18:59 +02:00
|
|
|
type: 'doc',
|
2023-10-31 15:38:03 +01:00
|
|
|
id: 'unleash-academy/introduction',
|
2022-01-24 13:41:29 +01:00
|
|
|
},
|
|
|
|
|
items: [
|
2023-10-31 15:38:03 +01:00
|
|
|
'unleash-academy/foundational',
|
|
|
|
|
'unleash-academy/advanced-for-devs',
|
|
|
|
|
'unleash-academy/managing-unleash-for-devops',
|
2022-01-12 11:44:14 +01:00
|
|
|
],
|
|
|
|
|
},
|
2024-02-01 07:10:30 +01:00
|
|
|
{
|
|
|
|
|
type: 'ref',
|
|
|
|
|
id:'welcome',
|
|
|
|
|
label: 'Docs',
|
|
|
|
|
className: 'show-when-collapsed',
|
|
|
|
|
}
|
2024-01-29 19:30:18 +01:00
|
|
|
],
|
|
|
|
|
documentation: [
|
|
|
|
|
'welcome',
|
|
|
|
|
'quickstart',
|
2023-10-31 15:38:03 +01:00
|
|
|
{
|
|
|
|
|
label: 'Feature Flag Best Practices',
|
|
|
|
|
collapsed: true,
|
docs: add "The Anatomy of Unleash" (#2138)
## What
This PR
1. adds a new topic document, "The Anatomy of Unleash", which explains
how Unleash is built up as a system.
2. It also moves the "topic guides" sidebar entry from position 4 to
position 2.
3. Finally, it introduces a new `Figure` component for the
documentation, to be used with images that should be shown with
captions.
## Why
Referring to the same numbers as mentioned above, here's some background
for these changes:
1. We have gotten requests from enterprise users for a way to help new
Unleash users understand the system. Together with customer success and
customer journey, we agreed that an explanatory guide would be suitable.
It aims to give the reader an introduction into what pieces constitute
the Unleash system.
2. As part of a discussion, it was suggested to move topic guides higher
up to make them more visible. There's a few reasons for this:
1. New users of Unleash should be able to keep reading about Unleash
after the basic introductory material. When left at the bottom, topic
guides are often overlooked
2. As a justification, it was proposed that reference docs are often the
last thing you look for, so it makes sense to put that last.
3. Thinking about a new user's flow, it also makes some sense: first
read introductory material, then dive deeper into what Unleash is and
what you can use it for, then look for how-to guides if you're stuck,
and finally consult the reference material for later.
3. These diagrams aren't necessarily very self-explanatory, so adding a
caption makes a lot of sense. We didn't have a component from this
previously, so I added one.
Co-authored-by: NicolaeUnleash <103567375+NicolaeUnleash@users.noreply.github.com>
Co-authored-by: Simon Hornby <liquidwicked64@gmail.com>
## Commits
* docs: add raw export of anatomy document
* docs: move the topic guides section to near top of sidebar
* docs: add inter-doc links, some reformatting
* docs: fix broken links
* docs: add a Figure element for figures with captions
* docs: add more styling to figures
* docs: align on styles
* Fix: add fuller figure caption
* docs: rephrase heading
* Docs(test): try new way of importing images
* Docs(test): images take 3
* docs: Convert all images to using the figure component
* docs: add projects to list of top-level resources
* docs: add captions for all figures.
* docs: reorder images
* Docs(fix): typo: extra brackets
* Docs(style): remove box shadows and border on fig caption images
* Docs(chore): remove commented-out css
* Docs(refactor): use css variable for small font size.
To facilitate reusability and convey meaning.
* docs: rename anatomy doc
* docs: add note about strategies vs constraints
* Updating the images
* Apply suggestions from code review
Co-authored-by: Simon Hornby <liquidwicked64@gmail.com>
* Update website/docs/topics/the-anatomy-of-unleash.mdx
* Docs(fix): remove redundant comma
* docs: add link to node js sdk
* docs: mention that a toggle must be active in an env to be enabled
* docs: add note about environments and api keys
* Docs(reword): swap dev and prod in example
* docs: fix typo in the image
* docs: make figures in text full-width
* docs: move environments and API keys call-out to after figure
* docs: add borders to figures
* docs: add image float css idea
* Revert "docs: add image float css idea"
This reverts commit 69f27d304b4a4d2a7422046475380011345736a2.
Co-authored-by: NicolaeUnleash <103567375+NicolaeUnleash@users.noreply.github.com>
Co-authored-by: Simon Hornby <liquidwicked64@gmail.com>
2022-10-19 13:14:49 +02:00
|
|
|
type: 'category',
|
|
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
2023-10-31 15:38:03 +01:00
|
|
|
title: 'Feature Flag Best Practices',
|
|
|
|
|
description: 'Principles and recommendations for best practices of using feature flags.',
|
docs: add "The Anatomy of Unleash" (#2138)
## What
This PR
1. adds a new topic document, "The Anatomy of Unleash", which explains
how Unleash is built up as a system.
2. It also moves the "topic guides" sidebar entry from position 4 to
position 2.
3. Finally, it introduces a new `Figure` component for the
documentation, to be used with images that should be shown with
captions.
## Why
Referring to the same numbers as mentioned above, here's some background
for these changes:
1. We have gotten requests from enterprise users for a way to help new
Unleash users understand the system. Together with customer success and
customer journey, we agreed that an explanatory guide would be suitable.
It aims to give the reader an introduction into what pieces constitute
the Unleash system.
2. As part of a discussion, it was suggested to move topic guides higher
up to make them more visible. There's a few reasons for this:
1. New users of Unleash should be able to keep reading about Unleash
after the basic introductory material. When left at the bottom, topic
guides are often overlooked
2. As a justification, it was proposed that reference docs are often the
last thing you look for, so it makes sense to put that last.
3. Thinking about a new user's flow, it also makes some sense: first
read introductory material, then dive deeper into what Unleash is and
what you can use it for, then look for how-to guides if you're stuck,
and finally consult the reference material for later.
3. These diagrams aren't necessarily very self-explanatory, so adding a
caption makes a lot of sense. We didn't have a component from this
previously, so I added one.
Co-authored-by: NicolaeUnleash <103567375+NicolaeUnleash@users.noreply.github.com>
Co-authored-by: Simon Hornby <liquidwicked64@gmail.com>
## Commits
* docs: add raw export of anatomy document
* docs: move the topic guides section to near top of sidebar
* docs: add inter-doc links, some reformatting
* docs: fix broken links
* docs: add a Figure element for figures with captions
* docs: add more styling to figures
* docs: align on styles
* Fix: add fuller figure caption
* docs: rephrase heading
* Docs(test): try new way of importing images
* Docs(test): images take 3
* docs: Convert all images to using the figure component
* docs: add projects to list of top-level resources
* docs: add captions for all figures.
* docs: reorder images
* Docs(fix): typo: extra brackets
* Docs(style): remove box shadows and border on fig caption images
* Docs(chore): remove commented-out css
* Docs(refactor): use css variable for small font size.
To facilitate reusability and convey meaning.
* docs: rename anatomy doc
* docs: add note about strategies vs constraints
* Updating the images
* Apply suggestions from code review
Co-authored-by: Simon Hornby <liquidwicked64@gmail.com>
* Update website/docs/topics/the-anatomy-of-unleash.mdx
* Docs(fix): remove redundant comma
* docs: add link to node js sdk
* docs: mention that a toggle must be active in an env to be enabled
* docs: add note about environments and api keys
* Docs(reword): swap dev and prod in example
* docs: fix typo in the image
* docs: make figures in text full-width
* docs: move environments and API keys call-out to after figure
* docs: add borders to figures
* docs: add image float css idea
* Revert "docs: add image float css idea"
This reverts commit 69f27d304b4a4d2a7422046475380011345736a2.
Co-authored-by: NicolaeUnleash <103567375+NicolaeUnleash@users.noreply.github.com>
Co-authored-by: Simon Hornby <liquidwicked64@gmail.com>
2022-10-19 13:14:49 +02:00
|
|
|
slug: '/topics',
|
|
|
|
|
},
|
|
|
|
|
items: [
|
2023-09-22 14:09:41 +02:00
|
|
|
{
|
|
|
|
|
type: 'category',
|
2023-10-31 15:38:03 +01:00
|
|
|
label: '11 Principles for Building and Scaling Feature Flag Systems',
|
2023-09-22 14:09:41 +02:00
|
|
|
link: {
|
|
|
|
|
type: 'doc',
|
|
|
|
|
id: 'topics/feature-flags/feature-flag-best-practices',
|
|
|
|
|
},
|
|
|
|
|
items: [
|
|
|
|
|
'topics/feature-flags/runtime-control',
|
|
|
|
|
'topics/feature-flags/never-expose-pii',
|
|
|
|
|
'topics/feature-flags/evaluate-flags-close-to-user',
|
|
|
|
|
'topics/feature-flags/scale-horizontally',
|
|
|
|
|
'topics/feature-flags/limit-payloads',
|
|
|
|
|
'topics/feature-flags/availability-over-consistency',
|
|
|
|
|
'topics/feature-flags/short-lived-feature-flags',
|
|
|
|
|
'topics/feature-flags/unique-names',
|
|
|
|
|
'topics/feature-flags/democratize-feature-flag-access',
|
|
|
|
|
'topics/feature-flags/prioritize-ux',
|
|
|
|
|
'topics/feature-flags/enable-traceability',
|
|
|
|
|
],
|
|
|
|
|
},
|
2023-09-22 16:41:11 +02:00
|
|
|
{
|
|
|
|
|
type: 'category',
|
|
|
|
|
label: 'Feature Flag Migrations',
|
|
|
|
|
link: {
|
|
|
|
|
type: 'doc',
|
|
|
|
|
id: 'topics/feature-flag-migration/feature-flag-migration-best-practices',
|
|
|
|
|
},
|
|
|
|
|
items: [
|
|
|
|
|
'topics/feature-flag-migration/feature-flag-migration-scope',
|
|
|
|
|
'topics/feature-flag-migration/business-case-feature-flag-migration',
|
|
|
|
|
'topics/feature-flag-migration/planning-feature-flag-migration',
|
|
|
|
|
'topics/feature-flag-migration/how-to-execute-feature-flag-migration',
|
|
|
|
|
'topics/feature-flag-migration/onbording-users-to-feature-flag-service',
|
|
|
|
|
],
|
|
|
|
|
},
|
2023-10-31 15:38:03 +01:00
|
|
|
'topics/a-b-testing',
|
|
|
|
|
],
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
label: 'Feature Flag Tutorials',
|
|
|
|
|
type: 'category',
|
|
|
|
|
collapsed: true,
|
|
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
|
|
|
|
title: 'Feature Flag Tutorials',
|
|
|
|
|
description: 'Tutorials to implement feature flags with your framework.',
|
|
|
|
|
slug: 'feature-flag-tutorials',
|
|
|
|
|
},
|
|
|
|
|
items: [
|
2024-01-18 17:39:25 +01:00
|
|
|
{
|
|
|
|
|
type: 'category',
|
2024-01-24 16:14:50 +01:00
|
|
|
label: 'React',
|
2024-01-18 17:39:25 +01:00
|
|
|
link: {
|
|
|
|
|
type: 'doc',
|
|
|
|
|
id: 'feature-flag-tutorials/react/implementing-feature-flags',
|
|
|
|
|
},
|
|
|
|
|
items: [
|
2024-01-24 16:14:50 +01:00
|
|
|
{
|
|
|
|
|
type: 'doc',
|
|
|
|
|
label: 'Examples',
|
|
|
|
|
id: 'feature-flag-tutorials/react/examples',
|
|
|
|
|
},
|
2024-01-18 17:39:25 +01:00
|
|
|
],
|
|
|
|
|
},
|
2024-01-24 14:00:33 +01:00
|
|
|
{
|
|
|
|
|
type: 'category',
|
2024-01-24 16:14:50 +01:00
|
|
|
label: 'Python',
|
2024-01-24 14:00:33 +01:00
|
|
|
link: {
|
|
|
|
|
type: 'doc',
|
|
|
|
|
id: 'feature-flag-tutorials/python/implementing-feature-flags',
|
|
|
|
|
},
|
2024-02-01 23:08:49 +01:00
|
|
|
items: [
|
|
|
|
|
{
|
|
|
|
|
type: 'doc',
|
|
|
|
|
label: 'Examples',
|
|
|
|
|
id: 'feature-flag-tutorials/python/examples',
|
|
|
|
|
},
|
|
|
|
|
],
|
2024-01-24 14:00:33 +01:00
|
|
|
},
|
2024-02-19 17:29:10 +01:00
|
|
|
{
|
|
|
|
|
type: 'doc',
|
|
|
|
|
label: 'Serverless',
|
|
|
|
|
id: 'feature-flag-tutorials/serverless/implementing-feature-flags-in-aws-lambda',
|
|
|
|
|
},
|
2024-01-24 16:14:50 +01:00
|
|
|
{
|
|
|
|
|
type: 'doc',
|
|
|
|
|
label: 'Flutter',
|
|
|
|
|
id: 'feature-flag-tutorials/flutter/a-b-testing',
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
type: 'doc',
|
|
|
|
|
label: 'Next.js',
|
|
|
|
|
id: 'feature-flag-tutorials/nextjs/implementing-feature-flags',
|
|
|
|
|
},
|
2024-02-19 17:29:10 +01:00
|
|
|
|
docs: add "The Anatomy of Unleash" (#2138)
## What
This PR
1. adds a new topic document, "The Anatomy of Unleash", which explains
how Unleash is built up as a system.
2. It also moves the "topic guides" sidebar entry from position 4 to
position 2.
3. Finally, it introduces a new `Figure` component for the
documentation, to be used with images that should be shown with
captions.
## Why
Referring to the same numbers as mentioned above, here's some background
for these changes:
1. We have gotten requests from enterprise users for a way to help new
Unleash users understand the system. Together with customer success and
customer journey, we agreed that an explanatory guide would be suitable.
It aims to give the reader an introduction into what pieces constitute
the Unleash system.
2. As part of a discussion, it was suggested to move topic guides higher
up to make them more visible. There's a few reasons for this:
1. New users of Unleash should be able to keep reading about Unleash
after the basic introductory material. When left at the bottom, topic
guides are often overlooked
2. As a justification, it was proposed that reference docs are often the
last thing you look for, so it makes sense to put that last.
3. Thinking about a new user's flow, it also makes some sense: first
read introductory material, then dive deeper into what Unleash is and
what you can use it for, then look for how-to guides if you're stuck,
and finally consult the reference material for later.
3. These diagrams aren't necessarily very self-explanatory, so adding a
caption makes a lot of sense. We didn't have a component from this
previously, so I added one.
Co-authored-by: NicolaeUnleash <103567375+NicolaeUnleash@users.noreply.github.com>
Co-authored-by: Simon Hornby <liquidwicked64@gmail.com>
## Commits
* docs: add raw export of anatomy document
* docs: move the topic guides section to near top of sidebar
* docs: add inter-doc links, some reformatting
* docs: fix broken links
* docs: add a Figure element for figures with captions
* docs: add more styling to figures
* docs: align on styles
* Fix: add fuller figure caption
* docs: rephrase heading
* Docs(test): try new way of importing images
* Docs(test): images take 3
* docs: Convert all images to using the figure component
* docs: add projects to list of top-level resources
* docs: add captions for all figures.
* docs: reorder images
* Docs(fix): typo: extra brackets
* Docs(style): remove box shadows and border on fig caption images
* Docs(chore): remove commented-out css
* Docs(refactor): use css variable for small font size.
To facilitate reusability and convey meaning.
* docs: rename anatomy doc
* docs: add note about strategies vs constraints
* Updating the images
* Apply suggestions from code review
Co-authored-by: Simon Hornby <liquidwicked64@gmail.com>
* Update website/docs/topics/the-anatomy-of-unleash.mdx
* Docs(fix): remove redundant comma
* docs: add link to node js sdk
* docs: mention that a toggle must be active in an env to be enabled
* docs: add note about environments and api keys
* Docs(reword): swap dev and prod in example
* docs: fix typo in the image
* docs: make figures in text full-width
* docs: move environments and API keys call-out to after figure
* docs: add borders to figures
* docs: add image float css idea
* Revert "docs: add image float css idea"
This reverts commit 69f27d304b4a4d2a7422046475380011345736a2.
Co-authored-by: NicolaeUnleash <103567375+NicolaeUnleash@users.noreply.github.com>
Co-authored-by: Simon Hornby <liquidwicked64@gmail.com>
2022-10-19 13:14:49 +02:00
|
|
|
],
|
|
|
|
|
},
|
2022-01-12 11:44:14 +01:00
|
|
|
{
|
2023-10-31 15:38:03 +01:00
|
|
|
label: 'Understanding Unleash',
|
2022-01-26 11:51:35 +01:00
|
|
|
collapsed: false,
|
2022-01-12 11:44:14 +01:00
|
|
|
type: 'category',
|
2022-01-14 08:19:34 +01:00
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
2023-10-31 15:38:03 +01:00
|
|
|
title: 'Understanding Unleash',
|
|
|
|
|
description: 'Documentation on how Unleash works, high-level architecture and important concepts.',
|
|
|
|
|
slug: 'understanding-unleash',
|
2022-01-14 08:19:34 +01:00
|
|
|
},
|
2022-01-12 11:44:14 +01:00
|
|
|
items: [
|
2023-10-31 15:38:03 +01:00
|
|
|
'understanding-unleash/unleash-overview',
|
|
|
|
|
'understanding-unleash/the-anatomy-of-unleash',
|
|
|
|
|
'understanding-unleash/managing-constraints',
|
|
|
|
|
'understanding-unleash/proxy-hosting',
|
|
|
|
|
'understanding-unleash/data-collection',
|
2022-01-14 13:19:13 +01:00
|
|
|
{
|
2022-01-24 13:41:29 +01:00
|
|
|
type: 'category',
|
|
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
2023-10-31 15:38:03 +01:00
|
|
|
title: 'Unleash Concepts',
|
2022-01-24 13:41:29 +01:00
|
|
|
description:
|
2023-10-31 15:38:03 +01:00
|
|
|
'Documents describing the inner parts of Unleash.',
|
|
|
|
|
slug: '/reference',
|
2022-01-24 13:41:29 +01:00
|
|
|
},
|
2023-10-31 15:38:03 +01:00
|
|
|
label: 'Unleash Concepts',
|
2023-09-01 15:39:23 +02:00
|
|
|
items: [
|
2023-10-31 15:38:03 +01:00
|
|
|
'reference/activation-strategies',
|
|
|
|
|
'reference/api-tokens-and-client-keys',
|
|
|
|
|
'reference/archived-toggles',
|
|
|
|
|
'reference/banners',
|
|
|
|
|
'reference/change-requests',
|
|
|
|
|
'reference/custom-activation-strategies',
|
|
|
|
|
'reference/dependent-features',
|
|
|
|
|
'reference/environments',
|
|
|
|
|
'reference/event-log',
|
|
|
|
|
'reference/event-types',
|
|
|
|
|
'reference/feature-flag-naming-patterns',
|
|
|
|
|
'reference/feature-toggles',
|
|
|
|
|
'reference/feature-toggle-types',
|
|
|
|
|
'reference/feature-toggle-variants',
|
|
|
|
|
'reference/front-end-api',
|
|
|
|
|
'reference/impression-data',
|
|
|
|
|
'reference/login-history',
|
|
|
|
|
'reference/maintenance-mode',
|
|
|
|
|
'reference/network-view',
|
|
|
|
|
'reference/notifications',
|
|
|
|
|
'reference/playground',
|
|
|
|
|
'reference/public-signup',
|
|
|
|
|
'reference/projects',
|
|
|
|
|
'reference/project-collaboration-mode',
|
|
|
|
|
'reference/rbac',
|
2024-01-31 12:28:15 +01:00
|
|
|
'reference/search-operators',
|
2023-10-31 15:38:03 +01:00
|
|
|
'reference/segments',
|
|
|
|
|
'reference/service-accounts',
|
|
|
|
|
'reference/sso',
|
|
|
|
|
'reference/stickiness',
|
|
|
|
|
'reference/strategy-constraints',
|
|
|
|
|
'reference/strategy-variants',
|
|
|
|
|
'reference/tags',
|
|
|
|
|
'reference/technical-debt',
|
|
|
|
|
'reference/unleash-context',
|
2023-09-01 15:39:23 +02:00
|
|
|
],
|
|
|
|
|
},
|
2022-01-12 11:44:14 +01:00
|
|
|
],
|
|
|
|
|
},
|
2022-01-25 12:20:53 +01:00
|
|
|
{
|
2023-10-31 15:38:03 +01:00
|
|
|
label: 'Using Unleash',
|
2022-01-26 11:51:35 +01:00
|
|
|
collapsed: false,
|
2022-01-11 14:54:37 +01:00
|
|
|
type: 'category',
|
2022-01-24 13:41:29 +01:00
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
2023-10-31 15:38:03 +01:00
|
|
|
title: 'Using Unleash',
|
|
|
|
|
description: 'Documentation on how to accomplish specific tasks when building with Unleash, including API and SDK documentation.',
|
|
|
|
|
slug: '/using-unleash',
|
2022-01-24 13:41:29 +01:00
|
|
|
},
|
2022-01-11 14:54:37 +01:00
|
|
|
items: [
|
2022-01-11 13:43:19 +01:00
|
|
|
{
|
2022-01-12 11:44:14 +01:00
|
|
|
label: 'APIs',
|
2023-10-31 15:38:03 +01:00
|
|
|
collapsed: true,
|
|
|
|
|
type: 'category',
|
|
|
|
|
link: {
|
|
|
|
|
title: 'Unleash Server APIs',
|
|
|
|
|
type: 'generated-index',
|
|
|
|
|
description:
|
|
|
|
|
'Generated API docs based on the Unleash OpenAPI schema.',
|
|
|
|
|
slug: '/reference/api/unleash',
|
|
|
|
|
},
|
2022-01-12 11:44:14 +01:00
|
|
|
items: [
|
2023-10-31 15:38:03 +01:00
|
|
|
require('./docs/reference/api/unleash/sidebar.js'),
|
Add OpenAPI docs (#1391) (#2066)
## What
This PR (finally 🎉) adds generated OpenAPI docs to the official Unleash documentation. In addition to generating docs when things get merged to main, it also pushes new doc updates every day at 12:00 AM (cron `@daily`).
## Why
Now that we have OpenAPI'd all the things, we can finally start using it. This will allow us to remove hand-written api docs from the documentation and should make sure everything is always kept up to date.
### Generating from us-hosted (Unleash enterprise)
Unleash has several different versions (open source, pro, enterprise). The versions do not necessarily have the exact same api surface. In fact, the enterprise version has a few endpoints that open source does not.
Because we want to have _all_ endpoints listed in the documentation we need to generated the docs from an enterprise spec. Which brings us into the next point:
### The need for scheduled jobs
Regarding the daily scheduled tasks to update the documentation: why do we need that?
The docs are generated from the tip of the main branch. For most of the docs, this is good and something that we want. However, because the OpenAPI docs are generated from the enterprise edition, it _will not be in sync_ with the open source main branch.
Also, we probably do not want the docs to list the current bleeding edge api changes. Instead, we should prefer to use the latest enterprise release (roughly). However, because we don't get notified when this version is released and deployed, we'll instead run the API generation on a daily cadence.
This isn't the perfect solution, but it's simple and gets us 80% of the way there. More intricate solutions can be set up later.
## How
- By adding a scheduled workflow to the generate docs config.
- By adding .gitignore entries for the generated files
There's also some minor changes in styling etc.
## Dependencies
This is dependent on the changes introduced in #2062 having propagated to the enterprise release, which will probably not be for another week or so.
## Discussion
What should the API reference docs url be? I've set it to be `/reference/api/unleash/*` for now, but I'm on the fence about whether it should be `apis` or `api` in there. I also want to get the proxy and other APIs in there as we grow.
-------
## Commits
* docs: style openapi operation buttons
* docs: minor operation badge adjustments
* docs: use permalink to css snippet i copied
* docs: ignore files related to openapi generation
* docs: re-enable openapi docs
* Docs(#1391): prep for integration
* docs(#1391): run docs generation daily
* docs(#1391): add generation step to doc prs too
* docs(#1391): use the US hosted instance to generate docs
* docs(#1391): move doc generation into build command
* docs(#1391): use `/reference/api/*` instead of `/reference/apis/*`
2022-09-19 14:50:24 +02:00
|
|
|
{
|
2023-10-31 15:38:03 +01:00
|
|
|
'System API': [
|
|
|
|
|
'reference/api/legacy/unleash/internal/prometheus',
|
|
|
|
|
'reference/api/legacy/unleash/internal/health',
|
2023-07-04 14:19:34 +02:00
|
|
|
],
|
2023-10-31 15:38:03 +01:00
|
|
|
'(Legacy Docs) Admin API': [
|
|
|
|
|
'reference/api/legacy/unleash/admin/addons',
|
|
|
|
|
'reference/api/legacy/unleash/admin/context',
|
|
|
|
|
'reference/api/legacy/unleash/admin/events',
|
|
|
|
|
'reference/api/legacy/unleash/admin/features-v2',
|
|
|
|
|
'reference/api/legacy/unleash/admin/feature-types',
|
|
|
|
|
'reference/api/legacy/unleash/admin/features',
|
|
|
|
|
'reference/api/legacy/unleash/admin/archive',
|
|
|
|
|
'reference/api/legacy/unleash/admin/metrics',
|
|
|
|
|
'reference/api/legacy/unleash/admin/projects',
|
|
|
|
|
'reference/api/legacy/unleash/admin/segments',
|
|
|
|
|
'reference/api/legacy/unleash/admin/state',
|
|
|
|
|
'reference/api/legacy/unleash/admin/strategies',
|
|
|
|
|
'reference/api/legacy/unleash/admin/tags',
|
|
|
|
|
'reference/api/legacy/unleash/admin/user-admin',
|
|
|
|
|
],
|
|
|
|
|
'(Legacy Docs) Client API': [
|
|
|
|
|
'reference/api/legacy/unleash/client/features',
|
|
|
|
|
'reference/api/legacy/unleash/client/metrics',
|
|
|
|
|
'reference/api/legacy/unleash/client/register',
|
|
|
|
|
],
|
|
|
|
|
|
2023-07-04 14:19:34 +02:00
|
|
|
},
|
2023-10-31 15:38:03 +01:00
|
|
|
]
|
2022-01-12 11:44:14 +01:00
|
|
|
},
|
|
|
|
|
{
|
2022-09-15 09:02:10 +02:00
|
|
|
label: 'Application SDKs',
|
2023-10-31 15:38:03 +01:00
|
|
|
type: 'category',
|
refactor: move docs into new structure / fix links for SEO (#2416)
## What
This (admittedly massive) PR updates the "physical" documentation
structure and fixes url inconsistencies and SEO problems reported by
marketing. The main points are:
- remove or move directories : advanced, user_guide, deploy, api
- move the files contained within to the appropriate one of topics,
how-to, tutorials, or reference
- update internal doc links and product links to the content
- create client-side redirects for all the urls that have changed.
A number of the files have been renamed in small ways to better match
their url and to make them easier to find. Additionally, the top-level
api directory has been moved to /reference/api/legacy/unleash (see the
discussion points section for more on this).
## Why
When moving our doc structure to diataxis a while back, we left the
"physical' files lying where they were, because it didn't matter much to
the new structure. However, that did introduce some inconsistencies with
where you place docs and how we organize them.
There's also the discrepancies in whether urls us underscores or hyphens
(which isn't necessarily the same as their file name), which has been
annoying me for a while, but now has also been raised by marketing as an
issue in terms of SEO.
## Discussion points
The old, hand-written API docs have been moved from /api to
/reference/api/legacy/unleash. There _is_ a /reference/api/unleash
directory, but this is being populated by the OpenAPI plugin, and mixing
those could only cause trouble. However, I'm unsure about putting
/legacy/ in the title, because the API isn't legacy, the docs are. Maybe
we could use another path? Like /old-docs/ or something? I'd appreciate
some input on this.
2022-11-22 10:05:30 +01:00
|
|
|
link: { type: 'doc', id: 'reference/sdks/index' },
|
2022-01-24 13:41:29 +01:00
|
|
|
items: [
|
2022-01-11 14:54:37 +01:00
|
|
|
{
|
2022-01-13 11:07:44 +01:00
|
|
|
type: 'category',
|
|
|
|
|
label: 'Server-side SDKs',
|
|
|
|
|
items: [
|
docs: auto-generate remaining server-side SDK docs (#2858)
This PR builds on the preceding doc auto-generation PRs and generates
documentation for the remaining server-side SDKs.
## Why
Refer to https://github.com/Unleash/unleash/pull/2809 for more context
about generating SDK docs.
## What
- Adds generation for the remaining server-side SDKs
- Moves generated docs from the `/reference/sdks` directory to
`/generated` directory.
- Makes sure that the URLs do not change because of the move by using
the `slug` frontmatter property.
- replaces relative github links in the markdown documents so that they
become absolute github links. (refer to the next section)
- Updates some image styling so that it doesn't apply to readme badges
(we don't need them using `display: block`)
### On link replacing:
This PR adds handling of links in the generated documentation.
Specifically, it changes links in one case:
Relative links to github. Links to code and other files in the
repository. These are prefixed with the repository's URL.
While this should work in most cases, it will fail in cases where the
links to the files are not on the repository's primary branch.
(typically main, but could also be "v3", for instance). In these cases,
the links will get a double branch in the URL and will fail. However, I
see no easy way around this (though suggestions are definitely
accepted!), and think it's a fair tradeoff. It takes the links from
"definitely failing" to "will work in the vast majority of cases".
Note: I originally also wanted to handle the case where the link is an
absolute link to docs.getunleash.io. We could turn these into relative
urls to avoid full page reloads and enjoy a smoother experience.
However, the client-side redirects don't work correctly if the relative
URL goes to a redirect page, so you end up with a 404 page. As such, I
think it's better to leave the links as absolute for now.
2023-01-13 12:40:28 +01:00
|
|
|
{
|
|
|
|
|
type: 'autogenerated',
|
|
|
|
|
dirName: 'generated/sdks/server-side',
|
|
|
|
|
},
|
2022-01-13 11:07:44 +01:00
|
|
|
],
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
type: 'category',
|
|
|
|
|
label: 'Client-side SDKs',
|
|
|
|
|
items: [
|
2023-01-25 14:36:50 +01:00
|
|
|
{
|
|
|
|
|
type: 'autogenerated',
|
|
|
|
|
dirName: 'generated/sdks/client-side',
|
|
|
|
|
},
|
2022-01-13 11:07:44 +01:00
|
|
|
],
|
|
|
|
|
},
|
|
|
|
|
{
|
2022-01-11 14:54:37 +01:00
|
|
|
type: 'link',
|
2022-01-13 11:07:44 +01:00
|
|
|
label: 'Community SDKs',
|
refactor: move docs into new structure / fix links for SEO (#2416)
## What
This (admittedly massive) PR updates the "physical" documentation
structure and fixes url inconsistencies and SEO problems reported by
marketing. The main points are:
- remove or move directories : advanced, user_guide, deploy, api
- move the files contained within to the appropriate one of topics,
how-to, tutorials, or reference
- update internal doc links and product links to the content
- create client-side redirects for all the urls that have changed.
A number of the files have been renamed in small ways to better match
their url and to make them easier to find. Additionally, the top-level
api directory has been moved to /reference/api/legacy/unleash (see the
discussion points section for more on this).
## Why
When moving our doc structure to diataxis a while back, we left the
"physical' files lying where they were, because it didn't matter much to
the new structure. However, that did introduce some inconsistencies with
where you place docs and how we organize them.
There's also the discrepancies in whether urls us underscores or hyphens
(which isn't necessarily the same as their file name), which has been
annoying me for a while, but now has also been raised by marketing as an
issue in terms of SEO.
## Discussion points
The old, hand-written API docs have been moved from /api to
/reference/api/legacy/unleash. There _is_ a /reference/api/unleash
directory, but this is being populated by the OpenAPI plugin, and mixing
those could only cause trouble. However, I'm unsure about putting
/legacy/ in the title, because the API isn't legacy, the docs are. Maybe
we could use another path? Like /old-docs/ or something? I'd appreciate
some input on this.
2022-11-22 10:05:30 +01:00
|
|
|
href: '/reference/sdks#community-sdks',
|
2022-01-11 14:54:37 +01:00
|
|
|
},
|
2022-01-11 15:06:32 +01:00
|
|
|
],
|
2022-01-24 13:41:29 +01:00
|
|
|
},
|
|
|
|
|
{
|
2023-10-31 15:38:03 +01:00
|
|
|
label: 'Integrations',
|
2022-01-12 11:44:14 +01:00
|
|
|
type: 'category',
|
2023-09-14 15:27:51 +02:00
|
|
|
link: { type: 'doc', id: 'reference/integrations/index' },
|
2022-01-12 11:44:14 +01:00
|
|
|
items: [
|
2023-09-14 15:27:51 +02:00
|
|
|
'reference/integrations/datadog',
|
2022-01-12 11:44:14 +01:00
|
|
|
{
|
|
|
|
|
'Jira Server': [
|
refactor: move docs into new structure / fix links for SEO (#2416)
## What
This (admittedly massive) PR updates the "physical" documentation
structure and fixes url inconsistencies and SEO problems reported by
marketing. The main points are:
- remove or move directories : advanced, user_guide, deploy, api
- move the files contained within to the appropriate one of topics,
how-to, tutorials, or reference
- update internal doc links and product links to the content
- create client-side redirects for all the urls that have changed.
A number of the files have been renamed in small ways to better match
their url and to make them easier to find. Additionally, the top-level
api directory has been moved to /reference/api/legacy/unleash (see the
discussion points section for more on this).
## Why
When moving our doc structure to diataxis a while back, we left the
"physical' files lying where they were, because it didn't matter much to
the new structure. However, that did introduce some inconsistencies with
where you place docs and how we organize them.
There's also the discrepancies in whether urls us underscores or hyphens
(which isn't necessarily the same as their file name), which has been
annoying me for a while, but now has also been raised by marketing as an
issue in terms of SEO.
## Discussion points
The old, hand-written API docs have been moved from /api to
/reference/api/legacy/unleash. There _is_ a /reference/api/unleash
directory, but this is being populated by the OpenAPI plugin, and mixing
those could only cause trouble. However, I'm unsure about putting
/legacy/ in the title, because the API isn't legacy, the docs are. Maybe
we could use another path? Like /old-docs/ or something? I'd appreciate
some input on this.
2022-11-22 10:05:30 +01:00
|
|
|
'reference/integrations/jira-server-plugin-installation',
|
|
|
|
|
'reference/integrations/jira-server-plugin-usage',
|
2022-01-12 11:44:14 +01:00
|
|
|
],
|
2023-04-17 15:16:01 +02:00
|
|
|
'Jira Cloud': [
|
|
|
|
|
'reference/integrations/jira-cloud-plugin-installation',
|
|
|
|
|
'reference/integrations/jira-cloud-plugin-usage',
|
|
|
|
|
],
|
2022-01-12 11:44:14 +01:00
|
|
|
},
|
2023-09-23 00:19:17 +02:00
|
|
|
'reference/integrations/slack-app',
|
2023-09-14 15:27:51 +02:00
|
|
|
'reference/integrations/slack',
|
|
|
|
|
'reference/integrations/teams',
|
|
|
|
|
'reference/integrations/webhook',
|
2022-01-12 11:44:14 +01:00
|
|
|
],
|
2022-01-11 13:43:19 +01:00
|
|
|
},
|
2022-01-26 11:51:35 +01:00
|
|
|
{
|
2023-10-31 15:38:03 +01:00
|
|
|
label: 'How-to guides',
|
2022-01-26 11:51:35 +01:00
|
|
|
type: 'category',
|
|
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
2023-10-31 15:38:03 +01:00
|
|
|
title: 'How-to guides',
|
|
|
|
|
description: 'Step-by-step recipes for you to follow.',
|
|
|
|
|
slug: '/how-to',
|
|
|
|
|
},
|
|
|
|
|
items: [
|
|
|
|
|
{
|
|
|
|
|
label: 'Unleash API guides',
|
|
|
|
|
type: 'category',
|
|
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
|
|
|
|
title: 'How-to: Unleash API',
|
|
|
|
|
description: 'Learn how to work with the Unleash API',
|
|
|
|
|
slug: '/how-to/api',
|
|
|
|
|
},
|
|
|
|
|
items: [
|
|
|
|
|
'how-to/how-to-create-api-tokens',
|
|
|
|
|
'how-to/how-to-create-personal-access-tokens',
|
|
|
|
|
'how-to/how-to-create-project-api-tokens',
|
|
|
|
|
'how-to/how-to-create-service-accounts',
|
|
|
|
|
'how-to/how-to-download-login-history',
|
|
|
|
|
'how-to/how-to-use-the-admin-api',
|
|
|
|
|
'how-to/how-to-enable-openapi',
|
|
|
|
|
],
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
label: 'Unleash Proxy guides',
|
|
|
|
|
type: 'category',
|
|
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
|
|
|
|
title: 'How-to: The Unleash Proxy',
|
|
|
|
|
description: 'Learn how to work with the Unleash Proxy',
|
|
|
|
|
slug: '/how-to/proxy',
|
|
|
|
|
},
|
|
|
|
|
items: ['how-to/how-to-run-the-unleash-proxy'],
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
label: 'Feature flags, strategies, context',
|
|
|
|
|
type: 'category',
|
|
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
|
|
|
|
title: 'How-to: general Unleash tasks',
|
|
|
|
|
description:
|
|
|
|
|
'Guides for how to perform general Unleash tasks.',
|
|
|
|
|
slug: '/how-to/misc',
|
|
|
|
|
},
|
|
|
|
|
items: [
|
|
|
|
|
'how-to/how-to-add-strategy-constraints',
|
|
|
|
|
'how-to/how-to-add-feature-flag-naming-patterns',
|
|
|
|
|
'how-to/how-to-capture-impression-data',
|
|
|
|
|
'how-to/how-to-create-feature-toggles',
|
|
|
|
|
'how-to/how-to-create-and-display-banners',
|
|
|
|
|
'how-to/how-to-define-custom-context-fields',
|
|
|
|
|
'how-to/how-to-use-custom-strategies',
|
|
|
|
|
'how-to/how-to-schedule-feature-releases',
|
|
|
|
|
'how-to/how-to-synchronize-unleash-instances',
|
|
|
|
|
],
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
label: 'Environments',
|
|
|
|
|
type: 'category',
|
|
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
|
|
|
|
title: 'How-to: environments',
|
|
|
|
|
description: 'Environments how-to guides.',
|
|
|
|
|
slug: '/how-to/env',
|
|
|
|
|
},
|
|
|
|
|
items: [
|
|
|
|
|
'how-to/how-to-clone-environments',
|
|
|
|
|
'how-to/how-to-import-export',
|
|
|
|
|
'how-to/how-to-environment-import-export',
|
|
|
|
|
],
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
label: 'Users and permissions',
|
|
|
|
|
items: [
|
|
|
|
|
'how-to/how-to-add-users-to-unleash',
|
|
|
|
|
'how-to/how-to-create-and-assign-custom-root-roles',
|
|
|
|
|
'how-to/how-to-create-and-assign-custom-project-roles',
|
|
|
|
|
'how-to/how-to-create-and-manage-user-groups',
|
|
|
|
|
'how-to/how-to-set-up-group-sso-sync',
|
|
|
|
|
],
|
|
|
|
|
type: 'category',
|
|
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
|
|
|
|
title: 'How-to: users and permissions',
|
|
|
|
|
description: 'Users and permission how-to guides.',
|
|
|
|
|
slug: '/how-to/users-and-permissions',
|
|
|
|
|
},
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
label: 'Single Sign-On (SSO)',
|
|
|
|
|
items: [
|
|
|
|
|
'how-to/how-to-add-sso-open-id-connect',
|
|
|
|
|
'how-to/how-to-add-sso-saml',
|
|
|
|
|
'how-to/how-to-add-sso-saml-keycloak',
|
|
|
|
|
'how-to/how-to-add-sso-google',
|
|
|
|
|
'how-to/how-to-add-sso-azure-saml',
|
|
|
|
|
'how-to/how-to-setup-sso-keycloak-group-sync',
|
|
|
|
|
],
|
|
|
|
|
type: 'category',
|
|
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
|
|
|
|
title: 'How-to: Single Sign-On',
|
|
|
|
|
description: 'Single Sign-On how-to guides.',
|
|
|
|
|
slug: '/how-to/sso',
|
|
|
|
|
},
|
|
|
|
|
},
|
|
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
type: 'category',
|
|
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
|
|
|
|
title: 'Self-Hosting Unleash',
|
2022-01-26 11:51:35 +01:00
|
|
|
description:
|
2023-10-31 15:38:03 +01:00
|
|
|
'All you need to learn how to deploy and manage your own Unleash instance.',
|
|
|
|
|
slug: '/using-unleash/deploy',
|
2022-01-26 11:51:35 +01:00
|
|
|
},
|
2023-10-31 15:38:03 +01:00
|
|
|
label: 'Self-Hosting Unleash',
|
2022-01-26 11:51:35 +01:00
|
|
|
items: [
|
2023-10-31 15:38:03 +01:00
|
|
|
'using-unleash/deploy/getting-started',
|
|
|
|
|
'using-unleash/deploy/configuring-unleash',
|
|
|
|
|
'using-unleash/deploy/database-setup',
|
|
|
|
|
'using-unleash/deploy/database-backup',
|
|
|
|
|
'using-unleash/deploy/email-service',
|
|
|
|
|
'using-unleash/deploy/google-auth-hook',
|
|
|
|
|
'using-unleash/deploy/upgrading-unleash',
|
|
|
|
|
'using-unleash/deploy/securing-unleash',
|
2024-01-23 18:17:10 +01:00
|
|
|
'using-unleash/deploy/license-keys',
|
2023-10-31 15:38:03 +01:00
|
|
|
],
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
label: 'Troubleshooting',
|
|
|
|
|
type: 'category',
|
|
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
|
|
|
|
title: 'How-to: troubleshooting',
|
|
|
|
|
description:
|
|
|
|
|
'Troubleshooting common problems. If you want to suggest new items, please phrase the title as a concrete problem',
|
|
|
|
|
slug: '/using-unleash/troubleshooting',
|
|
|
|
|
},
|
|
|
|
|
items: [
|
|
|
|
|
'using-unleash/troubleshooting/cors',
|
2024-02-15 15:49:21 +01:00
|
|
|
'using-unleash/troubleshooting/https',
|
2023-11-14 13:53:34 +01:00
|
|
|
'using-unleash/troubleshooting/email-service',
|
2023-10-31 15:38:03 +01:00
|
|
|
'using-unleash/troubleshooting/feature-not-available',
|
|
|
|
|
'using-unleash/troubleshooting/flag-exposure',
|
|
|
|
|
'using-unleash/troubleshooting/flag-not-returned',
|
2024-02-15 15:49:21 +01:00
|
|
|
'using-unleash/troubleshooting/flag-abn-test-unexpected-result',
|
2022-01-26 11:51:35 +01:00
|
|
|
],
|
|
|
|
|
},
|
Source proxy and Edge docs from GitHub (#3122)
## What
The main purpose of this PR is to
1. Delete the proxy docs in this repo and replace them with the proxy's
GitHub readme.
2. Add the docs for Unleash Edge.
### Detailed change description
This PR contains a lot of small changes in a large number of files. To
make it easier to get an overview, here's a detailed description of what
happens where:
#### In the `website/docs`directory
Except for the deletion of the proxy doc, all changes in this directory
are rewriting internal links, so that they point to the newly generated
document instead.
#### `package.json` and `yarn.lock`
When including the documentation for Edge, we also want to render the
mermaid diagrams it uses. Docusaurus supports this via a plugin. All
changes in these files are related to installing that plugin.
#### `docusaurus.config.js`
There's two types of changes in this file:
1. Mermaid-related changes: we ask docusaurus to render mermaid in
markdown files and add the plugin
2. Document generation. There's some rewrites to the sdk doc generation
plus an entirely new section that generates docs for Edge and the proxy
#### `sidebars.js`
Two things:
1. Add the edge docs
2. Move both the Edge and the proxy docs up a level, so that they're
directly under "reference docs" instead of nested inside "unleash
concepts".
#### In the `website/remote-content` directory
These are the remote content files. Previously, all of this lived only
in a `readme-fns.js` file, but with the introduction of Edge and proxy
docs, this has been moved into its own directory and refactored into
three files (`shared`, `sdks`, `edge-proxy`).
#### `custom.css`
Style updates to center mermaid diagrams and provide more space around
them.
#### In `static/img`
The image files that were included in the proxy doc and that have been
deleted.
## Why
For two reasons:
1. Reduce duplication for the proxy. Have one source of truth.
2. Add docs for edge.
## Discussion points and review wishes
This is a big PR, and I don't expect anyone to do a line-by-line review
of it, nor do I think that is particularly useful. Instead, I'd like to
ask reviewers to:
1. Visit the [documentation
preview](https://unleash-docs-git-docs-source-proxy-gh-unleash-team.vercel.app/reference/unleash-proxy)
and have a look at both the proxy docs and the Edge docs. Potentially
have a look at the SDK docs too to verify that everything still works.
2. Consider whether they think moving the proxy and edge docs up a level
(in the sidebar) makes sense.
3. Let me know what slug they'd prefer for the Edge docs. I've gone with
`unleash-edge` for now (so that it's
`docs.getunleash.io/reference/unleash-edge`), but we could potentially
also just use `edge`. WDYT?
4. Read through the detailed changes section.
5. Let me know if they have any other concerns or questions.
## Screenies
The new proxy doc:
The new edge doc:
2023-02-16 13:36:28 +01:00
|
|
|
'generated/unleash-edge',
|
|
|
|
|
'generated/unleash-proxy',
|
2022-01-11 13:43:19 +01:00
|
|
|
],
|
2022-01-11 14:54:37 +01:00
|
|
|
},
|
2022-11-29 08:57:27 +01:00
|
|
|
{
|
2023-10-31 15:38:03 +01:00
|
|
|
label: 'Contributing to Unleash',
|
2022-11-29 08:57:27 +01:00
|
|
|
type: 'category',
|
|
|
|
|
collapsed: true,
|
|
|
|
|
link: {
|
|
|
|
|
type: 'generated-index',
|
2023-10-31 15:38:03 +01:00
|
|
|
title: 'Contributing to Unleash',
|
2022-11-29 08:57:27 +01:00
|
|
|
description: 'Learn how to contribute to unleash.',
|
2023-10-31 15:38:03 +01:00
|
|
|
slug: '/contributing',
|
2022-11-29 08:57:27 +01:00
|
|
|
},
|
|
|
|
|
items: [
|
|
|
|
|
'contributing/developer-guide',
|
|
|
|
|
'contributing/frontend/overview',
|
|
|
|
|
'contributing/backend/overview',
|
|
|
|
|
{
|
|
|
|
|
type: 'category',
|
|
|
|
|
label: 'Architectural Decision Records',
|
|
|
|
|
items: [
|
|
|
|
|
{
|
|
|
|
|
type: 'autogenerated',
|
|
|
|
|
dirName: 'contributing/ADRs', // '.' means the current docs folder
|
|
|
|
|
},
|
|
|
|
|
],
|
|
|
|
|
},
|
|
|
|
|
],
|
|
|
|
|
},
|
2024-02-01 07:10:30 +01:00
|
|
|
{
|
|
|
|
|
type: 'ref',
|
|
|
|
|
id:'unleash-academy/introduction',
|
|
|
|
|
label: 'Unleash Academy',
|
|
|
|
|
className: 'show-when-collapsed',
|
|
|
|
|
}
|
2022-01-25 12:20:53 +01:00
|
|
|
],
|
2023-10-27 16:16:56 +02:00
|
|
|
};
|
