how (or should) i create my own wiki capabilities

Question

i have an asp.net website and over time is been more and more of a data repository where i have numerous database tables and the site just ships out this data.

I am realizing that a WIKI might actually start to be a better model for what my website is turning into. or atleast parts of it as its really just adding and updating content that i am doing. here is my dilema:

There are certain parts of the site that do need to be non WIKI and fully customizable,etc. Should i go and build my own WIKI capapabilities into my website so i can make it part WIKI (embedded when i need it) and the rest regular asp.net. If the answer if yes, are there any tips or boiler plate code on how to build and host a WIKI

the alternative is to use an existing WIKI software. i have tried most of them and my issue is that i need to host it myself on windows and as mentioned above i want to have complete control and have just a simple WIKI page editable inside my site. i have tried using frames, etc to simulate this but it all seems kind of hacky.

Any advice on:

A. if you think i should build the WIKI part of my site below is there best practice, boiler plate code on how to do this quickly?

B. if you think i shouldn't go reinvent the wheel, is there any existing windows hosted software that i can embed in my site without losing any control.

Answer 1

Rolling your own is a waste of time unless you have some major change or addition to the functionality of a wiki not otherwise available in existing systems (and even then, it's often a waste of time to start over than to branch an existing setup).

I recommend using something like ScrewTurn, which is open-source and ASP.NET, which gives you a fully-functioning wiki with no development, as well as gives you as much control as necessary if you do need to make changes.

Answer 2

I would agree with Rex M. You don't need to start from scratch. Leverage an open source product that is already available and build on it (if you even need too).

The added benefit of that is from a collaborative perspective when you build some interesting functionality into your version of the software and then share that back with the community.

Chances are if you need to build something and find it useful that other folks somewhere have close to the same needs and would welcome your features and enhancements.

That's the beauty of open source.