<gtirl...@ocadu.ca><mailto:gtirl...@ocadu.ca>, Fluid Work
<fluid-w...@fluidproject.org><mailto:fluid-w...@fluidproject.org>
Subject: Re: Moving away from Markdown to straight HTML for Inclusive Design
Guide site
Gio, I think your personal narrative of the process as "
Gio, I think your personal narrative of the process as "the least trained
for these things" is actually a very good example of how we should
approach these design challenges, and a reminder to be wary of what is
colloquially termed the "expert blind spot".
For me, that raises this question: does
These points are important - my own sense (not validated by research) is that
Markdown is primarily of value to those who already know HTML and can use the
Markdown syntax as a shorthand. Dana’s experience validates some of that.
I think there may be at least two separate threads of discussion
Hi All,
I can contribute my experience of being a fairly new user of both Markdown and
HTML. When I started working on the Guide, I had some experience with HTML, and
very little with Markdown. I found that I was having to learn both as we went
along for the reasons Jon pointed out - that
rk <fluid-w...@fluidproject.org><mailto:fluid-w...@fluidproject.org>
Subject: Re: Moving away from Markdown to straight HTML for Inclusive Design
Guide site
Hi, Jonathan:
I agree with a lot of Alan's points, moving to pure HTML seems like a step we
should only consider once we ha
><mailto:fluid-w...@fluidproject.org>
Subject: Re: Moving away from Markdown to straight HTML for Inclusive Design
Guide site
Hi, Jonathan:
I agree with a lot of Alan's points, moving to pure HTML seems like a step we
should only consider once we have reasonably exhausted the remaining
gt;<mailto:t...@raisingthefloor.org>
Date: October 6, 2016 at 8:05:18 AM
To: Hung, Jonathan <jh...@ocadu.ca><mailto:jh...@ocadu.ca>
Cc: Fluid Work <fluid-w...@fluidproject.org><mailto:fluid-w...@fluidproject.org>
Subject: Re: Moving away from Markdown to straight HTML for
Hi, Jonathan:
I agree with a lot of Alan's points, moving to pure HTML seems like a step
we should only consider once we have reasonably exhausted the remaining
options. Thankfully, I can already think of a few options off the top of
my head that would get us back to more pure markdown.
Let's
