Customizing the content on your site

Introduction

By default Academic Pages provides five different types of content that are used to generate pages:

• Blog Posts - found in _posts, these are structed as Markdown files (*.md) and support tagging by category tags by default.
• Portfolio - found in _portfolio, these can either be Markdown files (*.md) and parsed as such, or HTML files (*.html) where everything below the heading with be parsed as HTML. These support grouping by collection by default.
• Publications - found in _publications, these are intended to list publications (e.g., manuscripts, books, etc.) along citation information, abstracts, and downloads if desired.
• Talks - found in _talks, these are intended to list talks given in reverse chronological order (i.e., newest to oldest).
• Teaching - found in _teaching, these are intended to list classes talked in reverse chronological order (i.e., newest to oldest).

Collections and Categories

Within Academic Pages the majority of user content is classified as either a collection or a category. Collections include entries that make up the Portfolio, Publications, Talks, and Teaching and each has a different rendering pathway that allows for customization of the relevant aggregate page. Whereas category is intended to offer an additional level of filtering for blog posts and similar entries. Much of this distinction is limited to the programming of the template and rendering of websites that make use of the Academic Pages template.

Order of Publications

The default order of publications is controlled by the following in _pages/publications.md

{% for post in site.publications reversed %}
  {% include archive-single.html %}
{% endfor %}

The reversed keyword results in the entries being listed in reverse chronological order (i.e., newest to oldest), removing the keyword will result in chronological order (i.e., oldest to newest).

Order of Portfolio

The default order of publications is controlled by the following in _pages/portfolio.html

{% for post in site.portfolio %}
  {% include archive-single.html %}
{% endfor %}

In this case, the lack of the reversed keyword after site.portfolio indicates that the entries will be listed in chronological order (i.e., oldest to newest), adding the keyword as in the following example will result in reverse chronological order (i.e., newest to oldest):

{% for post in site.portfolio reversed %}
  {% include archive-single.html %}
{% endfor %}