Hi @MayPascaud@, thanks for the response! I figured it wasn’t possible to do this but just wanted to make sure.
I’ll lay out our use case, as think there are a few major shortcomings/issues with the COS that do need to be addressed (the other being a hubl repeater issue mentioned by @AJLaPorte_diagr).
So, I’m lead developer at a branding/marketing agency, our leadership (and existing/potential clients) want to be able to manage websites from their Hubspot dashboard rather than a separate CMS, and I want to be able to make it happen for them. Often our sites will have a lot of groups of related pages that may or may not share a single template - case studies, featured work, service offerings, team members, career listings, brand ambassadors, products/shop, locations, etc.
I would rather not use blogs to manage all these groups because they are not similar to blog content - they won’t need comments, topics, authors, date info, compositions feature, subscriptions, rss feeds, etc. They will not be continually published to.
But, these groups will need the ability to use separate templates within the same group/collection. We will also want to make highly customized “parent/listing pages” for these groups that use hubl modules for extra editable information unique to that page.. the way these blogs work now that is not possible, there is no editor view for blog listing pages. It is also much easier to jump between folders in the “landing pages” section than to go back and forth between different blogs to edit things.
Lastly I just wanted to point out that every CMS has the ability to pull the data from a given page via a unique identifier, it’s a useful utility feature.
Anywho, thanks again for your input, and here’s to hoping these concerns are able to be heard by someone with some influence on the COS product development roadmap… thanks again!