While part of me still wants to build somewhat complex layouts using nothing but HTML and CSS, these WordPress block pattern examples are really, really nice. I mean, in a WordPress context. Sure as heck beats shortcode wizardry.
Does my feed reader, a responsive web app, really need Micropub integration? I mean, I can simply long-press-to-Indigenous. On desktop, there’s text expanders, bookmarklets, or both.
@celia I mean, while these days (thanks to Flexbox/Grid) it’s often easier to just start writing CSS from scratch, a parent theme provides a bit of robustness, too (like any framework), and will cover a lot of things (content types, page templates, form styles) I may not immediately (want to) think of. The downside, like you said, is having to deal with specificity, media queries, etc.
@celia I use Gutenberg and sometimes have to tweak the front-end CSS a bit to make it work on all screens. (The WP.com versions of the same themes often come with proper block styles of their own, but are difficult to maintain.) I’ve built quite a few sites off the Karuna theme that all look very different. Most work is _disabling_ the templates/features I don’t need, and CSS (which I don’t mind so much, reminds me a bit of the CSS Zen Garden way back in the day).
(Those captions shouldn’t really be there, I guess. And I forgot to properly fill out the alt text in WP’s Media Library which is why it wasn't crossposted.) Also, not actually a question.
Which one is better?
A Microsub reader.
A feed aggregator and reader (and Microsub server).
> We shouldn’t stop kids from taking hard STEM classes just because we’re worried that they’ll have a better chance of becoming rich STEMlords; instead, we should just tax the STEMlords more[.]
@celia My go-to these days is a simple enough Automattic theme—all of them are based on the _s starter theme—and a child theme with fairly minimal CSS/PHP on top. All my child themes are, like, no more than five files or so.
My feed reader’s “timeline” moves really slow, so I’m not at all interested in anything “infinite scrolling” or optimized for “real-time” updates. It’s to do with marking new items as read, which using traditional pagination will “bump up” remaining items from, e.g., page 2 to page 1, meaning the (previously generated) link to page 2 may now lead to an empty page and those items might stay overlooked for a little while.
Adding cursor-based pagination to my RSS reader, to get rid of some (very) minor annoyances. (Note that Microsub’s paging—https://indieweb.org/Microsub-spec#Example_Paging_Workflow—works a bit different, still. Yay.)
The Fediverse should get rid of the addictive dark patternes that were copied from Twitter & co
> [T]he number of papers at top journals dedicated to climate economics is miniscule.
Reading https://darekkay.com/blog/avif-images/ and, interestingly, my RSS reader shows “This image is not supported in your browser” for the WebP image, too. But it is; I’m using the latest Firefox. (What I think is happening instead, is that my reader strips away `source` tags.)
Considering having my “Share on Pixelfed” plugin for WordPress added to the “official” WP.org repo.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!