Edit Content

Edit member profiles

Build the website locally

While editing the content of the website, you may want to check the actual visual rendering of your edits. In such case you'll need to use Hugo and the submodule(s) (check out the Installation section). Once installed, you will have to run hugo server: like so:

hugo server

This will return a message, something like:

Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)

You can copy paste http://localhost:1313/ is your web browser. The command hugo server start a watcher, so basically each time you change the content, it will update the local website!

Edit your data

Your name, role and links to your online profiles should be included in a .yaml file stored in data/members. For instance, the path to the file that stored details about Kevin Cazelles should be found in data/members/kevin_cazelles.yaml. Currently the options available are:

given_name: Kevin
family_name: Cazelles
info: kevin_cazelles
role: Post-doctoral fellow
alumni: false
github: KevCaz
twitter: KCazelles
researchgate: Kevin_Cazelles
website: http://kevincazelles.fr
orcid: 0000-0001-6619-9874
impactstory: 0000-0001-6619-9874
gscholar: xzvcu7cAAAAJ&hl
linkedin: kevin-cazelles-51552283
phone: +1 519 824 4120 (ext. 53700)
email: kcazelle@uoguelph.ca

Also publons is supported, e,g. publons: 1387840/timothy-bartley/.

Once the file filled out: your name, role and links to your online profiles will be automatically added to your profile. Note that info should is the name of the file (or folder) that includes your bio (see below).

Edit your bio

In order to edit your bio you have to edit the content of the content/members folder, there are two options:

1. create a folder that has your names and a Markdown file index.md file within, e.g. content/members/kevin_cazelles/index.md

2. create a Markdown file with your name, e.g. content/members/kevin_cazelles.md.

I recommend option 1 as you'll be able to store optional files (such as images) within this folder and using option 1 makes the search of those files pretty easy.

In your Markdown file, you'll simply add a YAML header:

---
member: kevin_cazelles
layout: members
---

layout indicates the type of the web page you are writing and the member filed is used to specify where your data are stored in the data/ folder and therefore you should provide the names of this file without extension so here as my file data in kevin_cazelles.yaml I used kevin_cazelles.

Edit the blog

WIP

Push your changes to update the website

To upload your changes you simply have to add your changes (git add -A), commit (git commit) and then push them (git push), Travis CI will do the rest. As always, be careful and merge the branch on GitHub first (git pull)!