| ▲ | simonw 13 hours ago | |
Yeah, I've been thinking some kind of reusable styles or style guide might be a good idea at this point. It's been fun collecting a bunch of inconsistent tool designs just to see how the different models behave, plus occasionally I go for something with a topical theme like https://tools.simonwillison.net/terminal-to-html or https://tools.simonwillison.net/new-yorker-style - but a little more consistency could be nice. | ||
| ▲ | gaigalas 13 hours ago | parent [-] | |
Definitely! Not only for the user, but it makes sense for the process of making the tools as well. If I left the agent for itself, it often come up with outrageous styles and I need to prompt it for something more sober. --- You can do a lot with just CSS. I restored this 2009 project of mine just now: https://alganet.github.io/ghiaweb/ It still works (minor misalignments though), all HTML is pure (no class=, no css=, no <div>). The global CSS does everything: the forms, the drop-down menus, etc. Nowadays, we can do even better, no build step or anything like that. | ||