34b01d9785
* first pass * reordered config options to match UI, added more * tweaks * add content for creating flows, add links to policies, update Style Guide * tweaks * procedurals, info about bindings * stages stub file * messy * reorg procedurals * tweak titles * tweaks * images * images, remove old images * tweak * tweaks and fixes * smaller image * tweak * had to rollback * starting over after VS Code branch war * fix links * more tweaks * Optimised images with calibre/image-actions * fighting build break * remove dupe image * replace image with diagram code * add image of UI, and reformat to look more like field names, not headings in the document * Optimised images with calibre/image-actions * new image * rest of Jens' edits * Optimised images with calibre/image-actions * fix order of stages in example * fixed arrows in image --------- Signed-off-by: Tana M Berry <tanamarieberry@yahoo.com> Co-authored-by: Tana M Berry <tana@goauthentik.com> Co-authored-by: authentik-automation[bot] <135050075+authentik-automation[bot]@users.noreply.github.com> Co-authored-by: Jens Langhammer <jens@goauthentik.io>
2.6 KiB
title
| title |
|---|
| Conceptual topic |
:::info
How to use this template: start with the markdown version of the template, either by copying the conceptual.tmpl.md file from our GitHub repo or downloading the template file using the following command:
wget https://raw.githubusercontent.com/goauthentik/authentik/main/website/developer-docs/docs/templates/conceptual.tmpl.md
Edit your markdown file as you work, reading this page for the descriptions of each section. You can build out a "stub file" with just headers, then gradually add content to each section. Use screenshots sparingly, only for complex UIs where it is difficult to describe a UI element with words. Refer to our Style Guide for writing tips and authentik-specific rules. :::
Use a title that focuses on the feature, component, or technology you are writing about... for example, "About authentik polices" or "Understanding outposts". For conceptual docs, the verb in the title should indicate a concept, such as "About" or "Overview" or "Understanding", followed by the noun (the component or object you are writing about).
In this first section, immediately after the title, write one or two sentences about the feature, component, or technology. The following sections can help break up the content.
Common use cases (optional section)
In this optional section, provide some example use cases for the feature. Who would use it, WHY? If you mention HOW to use the feature, be sure to link off to the related procedural doc. Also share situations where users might NOT want to use the feature; for example, if the feature is intended for a specific environment.
Overview of feature/component
Dive deeper into explaining the concepts behind the feature/component.
Write about the feature/functionalilty from the user's perspective. What is this feature used for, why should they use it, are there situations where they should not use it?
Pro Tip: If you were writing the related procedural topic, and you found that you had a lot to say about the topic, this is exactly where that info would go (not crowded up at the top of the procedural topic!).
Cover anything the user needs to know about the feature. If there are Reference docs or a related procedural doc for this feature or component, be sure to link to them from this page.
Important considerations
List anything that might be critical for user to know, such as situations where this feature might not be ideal, or pre-configs that need to be set, etc.