| | 6 | |
| | 7 | The aim is to embed one or multiple doxygen-generated documentation(s) within Trac, |
| | 8 | in order to have consistent look and feel, and easy referencing to doxygen pages |
| | 9 | using the usual TracLinks and the `doxygen:` prefix. |
| | 10 | |
| | 11 | The doxygen plugin provides a new main navigation tab (named ''Doxygen'' by default), |
| | 12 | which will present an index page. |
| | 13 | If you have to present only one documentation project, that index page can directly |
| | 14 | be a Doxygen-generated page, like the index.html, main.html (default) or hierarchy.html. |
| | 15 | An alternative is to pick a Wiki page to use as the index, and this is indeed the best |
| | 16 | option if you have multiple documentation projects to serve. That way you can build |
| | 17 | your own ''meta'' index the way you want, using `doxygen:...` links within that page. |
| | 18 | |
| | 19 | Configuring the Doxygen plugin should be easy if you have only one Doxygen generated |
| | 20 | documentation to wrap, and a bit more involved if you have many --but the goal is to |
| | 21 | have a great deal of flexibility, in the latter case. |
