We also have our own filter to include code snippets: https://github.com/neo4j/server/tree/master/manual/src/bin/resources/... The syntax we use may look strange, but it's very readable. The filter is tailored for our build setup, but it shouldn't be hard to change it to fit other cases.
We want to keep documentation and code close to each other, so each project has it's own documents, and that gets pulled together by the Maven build tool and pushed onto some scripting that executes asciidoc/a2x.
Very impressive, it amazes me what people get up to with AsciiDoc.
> We also have our own filter to include code snippets: > https://github.com/neo4j/server/tree/master/manual/src/bin/resources/... > The syntax we use may look strange, but it's very readable. The filter is > tailored for our build setup, but it shouldn't be hard to change it to fit other > cases.
It's a nice solution to your snippet problem, can it be installed using the new Filter Plugins mechanism (http://www.methods.co.nz/asciidoc/filters.html)? I'm certain that a lot of other users would be interested in using it.
> We want to keep documentation and code close to each other, so each project has > it's own documents, and that gets pulled together by the Maven build tool and > pushed onto some scripting that executes asciidoc/a2x.
>> The syntax we use may look strange, but it's very readable. The filter is >> tailored for our build setup, but it shouldn't be hard to change it to >> fit other >> cases.
> It's a nice solution to your snippet problem, can it be installed using > the new Filter Plugins mechanism > (http://www.methods.co.nz/asciidoc/filters.html)? I'm certain that a lot > of other users would be interested in using it.
At the moment we're under too heavy load to fix this (and even to upgrade to the new AsciiDoc version) but maybe we'll get around doing that eventually. Inbetween the code is open source so anyone who's more into the details regarding AsciiDoc can have a look at it :-)
> I've added it the list on the AsciiDoc home page -- let me know if it > needs editing.
Looks perfect to me.
>> BTW, we're still on version 8.6.3 - I hope to upgrade in a couple of >> weeks. So I >> haven't looked into how filters are handled in 8.6.4 yet.