Flag providers and backoffice signs #7325
Open
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
|
Before this is finalized and merged, please note that the Signs have changed names to Flags with this PR umbraco/Umbraco-CMS#20109 |
I've updated the documentation to reflect this. |
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.
📋 Description
This PR adds details of flag providers and backoffice signs that are targeted for 16.3. It will be added to with the client-side details when they are ready.
📎 Related Issues (if applicable)
Relates to PR: umbraco/Umbraco-CMS#19806 and umbraco/Umbraco-CMS#20109
✅ Contributor Checklist
I've followed the Umbraco Documentation Style Guide and can confirm that:
Product & Version (if relevant)
CMS 16.3
Deadline (if relevant)
Expect this to be published along with the RC for 16.3 which is scheduled for 2nd October.