Skip to content

Frontend: Decide on frontend framework #4

@wknd

Description

@wknd

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:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions