1
0
mirror of https://github.com/Unleash/unleash.git synced 2025-03-04 00:18:40 +01:00

docs: add projects to list of top-level resources

This commit is contained in:
Thomas Heartman 2022-10-11 16:37:57 +02:00
parent 8c014679b1
commit 4ca1f7e3e6

View File

@ -13,6 +13,7 @@ The end of this guide presents a [short use case, explaining how you might confi
Some things in Unleash are configured and defined on the global level. These options apply across the entire Unleash instance. The most important global configuration options for day-to-day operations are:
- [API access tokens](../reference/api-tokens-and-client-keys.mdx)
- [[Projects](../user_guide/projects.md)]
- [Segments](../reference/segments.mdx)
- [Strategy types](../user_guide/activation-strategies.md) (including [custom activation strategy types](../advanced/custom-activation-strategy.md))
- [Tag types](../advanced/tags.md)
@ -22,7 +23,7 @@ Some things in Unleash are configured and defined on the global level. These opt
## Projects
[**Projects**](../user_guide/projects.md) are the most basic component above the global level in Unleash. Projects contain feature toggles and their configurations, and a set of active environments, all of which well go through later in this article.
[**Projects**](../user_guide/projects.md) contain [feature toggles](../reference/feature-toggles.mdx) and their configurations, and a set of active [environments](../user_guide/environments.md).
All Unleash instances must have at least one project at any given time. New instances get a project called “Default”.