Skip to content

Conversation

mxsasha
Copy link
Contributor

@mxsasha mxsasha commented Sep 11, 2025

As already discussed in Slack, just porting over from hackmd


📚 Documentation preview 📚: https://writethedocs-www--2434.org.readthedocs.build/

@mxsasha mxsasha requested a review from a team September 11, 2025 14:49
Welcome Wagon Tour is scheduled for:

- Monday at 8:45 (meet near Registration)
Copy link
Contributor

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

Copy link
Contributor

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'

Copy link
Contributor

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

Copy link
Contributor

@plaindocs plaindocs Sep 11, 2025

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 %}

Copy link
Contributor

@plaindocs plaindocs Sep 11, 2025

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?

Copy link
Contributor Author

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.

Copy link
Contributor

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

Copy link
Contributor

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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

Copy link
Contributor Author

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.

@mxsasha mxsasha enabled auto-merge (squash) September 12, 2025 09:44
@mxsasha mxsasha merged commit b6a92d6 into main Sep 12, 2025
7 checks passed
@mxsasha mxsasha deleted the ber-guide branch September 12, 2025 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants