[MSHOP-17] Use pages instead of data module to define Product Categories Created: 25/Oct/11  Updated: 21/Jul/15  Resolved: 04/Nov/11

Status: Closed
Project: Magnolia Shop (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Improvement Priority: Blocker
Reporter: Boris Kraft Assignee: Teresa Miyar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MSHOP-13 Shop home page template should contai... Closed
is related to MSHOP-12 Allow editing of Current offers from ... Closed
is related to MSHOP-18 Detail page should use localized data... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

I spoke with Will why he has used the data module to define the product category hierarchy instead of using a "Product Category" page template to do so. The reason why is that he wanted to be able to have localized URL's for SEO reasons. In other words, this is a workaround, nothing more, and makes understanding and using the shop module unnecessarily complicated.

Please define a page template "Product Category" and ensure this works the same way like now to support localization. In other words, if the page is served for German, the URL should contain the German category (== Page Title) (currently in addition to the English one but I think we could drop the English one in that case)

If so, this would solve a lot of issues at once:

  1. it would be much more intuitive to create the product category hierarchy
  2. it would allow us to use standard pages & their functionality for instance to have a header per product category
  3. it would reduce the complexity of the shop configuration interface (because the categories move out of the data module)
  4. it would make it clear what product categories actually are (i.e. that they define the page hierarchy)

Once implemented, drop the Product Categorization scheme we currently use as it would not be needed anymore. Update the product category selection dialog for the products to use this page structure instead.



 Comments   
Comment by Jan Haderka [ 22/Nov/11 ]

Just not sure how much sense it makes to have all queries in xpath since it is deprecated as of JCR 2.0.

Generated at Mon Feb 12 07:08:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.