Towards independence from a SQL database based design
|Reported by:||Owned by:|
This is a design suggestion / question.
Have looked a lot for tool that allow me to combine knowledge from wiki and code.
Have been using
Confluence for years and it is a great wiki but since removal of
WikiText based syntax I find hard to think about this interlinking.
Trac is unique due to its wiki centric design and has great support for both
Ideally it would be
Git based - some wikis are - so that I can use regular files to edit knowledge, version control changes and process the pages with things like
I understand that
Trac needs a database to provide for the ability to refactor/rename wiki pages while maintaining the interlinking.
My request is if it is somehow possible to export the wiki pages to external files (could be source controlled in Git) but/and still be able to "process" as if they were in the database.
For example I would like to generate a static website that looks just like the one served by the server but without the ability to edit.
Also, would like to use
Laika to process these exported pages because of its great way to customize
restructuredText (see http://planet42.github.io/Laika/extending-laika/extending-rst.html).
The gist of my ask, from a design standpoints, is for a way to abstract over the fact that pages are in the database and make it possible to work with them using the
Trac core code, even if they are on disk.
Maybe there is no actual change required to core code and there is already a way to use the core
Trac code/api somehow to generate such a static website and process externally?
Hope this is not too obscure. Please advise if and how I can clarify. Thanks Nick