DEV Community

Discussion on: Github pages for your simple web projects

Collapse
 
michaelcurrin profile image
Michael Currin

That's a nice motivation for using GH Pages and what you can put on it. It would have been good to mention Jekyll since it is in your cover image.

To make it more practical around tech and deploys flows, here is what I typically use GH Pages for:

  • Plain HTML, JS and CSS. No build step. If you like DocsifyJS, then you can set up a docs site like that.
  • Jekyll. No need to configure a build step. GH Pages will run Jekyll for you, against a fixed set of gems like themes and plugins.
  • React or Vue app with Node (or Deno). I use GitHub Actions to handle dependencies and building the static app output.
  • React or Vue without Node or package.json or GitHub Actions. Load the dependencies by URL on the frontend using ES Modules.
  • GitHub Actions and some other flow like Jekyll 4, MkDocs, Next (static mode), Nuxt...

Also Netlify is a more advanced competitor to GitHub Pages. But for most projects, GitHub Pages and sometimes GH Actions works great.

Collapse
 
akashkumarsikarwar profile image
Akash Kumar Sikarwar

Thanks, Michael. The cover page was a bit misleading, I have updated it to the scope of github actions light intro.