Hello.  

I'd just like to say thanks to Stuart and the AsciiDoc community.  I have been 
an AsciiDoc user for several years and I have always found AsciiDoc to be a 
great fit for my documentation needs.

I'd also like to share a prototype that permits one to use AsciiDoc for Erlang 
program documentation 
(http://www.erlang.org/doc/apps/edoc/chapter.html#Introduction).  This 
prototype permits an Erlang program's documentation to be written in AsciiDoc 
format rather than XHMTL and/or edoc's wiki notation.  This prototype can be 
found on GitHub (https://github.com/norton/asciiedoc). 

Thanks again for the great tool.

cheers,

Joe N.

On Dec 5, 2012, at 10:26 AM, Stuart Rackham <[email protected]> wrote:

> Hi Dan
> 
> On 04/12/12 11:19, Dan Allen wrote:
>> Stuart and the AsciiDoc community,
>> 
>> I'm a big fan of AsciiDoc (thanks to Matthew McCullough for turning me
>> on to it). I'm interested in continuing to promote it with the goal of
>> improving documentation (software or otherwise) across the globe.
>> 
>> I recently gave a presentation on AsciiDoc [1] (composed from AsciiDoc)
>> at RWX 2012 which I'd like to share. It's rendered using dzslides, an
>> awesome HTML5-based presentation framework. I developed a custom backend
>> to AsciiDoc to generate the HTML5 and linked assets that dzslides
>> requires [2].
>> 
>> I plan to keep this talk in my repertoire for the 2013 conference season.
>> 
>> ...on to my main point:
>> 
>> Since I anticipate a groundswell of adoption for AsciiDoc in the near
>> future (or at least I hope so), I reserved the domain names asciidoc.org
>> and asciidoc.info in order to donate them to project. The motivation for
>> reserving the domains was two-fold. First, to prevent the domains from
>> being snatched up and used for an unrelated purpose and, second, to make
>> it easier for people to find the project page (methods.co.nz is sort of
>> hard to remember ;))
>> 
>> For now, I have setup a 301 redirect on each domain to point them to the
>> current AsciiDoc project page.
>> 
>> I'm happy to manage the domains on behalf of the project, which Stuart
>> is in support of. If you have other ideas about how to manage the
>> domains as a group, I'm certainly open to handling them another way.
>> Feedback welcome.
> 
> Thank you for this generous offer, I'd love to move AsciiDoc to it's own
> domain, it's been hanging off my site to long -- just a time and
> resources issue on my part. It's well past time AsciiDoc had it's own
> domain.
> 
> I would prefer someone else/others to manage the domains, Dan's the
> obvious choice, but this is something the community needs to address (I
> don't know how this sort of stuff is done, but we don't want to lose
> control the domain names in the future).
> 
> I'm stretched to thin to take anything else on at the moment (I've been
> AWOL from the discussion list for a while now, but will get back to it
> hopefully soon :-)
> 
> To get the ball rolling I can change the docs and the website content to
> point to asciidoc.org. Longer term I'd like to offload the website
> administration to others -- shouldn't be to onerous the website itself
> is in the repo and the AsciiDoc AAP build scripts rebuild and upload the
> website.
> 
> 
> Cheers, Stuart
> 
> PS: If you haven't already done so take a look at Dan's slide-show, I
> think you'll be impressed.
> 
>> 
>> I'm honored to be a part of the vision to transform documentation. We
>> constantly hear that documentation is weakest leg of software--open
>> source software in particular. There's no shortage of passion in many of
>> the projects, which points to the fact that a *huge* barrier must exist
>> that prevents documentation from being written. AsciiDoc has proven to
>> allow the gates in your mind to open and the words pour into the editor.
>> 
>> It quickly became apparent to me that the value in AsciiDoc was more
>> than just a terse syntax, but the capability to preserve the semantics
>> of the document (and to promote DRY). Before using AsciiDoc, I used
>> Textile and Markdown extensively and that's how I was able to recognize
>> that AsciiDoc stood out. It's time to drop the angled brackets, but in
>> doing so we don't want to lose the semantics. AsciiDoc strikes that balance.
>> 
>> Cheers,
>> 
>> Dan Allen
>> http://google.com/profiles/dan.j.allen
>> 
>> [1] http://mojavelinux.github.com/decks/asciidoc-with-pleasure
>> <http://mojavelinux.github.com/decks/asciidoc-with-pleasure/>
>> [2] https://github.com/mojavelinux/asciidoc-dzslides-backend
>> 
>> -- 
>> You received this message because you are subscribed to the Google
>> Groups "asciidoc" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/asciidoc/-/XC0g4XEIkCEJ.
>> 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.
> 
> -- 
> 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.
> 

-- 
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.

Reply via email to