Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on RFC 7764 – Guidance on Markdown.
Instead of markdown we need something what I name as flat structural text format.
<text>Base level text</text> <text li="disk">Bulleted list item</text> <text li="numeric">Numeric list item</text> <text li="numeric" level=2>Another list item</text> ... <text>Inline <span bold>bold</span><span bold italic>bold and italic</span></text> ...
That 1:1 mapping is mission critical for human editing - our mental model of text is flat.
In fact that markdown is an attempt to provide such flat structural text representation. Ugly one we shall admit.
Microsoft Word, AFAIU, uses also flat DOM model internally, that's why its WYSIWYG is quite good.
HTML version 2 was last version that allowed unambiguous WYSIWYG editing of HTML. The one that had no idea of CSS.
[1] http://blocknote.net - WYSIWYG HTML editor that uses internal flat model.
That's very subjective and only in very simple cases. Like "markdown" version here, on HN.
Instead of markdown we need something what I name as flat structural text format.
In this case it will be trivial[1] to write WYSIWYG editor that has 1:1 mapping between markup and screen representation.That 1:1 mapping is mission critical for human editing - our mental model of text is flat.
In fact that markdown is an attempt to provide such flat structural text representation. Ugly one we shall admit.
Microsoft Word, AFAIU, uses also flat DOM model internally, that's why its WYSIWYG is quite good.
HTML version 2 was last version that allowed unambiguous WYSIWYG editing of HTML. The one that had no idea of CSS.
[1] http://blocknote.net - WYSIWYG HTML editor that uses internal flat model.