This is the home page and table of content for people modifying FlexWiki as well as building software to work with it. Before digging in here, you should already be pretty familiar with the UserGuide and the AdministratorGuide.

If you are just now considering becoming a developer for FlexWiki, you should seriously consider reading DeveloperHome before going any further. It's designed to walk you through what you need to know early on -- especially in terms of project processes.

Below is an automatically generated list of developer-guide topics, organized by section...

Introduction

• FlexWikiBasics - Basic concepts of FlexWiki
• FlexWikiTerminology - Provides an overview of basic FlexWiki terms like Topic, Namespace and Federation.

Getting Started

• BuildSystem - Describes that automated build system that FlexWiki uses.
• DeveloperSetup - How to get set up to do development work on FlexWiki on your machine
• FlexWikiCore - This is the main FlexWiki engine and associated tools.
• UnderstandingSubversion - What you need to know about Subversion.

Developer Processes

• BecomingAContributor - What do you need to do to be able to checkin changes to FlexWiki?
• BecomingACoreDeveloper - How to become a CoreDeveloper
• NewDeveloperCheckinProcess - How NewDevelopers get their changes checked in
• SharedAssemblyInfo - Every project should include a link to the SharedAssemblyInfo.cs file in the solution folder.

Plugins

• HowToCreateAPlugIn - Information about how to create a PlugIn
• PlugInInstallation - How to install a PlugIn for FlexWiki
• PlugInOverview - Overview information about FlexWiki PlugIns for developers, users and administrators

Testing

• BuildVerificationTests - Automated tests that happen as part of every build that execute against a fully installed version of FlexWiki, allowing the build to verify correct operation in a web context.
• StandaloneTestingDetails - An overview of the different kinds of automated tests available for FlexWiki development.
• TestingFlexWiki - Testing of FlexWiki is done with two kinds of testing: standalone and interactive.

Tools