👉 English | 简体中文
This is a quick start template for Hugo theme FixIt. It uses Git submodule feature to load the theme.
It comes with a basic theme structure and configuration. GitHub action has been set up to deploy the blog to a public GitHub page automatically. Also, there's a cron job to update the theme automatically everyday.
▸ .github/ # GitHub configuration
▸ archetypes/ # page archetypes (like scaffolds of archetypes)
▸ assets/ # css, js, third-party libraries etc.
▸ config/ # configuration files
▸ content/ # markdown files for hugo project
▸ data/ # blog data (allow: yaml, json, toml), e.g. friends.yml
▸ public/ # build directory
▸ static/ # static files, e.g. favicon.ico
▸ themes/ # theme submodules
For a complete quick start, see this page.
Hugo: >= 0.132.0 (extended version)
-
Click Use this template, and create your repository on GitHub.
-
Once the repository is created, just clone and enjoy it!
# Clone with your own repository url git clone --recursive https://github.com/<your_name>/<your_blog_repo>.git
Tip
The repository name determines your GitHub Pages URL, for example:
Repository Name | GitHub Pages |
---|---|
<your_name>.github.io |
https://<your_name>.github.io/ |
blog |
https://<your_name>.github.io/blog/ |
# Development environment
hugo server
# Production environment
hugo server -e production
When your site is ready to deploy, run the following command:
hugo
Note
You may have noticed that the first automatic deployment of GitHub Actions after the template initialization failed. This is because you have not configured Workflow permissions and GitHub Pages.
- Head to Setting => Actions => General => Workflow permissions => Check "Read and write permissions".
- GitHub Pages settings: Setting => Pages => Source: GitHub Actions.
- Modify
config/_default/hugo.toml
filebaseURL
to your site URL. - Commit the changes from the previous step to the
main
branch, and GitHub Actions will automatically build and deploy the site to GitHub Pages.
Afterwards you can upgrade the theme with the following command:
# Update theme manually
git submodule update --remote --merge themes/FixIt
Start via NPM script
npm install
# build the blog
npm run build
# run a local debugging server with watch
npm run server
# run a local debugging server in production environment
npm run server:production
# update theme submodules
npm run update:theme