iommi classification

[boxed]

Hi,

I noticed iommi on your list, which I appreciate a lot, but the classification seems a bit off. The primary use case of iommi is tables+forms, so I would expect it to be visible under the forms heading, and under a tables heading. There is some js in iommi to make it slightly fancier for some things, but it's not really doing anything fancy enough to warrant being put in the full-stack frameworks category I think. It seems like overselling that part :P

Maybe it should be removed from full-stack and added to forms, general, and views? It's a bit awkward being in multiple places, but that's our fault for putting so much stuff into it I guess.

Looking forward to hearing your thoughts.

[jefftriplett]

I think that fitting into multiple places is what threw it. I'm happy to move it into the category that is the best fit, but we have no interest in putting a project in multiple categories because of the nature of these Awesome Libraries (it throws our linter off and I agree with it).

Do you have a preferred category?

[boxed]

Maybe just "general" then? I can make a PR moving it there and trying to write a single line summary. Maybe something like "provides forms, tables, and more". A bit vague but 🤷‍♂️