HackThisSite / revival

revival project
10 stars 2 forks source link

Frontend: Decide on frontend framework #4

Open wknd opened 2 years ago

wknd commented 2 years ago

We gotta decide on what framework to look at.

Considerations:

Some options:

(*) frameworks that only build static sites and leave you in full control, they don't add any JS to said static site themselves.

If using one of the framework agnostic builders, we will still need to pick a js framework to handle the dynamic portions. Some options:

simonwuelker commented 2 years ago

https://ssg-build-performance-tests.netlify.app/ might be interesting (gridsome and scully not included)

wknd commented 2 years ago

gotta admit currently I am liking hugo with solid.. I'll make a proof of concept for it soon

wknd commented 2 years ago

I did a bunch of experiments, and I really like both hugo and solid. But it is not really suited for what I had in mind.

tl;dr: the way solid generates components seemed hard to do dynamically without using javascript itself. While i got it working fine to have a single login component on every page, it was sorta hacky. And having for instance a series of components dynamically placed on a page by hugo seemed very hard, you'd have to use js to do it properly.

Astro + solid seemed like it would be better suited for it. Even though its the slowest of the bunch. I think astro also recently(or will soon?) added more fancy serverside rendering which could be useful for the more fancy pages. And for dynamic pages we could also just use solid only.