Creating Pages or News - Parallel-in-Time/parallel-in-time.github.io GitHub Wiki

If you don't need one of the given YAML field, leave it empty or remove it.

Most pages have a subnavbar entry in their YAML header. This field is used as an identifier in the dropdown subnavigation. You will want to give a short unique identifier here.

The date of a page is the datetime of its first creation and update should be set and updated to the current datetime whenever updates are made to that page. A datetime is always of the form:

YYYY.MM.DD HH:MM:SS +ZZZZ

where +ZZZZ is the time zone in HHMM notation relative to UTC. For DST in Europe/Berlin, this would be +0200 and for DST in Los Angeles -0700.

A boolean value to specify, whether the date or update time should be visible at the end of the page.

Some pages can have a short_desc field. The text entered here will show up on the overview pages, e.g. for projects or groups.

Copy the news post template into the _posts folder, rename it to be a .md file while complying with the naming convention and fill in its content appropriately.

The YAML field categories is either empty or a list of keywords for this news entry. They will show up at the end of the news post and link to other news entries with the same category.

Within the content of the news post, you can use one separator <!--more--> to indicate the end of the teaser. Usually, the teaser is the first paragraph and should end with this separator. On the news index page only the teaser will be shown and the whole news post if no separator has been used.

Code pages, those which show up in parallel-in-time.github.io/codes/, reside in the _codes folder. To add a new code, copy the code template into this folder, rename it to be a .md file and fill it with your content accordingly. It will automatically/-magically show up on the codes index page and as a link in the navigation drop down.

The developers YAML field is a list of developers, which will show up in the sidebar. Each developer has a name, email and optional boolean flag to indicate, whether he or she is a lead developer of that code.

The github_repo YAML field must be of the form <username>/<repo> as given by GitHub.

The events are split up into two groups: upcoming and past.

To add a new event (upcoming or past), copy the appropriate template (event past template or event past template) into the corresponding folder (_events_past or _events_upcoming), rename it to be a .md file while complying with the naming convention and fill it with your content accordingly. It will automatically/-magically show up on the events index page and as a link in the navigation drop down.

Just move the .markdown file from _events_upcoming to _events_past and change the subnavbar YAML field in it from Upcoming to Past as well as in the field permalink replace upcoming by past.
That's it.

Group pages, those which show up in parallel-in-time.github.io/groups/, reside in the _groups folder. To add a new group, copy the group template into this folder, rename it to be a .md file and fill it with your content accordingly. It will automatically/-magically show up on the groups index page and as a link in the navigation drop down.

The members YAML field is a list of the group members, which will show up in the sidebar. Each member has a name, email and optional boolean flag to indicate, whether he or she is the corresponding member, i.e. group head.

Method pages, those which show up in parallel-in-time.github.io/methods/, reside in the _methods folder. To add a new method, copy the method template into this folder, rename to be a .md file and fill it with your content accordingly. It will automatically/-magically show up on the methods index page and as a link in the navigation drop down.

Project pages, those which show up in parallel-in-time.github.io/projects/, reside in the _projects folder. To add a new project, copy the project template into this folder, rename to be a .md file and fill it with your content accordingly. It will automatically/-magically show up on the projects index page and as a link in the navigation drop down.