Page build failure when I change from Jekyll to Hugo

Hello,
I am trying to build a website on Github. I originally had built a Jekyll website. However, I removed it (the whole repository) since I wanted to create a completely new website. Then, I keep having the error messages below:

The page build failed for the `master` branch with the following error:

The variable `{{2\left( {x + 4}` on line 50 in `exampleSite/content/slides/example/index.md` was not properly closed with `}}`. For more information, see https://docs.github.com/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites#tag-not-properly-terminated.

For information on troubleshooting Jekyll see:

  https://docs.github.com/articles/troubleshooting-jekyll-builds

If you have any questions you can submit a request on the Contact GitHub page at https://support.github.com/contact?repo_id=315911396&page_build_id=217375615

I referred to websites, but I have no ideas on how to solve them. Could anyone help me, please?

Hey there! Basically you’ll need to tell Pages not to use Jekyll. By default, Pages always attempts to parse/build files with Jekyll, but if you have files that use syntax that Jekyll doesn’t understand you can get errors like this. To tell Pages to completely skip the Jekyll build, you just need to add a .nojekyll file to the root of your pages branch. See this doc for more info: https://docs.github.com/en/free-pro-team@latest/github/working-with-github-pages/about-github-pages#static-site-generators

1 Like

Hey! Thanks a lot for your answer, it indeed helps!
Then, is it right that I add a .nojekyll in the myname.github.io repository?

add a .nojekyll in the myname.github.io repository?

If that’s the repository that’s publishing your Page, yes. It needs to be in the branch that’s defined as the source of your Pages site. If there’s a .nojekyll file in the source branch, then the files in that branch are effectively what gets deployed to the back-end that serves the site.

1 Like

Aha, I see!
I appreciate your clarification, @tcbyrd!!!

1 Like