-
Notifications
You must be signed in to change notification settings - Fork 115
Editing Pages
The same steps apply as for adding new content. Make sure you have read and understood the Contributor's Workflow. Especially, make sure, you have updated your local copy.
The following steps are to be done in Step 2 of the Contributor's Workflow, after you have switched onto a separate branch.
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 automaticallymagically show up on the events index page.
Continue with Step 3 of the Contributor's Workflow.
Just move the corresponding .md file from _events_upcoming to _events_past.
That's it.
Continue with Step 3 of the Contributor's Workflow.
The same steps apply as for adding new content. Make sure you have read and understood the Contributor's Workflow. Especially, make sure, you have updated your local copy.
The following steps are to be done in Step 2 of the Contributor's Workflow, after you have switched onto a separate branch.
The most five recent news will show up on the front page. All news will show up on both the news index page and the news archive.
Before adding a new news post, read the source of the news_post template carefully.
To add a new news post, copy the news_post template into the _posts folder, rename it to be a .md file while complying with the news post naming convention and fill it with your content accordingly.
It will automaticallymagically show up on the site's front page.
Continue with Step 3 of the Contributor's Workflow.
The same steps apply as for adding new content. Make sure you have read and understood the Contributor's Workflow. Especially, make sure, you have updated your local copy.
The following steps are to be done in Step 2 of the Contributor's Workflow, after you have switched onto a separate branch.
Project pages, those which show up on the projects index page under all topics they belong to, reside in the _projects folder.
There is a speciality with project pages, as they will be used by an automated script to generate the LaTeX sources for the annual JLESC report. The curious can read more about the LaTeX Report Generator.
Before adding a new project, read the source of the project_page template carefully.
Adding a new project starts with two steps:
-
Copy the
project_pagetemplate to the_projectfolder and rename it according to the scheme describe in the template's "How To Use This Template"-comment. -
Copy the accompanying BibTeX file for the project's external references to the
_bibliography/externalsfolder and name it exactly as the project file. But with the file extension.bibinstead of.md.
Now follow the instructions in both the project file and the corresponding BibTeX file closely.
Follow them both to the very end of the files!
Continue with Step 3 of the Contributor's Workflow.
The same steps apply as for adding new content. Make sure you have read and understood the Contributor's Workflow. Especially, make sure, you have updated your local copy.
The following steps are to be done in Step 2 of the Contributor's Workflow, after you have switched onto a separate branch.
Software pages, those which show up on the software index page, reside in the _software folder.
Before adding a new software, read the source of the software_page template carefully.
To add a new software, copy the software_page template into the _software folder, rename it to be a .md file and fill it with your content accordingly.
It will automaticallymagically show up on the software index page.
Please, by all means, notify us when anything is unclear in this wiki or the in-source documentation!