Ideas for Arc XP

ThIs Arc Idea was suggested by ACS on ticket ACS-5492, wich contains more details in examples.

The general problem is this:  We have pages that use features that are populated from a collection of stories, or a content feed (in the case of pages featuring galleries, which currently can't be included in a collection.), Multiple features on a page pull from different offsets in the collection or content feed . We have set up our workflow so that editors can update these pages by adding and rearranging stories in a collection and publishing the collection, without the need to publish a new version of the page in PageBuilder. IN fact these editors do not use pagebuilder in their workflow, nor do they have permissions to use it.

The ACS ticket suggested we request "for there to be a way to clear all the content of a PB page at once."   During an Arc onsite visit this week, this was brought up and a suggestion was made that this might be addressed by a button to clear  all caching for a page.  The problem is that this button would need to be in PageBuilder, and the editors making these updates do not use pagebuilder.

Could there be a configuration option in PageBuilder to say a page should be cached as a whole for customers who needed this. (I realize that some customers.might not want the entire page cached as a whole, as certain features might be personalized.)

Another approach might be providing a way in PageBuilder to assign multiple features to a single caching group. so that if any any feature in the group is  updated, cache would be purged for all the features in that group.

Nota Bene:  These suggestions are based on Zero understanding of how 1) PageBuilder caching and any other caching hat occurs in Arc when a collection gets updated and the corresponding page is displayed, and 2) how features get updated when a collection that drives them gets updated and published.   I am probably not the only customer that would benefit from Arc providing clear information on this.

Two other questions based on this statement on the ACS ticket:

"So each feature on a page, or instance of a feature, is cached separately. So if Feature1 and Feature2 use the same content source but with different offsets, the TTL will most assuredly be different and during the overlap, the same story could appear twice. Since this is the behavior we have always had, there is not a way to clear this."

Q1:  Is this happening to other customers as well, or are we unique, and this has something to do with the way our PageBuilder templates were implemented as part of onboarding or subsequent development we did ourselves?

Q2:  Is this somehow related to our still being on PageBuilder Classic, rather than on Fusion based PageBuilder templates?

Sorry about the long idea submission, but it's a complicated issue, and I can be obsessive. ::-)

Thanks!

Ian Krantz

Philadelphia Media Network