Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frontend: Decide on frontend framework #4

Open
wknd opened this issue Feb 12, 2022 · 3 comments
Open

Frontend: Decide on frontend framework #4

wknd opened this issue Feb 12, 2022 · 3 comments

Comments

@wknd
Copy link
Member

wknd commented Feb 12, 2022

We gotta decide on what framework to look at.

Considerations:

  • most content is static of which the code would be hosted in a different repo
  • to save on resources, it is important everything can be pre-rendered

Some options:

  • gatsby (react based)
  • next.js (react based)
  • nuxtJS (Vue version of next.js)
  • Jekyll (Used by github, but free build times may be too long for large archives of articles or news) *
  • hugo (Written in GO, allegedly fastest build times) *
  • gridsome (Vue based)
  • Eleventy (similar to jekyll?) *
  • scully (Angular based)

(*) 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
Copy link

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

@wknd
Copy link
Member Author

wknd commented Feb 13, 2022

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

@wknd
Copy link
Member Author

wknd commented Apr 23, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants