EDIT: some wording changes.
Next Gen Static Blogging
11–20 of 179 posts
Re: Next Gen Static Blogging
#12It is a neat idea, but the purist in me misses those tags, even though they are the main reason why I don't like writing HTML by hand.
Re: Next Gen Static Blogging
#13It is a neat idea, but the purist in me misses those tags, even though they are the main reason why I don't like writing HTML by hand.
What about the standard ... ... tags?
But for every paragraph I write I need to type
(and maybe even
, if I choose to).That's exactly the use case for Markdown, to get rid of that tedious stuff.
Re: Next Gen Static Blogging
#14Re: Next Gen Static Blogging
#15Earlier quoted context omitted.
What about the standard ... ... tags?
What about them? They occur exactly once, and I probably have a prepared file with them already in it. But for every paragraph I write I need to type (and maybe even , if I choose to). That's exactly the use case for Markdown, to get rid of that tedious stuff.
Re: Next Gen Static Blogging
#16Html - structure of the document CSS - appearance JS - interactivity
I could be wrong, but that's how I remember it. Is there an advantage to moving away from this fairly simple and unambiguous paradigm?
Re: Next Gen Static Blogging
#17If I'm understanding correctly, here, the semantic value of the element is ignored to increase DX. I personally wouldn't make that compromise, why is pre-processing not simple enough?
Re: Next Gen Static Blogging
#18Of late, I have been writing with just MarkDown and dropping in some of the simplest tool (Pandoc, Jekyll) possible to render as HTML.
Re: Next Gen Static Blogging
#19Shameless plug, I created the NeatCSS framework to have this "simple" look and feel. On that, however, I didn't try to avoid your typical HTML code.