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

Simple Submit/Deployment Question

System

I would like to organize folders in a given a workarea differently than how that would ultimately be deployed on a production website.

Ex:

Branch: mydocroot WA: TomWA

Workarea folders:
/a-n/aaaaa
/a-n/aaaaa/images
/a-n/nnnnn
/o-z/ooooo
/o-z/zzzzzz

Upon submission or deployment, I would like to remove /a-n and /o-z from the path so that ultimately the folders would reside in staging and/or the production docroot as:

aaaaa/
/aaaaa/images/
nnnnn/
ooooo/
zzzzzz/

What would be the best approach to take to achieve this goal?

Find more posts tagged with

Comments

nipper

OK, because I am answering it, doe not mean I think this is a good idea. I think it is a bad idea. Your previews and/or links are likely going to be messed up without some fancy footwork

Typically in a deployment you have a deployment path (path=".") which implies take form the workarea root. You can have path ="/aaa" which takes everything from /aaa and discards that folder when it places the files on the server.

Put the path in as a deployment parameter and have the calling routine add -k docroot=/aaa

Migrateduser

Thanks.

None of the files in these "child" folders have anything to do with one another. Each folder's contents is, in effect, a mini-site. My user base has over 1000 of these under a single docroot. The users all share a workarea. They don't wan't to add addtional branches. Teamsite misbehaves when the number of objects in a single folder/workarea exceeds 500 so I am looking into options that allow me (within limits) to organize these mini-site directories within teamsite differently.

test.txt

nipper

OK, so it sounds like you have the right approach. Branches would be better, but this will work. You are going to have to play with the docroot setting in the iw.cfg so everything previews correct. Also some other things to filter out the /aaaa (say you browse to an image)

The WF changes are not difficult, provided you have some perl experience, deployment changes are easy.

ISCBorisB

user [...] has over 1000 of these under a single docroot... The users all share a workarea... They don't wan't to add addtional branches

GUI (browser) navigation with such a setting may become very unpleasant

Migrateduser

With the 1000 folders in a single branch or after I break them down alphabetically?

I am open to/hoping for other suggestions