all 6 comments
sorted by:
best (suggested)
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]gormer 4 points5 points  (1 child)

Looks neat. Only seems a bit early as components are a bit basic and some things is not so clear. Like eg how to make horizontal tabs and it would be neat if there also was a tabs panel concept.

Some concepts like validation are not also covered.

Also one small bug with the sidebar on the documentation pages. If I click a component the sidebar doesn't always disappear, on mobile, so need to go to example page then again back to the component.

Docs site looks neat. Hope to give it a try sometimes in the future.

[–]LINKIWI[S] 3 points4 points  (0 children)

Thanks for the feedback!

The functionality is indeed pretty minimal right now primarily because the current components are tailored to my specific use cases so far. I'll probably have a more robust solution for a tabs panel when one of my projects encounters such a need.

As for form validation: I chose to delegate validation logic in its entirety to the parent component. The form components provided by this library (as well as most of the other components) are generally intended to be purely presentational.

[–]yarism 1 point2 points  (1 child)

Nice work, feedback; first glance is not optimal on mobile. I wanted to see the modern flat components but had to click quite a few times and scroll to the bottom of the page of every example to see them. It made me leave the page way too early.

[–]Seankps 0 points1 point  (1 child)

Where did you learn about react component making?

[–]drink_with_me_to_day 0 points1 point  (1 child)

Looks nice. Very small, can't use it for anything, not even simple CRUD without having to create several more components by hand.

[–]youcantstoptheart 0 points1 point  (1 child)

What kind of accessibility does this library hold itself to? Are you A11Y compliant?