Jekyll is basically a fancy templating engine, so rather than have the full HTML "header and footer" in every single file, all you need is to specify which layout you are using in the YAML header, and the body of the page.
Here is an example of a website I converted for my parents' business (disclaimer, I did not create that website, I simply converted it to Jekyll):
Jekyll is fully supported by GitHub; all you need to do is upload the project, and GitHub will "compile it" to static HTML automatically.
The only problem with Jekyll is when previewing the site locally, you need to run jekyll serve, you can't just open the in-progress HTML file in your browser. However, I find you quickly get used to this, and being able to change the template in one place and see the changes update across all pages more than makes up for not being able to "preview" the HTML as easily.
Jekyll is basically a fancy templating engine, so rather than have the full HTML "header and footer" in every single file, all you need is to specify which
layoutyou are using in the YAML header, and the body of the page.Here is an example of a website I converted for my parents' business (disclaimer, I did not create that website, I simply converted it to Jekyll):
Jekyll is fully supported by GitHub; all you need to do is upload the project, and GitHub will "compile it" to static HTML automatically.
The only problem with Jekyll is when previewing the site locally, you need to run
jekyll serve, you can't just open the in-progress HTML file in your browser. However, I find you quickly get used to this, and being able to change the template in one place and see the changes update across all pages more than makes up for not being able to "preview" the HTML as easily.