[docs-11806] New "Getting Started" Guide for Feature Flags #31297
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A-Rindone
added
the
getting_started
github-actions
bot
added
Architecture
Preview links (active after the
|
A-Rindone
changed the title
Convert to Hugo shortcodes
joepeeples
reviewed
Aug 27, 2025
testing if file names are case-sensitive
also remove some empty space in image, for readability
joepeeples
reviewed
Aug 27, 2025
Comment on lines
+4
to
+6
| - link: 'https://github.com/DataDog/openfeature-js-client/blob/main/README.md' | ||
| tag: 'Source Code' | ||
| text: 'OpenFeature JavaScript client documentation' |
There was a problem hiding this comment.
This repo is currently internal, so customers and anyone else outside of Datadog will get a 404 with this link. Same as in-line links to the page.
|
|
||
| {{< partial name="whats-next/whats-next.html" >}} | ||
|
|
||
| [1]: https://github.com/DataDog/openfeature-js-client/blob/main/README.md |
There was a problem hiding this comment.
As mentioned above, this repo is internal so links to the page will return a 404 for customers.
|
|
||
| * **Built for experimentation:** Target specific audiences for A/B tests, roll out features gradually with canary releases, and automatically roll back when regressions are detected. | ||
|
|
||
| * **Integration with Datadog:** Out-of-the-box integration with Datadog metrics, change tracking events, and more—no additional instrumentation needed. |
There was a problem hiding this comment.
Looks like a holdover from Eppo docs, but I don't know if we'd want to omit this, or revise to something more updated. @A-Rindone any thoughts?
Comment on lines
+103
to
+107
| - name: Feature Flags | ||
| identifier: getting_started_feature_flags | ||
| url: getting_started/feature_flags/ | ||
| parent: getting_started | ||
| weight: 11 |
There was a problem hiding this comment.
Should the page be nested under the Software Delivery grouping?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Creating the initial "Getting Started" guide for our upcoming Feature Flags product, as well as adding a new link in the sidebar under "Getting Started".
Note that this only impacts the "Getting Started" section.
Merge instructions
Please validate that images (screenshots) are handled correctly, and/or recommend any needed changes.
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