I'm the supporting designer for several product teams, ~20 developers total and Figma works well for us. I can do constraint-based component-driven design, and they get a rough approximation from Figma's code preview tool. Everything ambiguous is solved through communication, either with Figma comments or face-to-face.

https://www.figma.com/blog/guide-to-developer-handoff-in-figma/

I'm a bit confused as to what kind of hosting would Kirby need, since it uses static files? Currently I'm using Now, but that only allows immutable deploys—so impossible to update files later.

I was looking at this kind of tools just yesterday and didn't see Takeshape. Seems nice, but as a portfolio tool, I'm put off by the asset manager not having folders. Some projects can have dozens of pictures, and it seems like a pain to search for them, instead of just opening a folder.

Been using RSS for close to 10 years now, daily. I was very, very happy with the UI of Digg Reader because it Just Worked. Right now using flowreader.com because I'm a fan of being able to expand the news item in-place.

Unlikely to use a native app though, because going through feeds is part of my start-of-day routine when I sit down at my 27" screen.

No luck for existing sites, but for new projects they support exporting the html/css/js package.

Zeit.co uses a passwordless flow similar to Slack's Magic Link. You type your email, click the link in your mailbox and now you're logged in.

They also use it for their command line interface, which is beyond neat!

Likewise, very useful for helicopter view of multiple domains/sites.

For me, the examples to strive for are _Why's Poignant Guide to Ruby and Eloquent Javascript.

They are on opposite ends of the spectrum in terms of visual design, but for me they are winner's because the opinionated style was entertaining and so it kept me curious even if I sometimes struggled with internalizing the concepts.

I think the biggest thing that was done wrong, was failure to communicate the design principles in a clear and easily understandable way. Sure, they had the example screens and code samples, but the biggest thing that Material Design and Apple HIG do, is that they explain you in simplest terms what to put where to have a nice-looking app.

As a Windows Phone user who dabbles in front-end, I considered making a simple app. I dropped the project after 2 weeks of trying to piece together what UI components are available, how to use them, when and where. Even for the base grid I managed to find 4 separate incompatible versions. And then desktop and tablet Windows use a separate, different grid?

In other words, design thinking was solid. Developer thinking was solid. Communication with possible app designers? Disaster.

I can only hope that they will spend some time to create usable design documentation for next iteration. I mean, if a random CSS framework can document itself, how hard can it be?

Of the better-looking editors, I think Aloha is the only one that doesn't use contenteditable? But that one has it's own quirks.