Harold is a static site and blog generator based on Handlebars and Markdown. With a built-in search engine and ready-to-use responsive templates, including the one for docs websites.
Static sites and blogs with HaroldJS
npx create-harold-app@latest my-app
(npx is a package runner tool that comes with npm 5.2+ and higher, see instructions for older npm versions)
npm init harold-app@latest my-app
npm init is available in npm 6+
yarn create harold-app@latest my-app
yarn create is available in Yarn 0.25+
It will create a directory called my-app inside the current folder. Inside that directory, it will generate the initial project structure and install the transitive dependencies.
As an option, you can choose with which template it should init the project. Possible choices:
- default
- docs
- bare
If you want to init the project with docs
template, pass additional option -t docs
. For example: npm init harold-app@latest my-app -t docs
or with npm 7+ npm init harold-app@latest my-app -- -t docs
. The same for bare
template.
Write create-harold-app@latest --help
in a terminal to get the list of options.
You can prepare your template and reuse it on every new project initialization. You can do this by passing a path to your zip package. It can be a remote, hosted file or one from a local file system.
Examples:
npm init harold-app@latest my-app -t https://github.com/harold-js/harold-template-scaffold/archive/refs/heads/main.zip
with npm 7+
npm init harold-app@latest my-app -- -t https://github.com/harold-js/harold-template-scaffold/archive/refs/heads/main.zip
Or it can be also local file:
npm init harold-app@latest my-app -t ./main.zip
with npm 7+
npm init harold-app@latest my-app -- -t ./main.zip
Read more about it in the docs here: Custom templates.
From the newly created app's directory (in our case, my-app
), run npm start
. It will serve the app under localhost:3000
. To change the port, just add PORT
env, like: PORT=3002 npm start
.
Harold will search up the directory tree for configuration in the following places:
- a
harold
property in package.json - a
.haroldrc
file in JSON or YAML format - a
.haroldrc.json
,.haroldrc.yaml
,.haroldrc.yml
,.haroldrc.js
, or.haroldrc.cjs
file - a
harold.config.js
orharold.config.cjs
CommonJS module exporting an object
You can configure the directory for md files (by default posts
) and the directory for md files layouts (by default blog-layouts
). Quite helpful because these names are also used in urls. For example, by default, /posts/name-of-the-post
(name of the .md file), but you might want to build the docs website and have /docs/name-of-the-doc
(name of the .md file).
You can also configure the name for output directory using outputDirName
and if you want to host your site in subdirectory you would also need to add hostDirName
.
Example of .haroldrc
(placed in the root of the app or in the src directory):
{
mdFilesDirName: 'docs',
mdFilesLayoutsDirName: 'docs-layouts',
outputDirName: 'dist',
hostDirName: 'subfolder-name'
}
Remember to change these directories' names after you init your app.
If you are using the search system, change postsPath
in harold-search.js
.
- Check if there are any breaking changes in the
CHANGELOG.md
- In your project, update the version of
harold-scripts
package
Below are ready-to-use recipes. You can take them as inspiration or copy it as it is and use in your custom template. See more at www.haroldjs.com
You can use postsList
Handlebars helper with perPageLimit
param. You can use tags as categories. Posts will be divided into sections and listed by tag name.
You can use the postsList
with byTagName
, which you should set up the same as the current post tag or tags. This way, you will be able to display a similar posts list. Remember to do this in the layout hbs file, not in Markdown files.
In many cases, there is a need to add some custom files to the root of your website. You can do this using the optional src/statics
directory. Example: src/statics/robots.txt
will be placed in build/robots.txt
next to your index.html file. You can also nest your directories like src/statics/some-dir/some-dir/file.txt
. It will land in build/some-dir/some-dir/file.txt
.
If you want to host Harold's website under your main username (username.github.io), you would need to rename your output directory to supported by Github. It is the docs
directory. You would need to create a .haroldrc
file and put the output directory name there.
{
outputDirName: 'docs',
}
Build your Harold app and push it to the repo. Remember to add the .gitignore
file, and exclude node_modules
but keep the output directory (docs
).
Configure your Github Pages to take the source from the docs
directory.
Here is the quick walk-through video on how to do that:
If you want to host Harold's website under the repository subdirectory name (username.github.io/my-blog), you need to add hostDirName
and remember to keep your paths in order. You can use the relativePath
handlebars helper. The default template (from v0.4.0) is already using it, so it should work as-is.
{
outputDirName: 'docs',
hostDirName: 'my-blog'
}
With Netlify, it is a little bit simpler. You just need to point to the Git branch and directory you want to deploy your site. You don't even need the source in the repo because Netlify will run the build scripts for you.
Here is the quick walk-through video on how to do that:
I wanted to have a simple static site generator to build and host on Netlify. There are many such solutions, but I wanted to have complete control.
What is essential, I equipped it with three templates that you can use and modify for your needs. I prepared the templates system for custom ones in the future. I also plan to provide some other complete thematic templates.
- when you want to build a static website/blog with simple search functionality (default theme)
- when you want to build a small (maybe medium) site or blog
- when you don't want to use any big and complicated solution
- when you know how to use the Handlebars template system
- when you want to build bigger projects (not tested with big projects, tested with over 120 markdown files, works quite fast)
- when you don't want to use Scss (you can still write standard CSS in .scss files) or Handlebars
- when you want to rely on something which has big community
MIT