AsciiDoctor v FrameMaker - our experience

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

AsciiDoctor v FrameMaker - our experience

wolandscat
For those interested here is a blog post I made on Asciidoctor and our previous tool, FrameMaker. - thomas beale
Reply | Threaded
Open this post in threaded view
|

Re: AsciiDoctor v FrameMaker - our experience

LightGuardjp
Thanks for the write up and the criticism! I'm also glad you're sticking with us :)

On Monday, September 21, 2015, wolandscat [via Asciidoctor :: Discussion] <[hidden email]> wrote:
For those interested here is a blog post I made on Asciidoctor and our previous tool, FrameMaker. - thomas beale


If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/AsciiDoctor-v-FrameMaker-our-experience-tp3741.html
To start a new topic under Asciidoctor :: Discussion, email <a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;ml-node%2Bs49171n1h37@n6.nabble.com&#39;);" target="_blank">ml-node+s49171n1h37@...
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML


--
Sent from Gmail Mobile
Reply | Threaded
Open this post in threaded view
|

Re: AsciiDoctor v FrameMaker - our experience

wolandscat
There will be more in the future. The community is one of the best I have come across, and I have to say that the technical understanding of publishing details by Dan and others is first rate - I never expected a markdown based technology to be doing that.

At this point I think Adobe and MadCap should start worrying for the future of some of their tools ;-)

Since our work is for an open-source non-profit (openEHR.org), all the documents and related Git projects are in the open, so anyone who wants to use them as some kind of reference is welcome to do that (links on the blog post).

One day we might get into helping with development, but for now I think we can still add value by 'testing to death' everything that comes out.

Onward...
Reply | Threaded
Open this post in threaded view
|

Re: AsciiDoctor v FrameMaker - our experience

mojavelinux
Administrator

The community is one of the best I have come across

Thanks Thomas! It means so much to me and to the community to hear you say that. First and foremost, I want people to enjoy working on these problems together and I want the community to succeed because we are.
 
I have to say that the technical understanding of publishing details by Dan and others is first rate - I never expected a markdown based technology to be doing that.

The first thought that comes to mind when you say that is, "wow, I still have so much to learn about publishing." But I'm committed to learning it because I know that it is this understanding that is going to steer us towards the ultimate goal, which is to create the most efficient way to store content in both a semantic *and* human friendly way, and publish everywhere!
 

I think we can still add value by 'testing to death' everything that comes out.

That's tremendously helpful. But don't forget about your design input. That has been, and continues to be, extremely valuable as well.

We have some big challenges for 1.6.0 and beyond, and I'm excited to evolve the syntax so that it can handle ever more mature use cases with elegance and grace.

Thanks for your article (and design input). I've linked it on the new brainstorming page for tooling. See https://github.com/asciidoctor/asciidoctor/wiki/AsciiDoc-Tooling:-Requirements-and-Ideas

Cheers,

-Dan

--
Dan Allen | @mojavelinux | http://google.com/profiles/dan.j.allen
Reply | Threaded
Open this post in threaded view
|

Re: AsciiDoctor v FrameMaker - our experience

mojavelinux
Administrator
In reply to this post by wolandscat
>  the latest version (12) doesn’t even display properly on a modern hi-res laptop screen (Dell XPS)

I hate this problem with a passion. Mostly because the next day I wake up with a stiff neck from trying to lean into the monitor to read the text. I can't believe that applications weren't prepared for the inevitable appearance of HiDPI screens.

-Dan

--
Dan Allen | @mojavelinux | http://google.com/profiles/dan.j.allen
Reply | Threaded
Open this post in threaded view
|

Re: AsciiDoctor v FrameMaker - our experience

mojavelinux
Administrator
In reply to this post by wolandscat
> The real power of Asciidoctor is that it supports the integration of multiple sources of content into multiple publishing targets.

I like how you phrased that. We're always looking for how to explain the benefits of AsciiDoc and Asciidoctor and I think you've hit upon something that we've been glossing over. Thanks!

-Dan

On Mon, Sep 21, 2015 at 1:30 AM, wolandscat [via Asciidoctor :: Discussion] <[hidden email]> wrote:
For those interested here is a blog post I made on Asciidoctor and our previous tool, FrameMaker. - thomas beale


If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/AsciiDoctor-v-FrameMaker-our-experience-tp3741.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Dan Allen | @mojavelinux | http://google.com/profiles/dan.j.allen
Reply | Threaded
Open this post in threaded view
|

Re: AsciiDoctor v FrameMaker - our experience

mojavelinux
Administrator
In reply to this post by wolandscat
After reviewing your blog post, I realize that the claim "as easy as writing an e-mail" is an incomplete thought. Here's what I actually mean by that (drawing some on your comment).

Writing should start off as easy as writing an e-mail reply, but taking that approach should not sacrifice the ability down the road to integrate multiple sources of content and publish to multiple targets.

Obviously, the final document is going to have much more complicated markup, but that markup should still be strictly semantic, cleanly (or as cleanly as possible) separating semantic content from presentation.

-Dan

On Wed, Dec 9, 2015 at 4:25 PM, Dan Allen <[hidden email]> wrote:
> The real power of Asciidoctor is that it supports the integration of multiple sources of content into multiple publishing targets.

I like how you phrased that. We're always looking for how to explain the benefits of AsciiDoc and Asciidoctor and I think you've hit upon something that we've been glossing over. Thanks!

-Dan

On Mon, Sep 21, 2015 at 1:30 AM, wolandscat [via Asciidoctor :: Discussion] <[hidden email]> wrote:
For those interested here is a blog post I made on Asciidoctor and our previous tool, FrameMaker. - thomas beale


If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/AsciiDoctor-v-FrameMaker-our-experience-tp3741.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Dan Allen | @mojavelinux | http://google.com/profiles/dan.j.allen



--
Dan Allen | @mojavelinux | http://google.com/profiles/dan.j.allen