-
Notifications
You must be signed in to change notification settings - Fork 9
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
Switch to Eleventy #159
Comments
Yeah, there are a lot to choose from, a good resource to look at is https://www.staticgen.com/ |
I think I'm going to start with moving just the css part to node, and then we can decide whether or not we want to move the template part too |
We should definitely move to Eleventy. It isn't hard to switch, and it keeps getting better. |
I just pushed a work-in-progress branch: https://github.com/cloudfour/pwastats/tree/eleventy Note to future self: here's a theoretically helpful link: https://www.11ty.dev/docs/quicktips/tag-pages/ ...but it's not currently working. |
In the discussion of #148, there's been some talk of further entrenching this project's build process in Node-land to better align with our pattern library.
I know we originally chose Jekyll because of its straightforwardness compared to the Node solutions at the time. Now, though, our pal Zach Leatherman made eleventy
and there's an official Vue-based static-site generator with built-in PWA support.If we think at some point we might be drastically revising this project's build process anyway, it might make sense to consider a platform change.
Just food for thought! 🍔
Update
We've now used Eleventy half a dozen times and like it a lot. Zach works for Netlify now, so it's clearly the right choice given the build stack for this project. Let's do that!
@cloudfour/dev @cloudfour/pwastats
The text was updated successfully, but these errors were encountered: