Skip to content
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.

Sign up for GitHub

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

Jump to bottom

re: RFC 0025 - typo corrections #40

Merged
merged 1 commit into from
Jun 20, 2023
Merged

re: RFC 0025 - typo corrections #40

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 4 additions & 4 deletions cms/0025-reusable-content-with-global-blocks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

### Request for Contribution (RFC) 0025 : Reusable Content with Global Blocks

**Please comment on this RFC in this [RFC Dicsussion](https://github.com/umbraco/rfcs/discussions/35)**
**Please comment on this RFC in this [RFC Discussion](https://github.com/umbraco/rfcs/discussions/35)**

## Code of Conduct

Expand Down Expand Up @@ -73,7 +73,7 @@ We believe that Local Blocks still have relevance on sites, where you want to li

##### Make Global

We want to ensure a smooth transition between Local and Global Blocks, so that if you have a Local Block that you want to use in more than one Block List or Block Grid, - it should simply be possible to make it global. In this process, you need to give the Block a name and also place it in the correct folder - and the block will afterward be available in the Library folder:
We want to ensure a smooth transition between Local and Global Blocks, so that if you have a Local Block that you want to use in more than one Block List or Block Grid, - it should simply be possible to make it global. In this process, you need to give the Block a name and also place it in the correct folder - and the block will afterwards be available in the Library folder:

![Content Section - make global](https://github.com/umbraco/rfcs/blob/0025-reusable-content-with-global-blocks/cms/assets/global-blocks/Content%20-%20make%20global.jpg?raw=true)

Expand Down Expand Up @@ -121,13 +121,13 @@ As we think it makes sense to have the Block Settings as something that relates

Although we mention Tags as part of the new Library section, it's not in the scope of this RFC to discuss moving and updating Tags.

### Unrosolved issues
### Unresolved issues

Some of the answers that we hope to get out of this are:
- Related to the technical considerations, if we are right, that it makes most sense to have Block Settings stored within the Content Node or if there are more/better use cases for storing Block Settings globally too.
- In case you work with segments, if you can see any implications in this proposal.
- More perspectives on the proposed new section called “Library”. If it should be there at all and if so what it should include.
- The naming. Should we call it Global Blocks, resusable content or something else.
- The naming. Should we call it Global Blocks, reusable content or something else.

## Contributors

Expand Down