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

Best practices - TeamSite Folder structure vs. Application structure

alex_assard

Hello,
I am wondering if it is generally recommended to mirror your web application's structure inside the TS folder structure? In other words, do the files that are pushed to the server have to be organized in TS so that the folder structure matches the URL structure?

Thank you for your insight.

Find more posts tagged with

Comments

Adam Stoller

Hello,
I am wondering if it is generally recommended to mirror your web application's structure inside the TS folder structure? In other words, do the files that are pushed to the server have to be organized in TS so that the folder structure matches the URL structure?

Thank you for your insight.

As much as possible - yes - the directory structures should mirror one another.

When dealing with entire page contents - this is straight-forward.
When dealing with "component" pieces of content / content that appears in multiple places on multiple pages on the site - you still want to do this, but it's a bit less straight-forward.

If you don't do this - you're going to have a major headache trying to deal with deployments.

alex_assard

Thank you.
We'll be using this as a guideline.

Firenze

Agree that deployments are harder when the two don't match; however, want to add more food for thought when coming up with best practice.

Folder structures (including branches, workareas) should take into consideration more than publishing such as folder security, content re-use, workflow, browsability/navigation.

You may want to distinguish between the structures of source content DCRs and the like versus page templates and generated content.