What I think is missing for static blogs are comments.
Next Gen Static Blogging
91–100 of 179 posts
Re: Next Gen Static Blogging
#92Earlier quoted context omitted.
To be fair, you did write your post in Latin: > Lorem ipsum dolor sit amet, consectetur adipiscing elit. > Duis id maximus tortor. Sed nisi ante, fermentum vel nunc > et, tincidunt sagittis magna. In ultrices commodo lacus, id > tristique ipsum euismod laoreet.
Hmm I always thought lorem ipsum was a text with letter usage histograms similar to English, without distracting the reader with meaning. I could have sworn I read that somewhere...
You are almost right: The distribution of letters and length of words is similar to that of the Latin language. But it is not Latin and the text does not make sense. It's gibberish.
Re: Next Gen Static Blogging
#93Earlier quoted context omitted.
> I'm ALWAYS looking for a more simple blogging solution. Why?
> Once you choose the technology that runs your blog, use it. Don’t replace it, ever. Never ever rewrite it.[1] [1] https://macwright.com/2019/02/06/how-to-blog.html
This is good advice, for anything that can be tinkered with. Just as applicable to setting up a window manager on Linux, for example. It's an amazing rabbit hole, but it can consume you.
Re: Next Gen Static Blogging
#94I'm glad I'm not so blind that I need a screenreader for this site, because @mmackh doesn't seem to have given any consideration to accessibility. https://wave.webaim.org/report#/https://inoads.com/articles/... If this is "next gen", I think I'll stick to using emmet-mode in Emacs to write raw HTML, templating with m4 macros, validating with tidy, and doing the build and deployment with a makefile.
I bet that blind people can't wait for next 'next-gen' static blogging:
html::after { content: "Welcome to my blog" }
Re: Next Gen Static Blogging
#95I'm glad I'm not so blind that I need a screenreader for this site, because @mmackh doesn't seem to have given any consideration to accessibility. https://wave.webaim.org/report#/https://inoads.com/articles/... If this is "next gen", I think I'll stick to using emmet-mode in Emacs to write raw HTML, templating with m4 macros, validating with tidy, and doing the build and deployment with a makefile.
I bet that blind people can't wait for next 'next-gen' static blogging: html::after { content: "Welcome to my blog" }
Whenever people do stuff like this, alternative text protocols like Gemini make more sense.
Re: Next Gen Static Blogging
#96What I think is missing for static blogs are comments.
I can't and won't speak for anybody else, but if I wanted to provide random strangers with a free soapbox I wouldn't bother with a static blog. I'd just fire up a new Fediverse instance.
IMO, there's no need for comments. If people can't either send you an email or quote your blog with a link in their own blog, then they probably don't have much of value to say.
Re: Next Gen Static Blogging
#97So I'm guessing this isn't accessible for screen readers?
Re: Next Gen Static Blogging
#98Earlier quoted context omitted.
Hmm I always thought lorem ipsum was a text with letter usage histograms similar to English, without distracting the reader with meaning. I could have sworn I read that somewhere...
You are almost right: The distribution of letters and length of words is similar to that of the Latin language. But it is not Latin and the text does not make sense. It's gibberish.
Those are Latin words, drawn from a Latin source.
“Pencil what comma building twenty section human fedora”
is English, even if it makes no sense.
Re: Next Gen Static Blogging
#99I'm glad I'm not so blind that I need a screenreader for this site, because @mmackh doesn't seem to have given any consideration to accessibility. https://wave.webaim.org/report#/https://inoads.com/articles/... If this is "next gen", I think I'll stick to using emmet-mode in Emacs to write raw HTML, templating with m4 macros, validating with tidy, and doing the build and deployment with a makefile.
I thought the crowd on HN was more technically versed than this post. This self-titled "next-gen" blogging solution disregards SEO and accessibility. Am I wrong?
Re: Next Gen Static Blogging
#100Note that closing tags are optional † , so one can be an HTML purist and still write a decent HTML document with a relatively clean markup like this: Lorem Ipsum Lorem Ipsum Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis id maximus tortor. Sed nisi ante, fermentum vel nunc et, tincidunt sagittis magna. In ultrices commodo lacus, id tristique ipsum euismod laoreet. Maecenas at neque posuere, aliquet era…
And since we’re talking about optional things:
(Note that I say HTML tags; on foreign elements—meaning inline SVG and MathML—trailing slashes do make tags self-closing, XML-style.)
Also since I’m writing, that viewport declaration is wonky. It should have device-width, and it should not have maximum-scale which is user-unfriendly.
All up: