Summary
Put more work into showing what’s different about each example
Detailed Description
I’m just getting started with Preline, and I’m finding it difficult to read the documentation for different variants of each component. They just throw a long list of tailwind classes at you without telling you what’s different about each variant. I find myself going through the examples class-by-class to see exactly what’s different about each one, and that takes time.
So for example if I have a collapsible navbar and decide I’d rather just have a default navbar, I have to go through the HTML class by class and figure out exactly what I need to change. Some of it you could argue is obvious, like hs-collapse-* classes are relevant, but it’s not clear that those are the only things that need to change.
Maybe a little bit less of an issue are the button classes. Changing between a solid button and a ghost button seems like something that should be simple, but I have to go through each class to see what’s different.
Another thing is that it would be helpful if the most relevant classes were at the front of the class list. Having to scroll all the way to the end of the list is a pain, especially on desktop where scrolling to the side is harder. It’s also harder to read when the relevant classes is buried in the middle of a list of classes.
Having some sort of wrapping on the examples would also help.
Use Cases
Learning to use Preline
Summary
Put more work into showing what’s different about each example
Detailed Description
I’m just getting started with Preline, and I’m finding it difficult to read the documentation for different variants of each component. They just throw a long list of tailwind classes at you without telling you what’s different about each variant. I find myself going through the examples class-by-class to see exactly what’s different about each one, and that takes time.
So for example if I have a collapsible navbar and decide I’d rather just have a default navbar, I have to go through the HTML class by class and figure out exactly what I need to change. Some of it you could argue is obvious, like
hs-collapse-*classes are relevant, but it’s not clear that those are the only things that need to change.Maybe a little bit less of an issue are the button classes. Changing between a solid button and a ghost button seems like something that should be simple, but I have to go through each class to see what’s different.
Another thing is that it would be helpful if the most relevant classes were at the front of the class list. Having to scroll all the way to the end of the list is a pain, especially on desktop where scrolling to the side is harder. It’s also harder to read when the relevant classes is buried in the middle of a list of classes.
Having some sort of wrapping on the examples would also help.
Use Cases
Learning to use Preline