1
0
mirror of https://github.com/Unleash/unleash.git synced 2024-12-22 19:07:54 +01:00
unleash.unleash/website/docs/about-the-docs.md

65 lines
3.2 KiB
Markdown
Raw Normal View History

2021-02-28 22:12:19 +01:00
---
title: About the docs
slug: /
sidebar_position: 1
2021-02-28 22:12:19 +01:00
---
Welcome to the Unleash documentation, your one-stop shop to everything Unleash. Whether you're just getting started or have been using Unleash for years, you should be able to find answers to all your questions here.
## Getting help
Have questions that you can't find the answer to in these docs? You can always turn to [our GitHub](https://github.com/orgs/Unleash/discussions) or [the Unleash Slack community](https://slack.unleash.run/) and ask us questions directly (or just come and hang out 😄).
## Documentation structure
Our documentation is split into four parts, using the [Diátaxis documentation framework](https://diataxis.fr/):
- [Tutorials and introductory material](#tutorials)
- [How-to guides](#how-to-guides)
- [Reference documentation](#reference-documentation)
- [Topic guides](#topic-guides)
### Tutorials and introductory material {#tutorials}
New to Unleash? Not sure where to get started? The tutorials guide you through your first steps with Unleash:
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
- [Unleash introductory overview](./tutorials/unleash-overview.md)
- [Important Unleash concepts](./tutorials/important-concepts.md)
- [Quickstart guides](tutorials/quickstart.md)
### How-to guides
Our how-to guides show you how to perform a number of common tasks that you'll want to do. Think of them as recipes. They are more advanced than the tutorials and assume you have some working knowledge of Unleash.
The guides are organized into the following categories:
- [API how-tos](./how-to/api)
- [Feature toggles, strategies, context, and general how-tos](./how-to/misc)
- [Users and permissions how-tos](./how-to/users-and-permissions)
- [Single Sign-On (SSO) how-tos](./how-to/sso)
- [Troubleshooting how-tos](./how-to/troubleshooting)
### Reference documentation
The reference docs contain technical reference for Unleash and the API. Go here to find out how Unleash works and what configuration options are available. They're like an Unleash encyclopedia and assume you have a grip on key Unleash concepts.
The reference docs are organized into the following topics:
- [API documentation](./reference/api/legacy/unleash/index.md)
- [Unleash SDKs](./reference/sdks/index.md)
- [Deployment and management of Unleash](./reference/deploy)
- [Integrations](./reference/integrations/integrations.md)
- [Unleash concepts](./reference/concepts)
### Topic guides
[The topic guides](/topics) discuss high-level concepts related to Unleash and provide extra background information and explanations around these concepts.
## Other resources and communities
docs: Remove/update references to Heroku (#2099) ## What This PR removes or updates references in the docs to Heroku. Most of the code samples have been replaced with a more generic `unleash.example.com` url, while other references have been removed or updated. Also removes old OpenAPI files that are out of date and redundant with the new generation. ## Background Come November and Heroku will no longer offer free deployments of Unleash, so it's about time we remove that claim. Links to the heroku instance are also outdated because we don't have that instance running anymore. Finally, the OpenAPI files we do have there are old and static, so they don't match the current reality. ## Commits * Meta: update ignore file to ignore autogenerated docs I must've missed the ignore file when looking for patterns. * docs: delete old openapi file. This seems to have been a holdover from 2020 and is probably hand-written. It has been superseded by the new autogenerated OpenAPI docs. * docs: add notes for heroku changes to the frontend readme and pkg * docs: remove old openapi article and add redirects to new openapi * docs: fix link in overview doc: point to GitHub instead of heroku * docs: update quickstart docs with new heroku details * docs: remove reference to crashing heroku instance * docs: remove references to herokuapp in code samples * docs: add a placeholder comment * docs: update references for heroku updates * docs: keep using unleash4 for enterprise * docs: remove start:heroku script in favor of start:sandbox * docs: remove 'deploy on heroku button' Now that it's not free anymore (or won't be very shortly), let's remove it. * docs: remove extra newline
2022-10-19 14:02:00 +02:00
💻 The core of Unleash is all open source and [hosted on GitHub](https://github.com/Unleash/unleash/ 'Unleash on GitHub').
💬 If you've got questions or just wanna chat to the team and other Unleash users, leave us a little something on [GitHub Discussions](https://github.com/orgs/Unleash/discussions) or come [join our Slack community](https://slack.unleash.run/)
🐦 You can also follow us [on Twitter](https://twitter.com/getunleash 'Unleash on Twitter'), [LinkedIn](https://www.linkedin.com/company/getunleash/ 'Unleash on LinkedIn'), or [Instagram](https://www.instagram.com/getunleash/ 'Unleash on Instagram') for more updates and extra content.