Introduction theme for Hugo
Introduction is a minimalist, highly-versatile theme for Hugo. It can be configured as a single page, or as a full-featured site with multiple sections. It is multilingual, responsive, and includes a light and dark theme.
- Multilingual - supports side-by-side content in different language versions
- Custom index page sections from Markdown files
- Projects and Blog sections
- Page load fade-in CSS effect and smooth scrolling to anchor links
- Straightforward customization via
- Styled Markdown throughout with syntax highlighting
- Sass files included with instant compiling to CSS thanks to Hugo Pipes and PostCSS
- Thoughtful use of Sass variables makes creating new colour schemes easy
- Extended version of Hugo (latest version recommended)
- To make changes to the theme CSS:
Get the theme
Run from the root of your Hugo site:
$ git clone https://github.com/victoriadotdev/hugo-theme-introduction.git themes/introduction
Alternatively, you can include this repository as a git submodule. This makes it easier to update this theme if you have your Hugo site in git as well:
$ git submodule add https://github.com/victoriadotdev/hugo-theme-introduction.git themes/introduction
Preview the theme
Introduction ships with an fully configured example site. For a quick preview:
cd exampleSite/ hugo serve --themesDir ../..
http://localhost:1313/ in your browser to view the example site.
The following explains how to add content to your Hugo site. You can find sample content in the
hugo new home/index.md
title frontmatter will be the first large heading.
The content of
index.md will be shown as a subtitle line.
You might want to set
true in the frontmatter. See headless bundles for more information.
Content for the home page lives under
content/home/. You may add as many files as you want to in markdown format.
Each markdown file will show as a section on the home page and can be ordered by the
weight value in the file's frontmatter. You can set
image to show an image on the left side of the section. The image file must be in the
You may add a contact section by creating
hugo new home/contact.md
This will always be shown as the last section on the home page.
Introduction provides an easy way to showcase your projects. Each project can even have its own gallery, shown as an image carousel.
Start by creating an index file for the projects section:
hugo new projects/_index.md
title and some optional content to the file.
Add an optional
weight for ordering projects section.
To create a project, run:
hugo new projects/YourProjectName/index.md
The frontmatter of your new file contains some comments to help your configure your project.
You can set
external_link to make the project link to another website.
Add images to your project by placing image files in the
YourProjectName/ folder. If you add more then one photo, they will display as a carousel gallery. Images will be ordered by filename. The first image will be shown as the project preview image. You can change the order of your images by adding a
weight to that resource's parameters:
resources: - src: NameOfYourImage.jpg params: weight: -100
Create an index file for the blog:
hugo new blog/_index.md
Add an optional
weight for ordering blog section on your homepage
Create a new blog post with:
hugo new blog/YourEntryTitle.md
Posts will also display in the Blog section of the home page.
Configure your site
config.toml to the root folder of your Hugo site and change the fields as you like. Helpful comments are provided.
Introduction currently ships with support for English, German, Spanish and French. Contributions for other language translations are welcome.
To create a new language translation, add the
.toml file to the
i18n/ folder. See the existing files for the necessary fields.
See the hugo documentation for more details.
Introduction contains a default menu. If you want to override this, you can do so by defining a
config.toml to activate Hugo's internal Google Analytics template.
config.toml to activate Hugo's internal Disqus template.
You can add custom css files by placing them under
assets/ and adding the path to the file to
If you have a question or get stuck, please open an issue for help and to help those who come after you. The more information you can provide, the better!