Splitting https://ideas.arcxp.com/ideas/PB-I-311 into smaller ideas. First one below:
We have a large (100+) amount of pages and templates and managing them manually through PB is very cumbersome and time consuming. Especially difficult is looking up information about a specific component:
- is it used?
- on how many pages?
- on how many templates?
- what is its configuration?
- is the configuration the same on each usage or different?
There are two primary usages for this:
- if a component is being changed or renamed we need to update all the places where it was used, and
- if we suspect that a component isn’t used we want to be able to search all the pages to verify that before deleting it
Other usages include:
- allow QA to search for pages using a specific component after it has changed
- editors to search for example configurations of a component when they want to add it and aren't familiar how it's used
This tool should work with PB Data exporting the whole PB configuration, as well as with configuration exports of individual pages or templates (will we need two different tools for that?)
Grzegorz Junka
Hi Greg,
We released a recipe github repository that contain collection of scripts to analyze feature and content source from PageBuilder page/templates. Check out:
Github Repo
Recipe tutorial in ALC (with video demo)
You have some specifics noted in the idea description that the initial version of the scripts don't provide (yet), but I'm interested to see how we can extend them for more granular information they can print.
Feel free to reach out to me or your TAM about any questions.
Hi Greg,
Thanks for submitting this idea. I think both I and Katherine talked about this with you to understand more. This particular idea is a high-impact need and we have a corresponding initiative that may remove the need to do manual pb-data dump to JSON conversion. But we'll keep this aha idea in the backlog until we have clear details about the feature we're considering.