Father, husband, developer relations and web standards expert, and cat demo builder.
Raymond is a senior developer evangelist for Adobe. He focuses on document services, JavaScript, and enterprise cat demos.
It's been a hot minute or so since I played with web components, mainly because I've been re-evaluating when I think it best makes sense to use them. One idea I've been chewing over lately is that progressive enhancement could really be the sweet spot for components, something I really got into earlier this year when I shared a sortable table component that, if it failed to load, wouldn't break anything.
It's been a few days since my last post in this series. I'd like to blame something in specific but honestly, it's just life. Today's tip will - again - be short and sweet but hopefully helpful. The idea of a "featured" post is that there may be content that, no matter the age or view count in your stats, you want to highlight. It could be your first blog post. A post announcing a new job or life event. Or anything really. How can we use front matter to support this?
I've been using Alpine.js for quite a while now (although I still make silly mistakes, see the p.s. at the end) but haven't yet looked at the "official" plugins. Listed in the docs, those plugins include:
Welcome to another collection of links, and for today, a very "component" flavored set of links. I've been really interested in web components the past few months (you can peruse my articles on the topic) and lately there's been a lot of writing on the topic. That's been tied to chatter online as well, but one of the reasons I started this series of posts was to help people find things they may have missed on social media. Personally, I'm finding my own thoughts on the subject changing as well. I still like them, but I want to keep in mind the user experience on a site that uses them. As a web developer, I shouldn't sacrifice the end-user experience for my own developer experience. I think I'm most interested in cases where web components can progressively enhance functionality. Anyway, here's our links.
On September 11th, Todd Sharp, Scott Stroz, and myself will be launching a new livestream called The Undefined Show. Every Monday at 8 PM EST, we'll be hosting a session on different topics, including development, languages, developer relations, and most likely quite a bit of non-technical things as well. Heck, at bare minimum, join us to heckle!
I hope by now that folks are getting that the point of this series isn't so much technical but inspirational. I think a lot of people approaching front matter tend to keep it rather simple - title, date, tags or categories, and when I envisioned this series I really wanted to explore some more interesting things you could do. Today's entry is an example of that. Given that a (good) blog post always contains a date, how would you handle noting a post that's been edited? Here's a simple example.
Today I'm following up (heh, get it) on the series I started yesterday on interesting use cases for your Jamstack site's front matter. In yesterday's post, I described how to use front matter to define a list of "related posts" to a blog post. Today's post is a natural follow-up to that one and deals with... well follow-ups!
Want more posts? You can peruse a complete list of my content, or pop over to my search page to find what you're looking for.
