As editors we cannot always predict whether a block will need to be reused in the future. And since in SaaS there's no way to copy an inline block from one page to another or make an inline block shared without having to recreate it from scratch, this results in redundant work and takes a significant amount of time!
Use case example:
We create a large FAQ block specifically for page X, so we create it as inline block. Later, we create page Y, where we want to reuse some of these FAQs. Since the FAQs were originally created for page X, we now have to manually recreate them for page Y or as a shared block. This results in redundant work and takes a significant amount of time.
(In PaaS, we always use the "For this Page/Block" folder to copy content since all inline blocks are stored there, but this is not the case anymore in SaaS)
Ilse Peetsma
supported this idea
·
Totally agree with this request!
As editors we cannot always predict whether a block will need to be reused in the future. And since in SaaS there's no way to copy an inline block from one page to another or make an inline block shared without having to recreate it from scratch, this results in redundant work and takes a significant amount of time!
Use case example:
We create a large FAQ block specifically for page X, so we create it as inline block. Later, we create page Y, where we want to reuse some of these FAQs. Since the FAQs were originally created for page X, we now have to manually recreate them for page Y or as a shared block. This results in redundant work and takes a significant amount of time.
(In PaaS, we always use the "For this Page/Block" folder to copy content since all inline blocks are stored there, but this is not the case anymore in SaaS)