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

editions question

Ottawa_IWOV

All,

IS it possible to have all your editions deploy into a consolidated edition that will then be deployed to a product web server. Just so I don't confuse anyone...

branch 1
EDITION

branch 2
EDITION

branch 3
EDITION

Consolidated EDITION (editions from branch 1,2 & 3)

Then a teamsite-based deloyment to webservers.

Lucas Cochrane
lcochrane@dc.com

Find more posts tagged with

Comments

Adam Stoller

Editions are based on the content in the staging area for a specific branch. Period.

If you transfer content from the editions on the 3 branches into a workarea 4th branch, submit it, and then publish an edition on the 4th branch - you could deploy it from there.

Whether or not you really want to do this is another matter

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

Lucas;

If branch1-3 are each sub-branches of the same parent branch, then you could do a copy-to-area from each sub-branchs' staging to a workarea of the parent, submit and cut an edition. The new parent branch edition would have all the files from the 3 sub-branches.

This works well if the sub-branches represent a decomposition of a large content set, such as a website. However, if there are duplicate files in 2 or more sub-branches, they'll over-write each other in the parent branch.

bw

Bob Walden [bob.walden@interwoven.com]
Interwoven Education Group
IM: Yahoo, MSN bob_walden