I need to create a repository of system documentation in Sharepoint. The intended audience need quick and easy access to the documentation (= searchable), and must also be able to navigate easily between different parts (= hyperlinks). It also needs to be fairly easy to manage for the content editors, but this is of less importance.
The documentation will consist of:
- Rich text (large bodies of texts)
- Tables (property lists)
- Graphics (photographs and drawings)
Using the Sharepoint wiki functionality seems promising, but I have heard that there are issues with e.g. managing images. However, I think that it will be manageable.
Based on my lacking experience, I would create the following:
- One wiki library for end-users. This would contain all of the rich text, tables, and references to images.
- One asset library for content editors. This would contain all of the images, master documents (such as Visio files) and other documents not suitable for converting to wiki pages.
Is this a sane setup? Or am I Doing It Wrong? :-)