This Smashing article is a nice introduction to Tauri, which was news to me as well. It tells you why you might want to use Tauri instead of Electron, how to get set up for Tauri development, and how to build a Vue-based desktop app with the framework.
This is a nice, Smashing deep-dive by the author of React HereMaps:
Mailchimp CPO John Foreman drops some contra-conventional wisdom in this Smashing Magazine piece:
When I as CPO say, “we’re going to do this thing!” the reply then is often, “OK, so then what are we going to kill?” The Mythical Man-Month turns product development into a zero-sum game. If we want one thing, we must stop another. Now, that’s an actual myth, and I call hogwash.
WordPress is MASSIVE — so why would a site using WordPress consider moving to JAMstack? This technical case study from Sarah Drasner covers how Smashing Magazine manages their content and what an actual WordPress migration looks like (using Smashing Magazine).
In this two-part article series, we’ll cover what an actual WordPress migration looks like, using a case study of the very site you’re reading from right now.
We’ll talk through the gains and losses, the things we wish we knew earlier, and what we were surprised by. And then we’ll follow it up with a technical demonstration of one possible migration path, not off WordPress completely, but how you can serve decoupled WordPress so that you can have the best of both worlds: a JAMstack implementation of WordPress that gives you all the power of their dashboard and functionality, with better performance and security.
We don’t have the power to change the global cost of data inequality. But we do have the power to lessen its impact, improving the experience for everyone in the process.
So good…anyone collaborating on code with other humans should 💯read this.
Take a moment to remember the last time you collaborated in a code review. Did your team overcome feedback resistance and manage time expectations? Fostering a healthy mindset is the key to build trust and sharing knowledge with your colleagues.
One of the most amazing things about Open Source is how much it enables you to learn from the best. Just open up the source for your favorite library or framework and you can start learning from the best in the business. But that can feel intimidating. This article breaks down some approaches you can use to make it easier. As author Carl Mungazi says:
Reading source code is difficult at first but as with anything, it becomes easier with time. The goal is not to understand everything but to come away with a different perspective and new knowledge. The key is to be deliberate about the entire process and intensely curious about everything.
Margins in CSS seem simple enough at first glance. Applied to an element it forms a space around the element, pushing other elements away. However, there is more to a margin than you might think.
No kidding! Margin collapsing has got to be one of the hardest things about CSS for new developers, and this article not only goes into it and how to avoid it, but explains the “why” behind it.
A brilliant look at how CSS custom properties allow you to both utilize the cascade and provide some level of scoping and proximity-based styling. Prior solutions include the ‘big blunt hammer’ of inheritance-based styling or ignoring the cascade completely utilizing methodologies like BEM, but as author Miriam Suzanne points out:
Custom properties provide a new, browser-native solution; they inherit like any other property, but they don’t have to be used where they are defined.
I’m excited about native lazy loading! We’ve been using lozad.js for lazy loading with some success. There are times when it seems that IntersectionObserver fails to its job and an image won’t load. (If you scroll the element out and back in to the viewport, it will usually work the second time.)
I might try this hybrid approach and see what happens…
Fascinating read through covering historical context for accessibility and assistive technologies as well as diving into the way we do accessibility in the web today.
According to author Be Birchall this article aims to shift your perspective
by showing how web accessibility fits into the broader areas of technology, disability, and design. We’ll see how designing for different sets of abilities leads to insight and innovation. I’ll also shed some light on how the history of browsers and HTML is intertwined with the history of assistive technology.
Though to be honest, I think the most important conclusion the author makes might be this one:
If you need your site to perform on search engines other than Google, you will definitely need pre-rendering of some sort.
JAMStack is all that, whole grain low fat, I know you want a piece of that…
No but seriously now, I love what’s going on with the JAMstack and the implications for performance, security, and maintainability.
Not sure what this stack even is? Why should you care? In this interview, Vitaly Friedman of Smashing Magazine talks with Phil Hawksworth from Netlify about what it is all about:
JAMstack is all about a way of deploying and serving websites that don’t rely on an origin server, they don’t rely on requests hitting an active server all the time.
The JS community has some great open-source projects that make data visualization easier, however, there has not been a go-to solution for building real-time backends that can back these charts and make them real-time. With GraphQL, we can get a real-time backend running within seconds and use it to power real-time charts.
Vitaly Friedman, Editor-in-Chief and Co-founder of Smashing Magazine, breaks down the broken state of commercial web conferences saying:
The state of commercial web conferences is utterly broken. What lurks behind the scenes of such events is a widely spread, toxic culture despite the hefty ticket price. And more often than not, speakers bear the burden of all of their conference-related expenses, flights, and accommodation from their own pockets. This isn’t right, and it shouldn’t be acceptable in our industry.
…the general expectation is that speakers should speak for free as they’ve been given a unique opportunity to speak and that neither flights nor expenses should be covered for the very same reason.
The details of this post from Vitaly go much deeper than what I’ve shared here. I highly recommend taking 22 minutes to read this.
David Mark Clements shares tools, techniques, and tips for making high-performance Node.js servers in this super deep post on Smashing Magazine:
When it comes to performance, what works in the browser doesn’t necessarily suit Node.js. So, how do we make sure a Node.js implementation is fast and fit for purpose? Let’s walk through a hands-on example.
An increasingly common question — now that people are using CSS Grid Layout in production — seems to be “What are the best practices?” The short answer to this question is to use the layout method as defined in the specification. The particular parts of the spec you choose to use, and indeed how you combine Grid with other layout methods such as Flexbox, is down to what works for the patterns you are trying to build and how you and your team want to work.
Amazingly educational article. I’ve said it before, and I’ll say it again: when you want to learn about CSS Grid, Rachel Andrew is the source.
I was clueless about this until I saw the Smashing Mag headline in my feedbin:
Europe’s imminent privacy overhaul means that we all have to become more diligent about what data we collect, how we collect it, and what we do with it.
Read through and be aware of the implications. These changes become enforceable in May of 2018.
In this post Sarah Drasner covers common jQuery use cases and how to switch them over to Vue, and why you’d even want to.
This article isn’t a how-to, per se. It’s more like a research report written after attempting to build such an app for the first time. There’s nothing wrong with that, though, and this write-up is super useful if you’re about to tackle a similar problem space.
Open source libraries are tried, facial recognition services are evaluated, and their takeaways are solid, if not a bit disappointing.
As you can see, the really simple idea of using facial recognition functionality was not that simple to implement.
The entire piece is worth a read.