Feature/blueprint #893
Merged
Feature/blueprint #893
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
rename content template to content blueprint for naming consistency
implement same name as settings for document template
bkclerke
added a commit
to bkclerke/UmbracoDocs
that referenced
this pull request
Sep 21, 2023
Rename conten templates to document blueprints in v12 and new backoffice folders for naming consistency in the new backoffice update. See umbraco/Umbraco.CMS.Backoffice#893. NOTE: Images have not been updated.
5 tasks
iOvergaard
approved these changes
Sep 22, 2023
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.
Rename "Content Template" to "Document Blueprint" to be consistent in the CMS.
Description
Previously Content Template and Document Blueprint were different names in the backoffice for the same feature. Renamed Content Template to be Document Blueprint for naming consistency in the CMS.
Types of changes
Motivation and context
The naming for the same feature was different in the Content and Settings section.
How to test?
Right click on a content node in the content section and verify the Document Blueprint name. All notifications should also reflect Document Blueprint and the settings tree.
Screenshots (if appropriate)
Checklist