Skip to content

Commit 39a235a

Browse files
committed
Data file description
1 parent 20041ff commit 39a235a

File tree

1 file changed

+84
-0
lines changed

1 file changed

+84
-0
lines changed

README.md

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,3 +44,87 @@ kept in separate files and then is injected to the template via plugins kept in
4444

4545
Pull requests should go to `source` branch (not master) since travis builds the
4646
website from there.
47+
48+
A short description of the data files follow:
49+
50+
### Data
51+
52+
#### `publications.yml`
53+
54+
This contains publications that get displayed on the
55+
[/publications](http://reichlab.io/publications) page. A full featured entry for
56+
a publication looks something like the following:
57+
58+
```yaml
59+
title: Title of the publication
60+
doi: >
61+
[Optional] doi like 10.1371/journal.pone.0035564. This adds the links for
62+
'Open doi link' and 'Save to mendeley'.
63+
slug: >
64+
Unique identifier which also maps to a pdf in ./pdfs/publications/<slug>.pdf
65+
(in case a pdf link is not provided) and an image in
66+
./images/publications/<slug>.png
67+
journal: [Optional] Journal name
68+
year: year
69+
volume: [Optional] volume
70+
pages: [Optional] pages
71+
authors: Name of authors (this should be a yaml list but is just a string right now)
72+
keywords: >
73+
[Optional] Comma separated keywords (this also should be a list but is string
74+
as of now)
75+
abstract: Abstract
76+
preprint: [Optional] Link to a preprint
77+
pdf: >
78+
[Optional] Link to pdf. This takes priority over
79+
./pdfs/publications/<slug>.pdf
80+
github: [Optional] Github repository identifier like <user>/<repo>
81+
```
82+
83+
#### `team.yml`
84+
85+
This contains information about lab members. An entry looks like this:
86+
87+
```yaml
88+
name: Member name
89+
role: Role
90+
description: Blurb
91+
image: >
92+
A full url to an image (like https://example.com/image.png) or path to local
93+
image file (like /images/people/foo.png)
94+
# Links is a list of links the member wants to show under his/her description
95+
# In case of no links, put '[]' (empty list) here.
96+
links:
97+
- name: Link name
98+
url: Url
99+
- name: Link 2
100+
url: Url
101+
type: >
102+
[Optional] The type of member. This is different than role and is used to
103+
categorize list of members in sections like 'Alumni'.
104+
```
105+
106+
#### `research` and `teaching` sections
107+
108+
Both the [research](http://reichlab.io/research) and
109+
[teaching](http://reichlab.io/teaching) page are organized in terms of sections
110+
or themes which map to a set of markdown files in the directories `_research`
111+
and `_teaching` respectively. Each files contains metadata in its _yaml front
112+
matter_ and the section's summary as its main text. Here is an example markdown
113+
file:
114+
115+
```md
116+
---
117+
title: Section title text
118+
image: /images/research/foo.png # The image for the section
119+
# A list of projects which can either be a github identifier or a dictionary
120+
# with title and description keys
121+
projects:
122+
- user/repo
123+
- group/repo
124+
- title: Project title
125+
description: Project description
126+
publications: >
127+
[Optional] Comma separated keywords mapping to that of _data/publications.yml
128+
---
129+
Here goes the section summary.
130+
```

0 commit comments

Comments
 (0)