HPCE/gitea-pages
0
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Activity

fixing permalink note in post docs. fixing permalink on news.html file.

Browse Source
This commit is contained in:
tomjohnson1492
2016-07-20 07:18:35 -07:00
parent 37a0e4fef0
commit 3d0af7420b
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
pages/mydoc/mydoc_posts.md
View File

@ -28,7 +28,7 @@ title: My sample post
keywords: pages, authoring, exclusion, frontmatter keywords: pages, authoring, exclusion, frontmatter
summary: "This is some summary frontmatter for my sample post." summary: "This is some summary frontmatter for my sample post."
sidebar: mydoc_sidebar sidebar: mydoc_sidebar
permalink: mydoc_pages/ permalink: mydoc_pages.html
tags: content_types tags: content_types
--- ---
@ -39,7 +39,7 @@ tags: content_types
| **tags** | Optional | Tags for the page. Make all tags single words, with underscores if needed. Separate them with commas. Enclose the whole list within brackets. Also, note that tags must be added to \_data/tags_doc.yml to be allowed entrance into the page. This prevents tags from becoming somewhat random and unstructured. You must create a tag page for each one of your tags following the sample pattern in the tabs folder. (Tag pages aren't automatically created.) | | **tags** | Optional | Tags for the page. Make all tags single words, with underscores if needed. Separate them with commas. Enclose the whole list within brackets. Also, note that tags must be added to \_data/tags_doc.yml to be allowed entrance into the page. This prevents tags from becoming somewhat random and unstructured. You must create a tag page for each one of your tags following the sample pattern in the tabs folder. (Tag pages aren't automatically created.) |
| **keywords** | Optional | Synonyms and other keywords for the page. This information gets stuffed into the page's metadata to increase SEO. The user won't see the keywords, but if you search for one of the keywords, it will be picked up by the search engine. | | **keywords** | Optional | Synonyms and other keywords for the page. This information gets stuffed into the page's metadata to increase SEO. The user won't see the keywords, but if you search for one of the keywords, it will be picked up by the search engine. |
| **summary** | Optional | A 1-2 word sentence summarizing the content on the page. This gets formatted into the summary section in the page layout. Adding summaries is a key way to make your content more scannable by users (check out [Jakob Nielsen's site](http://www.nngroup.com/articles/corporate-blogs-front-page-structure/) for a great example of page summaries.) The only drawback with summaries is that you can't use variables in them. | | **summary** | Optional | A 1-2 word sentence summarizing the content on the page. This gets formatted into the summary section in the page layout. Adding summaries is a key way to make your content more scannable by users (check out [Jakob Nielsen's site](http://www.nngroup.com/articles/corporate-blogs-front-page-structure/) for a great example of page summaries.) The only drawback with summaries is that you can't use variables in them. |
| **permalink**| Required | This theme uses permalinks to facilitate the linking. You specify the permalink want for the page, and the \_site output will put the page into the root directory when you publish. The page will appear inside a folder by the same name, with the actual page being index.html. Browsers will automatically show the index.html file inside of any folder, so permalinks avoid the .html extension with file names. Permalink names don't have to match your file names, but it might be easier to keep them in sync. | | **permalink**| Required | This theme uses permalinks to facilitate the linking. You specify the permalink want for the page, and the \_site output will put the page into the root directory when you publish. Follow the same convention here as you do with page permalinks -- list the file name followed by the .html extension. |
{% include links.html %} {% include links.html %}

2
pages/news/news.html
View File

@ -13,7 +13,7 @@ folder: news
{% for post in site.posts limit:10 %} {% for post in site.posts limit:10 %}
<h2><a class="post-link" href="{{ post.url }}">{{ post.title }}</a></h2> <h2><a class="post-link" href="{{ post.url | remove: "/" }}">{{ post.title }}</a></h2>
<span class="post-meta">{{ post.date | date: "%b %-d, %Y" }} / <span class="post-meta">{{ post.date | date: "%b %-d, %Y" }} /
{% for tag in post.tags %} {% for tag in post.tags %}
<a href="{{ "tag_" | append: {{tag}}.html">{{tag}}</a>{% unless forloop.last %}, {% endunless%} <a href="{{ "tag_" | append: {{tag}}.html">{{tag}}</a>{% unless forloop.last %}, {% endunless%}