When using site tree features, is there a way using Hubl to loop through all child pages of a parent page.
This feature would allow us to create a basic form of collections, using the featured image and meta description of the child-page as the main references in an overview grid.
Example use case: cases
- Cases Overview (collection grid of all child pages)
-- Case detail
-- Case detail
-- Case detail
Any other help on approaching this very common use-case is much appreciated!
At the moment is not possibile for existing pages… only available for new pages. Quite disappointing because sitetree feature is pretty new, so all content that was created before cannot be organized in a structured way. I really hope the product development team can allow to drag and drop existing content into subcategories, implementing automatic redirect of old pages.
In the meantime, I would also appreciate if the product development team could suggest a solution on how to handle existing product pages that needs to be out under main categories pages
Hi all, I have found a solution from an another member of the community. Basically you can overcome the problem by editing the page urls and adding the category. (go on website pages, click on the page you want to edit > options > edit the existing url.
Ex: mywebsite>product will become mywebsite>category>product. Hubspot will automatically create a redirect from the old page to the new one. In this way you can reorganize your website sitetree.
Hello @ENasato , thank you for your reply, yes we can add a “slug” of parent page to any page and make it a child page:
Primary (domain.tld/primary)
Child A (domain.tld/primary/child-a)
Child B (domain.tld/primary/child-b)
Child C (domain.tld/primary/child-c)
The question was how can we list all Child pages on the Primary page?
without manual work - like creating a module where the user selects all child pages in the repeater
I did not find any bi-directional relationship or even one-way relationship, or a way that we can query subpages from the parent page in the Docs/Community - excluding dynamic pages.
for some small parts (portfolio, partners, topics…) I think making Archive have more sense even if it falls under Page