[MTE-56] Sitemap component Created: 14/Oct/15  Updated: 24/Mar/22  Resolved: 24/Mar/22

Status: Closed
Project: Magnolia Templating Essentials
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Outdated Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MTE-3 Navigation features 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)
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: MTE > 1.0

 Description   

There should be a component to create a sitemap on a public page of a website. It should be able to handle actual pages and in some way handle the "virtual pages" that are typically created to show content from content apps on a website (Usually be including a selector or querysring parameter to a a pages url, and sometimes with VirtualURIMapping to accomplish this.)

Possibly the component would require some parameter or dialog configuration to display the desired "virutal pages".

Probably this component will rely on the functionality provided by NavigationTemplatingFunctions.

Possibly this component should not be in MTE but in the Google Sitemap module. But its probably confusing to a developer that they would require the "google sitemap" module to create a regular sitemap on their website.



 Comments   
Comment by Christopher Zimmermann [ 24/Mar/22 ]

While Sitemaps are stilll important, I don't see it being aan OOTB MTE component.

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