Zaak <[email protected]> writes: > On Apr 26, 9:39 am, Phillip Lord <[email protected]> wrote: >> I maintain a number of blogs using Make, blogpost and asciidoc. One of >> the advantage of this is that I can edit the source anytime, then update >> wordpress (which I happen to be using) anytime. >> >> I hadn't thought of doing this with a distributed versioning backend, >> but it should be easy enough to do; it's the approach that iki-wiki >> takes for instance -- just run make everytime there is a commit. >> >> This works well for me; for the content, I use asciidoc. For everything >> else (RSS, tag clouds and the like), I use wordpress. Of course, there >> are some rough edges, but it saves me the effort of writing lots of >> content management presentation code, which is what I used to do. >> >> Phil >> > > > Exactly. I was also wondering if the community at large or our BDFL, > Stuart had any interest in an asciidoc-specific wiki, implemented with > asciidoc. I noticed that the web page is growing quite a bit, and it > might ease the load of keeping content up to date, and publishing user > submitted content if there were a crowd-sourced solution. Just wanted > to test the waters and see what people thought of this.
Speaking for myself, a wiki no, but a content system maybe. Phil -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
