AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
How to Make Documentation for Designers to Build UIs
Alina: I'm curious about the docs since the beginning of the product and now has there been changes so that people can find this screen because they can do this, can they do that? Like how do you guys handle this kind of situation? If you want people to adopt it but you don't know what they can and maybe what they cannot do. So we have a book about the Slint language itself, which is mostly targeting designers and people that really develop UIs. Then we have another book about basically prostate equation and C++ integration because we have bindings for different languages. That person finds everything in one place. We probably need to add some more documentation like something getting started section