Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
one-click template to use just-the-docs on GitHub Pages
Just The Docs Template is a bare-minimum Jekyll starter repo that creates a documentation site using the Just the Docs theme and publishes it to GitHub Pages through a GitHub Actions workflow.
Just The Docs Template is a GitHub repository template that gives you a minimal Jekyll site configured with the Just the Docs theme, a Gemfile, and a GitHub Pages / Actions deployment workflow. You use it by clicking "use this template" on GitHub to generate a new repository; the output is a working documentation site that you edit by replacing the contents of index.md and README.md. It is maintained by the Just the Docs community and licensed under the MIT License.
Gemfile that loads the just-the-docs gem, so theme version is managed through standard Bundler commands.pages.yml workflow builds the Jekyll site and publishes it to GitHub Pages; you only need to select GitHub Actions as the build source in repository Settings.bundle install and bundle exec jekyll serve to build and preview the site locally at localhost:4000.jekyll-seo-tag plugin; additional plugins like jekyll-default-layout are added by editing both the Gemfile and _config.yml.docs directory of an existing project and modify pages.yml to build from that subdirectory._site and can be uploaded to any static hosting platform, not just GitHub Pages._config.yml, and the theme provides the standard Just the Docs navigation and layout system.index.md and others) and have them automatically built and deployed with every push to the main branch._config.yml to match their project.docs directory of a project repo, using the modified workflow that triggers builds only when files under docs/** change._config.yml, and publish via GitHub Pages by selecting GitHub Actions as the build source.Gemfile to change the Just the Docs theme version, and add Jekyll plugins by listing them in the Gemfile and the plugins key of _config.yml.bundle install and bundle exec jekyll serve, and view the site at localhost:4000 before pushing changes._site directory to any web host or content delivery network after building the site locally.The template works through GitHub's template repository system. First, you click "use this template" to create a new repository; then you enable publishing by going to Settings > Pages > Build and deployment and selecting GitHub Actions as the source. After that, a GitHub Actions workflow installs Ruby, sets up the Jekyll environment, builds the site, and deploys the output to GitHub Pages. The workflow is triggered on pushes to the main branch, and changes can take up to 10 minutes to appear on the published site.
After creating a repository from the template, go to Settings > Pages > Build and deployment, choose GitHub Actions as the Source, and push any changes to the main branch. The included Actions workflow handles building the Jekyll site and deploying it automatically; updates can take up to 10 minutes to go live.
No. The template is designed to build and publish on GitHub Pages through Actions, so you can edit files directly on GitHub and let the workflow build the site. Local installation of Jekyll and Bundler is only required if you want to preview the site with bundle exec jekyll serve.
Add the gem to your Gemfile, then add the plugin name to a plugins list in _config.yml. For example, adding jekyll-default-layout requires both gem "jekyll-default-layout" in the Gemfile and plugins: [jekyll-default-layout] in the config. The jekyll-seo-tag plugin is already included automatically.
Yes. Copy the template files into a docs directory, move pages.yml to .github/workflows, and edit the workflow to set working-directory: docs, use the path docs/_site/ for the upload artifact, and restrict the trigger to paths under docs/**.
The repository is licensed under the MIT License, so you are free to reuse and extend the code as long as you keep the original license notice. The deployment workflow is based on GitHub's starter workflows, which also use the MIT License.
