Remove EdgeDB pricing blurb and fix capitalization#967
Remove EdgeDB pricing blurb and fix capitalization#967leslie-lau wants to merge 2 commits intomainfrom
Conversation
Deploying devcycle-docs with
|
| Latest commit: |
9356b45
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4aa9236e.devcycle-docs.pages.dev |
| Branch Preview URL: | https://feature-optin-remove-edgedb.devcycle-docs.pages.dev |
There was a problem hiding this comment.
Pull request overview
Updates the Feature Opt-In documentation to adjust pricing/plan messaging and revise various capitalization/wording details.
Changes:
- Updates Feature Opt-In intro/implementation text with broad capitalization changes (e.g., Feature/Environment/Variation/Targeting Rule).
- Changes settings navigation wording from Organization Settings to Project Settings.
- Replaces the EdgeDB billing note with new “not available on Free plans” + pricing page language, and updates the API reference for custom widgets to point to the Bucketing API.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Feature Opt-in allows end users of your product to opt-in to a list of eligible Features through a pre-built widget that can be implemented in your app and website with one line of code. Your team has the ability to customize the look & feel of this widget to your company's colour profile and logo. | ||
|
|
||
| This article explains how to implement our Feature Opt-in functionality on your app or website. |
There was a problem hiding this comment.
The doc uses inconsistent capitalization for the feature name: this section says "Feature Opt-in" while the page title and other sections use "Feature Opt-In". Please standardize the naming (including "Opt-In" vs "Opt-in") throughout to avoid confusing readers/search.
|  | ||
|
|
||
| Feature Opt-In is first enabled at the project level. It needs to be enabled manually because it leverages EdgeDB to manage a user's opt-in state. This means that enabling Feature Opt-In on a project can impact billing for your account. For more information on EdgeDB pricing visit our [pricing page](https://devcycle.com/pricing). | ||
| Feature Opt-In is first enabled at the Project level. It needs to be enabled manually because it leverages EdgeDB to manage a user's opt-in state. As a result, Feature Opt-In is not available on Free plans at this time. Visit our [pricing page](https://devcycle.com/pricing) for more details. |
There was a problem hiding this comment.
This paragraph still contains (and expands) pricing/plan messaging ("not available on Free plans" + link to pricing). Given the PR intent to remove the EdgeDB pricing blurb, consider removing plan/billing references here or updating the PR title/description to reflect the new pricing guidance, and verify the plan limitation statement is accurate/current.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Feature Opt-in allows end users of your product to opt-in to a list of eligible Features through a pre-built widget that can be implemented in your app and website with one line of code. Your team has the ability to customize the look & feel of this widget to your company's colour profile and logo. | ||
|
|
||
| This article explains how to implement our Feature Opt-in functionality on your app or website. |
There was a problem hiding this comment.
In this section the feature name is written as “Feature Opt-in”, but the page title and most other references use “Feature Opt-In”. Consider standardizing the capitalization here to avoid confusion/searchability issues.
| Feature Opt-in allows end users of your product to opt-in to a list of eligible Features through a pre-built widget that can be implemented in your app and website with one line of code. Your team has the ability to customize the look & feel of this widget to your company's colour profile and logo. | |
| This article explains how to implement our Feature Opt-in functionality on your app or website. | |
| Feature Opt-In allows end users of your product to opt-in to a list of eligible Features through a pre-built widget that can be implemented in your app and website with one line of code. Your team has the ability to customize the look & feel of this widget to your company's colour profile and logo. | |
| This article explains how to implement our Feature Opt-In functionality on your app or website. |
| Below the customization options and styling preview is the iFrame code snippet and a tool to test the widget with different user IDs. Select the Environment you would like to test or implement in the dropdown and insert any user ID to validate what the widget will look like for a given user by clicking "Open Preview". | ||
|
|
||
| This code snippet is initially presented in simple HTML format, but React and Angular alternatives are available via the "Frontend framework" dropdown above the code snippet. | ||
|
|
||
| The two most important parts of the iFrame code are the environment key and user ID. Make sure that you are setting the right key for the environment the widget will be displayed in, and ensure you always pass the relevant user ID for the user that is interacting with the widget. | ||
| The two most important parts of the iFrame code are the Environment key and user ID. Make sure that you are setting the right key for the Environment the widget will be displayed in, and ensure you always pass the relevant user ID for the user that is interacting with the widget. |
There was a problem hiding this comment.
These paragraphs start with extra leading whitespace compared to the rest of the document. It’s easy for indentation in Markdown/MDX to create unintended formatting (e.g., code blocks) and it also makes diffs noisier—please remove the leading spaces so these render consistently.
|  | ||
|
|
||
| When Opt-In is enabled for a feature the special targeting rules cannot be deleted, to remove the Opt-In targeting rules you must disable Opt-In entirely for the feature. This will automatically remove all of the special targeting rules. | ||
| When Opt-In is enabled for a Feature, the special Targeting Rules cannot be deleted, to remove the Opt-In Targeting Rules you must disable Opt-In entirely for the Feature. This will automatically remove all of the special Targeting Rules. |
There was a problem hiding this comment.
This sentence has a comma splice (“cannot be deleted, to remove…”). Please split it into two sentences or rework with a semicolon/"so" to improve readability.
| When Opt-In is enabled for a Feature, the special Targeting Rules cannot be deleted, to remove the Opt-In Targeting Rules you must disable Opt-In entirely for the Feature. This will automatically remove all of the special Targeting Rules. | |
| When Opt-In is enabled for a Feature, the special Targeting Rules cannot be deleted. To remove the Opt-In Targeting Rules, you must disable Opt-In entirely for the Feature. This will automatically remove all of the special Targeting Rules. |
No description provided.