diff --git a/docs/_data/portland-2026-config.yaml b/docs/_data/portland-2026-config.yaml index 7d67e6be2..a5bf06e8d 100644 --- a/docs/_data/portland-2026-config.yaml +++ b/docs/_data/portland-2026-config.yaml @@ -24,12 +24,12 @@ photos: buttons: top: - - text: Date and ticket information - link: /news/welcome - # - text: Sponsor us - # link: /sponsors/prospectus - #- text: Submit a Talk - # link: /cfp + # - text: Date and ticket information + # link: /news/welcome + - text: Sponsor the Conference + link: /sponsors/prospectus + - text: Submit a Talk + link: /cfp # - text: See the Schedule! # link: /schedule # - text: Buy a Ticket @@ -45,12 +45,12 @@ buttons: # - text: Conference recap # link: /news/thanks-recap bottom: - - text: Welcome to our conference - link: /news/welcome - # - text: Sponsor us - # link: /sponsors/prospectus - #- text: Submit a Talk - # link: /cfp + # - text: Welcome to our conference + # link: /news/welcome + - text: Sponsor us + link: /sponsors/prospectus + - text: Submit a Talk + link: /cfp # - text: Buy a Ticket! # link: /tickets # - text: See the Schedule @@ -179,7 +179,7 @@ cfp: url: "https://pretalx.com/wtd-portland-2026/cfp" # Open mid November, approx 12 weeks to submit ends: "January 19, 2026" # (Mon) 1 week, to review. It'll take a little longer to announce notification: "February 2, 2026" # (Mon) 8 weeks to write and prepare - speaker_tickets_by: April 13, 2026 # (Mon) Approx 3 weeks before + speaker_tickets_by: April 2, 2026 # (Mon) Approx 3 weeks before slides_by: "April 27, 2026" # (Mon) 1 week before preview: "TBD" # Preview URL TODO @@ -205,7 +205,7 @@ sponsors: # Things that change over time, listed in order of change flaglanding: True flaghassponsors: False -flagcfp: False +flagcfp: True flagticketsonsale: False flagsoldout: False flagspeakersannounced: False diff --git a/docs/conf/portland/2026/cfp.rst b/docs/conf/portland/2026/cfp.rst index 5007435a5..7df673099 100644 --- a/docs/conf/portland/2026/cfp.rst +++ b/docs/conf/portland/2026/cfp.rst @@ -5,7 +5,7 @@ Call for Proposals ================== -It's that time of year again: We're now accepting talk proposals for our next **in-person** {{ city }} conference, on {{date.main}}. +It's that time of year again: We're now accepting talk proposals for our next **in-person** {{ city }} conference, on {{date.main}}. New this year we're also accepting a few pre-recorded talks by remote speakers. Every year, Write the Docs invites people from all across our community to come up on stage to share their insights and experience. Whether you've worked on documentation for decades or you've just started this year, we want to hear from you! Read on to learn more about the goals of the conference and what we look for in talk proposals. @@ -108,19 +108,20 @@ If you are making assumptions about what your audience knows, state them up fron Check out topics that might be related to your talk from previous years: * `Portland {{year-1}} `_ -* `Atlantic {{year-1}} `_ +* `Berlin {{year-1}} `_ * `Portland {{year-2}} `_ * `Atlantic {{year-2}} `_ Writing your proposal --------------------- + Make sure you read this entire page before putting your proposal together, and pay particular attention to the following points: -- **Spoilers** It's pretty normal not to want to include your main point in your abstract, but please make sure to highlight it for the selection committee! -- **Research** We don't need all talks to be about an entirely new topic, but if you're suggesting a talk that looks really similar to one that was given last year, demonstrate that you realize this and mention why yours is different. -- **Tooling** We're pretty serious about preferring talks about people, process or principles than talks about tooling. If you are submitting a proposal about tooling, tell us what makes this one special. -- **Example proposal** Check out our :doc:`example proposal ` so you know what we expect to see in each field. +- **Spoilers** – It's pretty normal not to want to include your main point in your abstract, but please make sure to highlight it for the selection committee! +- **Research** – We don't need all talks to be about an entirely new topic, but if you're suggesting a talk that looks really similar to one that was given last year, demonstrate that you realize this and mention why yours is different. +- **Tooling** – We're pretty serious about preferring talks about people, process or principles than talks about tooling. If you are submitting a proposal about tooling, tell us what makes this one special. +- **Example proposal** – Check out our :doc:`example proposal ` so you know what we expect to see in each field. Unsure about speaking? @@ -133,7 +134,6 @@ If you need a hand preparing or honing your talk proposal, there are lots of goo * **Community mentorship** – We have an ever-growing pool of previous Write the Docs speakers, many of whom are happy to be a second pair of eyes on talk proposals. If you're interested in working with a past speaker, let us know at {{ shortcode }}@writethedocs.org! * **Meetup brainstorming** – For some in-person workshopping, check in on your `local meetup group `_ and see if they have a talk brainstorming session on their calendar. If they don't... ask if they're planning one! * **Slack hivemind** – You can also hit up the hivemind directly on the Write the Docs Slack, any time of day! (If you're not registered yet, you can at `https://www.writethedocs.org/slack/ `_.) -* **Twitter hivemind** – If Twitter is more your speed, `#writethedocs `__ will get you there. Selection process ----------------- @@ -151,24 +151,35 @@ Speaker benefits - Opportunity to share your views and perspectives with the community! - Waived attendance fee. -- Supplemental financial support if needed. If speaking incurs any costs that are difficult for you to cover, `contact us `_ and we'll do our best to help out. +- Supplemental financial support for travel, accommodations, or other costs. If speaking incurs any costs that are difficult for you to cover, `contact us `_ and we'll do our best to help out. If you already have a ticket, we will of course refund it - just drop us an email at `{{email}} `_. Speaker logistics ----------------- -Presentations will be **{{date.short}}**, scheduled in 30-minute blocks, delivered **in-person, on-stage, live in {{city}}**. -Please plan to attend the whole event. +New for Portland, in 2026 we're showing a few pre-recorded talks with live Q&A from remote speakers for our conference on **{{date.short}}**. + +- We'll accept a **maximum of two** pre-recorded talks, which will need to be uploaded around one month before the conference. Because there are only two slots, submitting a remote proposal does reduce the likeliehood of your talk being accepted. +- All other talks will be delivered **in-person, on-stage, live in {{city}}**. + +Both in-person and pre-recorded talks are 30 minutes long, followed by a few minutes of moderated Q&A immediately after the presentation. -All Speakers must read, understand, and agree to our :doc:`/code-of-conduct`. All talks and slides will need to follow our Code of Conduct. If you are unsure about any aspect of this, please ask us for clarification. +All Speakers must read, understand, and agree to our :doc:`/code-of-conduct`. All talks and slides must follow our Code of Conduct. If you are unsure about any aspect of this, please ask us for clarification. Timeline overview ----------------- + **{{cfp.ends}}** Call for Proposal ends +**{{cfp.speaker_tickets_by}}** + Register for speaker ticket (with dietary preferences, hoodie size, etc.) + +**April 9, 2026** + Upload date for recorded talks (remote speakers) + **{{cfp.notification}}** We'll let you know whether your proposal was accepted, and ask for some supplementary information about you. Make sure to confirm your talk as soon as you get the email. diff --git a/docs/conf/portland/2026/mailing-list.rst b/docs/conf/portland/2026/mailing-list.rst index 8ed60e33b..39d11d911 100644 --- a/docs/conf/portland/2026/mailing-list.rst +++ b/docs/conf/portland/2026/mailing-list.rst @@ -3,28 +3,148 @@ Join our mailing list ===================== +Stay connected with the Write the Docs community! Our mailing lists send out messages 1-2 times a month, and your email won't be shared or used for any other purpose. + .. raw :: html + +
- - + +
+
-
    • -
    • -
    • -
    • -
