On Mon, Mar 12, 2012 at 4:48 PM, Bill Burdick <[email protected]>wrote:
> Hey, looks pretty slick, dude! Probably if I change the Markdown thing to > use the JSON API, it'll be a lot faster for Markdown wikis. That's the great part of this approach: you can use the JSON API to store/fetch raw (unparsed) wiki content (which may be markdown) and render it client-side. The only real work there is transforming the markdown-generated output to intercept wiki-internal links such that they integrate with the local app. With that, you can use fossil as a back-end for a dedicated wiki site (not exposing the SCM itself). If you want to take that a step further... you could store JSON objects as wiki pages, where each object represents a page, containing the content and some metadata (e.g. contentType, so that we can use multiple formats at once). Rendering then becomes: a) find the renderer/converter suitable for page.contentType, b) pass the page to the renderer, c) manipulate the output (if desired) to fix intra-wiki links to integrate into the local app. That's how i do it in my custom wiki back-end, but now that this proof-of-concept is done i'd like to port my custom app to use the fossil backend (because i get versioning and compression, two features my app doesn't have). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
