Updated: This post turned into a 30-page article that SharePoint Advisor Magazine wants to publish. I will blog the link when it is publically available.
The new ONET.XML file contains details about how a new Site will be provisioned when it is first created. It is located in the XML folder of our new Site Definition (\60\TEMPLATE\1033\STS2\XML\ONET.XML). What follows is a summary of the changes I typically recommend:
- Protect your future by modifying the project element
Define an alternate .CSS file to override default SharePoint styles, a custom JavaScript file to override client-side script, and define what FrontPage can and can't do with a site.
- Security Trim the top Nav and add an Uber Admin Page
Remove the documents and lists, create and site settings options from the Top Nav, and add a link to an Uber Admin page customized for each site definition or each site. This page can be link-based or list-based.
- Differentiate between a list and a list template
Alter the labels on the Create page to reflect the fact that the options listed on that page are List Templates, not Lists.
- Alter the default lists
Remove Shared Documents, remove the spaces from the General Discussion URL, and optionally add an AdminLinks link list.
- Add ghosted direct-mode pages to each site root and post processing to site creation
Anticipate the need for any ghosted direct-mode pages in the root of each site including a local Uber Admin page, and add these pages to the site when it's initially provisioned. Also include a post site creation code page in the root to run site modifications you can't define in the ONET.
<Todd />