Live data from Hacker News

Next Gen Static Blogging

inoads.com

31–40 of 179 posts

Re: Next Gen Static Blogging

#31
post #21

Earlier quoted context omitted.

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.

Sure, I can type " Look, I don't hate hand-written HTML. I actually like it better than Markdown.

What about Enter, Enter to get

|

Re: Next Gen Static Blogging

#32

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?

[deleted]

Re: Next Gen Static Blogging

#33
post #10

Agree that static blogging is nice, but I think this specific look needs some tweaking - for example, there's too low contrast in color between the links and the background at https://inoads.com/blog

Thanks for the feedback. The colour scheme uses https://ethanschoonover.com/solarized/ as a foundation. This is how I have all my editors / IDEs set. I'll look at implementing this next: https://developer.mozilla.org/en-US/docs/Web/CSS/Media_Queri...

Re: Next Gen Static Blogging

#34
If the only thing being removed were tags, which don't have structural or semantic meaning, it would probably be just as easy to parse for screen readers and robots.

Two problems I see:

1. Where you have a heading you may want it and its associated content wrapped in a . Where you have a separated paragraph you really do probably want a

.

So these newlines aren't always just replacing s. The page has no structure except what can be derived from headings.

2. Wrapping everything in a tag seems like it could cause issues. It would probably be better to use and apply the clever one line of CSS mentioned in the post.

Re: Next Gen Static Blogging

#35
post #28
post #10

Agree that static blogging is nice, but I think this specific look needs some tweaking - for example, there's too low contrast in color between the links and the background at https://inoads.com/blog

I had to copy all the text out into a text editor to be able to read the article, not just the links. Contrast is out of vogue I guess.

I don’t understand the current fashion of making everything off-gray on off-gray. I guess it keeps designers employed.

Re: Next Gen Static Blogging

#36
it's like a, messy, non-standard semantic web... at this point, and i'm totally serious, why not starting again to work on XHTML 2.0 standard? We need it badly.

Re: Next Gen Static Blogging

#38
post #27

Cool. Go one step further and render the CSS inline. Of late, I have been writing with just MarkDown and dropping in some of the simplest tool (Pandoc, Jekyll) possible to render as HTML.

Here's some crazyness: https://dataswamp.org/~solene/2019-08-26-minimal-markdown.ht... I suppose it is not much hard to translate this into PHP...

I built mawkdown[0] off of solene's initial awk implementation!

[0]: https://github.com/icyphox/mawkdown

Re: Next Gen Static Blogging

#39
post #31
post #21

Earlier quoted context omitted.

Sure, I can type " Look, I don't hate hand-written HTML. I actually like it better than Markdown.

What about Enter, Enter to get |

I'm not interested in you selling me an editor or IDE.

And I have zero idea why you all insist that I must love writing HTML.

Leave me alone!

Re: Next Gen Static Blogging

#40
> No need for JavaScript or any other complicated backend or client-side frameworks. I can use PHP to introduce dynamic elements to the page, but that's optional.

This isn't the same "dynamic" - the author must know that JS can provide interaction without a page refresh; PHP (alone) cannot.

Post reply on HN