Microsoft Office Tutorials and References
In Depth Information
Also, when you click the help icon (the blue question mark), you w ill now see the new help collection
listed, and you can browse by the help categories and view any of the help topics you uploaded.
While we’re on the subject, ever wonder why when you click the help icon on a particular page in
SharePoint, it always takes you to the help table of contents, and not to that page’s relevant help
category? It’s not that hard to create contextual help. Using SharePoint Designer, in advanced mode, you
open the ASPX page itself that you want to have open the relevant help topic when the help icon is hit
and edit a single variable, navBarHelpOverrideKey. This variable uses a key, WSSEndUser, which
points to the generic SharePoint Foundation help collection. You can replace it with your custom
category by using your category as the key. The syntax is simply helpcollection category , for example _
companysite_travel. Once you save the page, the help icon on that page will go to the category you
want rather than the general help page (if you have that collection available for the site collection).
At this point, you’re probably wondering why SharePoint doesn’t use this feature by default. If it’s
that easy, how come all the default pages don’t use it?
The answer is simple: making this change to the code on the page detaches the page from the site
definition. As with other advanced editing done by SharePoint Designer (see the section “SharePoint
Designer Settings”), this means the page is now unique and is no longer using the site definition. It
would therefore be untouched if you made any upgrades, updates, or overall site changes. Because
contextual help requires pages to be detached from the site definitions, it’s usually not a good idea
unless you’re already planning on doing major customization (despite being really tempting). And
that is why even Microsoft doesn’t use contextual help on SharePoint’s pages.
Configuring Site Collections
You can make several changes to a site collection to customize how it behaves and what is
permitted. These configuration changes can all be done through Central Administration, under
Application Management. Just as with the site collection settings, these changes affect the entire
site collection and can vary between site collections. As is the case with most of what you do in
Central Administration, you can use PowerShell or STSADM to do them instead. However, for a
convenient idea of how something is done and what settings are required, Central Administration
is a great place to start. For more about PowerShell and STSADM, see Chapter 14.