views:

1091

answers:

5

I am looking to create an "Online Manual" site template in MOSS 2007, in order to create a number of sites that will hold static information on an array of topics.

-What site template should I use, I am currently thinking Publishing Site, but a Wiki might work?

-How should I show the navigation for the different "Chapters" (in the left side panel)? I could use the "Table of Contents" webpart, a custom view on a list, or something else.

-How should I store the created "Pages", 1 large Page Library, or separate Lists for each "Chapter"?

-Lastly, Should I just hard-code the navigation webpart to the master page so it appears on every page?

Thanks in advance for the help!

EDIT:
Thanks for the answer. My real issue is how I am going to create the left side navigation, to be shown on every page? It should be a Table of Contents type of view that has all of the pages grouped by chapters.

Thanks again!

+1  A: 

Keep the site as a publishing site template, as you will need to be able to publish pages. You can always add a wiki to the publishing site template if necessary.

A wiki is not appropriate for the static online manual contents as it is essentially a list that allows users to add/edit on the fly. The wiki could make sense as an adjunct to the manual allowing users to add supporting information.

The tricky part of a manual is the ordering of the pages, as at each stage you will need to have a next/back and a list of each page in the correct order.

We have created a custom navigation provider that generates information based on values within the pages. The pages weren't ordered however.

Storing the "Pages" in different lists is going to be more pain than pleasure unless you are dealing with more than 2000 pages per list..

Keep it as simple as possible I think.

Have a couple of page layouts, one for the "contents page" and one for a normal "page". Create a new content type for each of the layouts so you can store specific information on each page (e.g. the next/previous page url).

Nat
A: 

Must the site be in Sharepoint? There are a number of wiki engines/frameworks out there that are really great at this.

Ben Collins
Yup, has to be in SharePoint.
JWD
A: 

I'd think that a list view web part would be the way to go. Assuming your documents are sorted inside of chapters, you'd need to set the view type to recursive, and then group by the folder name (I think you can do that, don't have a SP installation accessible to me at the moment to verify).

Yuliy
A: 

I've built user guide using a Sharepoint wiki in the past with some success.

The left-hand navigation can be done by changing Sharepoint's standard left-hand menu to be a list of links to wiki pages. This is done by going to Site Settings -> Navigation (under Look and Feel) and changing the Navigation Editing and Sorting list. You could theoretically add every page there, but for readability I'd stick to only the chapter headings.

You can also change the site's permissions so that only you (or your documentation person) have permission to edit the pages.

Fuzzy Purple Monkey
+2  A: 

Thank you everyone for your help! I just wanted to let you know what I ended up doing to create the "Online Manual".

I created a custom

1) Master Page to allow for the desired 2-column layout.

2) Page Layout to persist the navigation control on all pages.

3) Document Library with "Chapter" and "Sort Order" custom columns

4) Web Part (in C#) that uses the object model to retrieve all pages from a document library and display them in a list grouped by "Chapter" and sorted by "Sort Order"

I used the Publishing site template to allow the contributors more freedom to create content.

Thanks again!

JWD