+ What types of updates would you like? +
    +
  • + + +
    • +
  • + + +
    • +
  • + + +
    • +
  • + + +
    • +
+
-
+
+
diff --git a/docs/conf/portland/2026/news/announcing-cfp.rst b/docs/conf/portland/2026/news/announcing-cfp.rst new file mode 100644 index 000000000..61e424123 --- /dev/null +++ b/docs/conf/portland/2026/news/announcing-cfp.rst @@ -0,0 +1,77 @@ +:template: {{year}}/generic.html +:banner: _static/conf/images/headers/portland-2024-speakers.jpg +:og:image: _static/conf/images/headers/portland-2024-speakers.jpg + +.. post:: Nov 25, 2025 + :tags: {{shortcode}}-{{year}}, website, cfp, tickets + +Announcing the Call for Proposals and Sponsorship Prospectus +============================================================ + +We're excited to announce our Portland `Call for Proposals `_! + +We're also launching our `sponsorship prospectus `_ with updated offerings based on feedback from last year. + +Our full website and tickets will be live soon. + +Read on for more details about getting involved this year. + +Call for Proposals +------------------ + +Speaking at Write the Docs is a fantastic way to share your ideas with our welcoming community of documentarians. + +If there's something you'd really like to see a talk on this year, submit a proposal, or send the submission link to someone else you would like to hear from! + +We're looking for ideas and use-cases from all disciplines and roles, so whether you're a technical writer, developer, UX designer, community manager, or support professional who cares about content and communication, we want to hear from you! + +We're looking for talk proposals to be delivered in-person, on-stage in Portland, on {{ date.short }}. + +New for 2026, we're also accepting a limited number of pre-recorded talks from remote speakers, so if you can't make it to {{city}} on {{ date.short }} you can still submit your proposal. + +You can read our full `Call for Proposals `__, and `submit your talk `__ on the website. + +The Call for Proposals will be open until **11:59 PM {{cfp.ends}} PST**, so harness that new year energy! + +Sponsorship Updates +------------------- + +Our `sponsorship prospectus `_ is updated for {{ year }}, +with various improvements based on sponsor feedback. + +Our sponsors are the folks building the tools and platforms that we use every day, and they help make Write the Docs conferences possible. +If that sounds like your company, please consider joining us this year! + +Tickets +------- + +Tickets will go on sale in {{ date.tickets_live }}. + +In-person ticket prices are the same as last year: + +* **Student/Unemployed**: *{{tickets.student.price}}* +* **Independent**: *{{tickets.independent.price}}* +* **Corporate**: *{{tickets.corporate.price}}* + +Virtual tickets will be sold in a similar fashion with 3 tiers this year: + +* **Student/Unemployed Virtual**: *{{tickets.virtual_student.price}}* +* **Independent Virtual**: *{{tickets.virtual_independent.price}}* +* **Corporate Virtual**: *{{tickets.virtual_corporate.price}}* + +As always, we try to keep ticket prices low so that the event is accessible to the widest range of people. +If you can't afford the tickets and still wish to attend, we will launch our grants program at the same time as tickets. + +Stay Updated +------------ + +Want to find out what's happening with the conference, or enjoy our monthly global community newsletter? +Sign up to one or more of our `mailing lists `_. Your information will never be shared with any third parties, and you can unsubscribe at any time. + +Want to connect with other documentarians before the conference? Join our `Slack `_. + +Thanks +------ + +We hope you will join us in person for yet another Write the Docs conference. +Whether as a speaker or attendee, you can bet it will be another excellent year. \ No newline at end of file