website/docs: Modal and wizard button labels#21549
website/docs: Modal and wizard button labels#21549GirlBossRush wants to merge 17 commits intomainfrom
Conversation
GirlBossRush
added
a11y
✅ Deploy Preview for authentik-integrations ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for authentik-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
GirlBossRush
changed the title
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #21549 +/- ##
==========================================
- Coverage 92.30% 92.29% -0.02%
==========================================
Files 1032 1032
Lines 59767 59767
Branches 2537 2537
==========================================
- Hits 55168 55162 -6
- Misses 4536 4540 +4
- Partials 63 65 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
authentik PR Installation instructions Instructions for docker-composeAdd the following block to your AUTHENTIK_IMAGE=ghcr.io/goauthentik/dev-server
AUTHENTIK_TAG=gh-111b000697d8380033a76a4077a867a9d6939110
AUTHENTIK_OUTPOSTS__CONTAINER_IMAGE_BASE=ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)sAfterwards, run the upgrade commands from the latest release notes. Instructions for KubernetesAdd the following block to your authentik:
outposts:
container_image_base: ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s
global:
image:
repository: ghcr.io/goauthentik/dev-server
tag: gh-111b000697d8380033a76a4077a867a9d6939110Afterwards, run the upgrade commands from the latest release notes. |
dominic-r
left a comment
dominic-r
left a comment
There was a problem hiding this comment.
I'd prefer to keep this existing bit, unless it's no longer gonna be possible in the product (Alternatively you can first create a provider separately, then create the application and connect it with the provider.) cc @tanberry
|
|
||
| 1. Log in to authentik as an administrator and open the authentik Admin interface. | ||
| 2. Navigate to **Flows and Stages > Stages** and click **Create**. | ||
| 2. Navigate to \*\*Flows and Stages > Stages\*\* and click \*\*New Stage\*\*. |
There was a problem hiding this comment.
| 2. Navigate to \*\*Flows and Stages > Stages\*\* and click \*\*New Stage\*\*. | |
| 2. Navigate to **Flows and Stages > Stages** and click **New Stage**. |
There was a problem hiding this comment.
How do those backslashes get added? Happens to me too...
|
|
||
| 1. [Create](../../flow/index.md#create-a-flow) a new flow or edit an existing one. | ||
| 2. On the flow's **Stage Bindings** tab, click **Create and bind stage** to create and add the Email Authenticator Setup stage. (If the stage already exists, click **Bind existing stage**.) | ||
| 2. On the flow's **Stage Bindings** tab, click **New Stage** to create and add the Email Authenticator Setup stage. (If the stage already exists, click **Bind Existing Stage**.) |
There was a problem hiding this comment.
What is the goal of changing these labels, especially this one? When I am on a Flow page, the original label of “Create and bind stage” feels so much more informative and clear to me… the new label of “New Stage" does not tell me that I will also be able to bind the stage.. it says I can just create a new stage (which I would normally do over on the Stages page).
| 3. In the list of flows, click the name of the flow to which you want to bind one or more stages. | ||
| 4. On the Flow page, click the **Stage Bindings** tab at the top. | ||
| 5. Here, you can decide if you want to create a new stage and bind it to the flow (**Create and bind Stage**), or if you want to select an existing stage and bind it to the flow (**Bind existing stage**). | ||
| 5. Here, you can decide if you want to create a new stage and bind it to the flow (**New Stage**), or if you want to select an existing stage and bind it to the flow (**Bind Existing Stage**). |
There was a problem hiding this comment.
Is there a decision to use capitalization on every word across all labels/buttons? We don't now, in many cases, especially where the label is more of a psuedo-sentence. We'll want to consider whether this style in the UI will "clash" stylistically with our Docs, where we use sentence-style capitalization....
The application list page now uses a split-button labeled "New Application" instead of the old "Create with Provider" dropdown. Update all 113 integration guides to match.
- "Create" → "New Flow", "New Stage", "New Policy" for trigger buttons - "Finish" → "Create Flow", "Create Stage", "Create Policy" for submit - "Create and bind stage" → "New Stage" / "Bind Existing Stage" - "Create" (binding submit) → "Create Stage Binding"
- "Create" → "New Provider" for trigger buttons - "Create with Provider" → "New Application" in RAC docs - "Create" → "New Property Mapping", "New RAC Endpoint", "New Prompt" for related entity creation
- "Create" → "New Source" for federation/social login pages - "Create" → "New Role", submit → "Create Role" - "Create" → "New Invitation" - Policy binding submit → "Create Policy Binding"
- "Create" → "New Endpoint Connector", "New Enrollment Token", "New Device Access Group", "New Flow" - Submit → "Create Device Access Group" - "Create" → "New Notification Rule", "New Notification Transport" - Binding submit → "Create Policy Binding"
GirlBossRush
force-pushed
the
web/docs-modal-revisions-labels
branch
from
acf87b5 to
111b000
Compare
✅ Deploy Preview for authentik-storybook ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
3 participants
Summary
Test plan
*Companion to #21206.*Companion to #21336