dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

made requested updates 

I made the requested updates. Mostly just small formatting improvements.
This commit is contained in:
Tom Johnson 2016-12-26 18:48:42 -08:00 committed by GitHub
parent 9e1c613818
commit b37b433b60
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/_docs/templates.md
View File

@ -421,13 +421,13 @@ The default is `default`. They are as follows (with what they filter):
### Includes ### Includes
If you have small page fragments that you want to include in multiple places on your site, you can use the `include` tag: If you have small page snippets that you want to include in multiple places on your site, save the snippets as *include files* and insert them where required, by using the `include` tag:
```liquid ```liquid
{% raw %}{% include footer.html %}{% endraw %} {% raw %}{% include footer.html %}{% endraw %}
``` ```
Jekyll expects all include files to be placed in an `_includes` directory at the root of your source directory. In the above example, this will embed the contents of `_includes/footer.html` into the calling file. Jekyll expects all **include files** to be placed in an `_includes` directory at the root of your source directory. In the above example, this will embed the contents of `_includes/footer.html` into the calling file.
For more advanced information on using includes, see [Includes](../includes). For more advanced information on using includes, see [Includes](../includes).
@ -539,7 +539,7 @@ You can also use the `link` tag to create a link in Markdown as follows:
{% endraw %} {% endraw %}
``` ```
Including `{% raw %}{{site.baseurl}}{% endraw %}` is optional — it depends on whether you want the link to be absolute or root-relative. (Including `{% raw %}{{site.baseurl}}{% endraw %}` is optional — it depends on whether you want to preface the page URL with the `baseurl` value.)
The path to the post, page, or collection is defined as the path relative to the root directory (where your config file is) to the file, not the path from your existing page to the other page. The path to the post, page, or collection is defined as the path relative to the root directory (where your config file is) to the file, not the path from your existing page to the other page.