-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add info on showing/hiding compliance frameworks #31990
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Add info on showing/hiding compliance frameworks #31990
Conversation
Preview links (active after the
|
|
||
To hide a framework, either on the Compliance page or on a page for a specific framework, click the **Options** button {{< img src="icons/kebab.png" alt="Options button" inline="true" style="height:1em">}}, then click **Hide framework**. | ||
|
||
Then, on the Compliance page, you can use the **Show hidden frameworks** toggle to show hidden frameworks at the bottom of the list, or hide them completely. When you show hidden frameworks, you can click **Show** on a hidden framework to add it back to the list. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then, on the Compliance page, you can use the **Show hidden frameworks** toggle to show hidden frameworks at the bottom of the list, or hide them completely. When you show hidden frameworks, you can click **Show** on a hidden framework to add it back to the list. | |
Then, on the Compliance page, you can use the **Show hidden frameworks** toggle to display hidden frameworks at the bottom of the list, or hide them completely. When hidden frameworks are visible, you can click **Show** next to any framework to add it back to the list. |
Hi Janine! just a quick suggestion here as I was reading through this section. There were a number of the word Show in this last paragraph so I changed one of them to the word display
to spice it up a bit, haha.
Additionally, the last sentence confused me a little bit, since it used the same syntax as the name of the function. Made a quick suggestion change. Let me know what you think!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @iadjivon , you're totally right that "show" was in there a lot! I was a little worried that users would see "when hidden frameworks are visible" and be like "oh no" because this is inherently difficult to write about 😂 I tried an alternate wording and just pushed it up. Let me know if that's clearer, and thanks so much for helping me clarify it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Janine, added a quick note, let me know what you think!
What does this PR do? What is the motivation?
Adds info on a minor new feature - the list of compliance frameworks can get a little long, so now you can hide ones that aren't relevant to you 🙂 This feature is already GA, so it's ready to be merged as soon as it passes review.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes