Skip to content

Commit dd88a2a

Browse files
updated guidelines
1 parent 0350a6a commit dd88a2a

File tree

1 file changed

+11
-9
lines changed

1 file changed

+11
-9
lines changed

Add_NEW_CONFERENCE_EDITION.md

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@ This guide provides step-by-step instructions for adding new conference editions
55
## Table of Contents
66
- [Content Directory Structure](#content-directory-structure)
77
- [1. Create Edition Content File](#1-create-edition-content-file)
8-
- [2. Add Session Content](#2-add-session-content)
9-
- [3. Add Speaker Information](#3-add-speaker-information)
8+
- [2. Move Session Content](#2-move-session-content)
9+
- [3. Add New Speaker Information](#3-add-new-speaker-information-if-already-exists-skip-this-step)
1010
- [Important Notes](#important-notes)
1111
- [Best Practices](#best-practices)
1212

@@ -79,7 +79,7 @@ Detailed description of the conference edition.
7979
Additional information and links.
8080
```
8181

82-
## 2. Add Session Content
82+
## 2. Move Session Content
8383

8484
1. Navigate to the `content/archive-sessions/` directory
8585
2. Create a new directory named `YYYY/` (replace YYYY with the year)
@@ -95,7 +95,7 @@ editionLink: "/previous-editions/YYYY/"
9595
Description of the sessions for this edition (For example, Browse through all sessions from the JSON Schema Conference YYYY. Click on a session to view details, watch the presentation, and access related resources.)
9696
```
9797

98-
4. Add individual session files in the `content/archive-sessions/YYYY/` directory with the following structure:
98+
4. Move all session files from `content/sessions/` to `content/archive-sessions/YYYY/`. Each session file should maintain structure below:
9999

100100
```yaml
101101
---
@@ -118,13 +118,15 @@ draft: false
118118
Session description and content.
119119
```
120120

121-
## 3. Add Speaker Information
121+
## 3. Add New Speaker Information (if the speaker already exists, then skip this step)
122122

123123
1. Navigate to the `public/speakers` directory
124-
2. Check if the speaker already exists by searching for their name in the `speakers/` directory
125-
3. If the speaker does not exist:
126-
- Create a new directory named after the speaker (e.g., `utkarsh/`)
127-
- Inside the new directory, create an index.html file which follows the previous speaker's index.html structure with the modified content based on the new speaker's information
124+
2. For each speaker in the current conference:
125+
- Check if the speaker already exists by searching for their name in the `speakers/` directory
126+
- If the speaker does not exist:
127+
- Create a new directory named after the speaker (e.g., `utkarsh/`)
128+
- Create an index.html file in their directory.
129+
- Follow the existing speaker's index.html structure while updating the content with the new speaker's information
128130

129131
## Important Notes
130132

0 commit comments

Comments
 (0)