Microsoft Office Tutorials and References
In Depth Information
The available site features vary from site template to site template (particularly as to which have
been activated). For the Team Site template, the features available out of the box are as follows:
Group Work Lists The new site template, Group Work Site, offers resource and team
scheduling for the site calendars. This is a feature that is actually available to most site templates;
it’s just not turned on, or activated for non–group work sites. You can activate it to use the ,
group work calendar capabilities if you like. For more on the Group Work Site template and
what it can do, see the “Group Work Site” section later in this chapter. By default this feature
is not activated for a team site.
Report Server File Sync This feature generally requires that you have Reporting Services
enabled on the SQL Server and in Central Administration, as well as configured for the site,
so you can synchronize reports made with SQL Server Reporting Services’ Report Builder
in a document library, with the data the reports reference in SQL Server. As you can see, this
feature has quite a number of requirements and is usually off by default.
Team Collaboration Lists This feature allows the site to offer most of the list and library
templates available for use on a team site. If it is off (and the Wiki Page Home Page feature is
off), you can create subsites, workspaces, and web part pages, and that’s it. All other list and
library templates are gone. Even making a custom list is not an option. This feature should
always be activated by default.
Wiki Page Home Page This feature forces a file named Home in the wiki library Site Pages on
a team site to be the site’s home page. The rich content area of a wiki page replaces the web part
area of a standard home page. Interestingly, if this feature is activated and Team Collaboration
Lists is deactivated, it will cause wiki library templates and the creation of new wiki pages to
still be available when all other list and library templates go away. This feature tends to be
activated for a team site by default. To revert the home page of the site to a web part page, deactivate
this feature (something we do in Chapter 5, “Introduction to Web Parts”).
After you’ve done a lot of work on a site—adding your custom logo, adjusting a theme, creating
new lists or document libraries, customizing the top link bar or Quick Launch bar—you may
want to make a copy of that site to make a new one just like it later. This is where saving it as a
template can come in handy. You can use the saved template to create new sites.
The site template can also include the actual data content of the site, including all the items in
the lists, document libraries, and workflows. Include the content only if you really want all this
data to be part of the template. For example, it might be nice to have a custom list as part of the
template, but you probably don’t want to include all your private human resource documents.
In general, “content” consists of the items inside lists and libraries but not those lists and
libraries themselves. So, the template “without content” will still include a Shared Documents
library, but it will be empty. Web parts are not considered content and will be included in the
template either way, but if the web part references any particular item in a list or library (such as
a picture in a picture library), it will not be included unless you include content. Naturally there
are exceptions—for example, the wiki home page (contained within the Site Pages library) is
included with the template, even if you chose to not include content.
Search JabSto ::

Custom Search