@grigs@CloudFour Thanks so much for sharing! I've been wrapping my head around cumulative layout shift, `aspect-ratio`, etc., so your debrief is incredibly helpful. Really appreciate your candor and generosity to take the time to share! 🙏
@CloudFour Hi there, I noticed that some of your recent blog posts have images that get compressed horizontally on narrower viewports. I'm sure you know, but I think adding `height: auto` should fix this?
@grigs@CloudFour My pleasure - thanks for all the invaluable knowledge you and your team shares! If not too much trouble, can you let me know what happened if you get to the bottom of it? Just curious from a workflow standpoint!
@forestryio Read-only content in the sidebar is great, but could there also be read-only fields (like an 'instructions' field) in front matter templates? Would be useful for providing page-specific help text to editors right in the context of editing a page.
@backblaze In the B2 docs (https://t.co/B2G0RloZkD) it looks like the units for max-age for cache control are half-seconds (5 minutes, `max-age=600`). The 'such as' adds ambiguity, but I'm guessing you meant either 10 minutes or `max-age=300`?
@SlackHQ @ThisIsPizza It looks like Slack iOS and desktop Mac apps still aren’t displaying images with embedded Display P3 profiles accurately. (Slack in Safari and Chrome seem to display them just fine.) Any timeline on when P3 will be supported in the standalone apps?
@PranavDixit I'm sure meant no harm, but calling people without disabilities "regular" can be alienating to people with disabilities. Google has some recommendations here: https://t.co/aztLg4JYXZ
@leebert Wow, sounds great! Let me know if I can be of help. (I do a bit of React and vanilla JS coding, but want to get my feet wet with TypeScript and Figma plugin dev, in case there’s some grunt work you could use some help with.)
@leebert Thanks for sharing your Figma plugin Design Tokenizer; it looks great, but I was just trying it out and noticed exported hex values for color styles didn't match what was spec'd in Figma (e.g. #0098FF exported as #0076c6, #FFA000 exported as #ffeccc). Any ideas why? Bug?
@leebert Oh, come to think of it, for my particular use case, it would be preferable to flatten the hierarchy for everything under “color”. (So the keys would be “Primary/Blue#0098FF” and then “Primary/Blue#0098FF/Light#28C0FF”.) That would break current behavior of plugin, though…
@leebert Thanks for looking in this! I think I've isolated the issue: I'm using some nested styles in my file, similar to screenshot below. It looks like the plugin doesn't correctly handle styles nested in this (admittedly kinda weird) way — only one value is getting exported.
@erikdkennedy Your Font Sizes in UI Design (https://t.co/38cO8aPRpr) is a great reference. One q: after explaining `sp` is intended for specifying font sizes, 2nd-to-last sentence says, 'For Android apps, just type “dp” into the box and call it a day.' Did you mean `sp` ?