[examplary_cable]

Awesome list!

I love that the cognitive overhead for web apps now is so great many people are "returning to monke" and coding in simple HTML/CSS/JS haha.

Question: Shouldn't the items be in the row so I can see all of them at once? Why are the items in the columns? I'll open a issue (:

[robertoandred]

None of these are simple HTML/CSS/JS.

[examplary_cable]

It's part of the new modern WebDev semantical lexicon:

!React = HTML/CSS/JS

¯\_(ツ)_/¯

[Blackthorn]

Htmx kinda is. I don't really know alpine but the GitHub docs remind me a bit of jQuery plugins.

[adparadox]

>Shouldn't the items be in the row

Maybe! I was messing with different UI approaches to relay this data and this made sense to me, but I'll see if switching to rows is more clear. Thanks for the idea!

[mNovak]

The column layout is basically impossible for me to meaningfully navigate on my laptop -- the scrollbar and descriptions don't both fit on the screen (appreciate the repeated titles at the bottom, but ultimately they don't say much)

[examplary_cable]

> The column layout is basically impossible for me to meaningfully navigate

Same. Somebody said it was done this way because of mobile. I'm not sure.

It's just weird to see "items" horizontally and properties vertically. I'm usually familiar with:

prop | prop | prop

item | value| value

item2| value| value

[bmacho]

Don't you have horizontal scrolling on your laptop? Edge of the trackpad, or 2-3 fingers?

[FireInsight]

On mobile, I actually think it's pretty good like this. The names of the fields should stay visible when scrolling, though. Maybe this could be made reactive?