TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: Markdown writers: plain text or WYSIWYG editor?
Subject:Re: Markdown writers: plain text or WYSIWYG editor? From:Joe Pairman <joepairman -at- gmail -dot- com> Date:Thu, 25 Oct 2018 09:37:56 +0200
At least half of lightweight markupâs appeal to writers is the unambiguous
storage of simple semantics.
With Word, a list is not a list and a heading is not a heading. There are
so many things you can do to mess those styles up.
Asciidoc, RST, and to some extent Markdown provide a clear way to specify
that a list is just a list; a heading just an h1, h2, or h3. But that
doesnât mean everyone wants to type out all those asterisks, dashes, and
hash symbols. Look at the popularity of all the Markdown tools that provide
keyboard shortcuts and semi-formatted views!
For my money, Dropbox Paper gets very close to perfection in terms of a
mass-market editor with unambiguous, unbreakable simple semantics and
really great UX. (It used to be a Medium copy but has now surpassed
Medium.) Not that Iâm recommending it as a tech docs tool, just an example
of a fantastic writing environment.
Joe
On Thu, Oct 25, 2018 at 02:50 Mark Giffin <mgiffin -at- earthlink -dot- net> wrote:
> I'm curious about writers who are working in Markdown or similar
> lightweight markup (asciidoc, restructuredtext etc etc).
>
> Do you work mostly in the raw text? Or do you use some kind of
> WYSYWIG-style graphical editor and stay away from the raw plain text
> syntax?
>
> Personally I would probably stick with the plain text.
>
> Mark Giffin
> Mark Giffin Consulting, Inc.
>http://markgiffin.com/
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Visit TechWhirl for the latest on content technology, content strategy and
> content development | https://techwhirl.com
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as joepairman -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com