mirror of
https://github.com/gohugoio/hugo.git
synced 2026-09-02 11:42:37 +00:00
Fix typos on lookup order page
This commit is contained in:
@@ -30,7 +30,7 @@ Most Hugo websites will only need the default template files at the end of the l
|
|||||||
|
|
||||||
The lookup order is best illustrated by example. The following shows you the process Hugo uses for finding the appropriate template to render your [single content][], but the concept holds true for all templates in Hugo.
|
The lookup order is best illustrated by example. The following shows you the process Hugo uses for finding the appropriate template to render your [single content][], but the concept holds true for all templates in Hugo.
|
||||||
|
|
||||||
1. The project is using the theme `mytheme`, which would be specified as `theme: mytheme` or `theme = "mytheme` in the project's [`config.toml` or `config.yaml`][config], respectively.
|
1. The project is using the theme `mytheme`, which would be specified as `theme: mytheme` or `theme = "mytheme"` in the project's [`config.toml` or `config.yaml`][config], respectively.
|
||||||
2. The layouts and content directories for the project are as follows:
|
2. The layouts and content directories for the project are as follows:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
@@ -61,10 +61,10 @@ The lookup order is best illustrated by example. The following shows you the pro
|
|||||||
```
|
```
|
||||||
|
|
||||||
|
|
||||||
Now we can look at the front matter for the three single-page content (i.e.`.md`) files.
|
Now we can look at the front matter for the three content (i.e.`.md`) files.
|
||||||
|
|
||||||
{{% note %}}
|
{{% note %}}
|
||||||
You may notice there are four markdown files but we are only going to review three for the *single* page lookup order. `_index.md` may seem like a single page of content but is actually a specific `kind` in Hugo. Whereas `my-first-post.md`, `my-second-post.md`, and `my-first-event.md` are all of kind `page`, all `_index.md` files in a Hugo project are used to add content and front matter to list pages. `events/_index.md` will render according to its [section template](/templates/section-templates/) and respective lookup order.
|
There are four markdown files but we are only going to review three for the *single* page lookup order. `_index.md` may seem like a single page of content but is actually a specific `kind` in Hugo. Whereas `my-first-post.md`, `my-second-post.md`, and `my-first-event.md` are all of kind `page`, all `_index.md` files in a Hugo project are used to add content and front matter to list pages. In this example, `events/_index.md` will render according to its [section template](/templates/section-templates/) and respective lookup order.
|
||||||
{{% /note %}}
|
{{% /note %}}
|
||||||
|
|
||||||
### Example: `my-first-post.md`
|
### Example: `my-first-post.md`
|
||||||
|
|||||||
@@ -26,8 +26,8 @@ Hugo assumes your content section and content type are the same unless you tell
|
|||||||
3. `/layouts/<TYPE>/single.html`
|
3. `/layouts/<TYPE>/single.html`
|
||||||
4. `/layouts/<SECTION>/single.html`
|
4. `/layouts/<SECTION>/single.html`
|
||||||
5. `/layouts/_default/single.html`
|
5. `/layouts/_default/single.html`
|
||||||
6. `/themes/<THEME>/layouts/<TYPE>/<LAYOUT.html`
|
6. `/themes/<THEME>/layouts/<TYPE>/<LAYOUT>.html`
|
||||||
7. `/themes/<THEME>/layouts/<SECTION>/LAYOUT.html`
|
7. `/themes/<THEME>/layouts/<SECTION>/<LAYOUT>.html`
|
||||||
8. `/themes/<THEME>/layouts/<TYPE>/single.html`
|
8. `/themes/<THEME>/layouts/<TYPE>/single.html`
|
||||||
9. `/themes/<THEME>/layouts/<SECTION>/single.html`
|
9. `/themes/<THEME>/layouts/<SECTION>/single.html`
|
||||||
10. `/themes/<THEME>/layouts/_default/single.html`
|
10. `/themes/<THEME>/layouts/_default/single.html`
|
||||||
|
|||||||
@@ -12,7 +12,6 @@
|
|||||||
}
|
}
|
||||||
@include MQ(XL) {
|
@include MQ(XL) {
|
||||||
top: .3em;
|
top: .3em;
|
||||||
// right:1em;
|
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user