Skip to content

Switch to static for frontend #1301

@XhmikosR

Description

@XhmikosR

This is something we discussed internally on Slack, but I'd like us to come to a consensus before I start working on it.

  1. We can still use Heroku as long someone sets up branch/PR previews. Not sure if we can control the response headers with Heroku. An alternative is Netlify which allows us to do redirects, customize the headers, etc.
  2. Which tool should we use? I personally like tools with less dependencies so I wouldn't go with Jekyll (Ruby, and also slow in general). Hugo is another alternative, we can load it through npm via the hugo-bin package
  3. Regarding the current data/bootstrapcdn.json, I guess we can generate it on build time. Hugo should make this easy, see https://gohugo.io/templates/files/.
  4. Regarding testing the frontend, we could just use the tool's we go with, built-in server, minus the redirects maybe. Otherwise we need to look into using something else for frontend testing

Note that with Hugo, we can use Sass, minify files, generate SRI hashes etc. I haven't really done this yet with Hugo myself, but it shouldn't be too hard.

/CC @jdorfman @jmervine @Johann-S

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