Earlier quoted context omitted.
The crate is 100% documented. what specific documentation do you think are lacking? Tutorials? That's for users to write. Calling iced not useful reads like an uninformed take
At some point you will need to realize that the endless people commenting about the lack of documentation is an issue with Iced, and the proverbial head in the sand approach will not help you. UI frameworks typically need more than just the type of documentation that Rust docs provide. We see this with just about every UI framework around. Just write some tutorials already.
Tutorials might be nice, but the library is evolving fast. I'm happier the core team spent time working on an animations API and debugging (including time travel) since the last release instead of working on guides for beginners.
Maybe that changes after 1.0.
Until then, countless users have learned to use it. Also iced is more a library than a framework. There's no right answer to the problems you'll be trying to solve, so writing guides on "best practices" is generally unhelpful if not downright harmful.