The document library is structured in a logical fashion for your authors. For example, your document library might be organized by enterprise module. However, your end users might find it easier to locate content stored by function or role (for example, sales order processing or sales clerk). The website view allows you to establish this user-friendly organization of content and addresses the question: "What's the best way for end users to locate on-the-job help?"
There are threetwo methods for creating a website hierarchy:
- Building the website via context assignment - This method allows you to manually populate the website by assigning context to document library content. This method is well-suited for a small end user population and a small number of documents.
- Building the website via dynamic website folders - This method automatically populates your website using properties stored in the document. By planning your hierarchy, and assigning values to properties within your template, you can manage a multi-dimensional website that updates based on your published or republished content. If you plan to include web and managed documents in your dynamic website folders, you can assign templates using the instructions found in Adding a Managed Document and Editing Properties and Adding a Web Document and Editing Properties. This method is well-suited for a larger end user community and a large number of documents.
- Building the website by duplicating the document library structure - This method automatically populates your website by duplicating the document library structure of an existing project.
If you are using optional group-based filtering, this option will affect the way content is displayed on the website. For more information on group-based filtering and working with groups, refer to Creating and Updating Groups.
To build the website view, you will be linking to content in the document library.