Align availability information in the docs #8177
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
melindafekete
changed the title
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Manifest Files |
website/docs/reference/integrations/jira-cloud-plugin-installation.md
Outdated
Show resolved
Hide resolved
website/docs/reference/integrations/jira-server-plugin-installation.md
Outdated
Show resolved
Hide resolved
website/docs/using-unleash/troubleshooting/feature-not-available.md
Outdated
Show resolved
Hide resolved
# Conflicts: # website/docs/how-to/how-to-set-up-group-sso-sync.md # website/docs/how-to/how-to-setup-sso-keycloak-group-sync.md # website/docs/reference/feature-lifecycle.md
melindafekete
changed the title
There was a problem hiding this comment.
All the notes in this file appear to use the same version number; shouldn't we then just use one availability note?
There was a problem hiding this comment.
Do you know if there is any reason why the current docs specifically say:
The following three sections: "Application Overview," "Connected Instances," and "Project Applications" were released in Unleash 5.11.
I think that's what got me confused
| @@ -574,12 +574,6 @@ This event fires when you drop all existing tags as part of a configuration impo | |||
|
|
|||
| ### `feature-potentially-stale-on` | |||
There was a problem hiding this comment.
do we not want to put event availibility in? this was released at some point, but not available to users previously. I wonder if that's useful info or not?
There was a problem hiding this comment.
Do you mean for events in general or this feature-potentially-stale-on event in particular?
Co-authored-by: Thomas Heartman <thomas@getunleash.io>
Remove environments 4.2 statement
About the changes
This PR standardizes the way we show version and plan requirements in the docs. It introduced consistent wording and formatting, so readers can see the requirements at a glance. When a feature is only Enterprise or Pro, the version requirement leads to the pricing page.
This Notion page documents the guidelines with some examples.
Here is a sample of a few pages covering different scenarios: