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; } } }

SitePublisher supports 1 WorkArea per branch

shweta_komal

The SitePublisher Developer guide, contains 1 line repeatedly:
"SitePublisher only supports a single Workarea per branch."

1. Does this mean that the branches under /default/main should have only 1 Workarea?

2. If my workflows are configured
- to deploy content directly from the WorkArea
- creates new Dynamic workarea associated with each deployment job.
Now if i install SitePublisher, will the above setup, with "Dynamic WorkAreas" work?

Find more posts tagged with

Comments

srosewall

1. Does this mean that the branches under /default/main should have only 1 Workarea?

Only if the branch includes sites using SitePublisher.
Branches which don't include SitePublisher sites can continue to use multiple workareas without any change in expected behaviour.

2. If my workflows are configured
- to deploy content directly from the WorkArea
- creates new Dynamic workarea associated with each deployment job.
Now if i install SitePublisher, will the above setup, with "Dynamic WorkAreas" work?

If your current branch/workareas don't include SitePublisher-based sites, then you should be fine - installing SitePublisher does not impact non-SitePublisher branch / multiple workarea use. The restriction is only for branches which include sites created and administered with SitePublisher.

Hope that helps.

shweta_komal

Hi,

Thank you; your answer was very precise for point#1.

But, could you please elaborate for point#2?

Given that my motive is to implement sitepublisher in the existing branches which have multiple workareas, (one WA for work/content and other WAs created by deployment jobs). And the current setup allows deployments to be done directly from the workarea, instead of edition; creating new dynamic workareas, everytime a new deployment job is created/executed.

How would you believe, enabling SitePublisher into the existing setup, affect? What are the changes to be implemented, as foreseen by you?

srosewall

Given that my motive is to implement sitepublisher in the existing branches which have multiple workareas, (one WA for work/content and other WAs created by deployment jobs). And the current setup allows deployments to be done directly from the workarea, instead of edition; creating new dynamic workareas, everytime a new deployment job is created/executed.

How would you believe, enabling SitePublisher into the existing setup, affect? What are the changes to be implemented, as foreseen by you?

You will need to consider changing your approach; you will need to flattern your multiple workareas down to a single workarea, and base your content processing around there only being one workarea.

The conventional approach with SitePublisher is to use the out-of-the-box Publish LiveSite Content (PLC) workflow which is based on filelist deployment; your users select the files/folders they wish to publish and submit them using the PLC.

Any other approach will be down to you to develop/test/implement and support.

Regards

shweta_komal

Thank you!!!!