That'd be sufficient in terms of making this have good functionality for standard Allura installs.
For SourceForge to continue to have a `[[download_button]]` in the default content of new wikis, though, we'd have to make the default wiki content configurable. An .ini setting might work but would be lengthy and cumbersome. An overridable template might be nice. Neighborhoods can have a "project template" specified for initial tool configuration and that includes support for `home_text` on a wiki, but then users can't choose their tools at all during project creation, so that's no good. Perhaps a new ticket for this :) --- ** [tickets:#6393] Allow plugins to register new markdown macros** **Status:** in-progress **Created:** Tue Jun 25, 2013 04:39 PM UTC by Tim Van Steenburgh **Last Updated:** Thu Jan 16, 2014 08:20 PM UTC **Owner:** Tim Van Steenburgh Right now all of our markdown macros are defined in Allura core, even those that are tool-specific. We should provide a way for plugins to register their own macros with the platform. --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
