Rockingcool
/
paige-hugo
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
My fork of the Paige theme for Hugo (https://github.com/willfaught/paige), with some modifications for my guitar website. See the 'myFork' branches for changes I made.
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
83 Commits
2 Branches
0 Tags
18 MiB
HTML 87.4%
CSS 11.4%
Python 0.9%
SCSS 0.3%
 
 
 
 
myFork
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '30ce9bcbf2'
${ noResults }
Go to file
Will Faught 30ce9bcbf2 Add more screenshots 3 years ago
.github/workflows Restore page_url config 3 years ago
archetypes Initial commit 3 years ago
exampleSite Change empty lists to show page title 3 years ago
images Add more screenshots 3 years ago
layouts Change empty lists to show page title 3 years ago
LICENSE Initial commit 3 years ago
README.md Add more screenshots 3 years ago
config.toml Add config.toml 3 years ago
go.mod Add go.mod 3 years ago
theme.toml Fix theme homepage 3 years ago

README.md

paige

A simple Hugo theme. Try it out.

Screenshots

Home page:

Single page:

List page:

Taxonomy page:

Term page:

404 page:

Markdown example:

Rich content example:

Placeholder text example:

Math typesetting example:

Emoji support example:

Features

  • Blog
  • Facebook sharing support
  • Google Analytics support
  • Landing page
  • Light color scheme
  • Menu navigation
  • Minimal design
  • Responsive, mobile-first layout
  • Sections for other kinds of content
  • Single column presentation
  • Social links
  • Twitter sharing support

Design

HTML metadata is set automatically. The HTML author is the site author. The HTML description is the page description. The HTML keywords is a union of the page keywords, tags, and categories. Enhanced Facebook and Twitter sharing is enabled. Google Analytics is included at the bottom of the body, if configured. You must create favicons yourself.

The HTML title is the page title, followed by a middle dot, followed by the site title. If one is missing, the other is used without the middle dot. If both are the same, only one is used without the middle dot.

The HTML body can have a header, a body, and a footer. The header has the section menus, if any; the page title, if any; the page description, if any; and the page date, if any. The body has the page content, if any. The footer has the site copyright notice, if any.

The section menus are activated if their path matches the current page. Pages in the directory content/ match the section path /. Pages in the directory content/foo/ match the section path /foo/. The section menu identifiers, names, weights, paths, and order are configured in config.yaml.

The page date is the publish date, if any; otherwise, it's the creation date.

Everything is stacked vertically in one column and aligned to the center.

The home page shows the blurb, description, greeting, and title parameters from content/_index.md, the avatar.jpg and cover.jpg images at the site root, and linked icons for all the social sites configured in config.yaml.

Single pages use the link front matter parameter, if any, as the reference for an anchor around the page title, if any.

List and term pages show page titles and descriptions per month and year in descending order. An empty list has a "Nothing here" body.

Taxonomy pages list term links in an inline, unordered, sorted list.

The 404 page has a "Not Found" header, and no body.

If partials/head.html exists in the site, it is included at the end of the head tag. If partials/body.html exists in the site, it is included at the end of the body tag.

Stock Bootstrap 5.2.2 CSS and JavaScript, and Bootstrap Icons 1.10.2, are used for style, functionality, and icons. They're loaded from the Bootstrap CDN for every page.

Configuration

See the example site directory for an example configuration.

Credits