Meta just published „Make a Video“. An AI model that turns text into videos 🤯 “A fluffy baby sloth with an orange knitted hat trying to figure out a laptop close up highly detailed studio lighting screen reflecting in its eye” makeavideo.studio

Be explicit when each component in a design system should or shouldn't be used. – Simplifies decision making – Lowers the learning curve for new teammates – Keeps the scope of the component clear – Maintains UI consistency React Spectrum is a perfect example of this.

Nike sells greatness, not clothes. RedBull sells adrenaline, not drinks. Polaroid sells memories and nostalgia, not cameras. Shopify sells the dream of entrepreneurship, not websites. The best brands sell stories, not things.

New favorite styling method: class names for components, data/aria attributes for states. Attributes are so much better than classes for states. No need to mess with string concatenation of conditional class names, you can have values instead of only booleans, etc. 👍

And here are four outputs from interiorai.com

One thing I don't see often in design systems – layouts and patterns. Having a great set of components is good, but it's just as important to guide people how to use and combine them into complete pages. It may be obvious to you, but not to someone new joining your team.

Have doubts whether a new component should be added to your design system or not? Implement it and put it into a `src/draft` folder within your app. If other people start using it in various pages, it's a good signal that it's useful enough to be added to the design system.

I follow one rule for painless and consistent spacing — never define margin inside components. Define spacing on the container element instead that positions these components. This way you're always in control of the layout💄

What's a good indicator that design system is working out great for your team? My bet is on the ability of developers to transform a design into code with minimal peeking into Sketch/Figma layers. "What component is this?" shouldn't happen.

It’s pretty simple: Google Meet (original) was previously Meet, which was the rebranded Hangouts Meet. Meet has been merged with Google Duo, which replaced Google Hangouts. Google Duo has been renamed Meet, and Meet has been temporarily named Google Meet (original), for clarity

🔥 These are 5 of my favorite tips for creating, moving and renaming files/folders in VS Code. File utils extension is 👌

SvelteKit 1.0 is here. Learn about the framework's latest features and deploy SvelteKit to Vercel. vercel.com/blog/using-sve…

Hm... this looks nice: developer.apple.com/tutorials/app-…

When you iOS SwiftUI code is so good, it just works on tvOS with next to _zero_ changes.

New app: Spaced — Organize your menu bar items into groups sindresorhus.com/spaced

Love this website/product zed.dev

Tried out transitioning a more menu into swipe actions in SwiftUI

Take a look at the new buttonRepeatBehavior() modifier, folks💡 #WWDC23

Yep, becoming a big fan of this after some small tweaks.