I've created issues in untangled-ui for the top-10 things (issues 9 through 13) to build (hopefully this week). The project is in good enough shape for others to help, and I'm available to answer questions. Thanks in advance to anyone in the community that wants to work on these. https://github.com/untangled-web/untangled-ui/issues I'm hoping to polish up the forms support this week, so anyone wanting to work on validation and form field rendering would be welcome help for that as well (issue #1).

Of course, you're welcome to start working on adding whatever you're pet favorite is as well

I'm about to put together a group here at work to start building the simplest of these, so please speak up before doing work 🙂

@tony.kay I can implement some of the low hanging fruits, like badge/labels in the next days.

ok. I just cleaned up some naming. I'll push. Then in an hour me and a number of devs are getting together

All good, I'll start this tomorrow, (time zones)

cool, thanks!

Is there any reason not to use a library such sablono? https://github.com/r0man/sablono

I don't want to infect ppls projects with more dependencies

If this were an app, I might consider it.

but as a lib, nah

I prefer the sablono syntax over the om/dom...less verbose and easier to read

Ok gotcha

It's reasonable for a library

Yeah. I'll give you an update on naming later after we meet. I think things that have no state like badge/label should all go in one namespace. I'm leaning towards elements if anyone wants to give input

@baris Just FYI there is a mostly (possibly completely) implemented button in exploration cards.