Especially regarding the workflow with Spot colors in Affinity Designer, Photo and Publisher.

Nothing beats https://fontba.se/ in my eyes...

May I ask how you, as a Front-End-Dev/Graphic Designer, get to attend these conferences?

I think it is very hasty to switch completely to a somewhat beta-product like Invision Studio for professional work.

As a print designer, I can tell you that Affinity is not even near a proper workflow for designs that contain spot-colors and InDesign and Illustrator still outperform it in this case (which is my case most of the time). As a UI/UX designer I can tell you, that none of the available software does a good job for the UI/UX use case - they lack the ability for proper responsive design with real data and animations - therefore I started to design directly in HTML/CSS only with the little help of a http://styletil.es to get the right overall look beforehand and which can be integrated into your current workflow easily.

Honestly: HTML/CSS (not JS!) is not that hard and would give the same result with the same effort - and even support small animations and proper responsive behavior and could be shared even more easily (ask your Backend-/Frontend-Dev for a solution)! The code does not have to be perfect: It doesn't matter if your Pro-Frontend-Dev rewrites the code completely - he/she has to do it anyway if you provide a simple static design. So on that front, you're not losing nor winning anything besides the fact that you will get better over time and get a proper feeling for problems that could occur during the design process immediately. And the day will come when your Pro-Frontend-Dev says something like "Perfect work, nothing else to do here. Now we can talk about the fullscreen 3D raindrops you wanted to be generatively created on the website for the client."

So yeah: Designers should code. And it isn't their passion nor will it be ever (visual != code) - but nobody said you need JS with its (for a designer) heavy to grasp concepts and logic. But after little to no time, HTML and CSS will feel like writing a word document. Have a look at some Browser-Tools or ask your devs for help to set up an easy to use environment with hot-reloading to get direct visual feedback - it will feel like dragging rectangles around in photoshop with just a small amount of wizardry added. And then just use it. Don't tinker with its configuration or extension in the first place. That will come when you feel safe in your workflow and you will learn to love the endless possibilities!

"did you take the photo yet?" - "no, we're recording a video" ...

Nice stuff! ...BUT:

Frontpage does stutter a lot on the latest Chrome-Release on my workstation. CPU-Usage drops by about 10% on a 6/12-Core Intel I7 when closing the tab of the frontpage or clicking a link to dive into the design system... perhaps it's just me, just wanted to let you know...

What about http://jonathantneal.github.io/sanitize.css/ ?

I also would throw in Prisma

We used Fastbill - now we're developing our own software...

I really like Jeet.gs because it's just css and doesn't bloat my markup. And I has a sass-version. And works the way I as a human think of a grid. And it's lightweight - so it does not come with anything else like in Bootstrap, Skeleton or Foundation. And for me it's easier to understand and use than Susy. And I can decide on my own, if I want to develop mobile-first or not. In combination with the bp-sass-mixin from Chris Coyier I'm able to write my grid-structure very fast for different breakpoints.

And, and, and....