Been crazy busy with #pixelfed development lately, I decided to take a break and work on something else for fun.
Inspired by an expiring domain, I started building my idea of a bespoke guide to the fediverse.
Can't wait to launch this, I think y'all will love it! #fediverse #activitypub
(I’ll sure know what to do once I reach “financial independence”! 😉 Still hate “crypto,” tho, don’t @ me.)
(And add `u-in-reply-to` classes to replies and all of these wonderful things. And `u-repost-of` to boosts. Dang, I would consider ditching Micropub if it did all that.)
I (now) do it the other way around, though, which is called POSSE (“Post on (your) own site, syndicate elsewhere”).
But it would be nice to see proper reply contexts, and threading added to that plugin’s feature list. One day.
Wouldn’t it be nice if I could just post on Mastodon and have my toots imported in #WordPress, using a CPT, perhaps? (Wait, I already can! https://github.com/janboddez/import-from-mastodon)
Kinda happy with that workflow, at least for smallish projects—might be why I like to split things up in bite-sized chunks (AKA “abstract away” the real nasty, ugly code in a separate file, class or package).
Although I occasionally dabble in Docker (and use a somewhat proper Valet setup for most of my WordPress stuff), nearly all my “development” consists of just hacking away on “build” sites like this. Later changes mostly happen in VS Code, where I’ll have PHPCS running to clean up things and help me find the most obvious flaws. Most of my “testing” is just that: static analysis/linting, and actually using the things I’m building. And lots of debug logging.
Web 3 Is Going Great! https://web3isgoinggreat.com
Leestip voor iedereen die ‘iets’ met open source doet https://mor10.com/open-source-considered-harmful/
Love this. Reminds me of “ligne claire,” and Adrian Tomine’s work.
> To minimize points and reduce complexity, I tried to stick with rectangles, ellipses, efficient lines, basic strokes, and solid blocks of color everywhere possible. Brushes and textures were off limits. A good, but challenging constraint.
https://lynnandtonic.com/thoughts/entries/case-study-2021-refresh/
Hehe. Just went through my spam folder. Mailgun it is. (There’s probably better options, and I don’t want this to become yet another “single point of failure” and so on, but lousy email deliverability, unfortunately, is real—and caused, in part, by the sort of “crappy” shared hosting I’m constantly promoting. 😃)
(I had a lot of spare time in university! Heck, I’m still just an amateur. My day job has absolutely nothing to do with programming, or design. Started side-gigging as a web developer only five years ago.)
I used to read all the web design blogs. Zeldman, Stopdesign, Mezzoblue, Veerle’s Blog. Remember when Smashing Magazine first came about and its articles were often—sometimes rightfully so—dismissed as little more than link lists with clickbaity titles (“17 Free Fonts You Should Be Using Right Now” or whatever). Heck, I remember Vitaly’s fonts posts on the personal blog that came before it.
(Or CSS-Tricks! 😄 No, seriously, I actually remember now, it was 456 Berea Street, which is mentioned at the bottom; the page itself seems gone, tho.) https://css-tricks.com/better-pull-quotes/
“Pull quotes,” way back, I would neither store in “custom fields” or “blocks.” I’d wrap the bit of text I wanted to highlight in a `span` with a `pullquote` class and have JavaScript use that to duplicate it into a left‑ or right-aligned `blockquote`. (Pretty sure I got that from a seventeen-year-old A List Apart article or so.) No duplicate content in the source and all! (Seriously, this must’ve been before ARIA roles and what not.)
You’ll never be able to replace ’em all with blocks, either. I mean, things like subheadings, yes. But a checkbox that determines if a post should be crossposted to Twitter or Mastodon or whatever? You’re going to put that in a “block”? Thought blocks were bits of content, not “meant to hold metadata for the _whole post_.”
This is very good. I use custom fields all the time, although I tend to build custom meta boxes—a few lines of code, really—rather that use the “native” UI. (Have never touched ACF; the Meta Box plugin, yes, for certain, more advanced field types and when deadlines were tight.)
“How to Use Native Custom Fields in WordPress (and 5 Useful Examples)” https://css-tricks.com/use-custom-fields-in-wordpress/ #WordPress
Engineer, web designer, and amateur guitarist. Likes web standards, accessibility, #PHP, #PunkRock, and the #IndieWeb. #nobot