The combination of the Carbon design system and NextJS should make for rapid website development, but I ran into a few small hurdles getting them to play nicely with one another using existing documentation and community guidelines.
What do you do when a website has loaded but the content is still being fetched from an API? One answer is to fill the page with animated placeholders, creating a skeleton of what the user can expect, with a dash of CSS animation to let them know that something's still going on behind the scenes.
I love books. I have a huge collection of them and I routinely add to it. But when it comes to the topic of spreading knowledge and information, I think the web wins. It may not be as nice to use, but it is more accessible, and that means it's more valuable.
I've been thinking a lot about an article I read recently that called out technical writing online for being overly trusted. But shouldn't that same argument apply more universally to third-party code coming from any source?
The new dominant layout methods in CSS – grid and flexbox – have solved a lot of issues. Still, sometimes the ideal layout is somewhere in the middle: a flexible grid-like mashup. With a bit of outside-the-box thinking, you can there from either angle.
There are several strong arguments for moving away from using "master branch" as default terminology, but what should it be replace with? Personally, I like the idea of extending the tree abstraction that we use when talking about branches, so have started using "trunk".
Marketing needs versus user experience is a topic that I have some deep misgivings over, but a recent post made me want to try and boil some of those thoughts down into their underlying rationale. I'm not sure I totally succeeded, but there we go.
Notes from the 2020 Jamstack Conf. Some interesting dives in the Jamstack community and various applications of Jamstack technologies, with tweet threads as usual.
Customising HTML lists often means sacrificing standard browser typesetting bonuses, like hanging indents. But with a little bit of modern CSS, you can get them back again, whilst still getting to use custom counters – like emoji 🚀
When using Craft in a headless configuration, your entry URIs will default to the wrong domain and won't be properly configured to match your actual site structure, but that can be fixed.
It turns out that there are a lot of gotchas to creating a clear category structure for media reviews. Well, after a year of messing around with various setups behind the scenes, I think I'm starting to get somewhere.