Here is a list of the various projects that we would like to develop for Confluence. A purpose of this page is to be a central location for brainstorming, so please add your ideas to the list. If you'd like, make your ideas link to their own page that discusses the idea in more depth.

List of Completed Project Ideas

Of course I welcome your suggestions for additional features for these projects. Several of these projects may have more advanced versions in the planning stages.

Amazon Web Services Plugin

Chat11 Custom Features

Amazon book linking macros

Random block include

Content refactoring

List of Inprogress Ideas

Must include plugin

Forces pages from one space to include pages from another space.

• Must Include Plugin

List of Future Project Ideas

Content Building

Encouraging the building of a variety of content within the Bobsgear wiki will help with generating traffic to test the various add-ins proposed in this project.
Attracting additional users to use this system will build up a base of users who can try out and test new features.

Email Verification of New Users

Users would be sent an email with a clickable link. Once that link is clicked, then their account is verified.

This is the kind of project that could be done with an external program. For example:

• New user registration screen is in external program
• New user entered and created in deactivated state in wiki.
• When email is verified, then the account is activated.
• Moderation could also happen before the account is activated.

Moderation of New User Creation

User accounts would be approved before creation. Either the system administrator would approve the user, or in the case of accounts created in association with a particular space, by the owner of that space.

This is the kind of project that could be done with an external program.

Moderation of New Wiki Space Creation

Wiki spaces would need to be approved before creation.

This project could be done with an external program. For example:

• New space registration screen goes to an external program.
• New space info is entered and the space is created, but it is made private.
• When space creation is verified by the moderator, then the space is given publicly accessible status.

Subdomain / Multi-domain support for Confluence

Confluence does not currently support the ability to serve content on multiple domains or subdomains.

Full implementation of this feature would probably require adding "multiple dashboard" support, so that a given domain, or group of domains, would only show the spaces of their associated subdomains.

This would enable Confluence to function as a wikifarm.

Space Cross Domain Syndicator

Display the content of a specific space on a domain different than the main Confluence installation. All editing, users accounts, etc., would happen on the main Confluence domain. This is a subset of the full multi-domain support.

The most important aspect of this would be to make links within the space to be local, while links to other spaces would be rendered as going direct to their syndicated domains, rather than the home wiki. So all the syndicated domains would have to be aware of other syndications.

Other features to include:

• Selective "nofollow"

Billing support

Billing support for Confluence includes a whole host of features:

• Metering the space usage of various spaces
• Limiting spaces to a certain amount of space usage (quota features)
  • Quota for attachments
• Billing to space owners
• Billing for user memberships
• Associating member signups with specific wiki spaces

Similiar in features to the control panels available for web hosting, such as Ensim, Control Panel, and others.

Atlassian prohibts the "sub-leasing" of a Confluence wiki isntallation. If a Confluence wiki installation is used in an incidental way to deliver content, and any charges to users are based on the access to the information, rather than because of being able to build their own wiki, then it is not a problem. These features could still be useful in an enterprise wiki situation where there are chargebacks to various departments based on their use of the wiki.

Usemod to Confluence converter

Closely associated with the chat11 markup to confluence converter necessary for conversion of the hivewiki to Confluence.

Chat11 Custom Features

Many custom features developed as part of the chat11 wiki system need to be ported to Confluence:

• Site templates?
• Photo gallery
• Time logging and billing system
• Book review wiki website maker, or Wiki Outline To Wiki Page Tree converter.

Hivewiki features

[RSS2WikiText] converter

[Metasearch2Wikitext] converter

Other interesting features

View raw wiki text of any page

Even without edit rights to the page.

Table tabulator

Tabulate the items in certain columns of a table.

Consecutive numbering macro

Could require multiple invocations of a macro to pass some kind of state between them. Some kind of state that is local to a particular rendering of a page, so that multiple simultaneous hits to a page wouldn't mix up their state info.
Use case:

• Leading column in a table to have a sequential number for all the rows.

Mass change utilities

• Mass deletion
• Mass reparent
  Selected items
• List of links
• All children of a page
• All unparented children

Truly Open Directory Project conversion

Conversion of various tools used in the development of http://www.askvino.com, a 4.5 million page wiki directory of the web. Later development will focus on a directory management layer on top of wiki.

Stability Add-ons

Watchdog

Need to be for both Linux and Windows. Automatically forces a restart of Confluence if it stops responding, or gets too slow.

NOTE: I am looking for a developer who will develop this from a specification to be provided.

Usage Rate Limiter

A layer that will watch for too frequent access to the system, and then block usage from IP addresses that are abusing the system.

NOTE: I am looking for a developer who will develop this from a specification to be provided.

API Guard

Limits access to the remote API. Scripts must first request permission to use the API, and then they will be watched to make sure they comply with certain limits on speed of access.

NOTE: I am looking for a developer who will develop this from a specification to be provided.

Porting Hivewiki Sites To Confluence

The wikifarm developed by Garnet Chaney at HiveWiki needs to be ported to Confluence. Of course this depends on the Subdomain / Multi-domain support, chat11 markup to confluence converter, and other Chat11 custom features.

Other Hivewiki custom features

Hivewiki Metasearch to Wiki Page

Hivewiki is the first wiki to support a metasearch to wiki page converter using [GetSearch] and [SearchList] post edit commands.

Related feature requests in Confluence Issue navigator

• Clean domain to space remapping
• Different domains running from same Confluence instance, but pointing to different spaces, or Virtual hosting

Discussion Forum Plugin

A wiki page could be used to store the posts to a forum thread. Various things would be needed to mimic forum functionality, while using the wiki pages as the database to store the threads. See http://jira.atlassian.com/browse/CONF-5595

Note that Atlassian currently uses the Jive Software forum software.

Better Email Box To Wiki Conversion

The current system for pulling email into Confluence does not allow the email to be edited. A better system would turn the emails into web pages, recognize threading to group related emails as parents / children, and make it easy for a moderator to clean up the threads at a later time.

Content posting delay

Allow a "Publish after" attribute of pages. Until the page publish date is reached, links to the article render as regular text.

• This could be done from the Confluence Republisher

See also:

• List of Implementation Methods
• Questions About How To Develop Confluence Add-ins Other Than Plugins
• Atlassian 2007 Codegeist Plugin Competition