This is an idea of JasonDossett's and MattWright's.

Basically the idea is to provide deep integration between FlexWiki 's wiki engine and SharePoint.

This might include:

• Changing the backend to use SharePoint lists instead of flat files
• Interesting idea! How would perf be? Could be implemented as a kind of AbstractContentBase -- DavidOrnstein
• Modifying the web app front end to look and feel like SharePoint and live in the SharePoint layouts directory
• Should this be a built in type (by modifying the xml template files in the _layouts directory) or a template file? Using a template file allows more people to use it since sharepoint users don't always have access to the layouts directory
• Create a custom content template like Document Library or List so that Wiki's could be added to a site as a first class citizen
• Create a Special WebPart for Displaying Documents in a Wiki Document Library.
• What would happen if I clicked on a link? Open in a new page? Use IFrame and open in the WebPart? or act as a link?
• Adding custom tags specific to SharePoint to allow things like inline discussions, links to SharePoint contentm etc.
• I was also thinking that maybe this should be a Site Template. It would show up in the Site Template list alongside: Team, Empty, MeetingWorkplace, etc.
• Provides for a entire site template to be provided, allowing for a more "wiki"ish presentation.

• More Random OneNote, SharePoint, Wiki Thoughts - http://www.greghughes.net/rant/CommentView,guid,c6591f8f-d9e8-4478-89ac-5a71334f54bd.aspx

Comment

We're using FlexWiki heavily within Sharepoint 01, and it's fantastic. It's the center of the window, and basically the center of our universe. I did move everything to the right border. Only request I have for now is that in Edit mode, the right pane (Save/Login) take up as little space as possible - on long page names, it can grab over half the real estate of a web part. Even if it means breaking up page names... they're non-clickable anyway. Otherwise, BRAVO!! ChristopherGaltenberg