Defaults and Standards
Aside from Building Blocks and Default Template Building Blocks (upon creation) there are no defaults, but you'll find the following as almost a standard:
System will often have folders for Schemas, Templates, and other system-related items as Pankaj suggests.
The SDL Education courses describe 3 ways to organize:
- By Department
- By Channel or website (or in your case, local vs. global use)
- By Department or Business unit
There's also by date. These aren't specific to Tridion--look at any file system to see the same patterns. Indeed, I'll often ask customers what their current folder organization looks like (outside Tridion) before finding a good fit for their Tridion setup.
I use the "key" analogy when describing organization best practice: it's not about where you should put items, but where you can easily find them (like my house keys).
So when looking at "requirements" for each content type I'll suggest folders that optimize how that item is managed in terms of creation, updates, and selections.
- For re-use (like with Images), as Bart mentions, consolidate items into fewer folders.
- For tasks with lots of related parts, group these into containing folders.
- For speed in creation or selection, place items higher in the folder structure.
- To "flatten" heavily nested folders, use a naming convention (e.g. prefixes can let you remove one level of folders). Also, you might not need global or local folders because you might be able to tell by the context of the current publication.
Most setups I've seen or suggested at least lock down the first level or two for folders.
You can cut & paste items so references to those items stay the same. However, here are some gotchas.
First of all, be careful with renames and Content Porter since it's based on WebDAV paths. Rename them manually across environments, map the differences, or handle duplicates as needed.
Folders are also related to:
Permissions -- you can restrict read, write, delete, and localize permissions based on folders. Assuming a folder structure up front is okay, but might mean needing to set lots of folder permissions for groups later.
Visible drop-downs -- it's not readily apparent, but
read permissions on the folders that contain Schemas and Component Template changes what each user sees in the form views. This is easy to change later by cutting & pasting Schemas into subfolders as needed (refer to warning on Content Porter though).
Image Paths -- Optionally image paths (if using template code to place images into Structure Groups) are based on folders. If needing to change the folder-based structure or paths later, then you'll have to unpublish and republish images. And since template can also indirectly publish images, this might mean republishing much of your website.
Training -- Editors learn where everything is in a Tridion setup quickly and may not appreciate wide-scale changes without warning. Also, if you've developed custom training on how to make articles, the screenshots and paths will be out-of-date if you change the folders. :-)
I talk more on the differences between organization in the build versus management phases of a Tridion project in this post.