66 lines
2.0 KiB
Markdown
66 lines
2.0 KiB
Markdown
# Add new blog post
|
|
|
|
1. Create new directory at
|
|
`/content/talks/yyyy-mm-dd-talk-title-event-name` and `index.md` in
|
|
the same directory and populate with the following metadata:
|
|
|
|
```toml
|
|
+++
|
|
title = "title of the talk"
|
|
date = "yyyy-mm-dd"
|
|
description = "description of talk, will be displayed in talk listing"
|
|
|
|
[taxonomies]
|
|
tags = ['gna']
|
|
|
|
[extra]
|
|
# **Only use author nicks in blog post Markdown files, it is used to lookup author details.**
|
|
author = 'imbatman' # speaker nickname
|
|
+++
|
|
```
|
|
|
|
2. Add author details in [`config.toml`](../config.toml) in `authors`
|
|
under `extra` section:
|
|
|
|
```toml
|
|
[extra]
|
|
# Put all your custom variables here
|
|
authors = [
|
|
{ "nick"="imbatman", name="Batman", "website"="https://batman.example.org" },
|
|
{ "nick"="superman", name="Superman", "website" ="https://superman.example.org" }
|
|
]
|
|
```
|
|
|
|
This information is used to render speaker and author information in
|
|
talks and blog posts respectively. **Only use author nicks in talks post
|
|
Markdown files, it is used to lookup author details.**
|
|
|
|
3. Add content to about the talk to the file created in step 1.
|
|
|
|
4. Add talk-related resources like slides and related material in the
|
|
directory created in step 1. They will be accessible via relative
|
|
URLs. For instance:
|
|
|
|
```bash
|
|
➜ website git:(master) ✗ tree content/talks/22-04-2022-hostea-introducing-hostea-forgefriends-monthly-meet
|
|
content/talks/22-04-2022-hostea-introducing-hostea-forgefriends-monthly-meet
|
|
├── index.md
|
|
└── slides
|
|
├── 2022-04-22-forgefriends-introducing-hostea.odp
|
|
└── 2022-04-22-forgefriends-introducing-hostea.pdf
|
|
|
|
1 directory, 3 files
|
|
```
|
|
|
|
```markdown
|
|
## Resources
|
|
|
|
- [slides(ODP)](./slides/2022-04-22-forgefriends-introducing-hostea.odp)
|
|
- [slides(PDF)](./slides/2022-04-22-forgefriends-introducing-hostea.pdf)
|
|
```
|
|
|
|
**WARNING: Don't storing large images or videos in Git repositories,
|
|
using content hosting services and link to them**
|
|
|
|
5. Commit and push to deploy talk details! 🎉
|