4 ms·
I am evaluating these options now: - https://github.com/alaq/adrien.sh https://github.com/alaq/adrien.sh for NextJS - https://github.com/sw-yx/swyxkit https:/
by nikivi 5y ago
I am evaluating these options now:
- https://github.com/alaq/adrien.sh https://github.com/alaq/adrien.sh for NextJS
- https://github.com/sw-yx/swyxkit https://github.com/sw-yx/swyxkit or Svelte
- https://github.com/SimeonGriggs/simeonGriggs https://github.com/SimeonGriggs/simeonGriggs for Remix
All have designs I like. I am only familiar with NextJS and find it a pleasure to work with.
- southerntofu 5y agoWhy all the JS/TS though? Part of what's great about a static site is serving simple HTML/CSS pages that look great, degrade gracefully, and don't hog users CPU/RAM like JS applets do.
- nikivi 5y agoWith Next/Svelte/Remix you can only ship HTML/CSS if you want. Reason to use those frameworks is that I find their mental model to fit nicely for progressive enhancement. For my blog, I plan to have interactive content via MDX or something similar so there will always be optional JS involved.
- southerntofu 5y agoThanks for the clear answer. I've previously heard of server-side rendering for JS frameworks but i was certainly not aware that several frameworks supported it, and that some people like you actually cared :)
- gitgud 5y agoTake a look at nextjs it serves plain HTML and CSS then hydrates it with JavaScript interactive-ness