Read the Content Editing section of the main README.
- The filename you choose determines the speaker page URL
- The
id
property should be the same as the filename
Example
---
name: Firstname Lastname
id: firstname-lastname
talk_id: my-cool-talk
company: "Speaker Company"
location: "City, Country"
featured: true
intro: "Intro text for speaker. Yes, I saw. You were doing well, until everyone died."
links:
- text: "@twitterhandletest"
url: "https://twitter.com/twitterhandletest"
- text: "example.com"
url: "http://example.com/"
---
Dr. Zoidberg, that doesn't make sense. But, okay! Is today's hectic lifestyle making you tense and impatient? Actually, that's still true. Good news, everyone! I've taught the toaster to feel love! And then the battle's not so bad? Bender, hurry! This fuel's expensive! Also, we're dying! Of all the friends I've had… you're the first. Who are you, my warranty?! No! The kind with looting and maybe starting a few fires!
id
: unique id for the speaker. Should correspond to the all lowercase filename (in the example that'd befirstname-lastname.md
)talk_id
: the id of the talk this speaker will give. Corresponds to a filename (without.md
-extension) in../_talks
.name
: the name of the speaker to be displayed in the header of the site.company
: the company of the speaker, will be displayed along with the name in teaser and speaker-header.featured
: if set to any value, speaker will appear on front pageintro
: the opening-paragraph for the speaker pagelinks
: a sorted list of links to appear below the speaker description. Each link has to contain the fieldstext
andurl
.- the content of the document (everything behind the "frontmatter"-/metadata-block – that is, after the
---
) is the content part of the speaker details page.