{"id":517,"date":"2009-06-11T20:57:00","date_gmt":"2009-06-11T20:57:00","guid":{"rendered":"https:\/\/brainlitter.itgroove.net\/2009\/06\/11\/how-to-implement-your-custom-business-templates-in-your-sharepoint-departmental-document-libraries\/"},"modified":"2009-06-11T20:57:00","modified_gmt":"2009-06-11T20:57:00","slug":"how-to-implement-your-custom-business-templates-in-your-sharepoint-departmental-document-libraries","status":"publish","type":"post","link":"https:\/\/regroove.ca\/brainlitter\/2009\/06\/11\/how-to-implement-your-custom-business-templates-in-your-sharepoint-departmental-document-libraries\/","title":{"rendered":"How to implement your custom Business Templates in your SharePoint Departmental Document Libraries"},"content":{"rendered":"
\n

As this is a frequently asked SharePoint question I get, I’m going to try and answer it as succinctly as possible. And as I’m a fan of screenshots (a picture is worth a 1000 words as they say<\/em>), I’m going to use them as much as possible, to limit how much I have to type. \ud83d\ude42 <\/p>\n

\u00a0<\/p>\n

Business Requirement <\/h1>\n

Your business needs to configure a document library to use your standard company templates, to create new documents such as Formal Letterhead, Fax Cover Sheets and other ‘pre-baked’ templates. <\/p>\n

\u00a0<\/p>\n

The Solution \u2013 Apply Custom Content Types to a Document Library <\/h1>\n

\u00a0<\/p>\n

There are a couple of steps necessary, to make this happen: <\/p>\n

\u00a0<\/p>\n

Note that I’m not going to cover customized views or adding metadata (columns) to either the document library or to the Content Types themselves, however, you should note that you can do so much more, to customize your document library and extend it with Content Types, than simply specifying a template to use. And there are several ways to skin this particular cat, but I’m going to provide the quick and dirty approach so you can get back to whatever else you may need to get done. <\/em><\/span><\/p>\n

<\/em><\/span>\u00a0<\/p>\n

    \n
  1. Give some thought to *where* these templates are going. Are you about to place them in the appropriate site and\/or document library? Have you planned this out effectively? Do you need to reuse this template in another site (this would also establish what site you create the content type in; the root, a top level site or just within a single sub site) <\/li>\n
  2. Establish\/Prepare your Document Templates and tuck them in a folder somewhere, ready for upload to your site as the base templates (Leave them in their standard file types, such as a Word .DOC file – they don’t need to be .DOT template files like they would if they were launched in Word). Better still (and too many steps to cover here), store them in a dedicated ‘Document Template Library) and then link to the URL’s, instead of uploading them <\/li>\n
  3. Create your Content Types within the site they will be used, or in the site above (perhaps the top level site collection, if you want to ‘reuse’ the content types in sub sites) <\/li>\n
  4. Configure your document library to ‘manage content types’ <\/li>\n
  5. Plug in (add) your content types <\/li>\n<\/ol>\n

    \u00a0<\/p>\n

    That’s it. Now, for the walkthrough version of the answer\u2026 <\/em><\/strong><\/p>\n

    \u00a0<\/p>\n

    Here’s the final result when done <\/h1>\n

    Why not start with the end result, to help clarify what we are intending to accomplish\/build here. <\/p>\n

    \u00a0<\/p>\n

    \"\" <\/p>\n

    There it is. With some immediate business benefits, including: <\/p>\n