From 8dedf9f6c1bc2e3a9e3ae2b33e8032eecc632650 Mon Sep 17 00:00:00 2001 From: Eric Holscher Date: Mon, 14 Oct 2024 14:46:49 -0700 Subject: [PATCH 01/26] Launch the full Portland 2025 site This is just a draft PR to do some initial testing, but will eventually get content updates before we go live. --- docs/_data/portland-2025-config.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/_data/portland-2025-config.yaml b/docs/_data/portland-2025-config.yaml index 72343b398..6eaa9ae73 100644 --- a/docs/_data/portland-2025-config.yaml +++ b/docs/_data/portland-2025-config.yaml @@ -261,9 +261,9 @@ sponsors: # brand: Read the Docs # Things that change over time, listed in order of change -flaglanding: True +flaglanding: False flaghassponsors: True -flagcfp: False +flagcfp: True flagticketsonsale: False flagsoldout: False flagspeakersannounced: False From c34d90e7922bc78afd947583a248cbe0383695bb Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Thu, 24 Oct 2024 14:03:03 +0200 Subject: [PATCH 02/26] Add support for info_by in cfp --- docs/_data/schema-config.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/_data/schema-config.yaml b/docs/_data/schema-config.yaml index 13954c860..8f3473e15 100644 --- a/docs/_data/schema-config.yaml +++ b/docs/_data/schema-config.yaml @@ -174,6 +174,7 @@ cfp-details: notification: str(required=True) video_by: str(required=False) slides_by: str(required=False) + info_by: str(required=False) gifts_by: str(required=False) preview: str(required=False) From 3118fda5db88de038cd9a37b2bf13dac81db855c Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Thu, 24 Oct 2024 14:03:41 +0200 Subject: [PATCH 03/26] Iterate on CFP, including adding a new timeline section --- docs/conf/portland/2025/cfp.rst | 44 ++++++++++++++++++++++++++------- 1 file changed, 35 insertions(+), 9 deletions(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index aee8d7f10..dd31c388c 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -64,10 +64,12 @@ We welcome talks from first-time speakers, from industry experts, and from every Whatever your background and experience, we prefer hearing about new approaches rather than about tried-and-tested technology. We especially welcome talks from underrepresented groups within the tech community. We want to hear a variety of viewpoints, so we limit speakers to two talks in any four year period at each location. -That said, we do strongly prefer talks written and given by a single speaker, and if you're planning to submit with a co-speaker, please let us know why you're doing so. If you're a WTD conference organizer, please only submit talks to conferences you're not actively organizing. +**People on stage** + +We *strongly* prefer talks written and given by one *single speaker*. If you're planning to submit with a co-speaker, please let us know why you're doing so. **Mix of roles and perspectives** @@ -97,7 +99,7 @@ What we’re looking for **Diverse topics** -The focus of Write the Docs is software documentation, but we actively seek talks that address a wide range of related subjects, at various levels of expertise. +The focus of Write the Docs is software documentation, and we actively seek talks that address a wide range of related subjects, at various levels of expertise. Documentation perspectives from other fields are welcome, as are topics from adjacent fields! **Practicality and positivity** @@ -107,7 +109,7 @@ Don't tell us why you hate something – tell us how you overcame the problems i **Process over tooling** -We tend to avoid talks about specific tools, which often turn into marketing pitches or tutorials. +We avoid talks about specific tooling, which often turn into marketing pitches or tutorials. We would much rather hear about process, culture, data, people, or the metaphysical side effects of spending your life thinking about docs. **Audience awareness** @@ -139,7 +141,8 @@ Selection process ------------------ We have a small panel of proposal reviewers, and make sure to have a similar diversity in the panel as we're aiming for in our speakers. -We rate talks out of five, and then discuss the top rated proposals. + +We rate talks out of five, and then discuss the top rated proposals, as well as intresting exceptions from that list. We actively balance for diversity in as many ways as we can, which means that we do not review talks anonymously. Maybe one day the industry will be in a place where can do that, but we're not there yet. @@ -166,6 +169,24 @@ If you already have a ticket, we will of course refund it - just drop us an emai Note that 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. +Timeline overview +----------------- + +**{{cfp.ends}}** + Call for Proposal ends + +**{{cfp.notification}}** + We'll let you know whether your proposal was accepted + +**{{cfp.slides_by}}** + We'll ask you for a copy of your slides so that our human captioners can prepare for your talk + +**{{cfp.info_by}}** + We'll ask you for your pronouns, how your pronounce your name and some intersting facts about you so our emcee can prepare to introduce you. + +**{{date.short}}** + Folks start giving talks on stage! + Example proposal ---------------- @@ -174,7 +195,7 @@ If you'd like some guidance on how to create a talk proposal, take a look at our Questions? ---------- -If you have any questions, please email us at `{{email}} `_ and let us know. +If you have any questions about any part of this process, please email us at `{{email}} `_, we'll be happy to chat. {% if flagcfp %} @@ -191,10 +212,15 @@ Submit your proposal at {{cfp.url}}. You'll need to sign up for a Pretalx accoun +You'll be able to edit your proposal up until we start reviewing talks. + {% endif %} -Write the Docs Atlantic 2024 ----------------------------- +Write the Docs Atlantic +----------------------- + +If you want to speak at Write the Docs but can't or don't want to attend an in-person event, keep an eye out for Write the Docs Atlantic, coming later in the year. + +This conference is entirely virtual, between the Central European Summer Time (CEST) and Eastern Daylight Time (EDT) time zones, so you can present or attend from almost anywhere. -If you want to speak at Write the Docs but can't or don't want to attend an in-person event, keep an eye out for Write the Docs Atlantic, coming later in 2024. -This conference is entirely virtual, between the Central European Summer Time (CEST) and Eastern Daylight Time (EDT) time zones, so you can present or attend from anywhere. \ No newline at end of file +Talks for Write the Docs Atlantic are pre-recorded, with live Question and Answer sessions. From d92c17cfe10385ccd12f6066d520c7321b2bc6ea Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Thu, 24 Oct 2024 14:04:20 +0200 Subject: [PATCH 04/26] Tweak CFP dates in config --- docs/_data/portland-2025-config.yaml | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/_data/portland-2025-config.yaml b/docs/_data/portland-2025-config.yaml index 6eaa9ae73..fb2c27120 100644 --- a/docs/_data/portland-2025-config.yaml +++ b/docs/_data/portland-2025-config.yaml @@ -1,6 +1,6 @@ name: Portland -shortcode: portland +shortcode: portland year: 2025 city: Portland local_area: Oregon @@ -155,11 +155,12 @@ about: job_fair_room: Sponsor area cfp: - url: "" # Open October 6 (Mon) -> 9 weeks to submit - ends: "January 21, 2025" # (Mon) 1 week, to review. It'll take a little longer to announce + url: "https://pretalx.com/wtd-portland-2025/cfp" # Open October 6 (Mon) -> 9 weeks to submit + ends: "January 21, 2025" # (Mon) 1 week, to review. It'll take a little longer to announce notification: "February 04, 2025" # (Mon) 8 weeks to write and prepare + info_by: "April 21, 2025" # (Mon) 2 weeks before for info for emcee slides_by: "April 28, 2025" # (Mon) 1 week before - preview: "TODO" # Preview URL TODO + preview: "TODO" # Preview URL TODO unconf: url: "" @@ -174,7 +175,7 @@ sponsors: # - name: gitbook # link: https://www.gitbook.com/?ref=writethedocs # brand: GitBook - # text: "GitBook combines powerful docs with AI-powered search and insights to give technical teams a single source of truth for their knowledge. + # text: "GitBook combines powerful docs with AI-powered search and insights to give technical teams a single source of truth for their knowledge. # Effortlessly create, surface and improve public and internal documentation that your users and teams will love. " # - name: readme # link: https://readme.com/?ref=writethedocs From 70da70423def4ed78cd416fdf60d9b2455f4fb8e Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Thu, 24 Oct 2024 14:07:17 +0200 Subject: [PATCH 05/26] Fix typos --- docs/conf/portland/2025/cfp.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index dd31c388c..a0fe688bc 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -142,7 +142,7 @@ Selection process We have a small panel of proposal reviewers, and make sure to have a similar diversity in the panel as we're aiming for in our speakers. -We rate talks out of five, and then discuss the top rated proposals, as well as intresting exceptions from that list. +We rate talks out of five, and then discuss the top rated proposals, as well as interesting exceptions from that list. We actively balance for diversity in as many ways as we can, which means that we do not review talks anonymously. Maybe one day the industry will be in a place where can do that, but we're not there yet. @@ -182,7 +182,7 @@ Timeline overview We'll ask you for a copy of your slides so that our human captioners can prepare for your talk **{{cfp.info_by}}** - We'll ask you for your pronouns, how your pronounce your name and some intersting facts about you so our emcee can prepare to introduce you. + We'll ask you for your pronouns, how your pronounce your name and some interesting facts about you so our emcee can prepare to introduce you. **{{date.short}}** Folks start giving talks on stage! From c0975c1f7475c11571a07662a927df932781c29c Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Thu, 24 Oct 2024 14:37:49 +0200 Subject: [PATCH 06/26] Add missing news index --- docs/conf/portland/2025/news/index.rst | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 docs/conf/portland/2025/news/index.rst diff --git a/docs/conf/portland/2025/news/index.rst b/docs/conf/portland/2025/news/index.rst new file mode 100644 index 000000000..e4b78ec89 --- /dev/null +++ b/docs/conf/portland/2025/news/index.rst @@ -0,0 +1,13 @@ +:template: {{year}}/generic.html + +News +==== + +Updates from the team. +More here as it happens! + + .. postlist:: 100 + :date: %A, %B %d, %Y + :format: {title} - {date} + :list-style: none + :tags: {{ shortcode }}-{{ year }} From aa01ce650508c1d6373730bd32cda07c59e72f17 Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Thu, 24 Oct 2024 14:52:37 +0200 Subject: [PATCH 07/26] Fix broken menu --- docs/_templates/2025/menu-desktop.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/_templates/2025/menu-desktop.html b/docs/_templates/2025/menu-desktop.html index 2593801d1..25c88ae0a 100644 --- a/docs/_templates/2025/menu-desktop.html +++ b/docs/_templates/2025/menu-desktop.html @@ -57,7 +57,7 @@
    • - About + About
      • Venue
        • @@ -98,5 +98,5 @@ {% if flagcfp %}
      • Speak
        • {% endif %} - +
      From f99a74efa31ac13674454158d2a04c0dd6c77eaf Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Thu, 24 Oct 2024 15:12:52 +0200 Subject: [PATCH 08/26] More CFP tweaks --- docs/conf/portland/2025/cfp.rst | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index a0fe688bc..667d37d0d 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -69,7 +69,9 @@ If you're a WTD conference organizer, please only submit talks to conferences yo **People on stage** -We *strongly* prefer talks written and given by one *single speaker*. If you're planning to submit with a co-speaker, please let us know why you're doing so. +We *strongly* prefer talks written and given by one *single speaker*. If you're planning to submit with a co-speaker, please let us know why, and take note that it will affect the chances of your talk being selected. + +You are of course welcome to write the talk with other people as long as only one person is presenting. **Mix of roles and perspectives** @@ -112,6 +114,10 @@ Don't tell us why you hate something – tell us how you overcame the problems i We avoid talks about specific tooling, which often turn into marketing pitches or tutorials. We would much rather hear about process, culture, data, people, or the metaphysical side effects of spending your life thinking about docs. +**Benefit to the community** + +How does your talk help improve the quality of documentation everywhere. Are you trying a new approach? Are you solving a known problem? Have you done the research into how folks have tried to solve your issue before? + **Audience awareness** When crafting talk proposals, remember that you're going to be talking to a mix of levels of expertise, skill sets, and professions. @@ -202,6 +208,13 @@ If you have any questions about any part of this process, please email us at `{{ Submit your proposal -------------------------- +Please make sure you read this entire page before submitting your proposal, 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 a new topic, but if you're suggesting a talk that looks really similar to one that was given last year, show you know that, 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** so you know what we expect to see in each field. + Submit your proposal at {{cfp.url}}. You'll need to sign up for a Pretalx account, unless you already have one from a previous conference. .. raw:: html From 00c67f3e0ea88a9d426d2c28310a4f2aaffdc376 Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Thu, 24 Oct 2024 15:32:15 +0200 Subject: [PATCH 09/26] More CFP fixes --- docs/conf/portland/2025/cfp.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index 667d37d0d..a8da2f4d6 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -71,7 +71,7 @@ If you're a WTD conference organizer, please only submit talks to conferences yo We *strongly* prefer talks written and given by one *single speaker*. If you're planning to submit with a co-speaker, please let us know why, and take note that it will affect the chances of your talk being selected. -You are of course welcome to write the talk with other people as long as only one person is presenting. +You are of course welcome to write the talk with other people, as long as only one person is presenting. **Mix of roles and perspectives** @@ -129,7 +129,7 @@ It can be helpful to check out topics that might be related to your talk from p * `Portland {{year-1}} `_ * `Atlantic {{year-1}} `_ * `Portland {{year-2}} `_ -* `Prague {{year-2}} `_ +* `Atlantic {{year-2}} `_ Not sure about speaking? ------------------------ From cc0d4bcb24f74d0e01940435a139a006a22b8792 Mon Sep 17 00:00:00 2001 From: Sam Date: Fri, 25 Oct 2024 12:11:38 +0300 Subject: [PATCH 10/26] Apply suggestions from code review Co-authored-by: Sarah Moir --- docs/conf/portland/2025/cfp.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index a8da2f4d6..52506c848 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -116,7 +116,7 @@ We would much rather hear about process, culture, data, people, or the metaphysi **Benefit to the community** -How does your talk help improve the quality of documentation everywhere. Are you trying a new approach? Are you solving a known problem? Have you done the research into how folks have tried to solve your issue before? +How does your talk help improve the quality of documentation everywhere? Are you trying a new approach? Are you solving a known problem? Have you done the research into how folks have tried to solve your issue before? **Audience awareness** @@ -188,7 +188,7 @@ Timeline overview We'll ask you for a copy of your slides so that our human captioners can prepare for your talk **{{cfp.info_by}}** - We'll ask you for your pronouns, how your pronounce your name and some interesting facts about you so our emcee can prepare to introduce you. + We'll ask you for your pronouns, how you pronounce your name, and some interesting facts about you so our emcee can prepare to introduce you. **{{date.short}}** Folks start giving talks on stage! From 2ee0164b552f738e50265b608c6f261f8b250257 Mon Sep 17 00:00:00 2001 From: Sam Date: Fri, 25 Oct 2024 12:27:45 +0300 Subject: [PATCH 11/26] Apply suggestions from code review --- docs/conf/portland/2025/cfp.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index 52506c848..bbed5f5e0 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -69,7 +69,7 @@ If you're a WTD conference organizer, please only submit talks to conferences yo **People on stage** -We *strongly* prefer talks written and given by one *single speaker*. If you're planning to submit with a co-speaker, please let us know why, and take note that it will affect the chances of your talk being selected. +We *strongly* prefer talks presented by one *single speaker*. If you're planning to submit with a co-speaker, please let us know why, and take note that it will affect the chances of your talk being selected. You are of course welcome to write the talk with other people, as long as only one person is presenting. From f895f1b861349ce7d31a0beeba648408fafa73d3 Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Mon, 28 Oct 2024 10:31:24 +0100 Subject: [PATCH 12/26] Toggle full site back off (sorry Eric :-p ) --- docs/_data/portland-2025-config.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/_data/portland-2025-config.yaml b/docs/_data/portland-2025-config.yaml index fb2c27120..093f53785 100644 --- a/docs/_data/portland-2025-config.yaml +++ b/docs/_data/portland-2025-config.yaml @@ -22,8 +22,8 @@ buttons: link: /news/welcome # - text: Sponsor us # link: /sponsors/prospectus - # - text: Submit a Talk - # link: /cfp + - text: Submit a Talk + link: /cfp # - text: See the Schedule! # link: /schedule # - text: Buy a Ticket! @@ -262,7 +262,7 @@ sponsors: # brand: Read the Docs # Things that change over time, listed in order of change -flaglanding: False +flaglanding: True flaghassponsors: True flagcfp: True flagticketsonsale: False From 806e2be0fd975a46a133a70af555e355a2e489fe Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Mon, 28 Oct 2024 10:31:56 +0100 Subject: [PATCH 13/26] Draft blog post --- .../portland/2025/news/announcing-cfp.rst | 70 +++++++++++++++++++ 1 file changed, 70 insertions(+) create mode 100644 docs/conf/portland/2025/news/announcing-cfp.rst diff --git a/docs/conf/portland/2025/news/announcing-cfp.rst b/docs/conf/portland/2025/news/announcing-cfp.rst new file mode 100644 index 000000000..bbb12a37c --- /dev/null +++ b/docs/conf/portland/2025/news/announcing-cfp.rst @@ -0,0 +1,70 @@ +:template: {{year}}/generic.html +:banner: _static/conf/images/headers/portland-2024-speakers.jpg +:og:image: _static/conf/images/headers/portland-2024-speakers.jpg + +.. post:: Oct 28, 2024 + :tags: {{shortcode}}-{{year}}, website, cfp, tickets + +Announcing the Call for Proposals and Sponsorship Prospectus +============================================================ + +We're excited to announce our Portland `Call for Proposals `_, opening even earlier than last year, even though the conference back at the start of May this time around. + +We're also launching our `Sponsorship Prospectus `_ for 2024 with all the information for sponsoring the conference. + +Read on for more details about how you can get involved this year. + +Call for Proposals +------------------ + +Speaking at Write the Docs is a fantastic way to share your ideas with our inspiring community of documentarians. +If there is something you'd really like to see a talk on this year, submit a proposal on it, or refer someone else who would be good! + +Every year, Write the Docs invites people from all across our community to come up on stage to share their insights and experience. +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 }}. + +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! + +(If you'd prefer not to attend an in-person event due to COVID-19 or any other reason, keep an eye out for our Atlantic conference held online in a timezone accessible to people all over the world). + + +Sponsorship Updates +------------------- + +Our `Sponsorship Prospectus `_ is updated for {{ year }}, +with various improvements based on sponsor feedback. + +We're focussing on in-person interaction at the conference, taking full advantage of {{ about.venue }} with plenty of space for sponsors to interact with attendees. + +Tickets +------- + +Tickets will go on sale in {{ date.tickets_live }}. + +As always, we keep ticket prices low so that the event is accessible to the widest range of people possible. +However, if you can't afford the tickets and still wish to attend, we will launch our grants program soon after opening ticket sales. + +Write the Docs Atlantic {{ year }} +--------------------------------- + +If you want to speak at Write the Docs, but can't or don't want to attend an in-person event, keep an eye out for Write the Docs Atlantic, an online conference coming later in {{ year }}. + +This conference will be entirely virtual, in a timezone that works for as many people as possible, so you can present and attend from anywhere. + +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 in real-time? 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. From 88f6166ab955e4e73336bb9f9979e76523031832 Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Mon, 28 Oct 2024 17:16:23 +0100 Subject: [PATCH 14/26] Tweak dates --- docs/conf/portland/2025/cfp.rst | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index bbed5f5e0..7777a5362 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -182,14 +182,12 @@ Timeline overview Call for Proposal ends **{{cfp.notification}}** - We'll let you know whether your proposal was accepted + We'll let you know whether your proposal was accepted, and ask you for some suplimentary information about you. + Make sure to confirm your talk as soon as you get the email. **{{cfp.slides_by}}** We'll ask you for a copy of your slides so that our human captioners can prepare for your talk -**{{cfp.info_by}}** - We'll ask you for your pronouns, how you pronounce your name, and some interesting facts about you so our emcee can prepare to introduce you. - **{{date.short}}** Folks start giving talks on stage! From bb7479497890f334035192144afda5207fb34b21 Mon Sep 17 00:00:00 2001 From: Sam Date: Tue, 29 Oct 2024 12:55:35 +0200 Subject: [PATCH 15/26] Apply suggestions from code review Co-authored-by: Alicia Duncan Co-authored-by: Eric Holscher <25510+ericholscher@users.noreply.github.com> --- docs/conf/portland/2025/cfp.rst | 14 +++++----- .../portland/2025/news/announcing-cfp.rst | 26 +++++++------------ 2 files changed, 17 insertions(+), 23 deletions(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index 7777a5362..33a3098a6 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -173,7 +173,7 @@ If you already have a ticket, we will of course refund it - just drop us an emai {% endif %} -Note that 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. +Note that 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. Timeline overview ----------------- @@ -182,11 +182,11 @@ Timeline overview Call for Proposal ends **{{cfp.notification}}** - We'll let you know whether your proposal was accepted, and ask you for some suplimentary information about you. + 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. **{{cfp.slides_by}}** - We'll ask you for a copy of your slides so that our human captioners can prepare for your talk + We'll ask for a copy of your slides so our human captioners can prepare for your talk **{{date.short}}** Folks start giving talks on stage! @@ -199,7 +199,7 @@ If you'd like some guidance on how to create a talk proposal, take a look at our Questions? ---------- -If you have any questions about any part of this process, please email us at `{{email}} `_, we'll be happy to chat. +If you have any questions about any part of this process, please email us at `{{email}} `_; we'll be happy to chat. {% if flagcfp %} @@ -209,9 +209,9 @@ Submit your proposal Please make sure you read this entire page before submitting your proposal, 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 a new topic, but if you're suggesting a talk that looks really similar to one that was given last year, show you know that, and mention why yours is different. +- **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** so you know what we expect to see in each field. +- **Example proposal** Check out our example so you know what we expect to see in each field. Submit your proposal at {{cfp.url}}. You'll need to sign up for a Pretalx account, unless you already have one from a previous conference. @@ -223,7 +223,7 @@ Submit your proposal at {{cfp.url}}. You'll need to sign up for a Pretalx accoun
      -You'll be able to edit your proposal up until we start reviewing talks. +You'll be able to edit your proposal up until the submission deadline. Please be considerate of our reviewers when making changes to talks you've already submitted. {% endif %} diff --git a/docs/conf/portland/2025/news/announcing-cfp.rst b/docs/conf/portland/2025/news/announcing-cfp.rst index bbb12a37c..63f702456 100644 --- a/docs/conf/portland/2025/news/announcing-cfp.rst +++ b/docs/conf/portland/2025/news/announcing-cfp.rst @@ -8,9 +8,9 @@ Announcing the Call for Proposals and Sponsorship Prospectus ============================================================ -We're excited to announce our Portland `Call for Proposals `_, opening even earlier than last year, even though the conference back at the start of May this time around. +We're excited to announce our Portland `Call for Proposals `_, opening even earlier than last year. -We're also launching our `Sponsorship Prospectus `_ for 2024 with all the information for sponsoring the conference. +We're also launching our `sponsorship prospectus `_ with all the information for sponsoring the conference. Read on for more details about how you can get involved this year. @@ -18,7 +18,7 @@ Call for Proposals ------------------ Speaking at Write the Docs is a fantastic way to share your ideas with our inspiring community of documentarians. -If there is something you'd really like to see a talk on this year, submit a proposal on it, or refer someone else who would be good! +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! Every year, Write the Docs invites people from all across our community to come up on stage to share their insights and experience. 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! @@ -35,36 +35,30 @@ The Call for Proposals will be open until **11:59 PM {{cfp.ends}} PST**, so harn Sponsorship Updates ------------------- -Our `Sponsorship Prospectus `_ is updated for {{ year }}, +Our `sponsorship prospectus `_ is updated for {{ year }}, with various improvements based on sponsor feedback. -We're focussing on in-person interaction at the conference, taking full advantage of {{ about.venue }} with plenty of space for sponsors to interact with attendees. +We're focusing on in-person interaction at the conference, taking full advantage of {{ about.venue }} with a dedicated space for sponsors in the hallway outside the main venue. Tickets ------- Tickets will go on sale in {{ date.tickets_live }}. -As always, we keep ticket prices low so that the event is accessible to the widest range of people possible. -However, if you can't afford the tickets and still wish to attend, we will launch our grants program soon after opening ticket sales. +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 soon after opening ticket sales. -Write the Docs Atlantic {{ year }} ---------------------------------- - -If you want to speak at Write the Docs, but can't or don't want to attend an in-person event, keep an eye out for Write the Docs Atlantic, an online conference coming later in {{ year }}. - -This conference will be entirely virtual, in a timezone that works for as many people as possible, so you can present and attend from anywhere. 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. +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 in real-time? Join our `Slack `_. +Want to connect with other documentarians in real-time? Join our `Slack `_. Thanks ------ -We hope you will join us in-person for yet another Write the Docs conference. +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. From 3fd323da415ed5f37f249c3be339c0d2ec9f6919 Mon Sep 17 00:00:00 2001 From: Sam Date: Tue, 29 Oct 2024 12:58:37 +0200 Subject: [PATCH 16/26] Update docs/conf/portland/2025/cfp.rst --- docs/conf/portland/2025/cfp.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index 33a3098a6..ad959cb7b 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -208,9 +208,9 @@ Submit your proposal Please make sure you read this entire page before submitting your proposal, 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! +- **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. +- **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 example so you know what we expect to see in each field. Submit your proposal at {{cfp.url}}. You'll need to sign up for a Pretalx account, unless you already have one from a previous conference. From b312280e1cde58fad7083b91a647e4769ec41122 Mon Sep 17 00:00:00 2001 From: Eric Holscher Date: Tue, 29 Oct 2024 14:05:58 -0700 Subject: [PATCH 17/26] Katie edits --- docs/conf/portland/2025/cfp.rst | 138 +++++++++++++++++++------------- 1 file changed, 82 insertions(+), 56 deletions(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index aee8d7f10..41925b86d 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -4,7 +4,7 @@ Call for Proposals ================== -It's that time of year again: We're now accepting talk proposals for our next **in-person** {{ city }} conference, coming up 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}}. 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. @@ -13,18 +13,13 @@ Read on to learn more about the goals of the conference and what we look for in In the meantime, mark your calendars: -**The deadline for submitting proposals is 11:59 PM {{tz}} on {{cfp.ends}}.** +- **Deadline: {{cfp.ends}} at 11:59 PM {{tz}}** +- **Acceptance emails: by {{cfp.notification}}** -We'll let you know if your proposal has been accepted by the end of {{cfp.notification}}. {% else %} We will announce the CFP dates soon. {% endif %} -.. contents:: - :local: - :depth: 1 - :backlinks: none - {% if flagcfp %} Ready to submit your talk? @@ -43,13 +38,13 @@ You can do that here: Conference goals ---------------- -Write the Docs conferences are our chance to get together to explore and celebrate the craft of documentation in a positive, inclusive environment. +Write the Docs conferences are our opportunity to get together to explore and celebrate the craft of documentation in a positive, inclusive environment. -Between the talks on stage, the discussions in the unconference, the collaboration on the writing day and other conversations, 100% of the content for our conferences comes from our community! Whether your job title is writer, developer, product manager, support advocate, librarian, or one of a hundred others, your perspective on what makes good docs is what this conference is all about. +**Our goal is to give documentarians a chance to connect and learn from each other.** -Our goal is to give documentarians a chance to connect and learn from each other. You'll have the chance to compare notes on what's happening in the industry, dig into questions of convention and good practice, and generally nerd out about all the things we love about documentation. +Between the talks on stage, the discussions in the Unconference, the collaboration on Writing Day and other conversations, 100% of the content for our conferences comes from our community! Your perspective on what makes good docs is what this conference is all about. -This year, as usual, we're trying to iterate on our tried and tested processes, both to improve our program and to give you, the speakers, a better idea of what to expect. + You'll have the chance to compare notes on what's happening in the industry, dig into questions of convention and good practice, and generally nerd out about all the things we love about documentation. Who we're looking for --------------------- @@ -60,26 +55,22 @@ That said, there are some more helpful and concrete pointers below. **Diverse group of speakers** -We welcome talks from first-time speakers, from industry experts, and from everyone in between. -Whatever your background and experience, we prefer hearing about new approaches rather than about tried-and-tested technology. -We especially welcome talks from underrepresented groups within the tech community. -We want to hear a variety of viewpoints, so we limit speakers to two talks in any four year period at each location. -That said, we do strongly prefer talks written and given by a single speaker, and if you're planning to submit with a co-speaker, please let us know why you're doing so. +We welcome first-time speakers, industry experts, and everyone in between. We especially welcome talks from underrepresented groups within the tech community. -If you're a WTD conference organizer, please only submit talks to conferences you're not actively organizing. +We want to hear a variety of viewpoints, so we limit speakers to two talks in any four year period at each location. +**Single vs. co-speakers** -**Mix of roles and perspectives** +We do strongly prefer talks written and given by a single speaker, and if you're planning to submit with a co-speaker, please let us know why you're doing so. -Talks from the scientific community, fiction writers, system administrators, and support staff – in addition to technical writers and software developers – are all valuable to our attendees. -**Diverse audience** +**Mix of roles and perspectives** -Likewise, we love the diversity of our community, and we encourage support-folks to attend talks about programming, developers to attend talks about writing, writers to attend talks about data, and so on and so forth. +Talks from the scientific community, fiction writers, system administrators, and support staff – as well as technical writers and software developers – all are valuable to our attendees. **Past speakers** -Past speaker roles include but are not limited to +View our past speaker roles, and always remember, you do not have to fit one of these to be a speaker! * Writers * Developers @@ -95,38 +86,39 @@ Past speaker roles include but are not limited to What we’re looking for ---------------------- -**Diverse topics** +**Broad topics** -The focus of Write the Docs is software documentation, but we actively seek talks that address a wide range of related subjects, at various levels of expertise. -Documentation perspectives from other fields are welcome, as are topics from adjacent fields! +The focus of Write the Docs is software documentation, but we actively seek talks that address a wide range of related subjects, at various levels of expertise. Documentation perspectives from other fields are welcome, as are topics from adjacent fields! **Practicality and positivity** -We prefer talks backed by experience and experimentation to talks about theory, and we definitely don't like talks that bad-mouth technologies or approaches. -Don't tell us why you hate something – tell us how you overcame the problems it was causing. +We prefer talks backed by experience and experimentation to talks about theory, and we definitely don't like talks that bad-mouth technologies or approaches. Don't tell us why you hate something – tell us how you overcame the problems it was causing. **Process over tooling** -We tend to avoid talks about specific tools, which often turn into marketing pitches or tutorials. -We would much rather hear about process, culture, data, people, or the metaphysical side effects of spending your life thinking about docs. +We tend to avoid talks about specific tools, which often turn into marketing pitches or tutorials. We would much rather hear about process, culture, data, people, or the metaphysical side effects of spending your life thinking about docs. + +**New ideas** + +Whatever your background and experience, we prefer hearing about new approaches rather than about tried-and-tested technology. **Audience awareness** -When crafting talk proposals, remember that you're going to be talking to a mix of levels of expertise, skill sets, and professions. +When crafting talk proposals, remember that you're going to be speaking to a mix of levels of expertise, skill sets, and professions. Your talk doesn't have to be relevant to everyone, but it should be relevant to most people and shouldn't make too many assumptions about what people already know. -If you are making those assumptions about what your audience knows, it helps everyone if you state them up front explicitly. +If you are making assumptions about what your audience knows, state them up front explicitly. -It can be helpful to check out topics that might be related to your talk from previous years as well: +Check out topics that might be related to your talk from previous years: * `Portland {{year-1}} `_ * `Atlantic {{year-1}} `_ * `Portland {{year-2}} `_ * `Prague {{year-2}} `_ -Not sure about speaking? +Unsure about speaking? ------------------------ -Don't worry too much about whether we will accept your talk proposal, just submit it anyway, and leave the selection up to us. Just because you're not sure whether your topic is a good fit, feel you don't have enough speaking experience for a conference, or you think someone else may be able to give a better talk on your topic does not mean you don't have awesome things to say. +Don't worry too much about whether we will accept your talk proposal. We encourage you to submit it anyway! You may be unsure if your topic is a good fit, whether you have enough speaking experience, or if someone else might give a better talk on your topic, but that does not mean you don't have valuable and awesome insights to share. If you need a hand preparing or honing your talk proposal, there are lots of good places to start: @@ -138,45 +130,72 @@ If you need a hand preparing or honing your talk proposal, there are lots of goo Selection process ------------------ -We have a small panel of proposal reviewers, and make sure to have a similar diversity in the panel as we're aiming for in our speakers. -We rate talks out of five, and then discuss the top rated proposals. +We have a small panel of proposal reviewers. We ensure that the diversity in the panel reflects who we aim to have as speakers. -We actively balance for diversity in as many ways as we can, which means that we do not review talks anonymously. Maybe one day the industry will be in a place where can do that, but we're not there yet. +Proposals are rated on a scale of five, after which we meet and discuss the top-rated submissions in detail. -Presentation format -------------------- - -Presentations will be scheduled in 30-minute blocks, delivered **in-person, on-stage, live**. +To actively promote diversity, we choose not to review talks anonymously, allowing us to intentionally balance various perspectives and backgrounds. Speaker benefits & logistics ----------------------------- +--------------------------- -If you are selected to speak at Write the Docs, we will waive your attendance fee. -If speaking incurs any costs that are difficult for you to cover, please `let us know `_ and we'll do our best to help out. +**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. If you already have a ticket, we will of course refund it - just drop us an email at `{{email}} `_. {% if flagcfp %} -**You'll hear from us with our proposal decisions by the end of {{cfp.notification}}**. +**Logistics** -**You'll be delivering your talk live, in-person in Portland, Oregon**. +Presentations will be **May 5-6, 2025**, scheduled in 30-minute blocks, delivered **in-person, on-stage, live in Portland, Oregon.** -{% endif %} +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. -Note that 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. - -Example proposal +CFP proposal ---------------- -If you'd like some guidance on how to create a talk proposal, take a look at our :doc:`Example proposal `. +Below is additional information and ideas to better complete specific prompts in the proposal. -Questions? ----------- +**Abstract** -If you have any questions, please email us at `{{email}} `_ and let us know. +This is the content Write the Docs posts on the conference schedule. -{% if flagcfp %} +Include a brief story, typically two to four paragraphs, describing your personal work experience with the topic. Write to appeal to our audience of documentarians. We’re suspicious of proposals that look like they belong at other conferences. + +Include a list of takeaways that our audience can learn from your talk, such as: + +- Lessons the audience can apply in their own work +- Ideas the audience should research further +- Spoilers that provide details about the talk + +Avoid walls of text. We recommend that you limit your abstract to a maximum of 300 words. If your proposal is accepted, this is what the audience will see in the program when they preview your talk. + +**Who and Why** + +Answer the questions: +- Who is this talk for? +- Why is this helpful, applicable, important, etc.? + +Help your audience think: “Oh yes, this talk could help me when I do X in my work!” + +Our audience creates documentation primarily for software. Given the variety of tools used for software documentation, we rarely accept talks that focus on a specific software tool or set of tools. If a talk does include tools, you should also discuss the wider context, applications, and implications of implementing the tools. + +Our audience goes beyond the technical writing community. Here’s a typical demographic distribution of people who attend our conferences: + +- Technical Writers (60%) +- Developers (10%) +- Support Staff (10%) +- Managers (10%) +- Community Contributors, Enthusiasts & Other Folks (10%) + +**Other Information** + +Based on your background, use this section to describe your qualifications to the selection committee. + +As discussed above, we've welcomed talks from first-time speakers, industry experts, and everyone in between. If you believe that you have something valuable to share, tell us why and submit your proposal. Submit your proposal -------------------------- @@ -193,6 +212,13 @@ Submit your proposal at {{cfp.url}}. You'll need to sign up for a Pretalx accoun {% endif %} +Questions? +---------- + +If you have any questions, please email us at `{{email}} `_ and let us know. + +{% if flagcfp %} + Write the Docs Atlantic 2024 ---------------------------- From 2714c36996b1313fbaa8a225782d19e0fadf148e Mon Sep 17 00:00:00 2001 From: Eric Holscher Date: Tue, 29 Oct 2024 14:17:54 -0700 Subject: [PATCH 18/26] Fix up obvious issues --- docs/conf/portland/2025/cfp.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index 025e7385d..7dd63b8e1 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -138,7 +138,7 @@ If you need a hand preparing or honing your talk proposal, there are lots of goo * **Twitter hivemind** – If Twitter is more your speed, `#writethedocs `__ will get you there. Selection process ------------------- +----------------- We have a small panel of proposal reviewers. We ensure that the diversity in the panel reflects who we aim to have as speakers. @@ -147,7 +147,7 @@ Proposals are rated on a scale of five, after which we meet and discuss the top- To actively promote diversity, we choose not to review talks anonymously, allowing us to intentionally balance various perspectives and backgrounds. Speaker benefits & logistics ---------------------------- +---------------------------- **Benefits** - Opportunity to share your views and perspectives with the community! @@ -256,8 +256,8 @@ If you have any questions, please email us at `{{email}} `_ an {% if flagcfp %} -Write the Docs Atlantic 2024 ----------------------------- +Write the Docs Atlantic +----------------------- If you want to speak at Write the Docs but can't or don't want to attend an in-person event, keep an eye out for Write the Docs Atlantic, coming later in the year. From a21877f5406174aa87900bdcd14d716373df524d Mon Sep 17 00:00:00 2001 From: Eric Holscher <25510+ericholscher@users.noreply.github.com> Date: Thu, 31 Oct 2024 14:09:24 -0800 Subject: [PATCH 19/26] Apply suggestions from code review Co-authored-by: Sam --- docs/conf/portland/2025/cfp.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index 7dd63b8e1..65222569d 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -59,7 +59,7 @@ We welcome first-time speakers, industry experts, and everyone in between. We es We want to hear a variety of viewpoints, so we limit speakers to two talks in any four year period at each location. -**Single vs. co-speakers** +**Number of speakers** We do strongly prefer talks written and given by a single speaker, and if you're planning to submit with a co-speaker, please let us know why you're doing so. @@ -75,7 +75,7 @@ Talks from the scientific community, fiction writers, system administrators, and **Past speakers** -View our past speaker roles, and always remember, you do not have to fit one of these to be a speaker! +Our speakers come from all over the industry, and have included the following roles * Writers * Developers @@ -102,7 +102,7 @@ We prefer talks backed by experience and experimentation to talks about theory, **Process over tooling** -We tend to avoid talks about specific tools, which often turn into marketing pitches or tutorials. We would much rather hear about process, culture, data, people, or the metaphysical side effects of spending your life thinking about docs. +We tend to avoid talks about specific tooling, which often turn into marketing pitches or tutorials. We would much rather hear about process, culture, data, people, or the metaphysical side effects of spending your life thinking about docs. **New ideas** @@ -160,7 +160,7 @@ If you already have a ticket, we will of course refund it - just drop us an emai **Logistics** -Presentations will be **May 5-6, 2025**, scheduled in 30-minute blocks, delivered **in-person, on-stage, live in Portland, Oregon.** +Presentations will be **{{date.short}}**, scheduled in 30-minute blocks, delivered **in-person, on-stage, live in {{city}}.** 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. @@ -252,7 +252,7 @@ You'll be able to edit your proposal up until the submission deadline. Please be Questions? ---------- -If you have any questions, please email us at `{{email}} `_ and let us know. +Email any questions about this process to us at `{{email}} `_. {% if flagcfp %} From 13848c148799c5d0ed03dcea2b353bae603c3972 Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Fri, 1 Nov 2024 17:21:41 +0100 Subject: [PATCH 20/26] More edits --- docs/conf/portland/2025/cfp.rst | 83 +++----------------- docs/conf/portland/2025/example-proposal.rst | 59 ++++++-------- 2 files changed, 34 insertions(+), 108 deletions(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index 65222569d..60321be70 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -35,6 +35,11 @@ You can do that here: {% endif %} +.. contents:: + :local: + :depth: 1 + :backlinks: none + Conference goals ---------------- @@ -65,7 +70,7 @@ We do strongly prefer talks written and given by a single speaker, and if you're **People on stage** -We *strongly* prefer talks presented by one *single speaker*. If you're planning to submit with a co-speaker, please let us know why, and take note that it will affect the chances of your talk being selected. +We *strongly* prefer talks _presented_ by one *single speaker*. If you're planning to submit with a co-speaker, please let us know why, and take note that it will affect the chances of your talk being selected. You are of course welcome to write the talk with other people, as long as only one person is presenting. @@ -73,21 +78,6 @@ You are of course welcome to write the talk with other people, as long as only o Talks from the scientific community, fiction writers, system administrators, and support staff – as well as technical writers and software developers – all are valuable to our attendees. -**Past speakers** - -Our speakers come from all over the industry, and have included the following roles - -* Writers -* Developers -* Designers -* Testers -* Support folks -* Developer advocates -* Community managers -* Scientists -* Librarians -* Teachers - What we’re looking for ---------------------- @@ -106,7 +96,7 @@ We tend to avoid talks about specific tooling, which often turn into marketing p **New ideas** -Whatever your background and experience, we prefer hearing about new approaches rather than about tried-and-tested technology. +This isn't a hard and fast rule, but we're more likely to include talks on topics that have not been covered before than talks that have been touched on in multiple recent conferences. **Benefit to the community** @@ -140,7 +130,7 @@ If you need a hand preparing or honing your talk proposal, there are lots of goo Selection process ----------------- -We have a small panel of proposal reviewers. We ensure that the diversity in the panel reflects who we aim to have as speakers. +We have a small panel of proposal reviewers. We ensure that the diversity in the panel reflects who we aim to have as speakers. Proposals are rated on a scale of five, after which we meet and discuss the top-rated submissions in detail. @@ -149,7 +139,7 @@ To actively promote diversity, we choose not to review talks anonymously, allowi Speaker benefits & logistics ---------------------------- -**Benefits** +**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. @@ -185,45 +175,7 @@ Timeline overview Example proposal ---------------- -Below is additional information and ideas to better complete specific prompts in the proposal. - -**Abstract** - -This is the content Write the Docs posts on the conference schedule. - -Include a brief story, typically two to four paragraphs, describing your personal work experience with the topic. Write to appeal to our audience of documentarians. We’re suspicious of proposals that look like they belong at other conferences. - -Include a list of takeaways that our audience can learn from your talk, such as: - -- Lessons the audience can apply in their own work -- Ideas the audience should research further -- Spoilers that provide details about the talk - -Avoid walls of text. We recommend that you limit your abstract to a maximum of 300 words. If your proposal is accepted, this is what the audience will see in the program when they preview your talk. - -**Who and Why** - -Answer the questions: -- Who is this talk for? -- Why is this helpful, applicable, important, etc.? - -Help your audience think: “Oh yes, this talk could help me when I do X in my work!” - -Our audience creates documentation primarily for software. Given the variety of tools used for software documentation, we rarely accept talks that focus on a specific software tool or set of tools. If a talk does include tools, you should also discuss the wider context, applications, and implications of implementing the tools. - -Our audience goes beyond the technical writing community. Here’s a typical demographic distribution of people who attend our conferences: - -- Technical Writers (60%) -- Developers (10%) -- Support Staff (10%) -- Managers (10%) -- Community Contributors, Enthusiasts & Other Folks (10%) - -**Other Information** - -Based on your background, use this section to describe your qualifications to the selection committee. - -As discussed above, we've welcomed talks from first-time speakers, industry experts, and everyone in between. If you believe that you have something valuable to share, tell us why and submit your proposal. +Take a look at our :doc:`Example proposal `, with additional guidance on the proposal format: Submit your proposal -------------------------- @@ -233,7 +185,7 @@ Please make sure you read this entire page before submitting your proposal, and - **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 example so you know what we expect to see in each field. +- **Example proposal** Check out our :doc:`example proposal ` so you know what we expect to see in each field. Submit your proposal at {{cfp.url}}. You'll need to sign up for a Pretalx account, unless you already have one from a previous conference. @@ -253,16 +205,3 @@ Questions? ---------- Email any questions about this process to us at `{{email}} `_. - -{% if flagcfp %} - -Write the Docs Atlantic ------------------------ - -If you want to speak at Write the Docs but can't or don't want to attend an in-person event, keep an eye out for Write the Docs Atlantic, coming later in the year. - -This conference is entirely virtual, between the Central European Summer Time (CEST) and Eastern Daylight Time (EDT) time zones, so you can present or attend from almost anywhere. - -Talks for Write the Docs Atlantic are pre-recorded, with live Question and Answer sessions. - -{% endif %} \ No newline at end of file diff --git a/docs/conf/portland/2025/example-proposal.rst b/docs/conf/portland/2025/example-proposal.rst index c4acddc2a..e3546bf42 100644 --- a/docs/conf/portland/2025/example-proposal.rst +++ b/docs/conf/portland/2025/example-proposal.rst @@ -3,58 +3,45 @@ Example talk proposal title =========================== -Substitute a catchy title that promises practical lessons - Abstract -------- -This is the content that Write the Docs would post on the conference schedule. To evaluate the quality of your proposal, the proposal committee also takes into account all of the other information that you provide. +The abstract is published in the conference schedule. +It should be publication ready, although it might be edited for brevity and consistency by the conference staff. -Include a brief story, typically two to four paragraphs, that describes your personal work experience with the topic. Make sure the abstract appeals to our audience of documentarians. We're suspicious of proposals that look like they belong at other conferences. +Include a brief story, typically two to four paragraphs, describing your personal work experience with the topic. Write to appeal to our audience of documentarians. +We work hard to include talks that are well suited to our audience. -Include a list of things that our audience can learn from your talk, such as: +Include a list of takeaways that our audience can learn from your talk, such as: -- Lessons that the audience can apply in their own work -- Things that audiences should research further +- Lessons the audience can apply in their own work +- Ideas the audience should research further - Spoilers that provide details about the talk -Help your audience think: "Oh yes, this talk could help me when I do X in my work!" - -Avoid walls of text. We recommend that you limit your proposal to a maximum of 300 words. If your proposal is accepted, this is what the audience will see in the program when they preview your talk. +Avoid walls of text. We recommend that you limit your abstract to a maximum of 300 words. Who and Why ----------- -Use this opportunity to show the selection committee that you empathize with your audience. Help them think: "Oh yes, this talk could help me when I do X in my work!" +Use this section to show the *selection committee* that you understand and empathize with your audience. +Help them think: "Oh yes, this talk could help me when I do X in my work!" -Our audience creates documentation primarily for software. Given the variety of tools used for software documentation, we rarely accept talks that focus on a specific software tool or set of tools. Talks that discuss tools should also discuss the wider context, applications, and implications of implementing the tools. +Answer the questions: -Our audience goes beyond the technical writing community. Here's a typical demographic distribution of people who attend our conferences: +- Who is this talk for? +- Why is this helpful, applicable, important, etc.? -* Technical Writers (60%) -* Developers (10%) -* Support Staff (10%) -* Managers (10%) -* Community Contributors, Enthusiasts & Other Folks (10%) +Our audience creates documentation primarily for software. Given the variety of tools used for software documentation, we rarely accept talks that focus on a specific software tool or set of tools. If a talk does include tools, you should also discuss the wider context, applications, and implications of implementing the tools. -Only the proposal committee will see the information that you include here. - -Other Information ------------------ +Our audience goes beyond the technical writing community. Here’s a typical demographic distribution of people who attend our conferences: -Based on your background, use this section to describe your qualifications to the selection committee. +- Technical Writers (60%) +- Developers (10%) +- Support Staff (10%) +- Managers (10%) +- Community Contributors, Enthusiasts & Other Folks (10%) -We welcome talks from first-time speakers, from industry experts, and from everyone in between. Whatever your background and experience, we prefer hearing about new approaches rather than about tried-and-tested technology. We especially welcome talks from underrepresented groups within the tech community. - -We've accepted talks from people who work in a variety of roles, including: +Other Information +----------------- -* Writers -* Developers -* Designers -* Testers -* Support -* Developer advocates -* Community managers -* Scientists -* Librarians -* Teachers +Based on your background, use this section to describe your qualifications to the selection committee, especially including community activities. From 4f06cb8c48a8eacdf9dc81a250347573021d1fa4 Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Fri, 1 Nov 2024 17:24:50 +0100 Subject: [PATCH 21/26] Dedupe --- docs/conf/portland/2025/cfp.rst | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index 60321be70..044660c4e 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -66,13 +66,9 @@ We want to hear a variety of viewpoints, so we limit speakers to two talks in an **Number of speakers** -We do strongly prefer talks written and given by a single speaker, and if you're planning to submit with a co-speaker, please let us know why you're doing so. +We prefer talks *presented* by one *single speaker*. If you're planning to submit with a co-speaker, please let us know why, and take note that it will affect the chances of your talk being selected. -**People on stage** - -We *strongly* prefer talks _presented_ by one *single speaker*. If you're planning to submit with a co-speaker, please let us know why, and take note that it will affect the chances of your talk being selected. - -You are of course welcome to write the talk with other people, as long as only one person is presenting. +You are of course welcome to write the talk with other people, if only one person is presenting. **Mix of roles and perspectives** From 72097edfefdc513f48be2ec39c445a3d076d08db Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Thu, 7 Nov 2024 16:50:09 +0000 Subject: [PATCH 22/26] Were gonna ask for this after acceptance --- docs/_data/portland-2025-config.yaml | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/_data/portland-2025-config.yaml b/docs/_data/portland-2025-config.yaml index 093f53785..dff69232f 100644 --- a/docs/_data/portland-2025-config.yaml +++ b/docs/_data/portland-2025-config.yaml @@ -158,7 +158,6 @@ cfp: url: "https://pretalx.com/wtd-portland-2025/cfp" # Open October 6 (Mon) -> 9 weeks to submit ends: "January 21, 2025" # (Mon) 1 week, to review. It'll take a little longer to announce notification: "February 04, 2025" # (Mon) 8 weeks to write and prepare - info_by: "April 21, 2025" # (Mon) 2 weeks before for info for emcee slides_by: "April 28, 2025" # (Mon) 1 week before preview: "TODO" # Preview URL TODO From b3c8532255f541a79e03050fc4a402e47ee34b46 Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Thu, 7 Nov 2024 16:50:34 +0000 Subject: [PATCH 23/26] Update the date --- docs/conf/portland/2025/news/announcing-cfp.rst | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/conf/portland/2025/news/announcing-cfp.rst b/docs/conf/portland/2025/news/announcing-cfp.rst index 63f702456..ec217a24a 100644 --- a/docs/conf/portland/2025/news/announcing-cfp.rst +++ b/docs/conf/portland/2025/news/announcing-cfp.rst @@ -2,17 +2,17 @@ :banner: _static/conf/images/headers/portland-2024-speakers.jpg :og:image: _static/conf/images/headers/portland-2024-speakers.jpg -.. post:: Oct 28, 2024 +.. post:: Nov 11, 2024 :tags: {{shortcode}}-{{year}}, website, cfp, tickets Announcing the Call for Proposals and Sponsorship Prospectus ============================================================ -We're excited to announce our Portland `Call for Proposals `_, opening even earlier than last year. +We're excited to announce our Portland `Call for Proposals `_! We're also launching our `sponsorship prospectus `_ with all the information for sponsoring the conference. -Read on for more details about how you can get involved this year. +Read on for more details about getting involved this year. Call for Proposals ------------------ @@ -31,7 +31,6 @@ The Call for Proposals will be open until **11:59 PM {{cfp.ends}} PST**, so harn (If you'd prefer not to attend an in-person event due to COVID-19 or any other reason, keep an eye out for our Atlantic conference held online in a timezone accessible to people all over the world). - Sponsorship Updates ------------------- From 384f8cbacbe7f0988fafd65ba99bd5f69bf301db Mon Sep 17 00:00:00 2001 From: Eric Holscher <25510+ericholscher@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:53:16 -0900 Subject: [PATCH 24/26] Update docs/conf/portland/2025/news/announcing-cfp.rst --- docs/conf/portland/2025/news/announcing-cfp.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/conf/portland/2025/news/announcing-cfp.rst b/docs/conf/portland/2025/news/announcing-cfp.rst index ec217a24a..27f375431 100644 --- a/docs/conf/portland/2025/news/announcing-cfp.rst +++ b/docs/conf/portland/2025/news/announcing-cfp.rst @@ -44,6 +44,12 @@ Tickets Tickets will go on sale in {{ date.tickets_live }}. +Prices are the same as last year: + +* **Student or Unemployed Tickets**: *{{tickets.student.price}}* +* **Independent Tickets**: *{{tickets.independent.price}}* +* **Corporate Tickets**: *{{tickets.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 soon after opening ticket sales. From b84cbd889e52d9988acbaab0c35bf6b19614d21f Mon Sep 17 00:00:00 2001 From: Sam Wright Date: Fri, 8 Nov 2024 14:38:05 +0000 Subject: [PATCH 25/26] Final edits (i hope) --- docs/conf/portland/2025/cfp.rst | 37 ++++++++++++++++++--------------- 1 file changed, 20 insertions(+), 17 deletions(-) diff --git a/docs/conf/portland/2025/cfp.rst b/docs/conf/portland/2025/cfp.rst index 044660c4e..2b9356811 100644 --- a/docs/conf/portland/2025/cfp.rst +++ b/docs/conf/portland/2025/cfp.rst @@ -49,7 +49,7 @@ Write the Docs conferences are our opportunity to get together to explore and ce Between the talks on stage, the discussions in the Unconference, the collaboration on Writing Day and other conversations, 100% of the content for our conferences comes from our community! Your perspective on what makes good docs is what this conference is all about. - You'll have the chance to compare notes on what's happening in the industry, dig into questions of convention and good practice, and generally nerd out about all the things we love about documentation. +You'll have the chance to compare notes on what's happening in the industry, dig into questions of convention and good practice, and generally nerd out about all the things we love about documentation. Who we're looking for --------------------- @@ -111,6 +111,17 @@ Check out topics that might be related to your talk from previous years: * `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. + + Unsure about speaking? ------------------------ @@ -132,26 +143,25 @@ Proposals are rated on a scale of five, after which we meet and discuss the top- To actively promote diversity, we choose not to review talks anonymously, allowing us to intentionally balance various perspectives and backgrounds. -Speaker benefits & logistics ----------------------------- +{% if flagcfp %} + +Speaker benefits +---------------- -**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. If you already have a ticket, we will of course refund it - just drop us an email at `{{email}} `_. -{% if flagcfp %} - -**Logistics** +Speaker logistics +----------------- -Presentations will be **{{date.short}}**, scheduled in 30-minute blocks, delivered **in-person, on-stage, live in {{city}}.** +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. 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. -Note that 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. - Timeline overview ----------------- @@ -176,13 +186,6 @@ Take a look at our :doc:`Example proposal `, with additional g Submit your proposal -------------------------- -Please make sure you read this entire page before submitting your proposal, 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. - Submit your proposal at {{cfp.url}}. You'll need to sign up for a Pretalx account, unless you already have one from a previous conference. .. raw:: html From 7bfdc43450c5d8425a71165389b1bcfb62f14cfe Mon Sep 17 00:00:00 2001 From: Sam Date: Sat, 9 Nov 2024 11:58:50 +0200 Subject: [PATCH 26/26] Update docs/conf/portland/2025/news/announcing-cfp.rst --- docs/conf/portland/2025/news/announcing-cfp.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/conf/portland/2025/news/announcing-cfp.rst b/docs/conf/portland/2025/news/announcing-cfp.rst index 27f375431..4a6a328ca 100644 --- a/docs/conf/portland/2025/news/announcing-cfp.rst +++ b/docs/conf/portland/2025/news/announcing-cfp.rst @@ -50,6 +50,12 @@ Prices are the same as last year: * **Independent Tickets**: *{{tickets.independent.price}}* * **Corporate Tickets**: *{{tickets.corporate.price}}* +Prices are the same as last year: + +* **Student or Unemployed Tickets**: *{{tickets.student.price}}* +* **Independent Tickets**: *{{tickets.independent.price}}* +* **Corporate Tickets**: *{{tickets.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 soon after opening ticket sales.