Scaffolding is a great way to provide a way for end user to create predefined pages like for instance, news pages.
Now suppose you have created your scaffold with just 2 fields:
You put the scaffold in production and it is used heavily by the end users, to create news pages. Unfortunately after a while your business user is like, 'I want to add a category as well'. Np, let's just change the scaffold and template to provide this functionality :-).
Question here is, what does this mean for the already created content (pages)? Is there a way to regenerate the created pages. What is the way to go here?
Next to that I wonder if it would be more interesting to create a more dynamic component that just renders the data in stead of create real pages using scaffolding.
Any thougths on this, anybody?
Solved! Go to Solution.
Here is the documentation:
http://dev.day.com/docs/en/cq/current/wcm/scaffolding.html
When you change the Scaffolding Template- the existing pages are updated. Therefore -- any new content added to the template is reflected in the page.
Here is the documentation:
http://dev.day.com/docs/en/cq/current/wcm/scaffolding.html
When you change the Scaffolding Template- the existing pages are updated. Therefore -- any new content added to the template is reflected in the page.
Thanks for the intel.
Is it also possible to leverage scaffolding on the publisher side. Suppose you want to enable end-users to be able to create pages themselves like on a mini site for instance?
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies