On Sun, Mar 17, 2013 at 8:21 AM, Tong Sun <[email protected]> wrote:

>
> On Mon, Mar 11, 2013 at 11:12 PM, Dan Allen <[email protected]> wrote:
>
>> Yep. I just posted some information +today to the Awestruct list with a
>> link to a prototype:
>>
>>
>> http://talk-archive.awestruct.org/A-preview-of-the-new-AsciiDoc-integration-td159.html
>>
>
> Thanks Dan,
>
> I took a look, and found that the solution is a bit heavy for personal
> use. Awestruct is, as I just learned, a static site generation tool. I.e.,
> it's more a enterprise level solution, whereas all I want to is to post my
> blog to some exiting blog sites.
>

I wouldn't describe it as an enterprise-level solution, but I do agree that
Awestruct is focused on creating full sites. Enterprise would imply running
on an application server, when all Awestruct does is generate a static HTML
website that can be hosted on any web server.


>
> I think I'll stick to WordPress and blogpost for the moment.
> Hope your team can implement blogpost alike for asciidoctor.
>

Personally, Awestruct (or something like it, like Jekyll), suits my needs.
But if someone wanted to step forward to develop a blog posting tool, I
would recommend creating one that works with any generated HTML output. I
don't see why the posting tool has to be coupled with the tool that
generates the HTML. In fact, it wouldn't be too difficult to rework
blogpost so that it delegated HTML generation to an external tool (in this
case asciidoctor).

-Dan

-- 
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://google.com/profiles/dan.j.allen
http://mojavelinux.com
http://mojavelinux.com/seaminaction

-- 
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/asciidoc?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to