replace jekyll with handlebars and custom js build, reorganize, cleanup [114]

norfolkjs / norfolkjs.github.io

Website code for Norfolk.js

http://www.norfolkjs.org

12 stars 19 forks source link

replace jekyll with handlebars and custom js build, reorganize, cleanup [114] #113

Closed iambriansreed closed 6 months ago

iambriansreed commented 7 months ago

In the last meetup we spent half the time figuring out the ruby setup just to build the site.

This felt weird considering this was a JavaScript meetup.

I reorganized the site to use node and some custom JS to build and deploy the site. Added handlebar.js support for templating.

This PR is a pretty big change and it might be easier to review the work here: https://github.com/iambriansreed/norfolkjs.github.io

Added a lot more information in the README.

https://github.com/norfolkjs/norfolkjs.github.io/issues/114

pchinjr commented 7 months ago

Coolio. I like where this is headed. We'll keep GitHub Pages as the target host. Since Jekyll is the default build tool for GH Pages, we'll need a custom GitHub Action to pull the code, build, and deploy. https://docs.github.com/en/pages/getting-started-with-github-pages/about-github-pages#static-site-generators I'm unsure if we must create a target branch with compiled assets for deployment, or if it can be done all inside a GitHub action on changes to 'main'. Are you able to check on a CI/CD solution with GitHub Actions to deploy?

iambriansreed commented 6 months ago

@pchinjr done. :)

You have to set up a token and add it as a secret.

You also have to make a repository variable to have the CNAME set.

The CNAME is so we can run our own copy for testing and development like mine: https://norfolkjs.iambrian.com