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

Creation of workareas within Main.

Aryan

Greetings!

We are in the process of creating a generic framework for site management. What I wanted to know from a design perspective is whether it is a good practice to have a workarea within the main branch. Since the frameowrk it self would need a workarea for it's maintainance and having a dedicated branch for the framework can have implications on licensing (see my thread http://devnet.interwoven.com/forums_vb/showthread.php?t=20707&forumid=11&highlight=license on licensing), i thought it best to have a workarea under the main branch as the maintainance and administration workarea for the framework.

Could somebody let me know if I am breaching any best practice in doing this?

Find more posts tagged with

Comments

Adam Stoller

Greetings!

We are in the process of creating a generic framework for site management. What I wanted to know from a design perspective is whether it is a good practice to have a workarea within the main branch. Since the frameowrk it self would need a workarea for it's maintainance and having a dedicated branch for the framework can have implications on licensing (see my thread http://devnet.interwoven.com/forums_vb/showthread.php?t=20707&forumid=11&highlight=license on licensing), i thought it best to have a workarea under the main branch as the maintainance and administration workarea for the framework.

Could somebody let me know if I am breaching any best practice in doing this?

Generally speaking, "best practice" is to not have anything stored / maintained directly on the "main" branch - everything should be handled in sub-branches - e.g.:

nipper

Generally speaking, "best practice" is to not have anything stored / maintained directly on the "main" branch - everything should be handled in sub-branches -

Yes but, IWOV is selling licenses with a limited # of branches. main counts as one, so a customer may need to use it.

So while I agree with Adam, that is not a stellar idea. There may be cases when you need to do it. non-best-practice is better than non-compliance.

I would love to see Sunil on this thread, because IMHO, placeholder branches (ones without a WA) should not count against the total # of branches. However that is my opinion, which really does not count for squat.

Andy

Aryan

Greetings Andy,

Did'nt get you on this.

There may be cases when you need to do it. non-best-practice is better than non-compliance.

nipper

Greetings Andy,

Did'nt get you on this.

My point is that if you purchased only 10 branches and need 10, your choice is to use main or create an 11th branch and be out of compliance. Using main in that case is the better of the options.

Aryan

Got it, Thanks.