Many static site generators, including Hugo and Jekyll, have file watching support and even automatic page reloads, so their workflow is barely different from editing raw html. You have to jump through some more hoops for raw html, but I expect you save time overall.
Next Gen Static Blogging
71–80 of 179 posts
Re: Next Gen Static Blogging
#72Earlier quoted context omitted.
I agree with ffpip's comment. I too found the contrast to be too low for my comfort. Here are the colors used for the body element in the CSS (see https://inoads.com/style.css ): background-color: #FDF6E3; color: #657B83; Now plug those values into https://webaim.org/resources/contrastchecker/ and we can see that this color scheme fails even the WCAG AA check (see https://i.imgur.com/iK7FRfU.png for a screenshot). I…
Ah, it seems this site is aware of my preference for a dark color scheme. @media (prefers-color-scheme: dark) { /* defaults to dark theme */ body { background-color: #002B36; color: #AAA; } } You are seeing the bright color scheme and I am seeing the dark. So when ffpip said either "darken the text or brighten the background," and I'm looking at the dark theme , that would mean reduce the contrast . I think we're all…
Ah! That makes sense. Indeed you had mentioned in your comment:
> Its use of gray text on a dark blue background is pretty common
That should have been a clue for me that you were seeing the dark color scheme.
Re: Next Gen Static Blogging
#73Earlier quoted context omitted.
> the opening tag is optional too but I retained it in the above example to specify the lang > Yeah, no. The text is in Latin (la), not in English (en).
~Any references to support your claim?~ [Edit: I notice now that the content is indeed written in Latin. It contains the "Lorem Ipsum" placeholder text. Nice catch! :-)]
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.
Re: Next Gen Static Blogging
#74I like the white-space: pre-line trick and very much like the omission of unnecessary and tags as the parsing of such valid source is neatly prescibed.
But abusing , and like that is a horrendous and pointless. Please use the proper tags to keep the web clean.
Re: Next Gen Static Blogging
#75Interesting 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?
You can have it auto-generated using directory indexes in Apache. You can even customize them (within limits). I've toyed with having a minimal blog, where I simply drop text files with file names beginning with their date in a folder and rely on directory indexes as a "home page".
I too was toying with a similar idea, but was finding the devil was in the details.
For instance, you want to sort by publish date, which isn't the same as file creation date. If you add it to the file name, to sort by that, then you can no longer use file names for urls, at least without some transformation.
So I was really curious how others were dealing with that in a clean way.
Re: Next Gen Static Blogging
#76Excellent performance, sketchy accessibility. But I applaud the effort to look for simplicity, even if it wouldn't work for many production use cases.
Re: Next Gen Static Blogging
#77Re: Next Gen Static Blogging
#78Earlier quoted context omitted.
~Any references to support your claim?~ [Edit: I notice now that the content is indeed written in Latin. It contains the "Lorem Ipsum" placeholder text. Nice catch! :-)]
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...
Re: Next Gen Static Blogging
#79A 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?
This structure vs appearance dichotomy was added after the fact, though, since CSS came significantly later than HTML. It has been used as a (misguided IMO) narrative to defend CSS's complexity and redundancy and is partially to blame for HTML and the web ceasing to be a straightforward medium for simple publishing, seized by big media and ad networks.
Re: Next Gen Static Blogging
#80I 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
> 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]