-
-
Notifications
You must be signed in to change notification settings - Fork 267
Open
Description
This is something we discussed internally on Slack, but I'd like us to come to a consensus before I start working on it.
- 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.
- 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
- 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/.
- 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.
Metadata
Metadata
Assignees
Labels
No labels