@DMakris wrote:
What is the best practice/approach to deal with page hierarchy?
Ex.
Let’s say that we have 5 product pages (HS websites pages ) and we want to show them by navigating to a central product page.
Hey there @DMakris, thanks for asking.
From an SEO perspective this blog post explains fairly well some good practices around creating an information architecture.
From a development standpoint there are 3 primary ways to build these product listing and individual product pages, and the path you take depends on the individual business’s needs.
Use normal web site pages with drag and drop areas
This is ideal for scenarios where a company has only a few products or services. It gives them a ton of flexibility to build the pages to suit their needs. However when you start having dozens of products this becomes more difficult to manage.
Use HubDB to create dynamic pages (CMS Hub Pro and Enterprise)
This enables you to create a massive amount of pages by updating one HubDB table - which is like editing a spreadsheet. This is especially useful in scenarios where products and services have similar types of data associated with them. Think things like:
- Price
- colors
- size
- features
With HubDB you can display all of that information in consistent ways across all of the product pages making the user experience more consistent and easy to understand.
Use custom objects (Requires an enterprise product)
Custom objects are a really powerful and unique way to go. To the developer using custom objects will feel very similar to working with HubDB. The advantage of custom objects though is that you can associate the data with your other CRM objects, to generate useful business insights.
We have an example of how this can be done for real estate - but it can be applied to almost any business.