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

Reference Implementation

KristerS

I've been looking for best practices information, but cannot find anything. Are there any best practices/reference implementation that can be followed when setting up a new TeamSite server? Is there anything for setting up branches, workareas, etc?

Reading the documentation shows that there is so much possibility to do most anything you want, and of course so much possibility to get yourself into trouble.

So, I'm just wondering if there is anything for a group to follow/compare against to make sure they are heading in the right direction.

Thanks,
Krister

Find more posts tagged with

Comments

ISCBorisB

I've been looking for best practices information, but cannot find anything. Are there any best practices/reference implementation that can be followed when setting up a new TeamSite server? Is there anything for setting up branches, workareas, etc?

Reading the documentation shows that there is so much possibility to do most anything you want, and of course so much possibility to get yourself into trouble.

So, I'm just wondering if there is anything for a group to follow/compare against to make sure they are heading in the right direction.

Thanks,
Krister

I'm not aware of any IWOV Best Practices Document on Branching. There are few Forum's threads discussing the issue,
take a look at [post=92327]this[/post] one for example. Search for them. Granted, it's not much and they are not detailed. They do however
show real life issues that people encountered in their Projects, outlines of solutions, options and the like.

Other than that, look for The Definitive Guide to Interwoven TeamSite (way too much useless RUP shpill in my opinion
but coherent and solid description of the IWOV concepts)

KristerS

Thanks for the pointers, ISCBorisB. That is very helpful!

Adam Stoller

Thanks for the pointers, ISCBorisB. That is very helpful!

Keep in mind that part of the reason that TS has been successful for so many customers is because it does not force all customers to use it in the same way - i.e. the requirements of the organization tend to dictate the details of the implementation and what works best for one organization may not work best for another.

This leads to the often disliked response ("it depends") when someone asks "how should I do this?"