.github
_data
_includes
_layouts
_sass
assets
docs
_data
_docs
01-quick-start-guide.md
02-structure.md
03-installation.md
04-upgrading.md
05-configuration.md
06-overriding-theme-defaults.md
07-navigation.md
08-ui-text.md
09-authors.md
10-layouts.md
11-posts.md
12-pages.md
13-collections.md
14-helpers.md
15-utility-classes.md
16-stylesheets.md
17-javascript.md
18-history.md
19-contributing.md
20-docs-2-2.md
21-license.md
_drafts
_layouts
_pages
_pets
_portfolio
_posts
_recipes
assets
Gemfile
_config.dev.yml
_config.yml
screenshot-layouts.png
screenshot.png
test
.editorconfig
.gitattributes
.gitignore
.travis.yml
CHANGELOG.md
Gemfile
LICENSE
README.md
Rakefile
_config.yml
banner.js
index.html
minimal-mistakes-jekyll.gemspec
package-lock.json
package.json
screenshot-layouts.png
screenshot.png
staticman.yml
1.3 KiB
1.3 KiB
title, permalink, excerpt, last_modified_at
title | permalink | excerpt | last_modified_at |
---|---|---|---|
Working with Pages | /docs/pages/ | Suggestions and Front Matter defaults for working with pages. | 2016-11-03T11:13:12-04:00 |
To better organize all of your pages you can centralize them into a single location similar to posts and collections.
Step 1: Start by placing pages (.md
or .html
files) into a _pages
directory. Meaningfully naming files should be the goal. Avoid patterns like /about/index.md
as it makes distinguishing between multiple index.md
files harder.
sample-project
└── _pages/
├── 404.md # custom 404 page
├── about.md # about page
└── contact.md # contact page
Step 2: Include pages to be sure Jekyll "sees" and processes the files inside of _pages
. Add include: ["_pages"]
to _config.yml
.
Step 3: Assign permalink overrides in the YAML Front Matter of each.
Examples:
filename | permalink |
---|---|
_pages/about.md | permalink: /about/ |
_pages/home.md | permalink: / |
_pages/contact.md | permalink: /contact/ |
Recommended Front Matter Defaults:
defaults:
# _pages
- scope:
path: ""
type: pages
values:
layout: single
author_profile: true