Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove hard coded title in Schedule #674

Closed
plaindocs opened this issue Sep 9, 2018 · 1 comment
Closed

Remove hard coded title in Schedule #674

plaindocs opened this issue Sep 9, 2018 · 1 comment
Assignees
@mxsasha

Comments

@plaindocs
Copy link
Contributor

The eu-2018-day-2.yaml etc files should use the talk title from 2018-prague-speakers.yaml

FAO @ericholscher @kelly-o
@plaindocs
Copy link
Contributor Author

Which would make it harder to read but also harder for errors to propagate.

We only use the schedule files in 1 place, so it could just be a case of storing and index or key for the speaker name and talk title and using those from the speakers yaml file.

@mxsasha mxsasha self-assigned this Jun 25, 2019
@mxsasha mxsasha mentioned this issue Jun 25, 2019
Closed
@mxsasha mxsasha mentioned this issue Jul 9, 2019
Merged
19 tasks
mxsasha added a commit that referenced this issue Jul 30, 2019
@mxsasha
Fix #674, fix #480 - Refactor schedule/session YAML process.
c471a3a 
For >=2020 websites, the schedule YAML is greatly simplified
and linked to the session (formerly speaker) YAML.
In addition, this commit introduces caching for conference context data.
mxsasha added a commit that referenced this issue Aug 6, 2019
@mxsasha
Fix #674, fix #480 - Refactor schedule/session YAML process.
467814b 
For >=2020 websites, the schedule YAML is greatly simplified
and linked to the session (formerly speaker) YAML.
In addition, this commit introduces caching for conference context data.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mxsasha mxsasha

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@plaindocs @mxsasha