nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

add to sitemap on publish?

pwoolcoc

Does anyone know if there is a way to add a .page file to the default.sitemap using workflow? For example, in the "Publish Livesite Content" workflow I would like it to add the .page to the sitemap based on it's position in the sites directory structure, so my users don't have that extra step every time they make a new page.

The reason I want to do this is that we have a site-navigation component that generates navigation based on the sitemap.

Find more posts tagged with

Comments

Migrateduser

I too want this business flow to be implemented in our project. Any pointers will be really helpful..

Thanks
Manu G

santosh013

Does anyone know if there is a way to add a .page file to the default.sitemap using workflow? For example, in the "Publish Livesite Content" workflow I would like it to add the .page to the sitemap based on it's position in the sites directory structure, so my users don't have that extra step every time they make a new page.

The reason I want to do this is that we have a site-navigation component that generates navigation based on the sitemap.

Hi,
You will have to update the sitemap and publish it to get the navigation on your site.
One thing your business users can do to avoid updating the sitemap and publishing it is to create pages and a left/right component to navigate to different pages not listed in Sitemap but it itself seems weird.

Thanks.

Rick Poulin

Does anyone know if there is a way to add a .page file to the default.sitemap using workflow? For example, in the "Publish Livesite Content" workflow I would like it to add the .page to the sitemap based on it's position in the sites directory structure, so my users don't have that extra step every time they make a new page.

Given your requirements, why would you bother with the sitemap? If it's entirely based on the folder structure, just have your component generate the navigation based on that.

Either way, you're going to need to do a bit of coding to either write that external, or write something that updates the sitemap file and republishes it. The difference is that the latter is not technically supported, since there's no official API to modify the sitemap and there are no guarantees that IWOV won't change its XML schema in the future.