-
Notifications
You must be signed in to change notification settings - Fork 519
Update attendee guide/venue info #2434
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.
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
Conversation
Welcome Wagon Tour is scheduled for: | ||
|
||
- Monday at 8:45 (meet near Registration) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there an easy way we could grab these times from the schedule YAML? say by title, even if we added the day to it? Then we wouldn't have to worry about it getting out of sync
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Basically just gotta untangle the data nesting from the YAML, and say 'gimme the one that says welcome wagon'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be useful for the speaker AV check slots as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something less obscenely ugly than this perhaps
{% with day_schedule=schedule.talks_day1 %}
{% for session in day_schedule %}
{% if session.title == '<i>Welcome Wagon conference introduction and venue tour</i>' %}
{{ session.time }}
{% endif %}
{% endfor %}
{% endwith %}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah crap, we have to do the duration math. Do we do that already? Looks like we do, so this is feasible.
@mxsasha any thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the time key should be the calculated actual start time, from a quick look at the code. So this can work as long as we don't change the name of the tour or have two tours. It is a bit messy. But also, we can't add it yet as there is no schedule, so I'll leave as is for now and we can circle back.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, that's about to hit over in #2399
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yeah, of course speaker tech checks aren't in the public schedule...
|
||
## Dress Code | ||
We don’t have one! Berlin is a casual-dress city and so is the Write the Docs conference. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don’t have one! Berlin is a casual-dress city and so is the Write the Docs conference. | |
We don’t have one! Berlin is a casual-dress city and so is the Write the Docs conference. |
I want to reword this casual-dress city but don't have any great suggestions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm yeah, let's stick with what we have for now then, I also do not have a better one.
As already discussed in Slack, just porting over from hackmd
📚 Documentation preview 📚: https://writethedocs-www--2434.org.readthedocs.build/