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 burtoogle <[email protected]> writes: > It works very well. When someone pushes to the central repo, the > script reformats the stuff that has changed and the result is > immediately visible in the html output. > > I would like to be able to share the script with you but, > unfortunately, it's > owned by my client so I can't do that but I will describe it it in > more detail if > you have any questions. > > Cheers, > > Mark > > On Apr 23, 5:12 pm, Zaak <[email protected]> wrote: >> While this mailing list is great, I had an idea the other day and I >> was wondering if there was any interest in it, and need to develop the >> idea further. After starting to implement a GTD work-flow with org- >> mode for Emacs, I came across worg (http://orgmode.org/worg/). Worg >> essentially combines git with org-mode publishing to create a wiki- >> like website whose content is user editable. I was thinking that a >> similar implementation for ascii-doc would be really neat. Also, it >> would give ascii-doc users a chance to contribute how-to articles and >> faqs. >> >> The idea is essentially this: Put a set of asciidoc source files under >> revision control using a distributed system like git or mercurial. >> Have some post-comit hook which will build (using asciidoc) the >> modified pages and post them to the web. This will create a wiki of >> sorts written natively in asciidoc. >> >> As I said, I need to develop this idea further, as I am not sure where >> to host the source code and corresponding website. Github? >> Sharesource? other? >> >> I think adding official or unofficial wiki functionality would be >> great for the asciidoc user community. >> >> -Zaak >> >> -- >> 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 >> athttp://groups.google.com/group/asciidoc?hl=en. -- Phillip Lord, Phone: +44 (0) 191 222 7827 Lecturer in Bioinformatics, Email: [email protected] School of Computing Science, http://homepages.cs.ncl.ac.uk/phillip.lord Room 914 Claremont Tower, skype: russet_apples Newcastle University, msn: [email protected] NE1 7RU -- 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.
