SCC FeedbackWe value your input! Tell us what you think about our Sana Commerce Cloud roadmap initiatives and the direction we're taking. If there's something specific you'd like to see, don't hesitate to share it with us below. Vote for ideas on the page to let us know what you find important. You can vote by clicking on an idea and then click thumbs up, down or neutral.
Individually allocable product group page templates and article detail page templates
Since product group pages and item detail pages are fully editable, it would be great if several different product group pages templates or item detail pages templates could be created and assigned to product groups or items individually. In this way, the display can be optimally adapted to the properties of the different product groups or articles.
Today, the layout (for both Desktop and Mobile) of the ProductPage is handled as follows:
If there is a change at the level of a specific ProductPage, this is used. Otherwise, the layout of the SystemPage "Product details" is used
One of our customers had to structure the layout of a group of articles in a different way than all the others. Specifically, these articles were to have 3 columns in the detail line instead of the 2 columns defined as standard:
In the first the images are shown.
In the second, the article detail is shown (Title, Short Description, Price, Variant, Quantity, Unit of Measure, etc...)
In the third, related articles are shown (vertically)
In order to do this, we had to manually update all pages one at a time. This means that if we need to change this layout in the future, we will have to intervene on all pages one at a time.This is why we propose the following idea: add a new layer through which you can define the layout of the ProductPage. In our opinion, the layout selection logic could be as follows:
If there is a change at the level of a specific ProductPage, this is used
Otherwise, if a "Group/Template" layout is associated with the ProductPage, this is used
Otherwise, the SystemPage layout "Product details" is used.
3
Duplicate content from product pages on desktop view to mobile sites
Duplicate content from product pages on desktop view to mobile sites

It would be helpful to use the "revert to default" button on the mobile view product pages similarly to how we use the revert to default button on the content pages so that we do not have to upload content twice.



For example: A number of our products utilise lengthy product descriptions that include photos and images. On desktop view we use the content building elements to build complementary layouts that showcase this information in a suitable format for each individual product. However, unlike on content pages where we are able to use "revert to default" to port the information over, we have to re-upload all of the description content again, meaning it takes twice as long to build a product page as it does a content page.

1
0
0