| 34 | Trac Wiki allows the use of macros to help with common needs like |
| 35 | a TOC or the insertion of a n image. They work similarly to Quickbook |
| 36 | templates. |
| 37 | There are only a bunch of them in the official Trac release, and it |
| 38 | will be very helpful to have a set of boost specific macros that makes |
| 39 | common things like referring to a particular section of boost docs |
| 40 | very easy. Something like: |
| 41 | |
| 42 | {{{ |
| 43 | [[BoostDocSection(regex,introduction)]] |
| 44 | }}} |
| 45 | |
| 46 | === Objectives === |
| 47 | |
| 48 | * Investigate current official [WikiMacros Macros] |
| 49 | and [http://trac.edgewall.org/wiki/MacroBazaar not so official macros] |
| 50 | to look for the things we may find useful ( See |
| 51 | [http://trac.edgewall.org/wiki/MacroBazaar#Includes Includes], |
| 52 | [http://trac.edgewall.org/wiki/MacroBazaar#LastModified Last Modified], |
| 53 | [http://trac.edgewall.org/wiki/MacroBazaar#AddComment Add comment], |
| 54 | [http://trac.edgewall.org/wiki/MacroBazaar#FootNote footnote], |
| 55 | [http://trac.edgewall.org/wiki/MacroBazaar#RSSget rss get] and |
| 56 | [http://trac.edgewall.org/wiki/MacroBazaar#VisitCounter visit counter] for some |
| 57 | examples). |
| 58 | |
| 59 | * Write a not too clutter proposal for new Boost specific WikiMacros, |
| 60 | including the rationale behind each decision. |
| 61 | |
| 62 | * [WikiMacros#DevelopingCustomMacros Implement the Macros] specified in the proposal. |
| 63 | Luckily Trac uses Python for this! |