Live data from Hacker News

Next Gen Static Blogging

inoads.com

11–20 of 179 posts

Re: Next Gen Static Blogging

#11
How well is this handled from the accessibility point of view? I imagine that wrapping text in consecutive “p” tags is semantically clearer, however on the other side it shouldn’t be too hard for any accessibility software to recognize this pattern described in the article.

EDIT: some wording changes.

Re: Next Gen Static Blogging

#13
post #12
post #2

It 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?

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

#14
post #12
post #2

It 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?

All of those tags are optional. It’s perfectly valid to omit them.

Re: Next Gen Static Blogging

#15
post #13
post #12

Earlier 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.

A lot of modern text editors will let you type 'p' and then tab and they will create the opening and closing tag for you.

Re: Next Gen Static Blogging

#16
A neat little css property aside, isn't the separation of concerns a cornerstone of web pages?

Html - 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

#17
post #6

If 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?

You could use instead (which I probably would). Jest tested it using dev tools, seems to work.

Re: Next Gen Static Blogging

#19
I ran to my desktop to load this up and have a look. I'm ALWAYS looking for a more simple blogging solution. I was hoping for mostly plain text plus an em tag here or there. It's a little more involved than that, but it's given me some ideas.

Shameless 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.

https://neat.joeldare.com

Re: Next Gen Static Blogging

#20
Interesting concept. This seems to simplify the writing part. What about the rest? Is the list of posts generated automatically (if so, how?), or does it require manual management? Do you need the code tag, or could it be something more semantically relevant, such as article?
Post reply on HN