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.

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

Ship 2024 website & ticket sales #2065

Merged
merged 38 commits into from
Dec 12, 2023
Merged

Ship 2024 website & ticket sales #2065

merged 38 commits into from
Dec 12, 2023

Conversation

ericholscher
Copy link
Member

@ericholscher ericholscher commented Dec 7, 2023

This includes a bunch of copy edits from Katie.


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

@ericholscher ericholscher requested a review from a team December 8, 2023 18:17
Copy link
Contributor

@plaindocs plaindocs left a comment

Choose a reason for hiding this comment

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

Looks solid.

docs/conf/portland/2024/convince-your-manager.rst Outdated Show resolved Hide resolved
@@ -4,11 +4,106 @@
Lightning Talks
===============

{% include "conf/events/lightning-talks.rst" %}
A lightning talk is a short talk, up to 5 minutes, where you share an idea, concept, or a bit of information you find interesting.
Copy link
Contributor

Choose a reason for hiding this comment

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

Why are we moving this back into the conf dir?

Copy link
Member Author

@ericholscher ericholscher Dec 11, 2023

Choose a reason for hiding this comment

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

Because trying to manage edits with a bunch of includes is really difficult with folks who don't know Git/Sphinx.

Copy link
Contributor

Choose a reason for hiding this comment

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

Agreed, but the includes are there for a reason. Especially if we're doing both ways, and across three conferences. I'd rather not revert here, how about just documenting where things are inline? But if we are are we doing it for all 2024 confs? And then how are we updating next year?

CC @mxsasha for comment here as well.

Copy link
Contributor

Choose a reason for hiding this comment

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

@ericholscher happy to decouple this from merging the PR if you want to merge

Copy link
Member Author

Choose a reason for hiding this comment

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

Yea, I think we can look at backporting changes once we've done our edits, but it's a bit harder because we're mixing "evergreen" and conference-specific content in ordering, because it reads nicer :/

docs/conf/portland/2024/news/announcing-tickets.rst Outdated Show resolved Hide resolved
docs/conf/portland/2024/schedule.rst Show resolved Hide resolved
docs/conf/portland/2024/sponsor-expo.rst Show resolved Hide resolved
docs/conf/portland/2024/unconference.rst Outdated Show resolved Hide resolved
@ericholscher ericholscher merged commit 338000d into main Dec 12, 2023
6 checks passed
@ericholscher ericholscher deleted the pdx-23-tickets-website branch December 12, 2023 18:11
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