diff --git a/docs/_data/portland-2025-config.yaml b/docs/_data/portland-2025-config.yaml
index bafd7a0cf7..968438c92c 100644
--- a/docs/_data/portland-2025-config.yaml
+++ b/docs/_data/portland-2025-config.yaml
@@ -1,5 +1,4 @@
 name: Portland
-
 shortcode: portland
 year: 2025
 city: Portland
@@ -14,7 +13,7 @@ hex: 3dd94a
 time_format: 12h
 
 photos:
-  default: _static/conf/images/headers/portland-2024-group.jpg
+  default: _static/conf/images/headers/portland-2025-small-group.jpg
 
 buttons:
   top:
@@ -83,8 +82,8 @@ sponsorship:
     price: $14,000
 
 grants:
-  url: ""
-  ends: 'February 1, 2025'
+  url: https://docs.google.com/forms/d/e/1FAIpQLSf3fGfW_8W1x3oeKeoUpg8ZPLvyY4cQvO5Bii_OTrgW97cLNw/viewform?embedded=true
+  ends: 'February 5, 2025'
   notification: 'February 14, 2025'
 
 shirts:
@@ -163,7 +162,11 @@ cfp:
 
 unconf:
   url: ""
-  date: "All day Monday and Tuesday"
+  date: "All day, Monday, May 5 and Tuesday, May 6"
+
+writing_day:
+  url: ""
+  date: Sunday, May 4, 9 AM - 5 PM
 
 hike:
   date: Saturday, May 3, 2 PM
@@ -265,10 +268,10 @@ sponsors:
     #   brand: Read the Docs
 
 # Things that change over time, listed in order of change
-flaglanding: True
+flaglanding: False
 flaghassponsors: True
 flagcfp: True
-flagticketsonsale: False
+flagticketsonsale: True
 flagsoldout: False
 flagspeakersannounced: False
 flagrunofshow: False
diff --git a/docs/_data/schema-config.yaml b/docs/_data/schema-config.yaml
index 8f3473e15a..3be947ba68 100644
--- a/docs/_data/schema-config.yaml
+++ b/docs/_data/schema-config.yaml
@@ -34,6 +34,7 @@ cfp: include('cfp-details', required=False)
 grants: include('grants-details', required=False)
 shirts: include('shirts-details', required=False)
 unconf: include('unconf-details', required=False)
+writing_day: include('writing_day-details', required=False)
 lightning_talks: include('lightning_talks-details', required=False)
 hike: include('hike-details', required=False)
 
@@ -191,8 +192,12 @@ unconf-details:
   url: str(required=True)
   date: str(required=False)
 
+writing_day-details:
+  url: str(required=False)
+  date: str(required=True)
+
 hike-details:
-  date: str(required=False)
+  date: str(required=True)
 
 lightning_talks-details:
   signup_url: str(required=True)
diff --git a/docs/_static/conf/images/headers/2025/grants.jpg b/docs/_static/conf/images/headers/2025/grants.jpg
new file mode 100644
index 0000000000..a43cdafb9c
Binary files /dev/null and b/docs/_static/conf/images/headers/2025/grants.jpg differ
diff --git a/docs/_static/conf/images/headers/2025/lightning-talks.jpg b/docs/_static/conf/images/headers/2025/lightning-talks.jpg
new file mode 100644
index 0000000000..e4278a1b35
Binary files /dev/null and b/docs/_static/conf/images/headers/2025/lightning-talks.jpg differ
diff --git a/docs/_static/conf/images/headers/2025/unconference.jpg b/docs/_static/conf/images/headers/2025/unconference.jpg
new file mode 100644
index 0000000000..137be5ad7f
Binary files /dev/null and b/docs/_static/conf/images/headers/2025/unconference.jpg differ
diff --git a/docs/_static/conf/images/headers/2025/volunteer.jpg b/docs/_static/conf/images/headers/2025/volunteer.jpg
new file mode 100644
index 0000000000..ec8abeeddf
Binary files /dev/null and b/docs/_static/conf/images/headers/2025/volunteer.jpg differ
diff --git a/docs/_static/conf/images/headers/2025/writing-day.jpg b/docs/_static/conf/images/headers/2025/writing-day.jpg
new file mode 100644
index 0000000000..104f151732
Binary files /dev/null and b/docs/_static/conf/images/headers/2025/writing-day.jpg differ
diff --git a/docs/_static/conf/images/pics/2025/lightning-talks.jpg b/docs/_static/conf/images/pics/2025/lightning-talks.jpg
new file mode 100644
index 0000000000..b2feb13880
Binary files /dev/null and b/docs/_static/conf/images/pics/2025/lightning-talks.jpg differ
diff --git a/docs/_static/conf/images/pics/2025/unconference.jpg b/docs/_static/conf/images/pics/2025/unconference.jpg
new file mode 100644
index 0000000000..cab2bca06e
Binary files /dev/null and b/docs/_static/conf/images/pics/2025/unconference.jpg differ
diff --git a/docs/_static/conf/images/pics/2025/volunteer.jpg b/docs/_static/conf/images/pics/2025/volunteer.jpg
new file mode 100644
index 0000000000..5eaa6db4e8
Binary files /dev/null and b/docs/_static/conf/images/pics/2025/volunteer.jpg differ
diff --git a/docs/_static/conf/images/pics/2025/writing-day-2.jpg b/docs/_static/conf/images/pics/2025/writing-day-2.jpg
new file mode 100644
index 0000000000..b05badfb62
Binary files /dev/null and b/docs/_static/conf/images/pics/2025/writing-day-2.jpg differ
diff --git a/docs/_static/conf/images/pics/2025/writing-day.jpg b/docs/_static/conf/images/pics/2025/writing-day.jpg
new file mode 100644
index 0000000000..9ba17a69a4
Binary files /dev/null and b/docs/_static/conf/images/pics/2025/writing-day.jpg differ
diff --git a/docs/_templates/2025/base.html b/docs/_templates/2025/base.html
index 170f9b1ef3..778b7a9869 100644
--- a/docs/_templates/2025/base.html
+++ b/docs/_templates/2025/base.html
@@ -97,9 +97,6 @@ <h2 class="uk-first-column"><a href="/conf/{{ shortcode }}/{{ year }}/sponsors/"
                         <a href="https://www.linkedin.com/company/write-the-docs">
                             <img style="height: 25px; border-radius: 5px;" src="{{ pathto('_static/conf/images/icons/linkedin.png', 1) }}" alt="LinkedIn">
                         </a>
-                        <a href="https://twitter.com/writethedocs">
-                            <img src="{{ pathto('_static/conf/images/icons/twitter-footer-white.svg', 1) }}" alt="Twitter">
-                        </a>
                         <a href="https://www.flickr.com/photos/writethedocs/">
                             <img src="{{ pathto('_static/conf/images/icons/flickr-footer-white.svg', 1) }}" alt="Flickr">
                         </a>
diff --git a/docs/_templates/2025/menu-desktop.html b/docs/_templates/2025/menu-desktop.html
index 25c88ae0ae..762faedf25 100644
--- a/docs/_templates/2025/menu-desktop.html
+++ b/docs/_templates/2025/menu-desktop.html
@@ -5,7 +5,9 @@
         <a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/schedule') }}">Program</a>
         <div class="uk-navbar-dropdown">
           <ul class="uk-nav uk-navbar-dropdown-nav">
+          {% if flaghasschedule %}
             <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/schedule') }}">Schedule</a></li>
+          {% endif %}
             {% if flagspeakersannounced %}
             <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/speakers') }}">Speakers</a></li>
             {% endif %}
@@ -17,9 +19,6 @@
             {% endif %}
             <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/lightning-talks') }}">Lightning Talks</a></li>
             <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/unconference') }}">Unconference</a></li>
-            {% if not flagisvirtual %}
-              <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/sponsor-expo') }}">Sponsor Expo</a></li>
-            {% endif %}
             {% if flaghashike %}
             <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/hike') }}">Hike</a></li>
             {% endif %}
@@ -62,13 +61,17 @@
           <ul class="uk-nav uk-navbar-dropdown-nav">
             <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/venue') }}">Venue</a></li>
             {% if not flagisvirtual %}
+            {% if flagspeakersannounced %}
                 <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/visiting') }}">Visiting {{ city }}</a></li>
                 <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/attendee-guide') }}">Attendee Guide</a></li>
+            {% endif %}
                 <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/health') }}">Health and Safety Policy</a></li>
                 <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/volunteer') }}">Volunteer Info</a></li>
             {% endif %}
             <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/code-of-conduct') }}">Code of Conduct</a></li>
+            {% if flagspeakersannounced %}
             <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/team') }}">Meet the Team</a></li>
+            {% endif %}
             <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/contact') }}">Contact us</a></li>
             {% if flaghasbadgeflair %}
             <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/badge-flair') }}">Badge Flair Contest</a></li>
@@ -93,7 +96,13 @@
     </ul>
   </li><!--- Parent element with it's children -->
 
-  <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/news') }}">News</a></li>
+  <li>
+    <ul class="uk-navbar-nav">
+      <li>
+        <a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/news') }}">News</a>
+      </li>
+    </ul>
+  </li>
 
   {% if flagcfp %}
   <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/cfp') }}" class="uk-button uk-button-ghost uk-text-uppercase">Speak</a></li>
diff --git a/docs/_templates/2025/menu-mobile.html b/docs/_templates/2025/menu-mobile.html
index 96410c445a..d3d0ba0151 100644
--- a/docs/_templates/2025/menu-mobile.html
+++ b/docs/_templates/2025/menu-mobile.html
@@ -2,7 +2,9 @@
   <li class="uk-parent">
     <a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/schedule') }}">Program</a>
     <ul class="uk-nav-sub">
+      {% if flaghasschedule %}
       <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/schedule') }}">Schedule</a></li>
+      {% endif %}
       {% if flagspeakersannounced %}
       <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/speakers') }}">Speakers</a></li>
       {% endif %}
@@ -14,9 +16,6 @@
       {% endif %}
       <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/lightning-talks') }}">Lightning Talks</a></li>
       <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/unconference') }}">Unconference</a></li>
-      {% if not flagisvirtual %}
-        <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/sponsor-expo') }}">Sponsor Expo</a></li>
-      {% endif %}
       {% if flaghashike %}
       <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/hike') }}">Hike</a></li>
       {% endif %}
@@ -47,13 +46,17 @@
     <ul class="uk-nav-sub">
       <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/venue') }}">Venue</a></li>
       {% if not flagisvirtual %}
+          {% if flagspeakersannounced %}
           <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/visiting') }}">Visiting {{ city }}</a></li>
           <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/attendee-guide') }}">Attendee Guide</a></li>
+          {% endif %}
           <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/health') }}">Health and Safety Policy</a></li>
           <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/volunteer') }}">Volunteer Info</a></li>
       {% endif %}
       <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/code-of-conduct') }}">Code of Conduct</a></li>
+      {% if flagspeakersannounced %}
       <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/team') }}">Meet the Team</a></li>
+      {% endif %}
       <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/contact') }}">Contact us</a></li>
       {% if flaghasbadgeflair %}
       <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/badge-flair') }}">Badge Flair Contest</a></li>
@@ -70,7 +73,9 @@
     </ul>
   </li>
 
-  <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/news') }}">News</a></li>
+  <li class="uk-parent">
+  <a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/news') }}">News</a>
+  </li>
 
   {% if flagcfp %}
   <li><a href="{{ pathto('conf/'+shortcode+'/'+year_str+'/cfp') }}"
diff --git a/docs/conf/portland/2025/contact.rst b/docs/conf/portland/2025/contact.rst
index aa61ee28ca..3d310e17e8 100644
--- a/docs/conf/portland/2025/contact.rst
+++ b/docs/conf/portland/2025/contact.rst
@@ -9,9 +9,12 @@ If you have any questions or concerns,
 the best way to reach us is via email.
 You can email us at {{ shortcode }}@writethedocs.org.
 
+{% if flagspeakersannounced %}
 
 Press Kit
 ---------
 
 If you're looking to get logos or other assets,
-you can find them on our :doc:`/conf/{{shortcode}}/{{year}}/press-kit` page.
\ No newline at end of file
+you can find them on our :doc:`/conf/{{shortcode}}/{{year}}/press-kit` page.
+
+{% endif %}
\ No newline at end of file
diff --git a/docs/conf/portland/2025/convince-your-manager.md b/docs/conf/portland/2025/convince-your-manager.md
new file mode 100644
index 0000000000..c860baf5be
--- /dev/null
+++ b/docs/conf/portland/2025/convince-your-manager.md
@@ -0,0 +1,101 @@
+---
+template: {{year}}/generic.html
+og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
+---
+
+# Convince Your Manager
+
+Do you need help justifying why your manager should send you to Write the Docs? Do you need help convincing your community to submit a Writing Day Project? Don’t worry – you’re not alone. Based on the experiences of some of our previous attendees, we’ve put together two sample emails and a list of resources below. Feel free to adapt and share with your employer and community to convince them that there are many benefits of attending!
+
+## Sample Email #1
+
+### Convince your manager to send you to Write the Docs
+
+Remember to change the things in [brackets]!
+
+*FROM: [your name]*
+
+*TO: [your employer or manager’s name]*
+
+*SUBJECT: Professional Development: Documentation Community Conference*
+
+*I’d like to attend Write the Docs Portland from May 4-6, 2025. This three-day event explores the art and science of documentation, and covers a diverse range of topics related to documentation in the software industry.*
+
+*Write the Docs conferences bring together everyone who writes the docs – Tech Writers, Developers, Developer Relations, Customer Support – making the events an ideal networking opportunity. Each conference successfully combines a number of different event formats to deliver engaging, practical, and timely content.*
+
+*There is a single track of talks, a parallel unconference event, and a community writing day. The [sessions from last year](https://www.writethedocs.org/conf/portland/2024/speakers/) will give you a good idea of the kinds of topics covered, many of which are relevant to my work.*
+
+*Costs:*
+
+- *[Conference ticket](https://www.writethedocs.org/conf/portland/2025/tickets/) - $650*
+
+*Benefits:*
+
+- *Discovering solutions to problems I’m facing at work*
+- *Exposure to the latest ideas, techniques, and tools for software docs*
+- *Opportunity to learn from the best doc teams in the industry*
+- *Building professional connections with other documentarians*
+
+*Thanks in advance, [your name]*
+
+### Corporate Resources
+
+When discussing how to pitch the conference, a few generally helpful tips emerged:
+
+- Highlight specific talks that relate to ongoing projects at work (after talk line up has been announced).
+- If your company is looking to hire another documentarian, the networking is an excellent resource.
+- Attending raises the visibility of your company in the community. 
+- Establishes your team's reputation for caring about their docs.
+- Share info about previous conferences. View the [main page overview](https://www.writethedocs.org/conf/portland/2025/) explaining Write the Docs, history, and schedule overview.
+
+## Sample Email # 2
+
+### Convince your manager or community to participate in Writing Day
+
+
+
+Remember to change the things in [brackets]!
+
+*FROM: [your name]*
+
+*TO: [your employer or community lead's name]*
+
+*SUBJECT: Docs hackathon: Documentation Community Conference*
+
+*I’d like to attend Write the Docs Portland from May 4-6, 2025. This three-day event explores the art and science of documentation, and covers a diverse range of topics related to documentation in the software industry. I am particularly interested in leading a project at Writing Day. I believe this event can positively impact our project and community.*
+
+*Writing Day is modeled after the concept of “code sprints” or “hackathons”, which are common in open-source conferences. The primary goal is to bring interesting individuals into the same room and have them work towards a shared goal; in this case the goal is creating or improving documentation or other related projects.*
+
+*Costs:*
+
+- *[Conference ticket](https://www.writethedocs.org/conf/portland/2025/tickets/) - $650*
+
+*Writing Day Benefits:*
+
+- *Introduce our project and community to a new audience and demographic in our industry*
+- *Get highlighted as a project in the conference blog and announcements (must submit online by April 17, 2025)*
+- *Onboard documentation enthusiasts to increase the likelihood of post-conference contributions*
+- *Strategically tackle documentation tickets and requests*
+- *Update existing documentation
+Peer review new and existing documentation*
+
+*Conference Benefits:*
+
+- *Exposure to the latest ideas, techniques, and tools for software docs*
+- *Opportunity to learn from the best doc teams in the industry*
+- *Building professional connections with other documentarians*
+
+*Bringing our project to Writing Day benefits us as a community. It gives us the opportunity to improve our documentation and create a more inclusive project.*
+
+*Thanks in advance, [your name]*
+
+### Writing Day Resources
+
+When discussing how to pitch Writing Day, a few helpful tips emerged:
+
+- Highlight specific projects from a previous [Writing Day project list. ](https://www.writethedocs.org/conf/portland/2023/writing-day/#project-listing)
+- If your community is looking for regular documentation contributions, this is a great place to onboard potential contributors and editors.
+- Attending raises the visibility of your company in the community. 
+- Establishes your team's reputation for caring about their docs.
+- Review the [tips for leading a project](https://www.writethedocs.org/conf/portland/2025/writing-day/#lead-a-project) at Writing Day.
+- Share info about previous conferences. View the [main page overview](https://www.writethedocs.org/conf/portland/2025/) explaining Write the Docs, history, and schedule overview.
diff --git a/docs/conf/portland/2025/convince-your-manager.rst b/docs/conf/portland/2025/convince-your-manager.rst
deleted file mode 100644
index a5f625fb7a..0000000000
--- a/docs/conf/portland/2025/convince-your-manager.rst
+++ /dev/null
@@ -1,142 +0,0 @@
-:template: {{year}}/generic.html
-:og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
-
-
-Convince Your Organization
-==========================
-
-Convince Your Manager
----------------------
-
-Do you need help justifying why your employer should send you to Write the Docs? Don't worry – you're not alone.
-Based on the experiences of some of our previous attendees, we've put together a sample email and list of resources below.
-Feel free to adapt and share with your manager to show them the many benefits of attending!
-
-Sample email
-^^^^^^^^^^^^^
-
-Remember to change the things in `[brackets]`!
-
-----
-
-  FROM: [your name]
-
-  TO: [your employer or manager's name]
-
-  SUBJECT: Professional Development: Documentation Community Conference
-
-  I'd like to attend Write the Docs {{city}}, which takes place {{ date.main }}. This three-day event explores the art and science of documentation, and covers a diverse range of topics related to documentation in the software industry.
-
-  Write the Docs conferences bring together everyone who writes the docs – Tech Writers, Developers, Developer Relations, Customer Support – making the events an ideal networking opportunity.
-  Each conference successfully combines a number of different event formats to deliver engaging, practical, and timely content.
-
-  There is a single track of talks, a parallel unconference event, and a community writing day. The `sessions from last year </conf/{{ shortcode }}/{{year-1}}/speakers/>`_ will give you a good idea of the kinds of topics covered, many of which are relevant to my work.
-
-  Costs:
-
-  * Conference ticket - {{tickets.corporate.price}}
-
-  Benefits:
-
-  * Discovering solutions to problems I'm facing at work
-  * Exposure to the latest ideas, techniques, and tools for software docs
-  * Opportunity to learn from the best doc teams in the industry
-  * Building professional connections with other documentarians
-
-  Thanks in advance,
-  [your name]
-
-----
-
-Corporate Resources
-^^^^^^^^^^^^^^^^^^^
-
-When discussing how to pitch the conference, a few generally helpful tips emerged:
-
-* Highlight a few specific talks that relate to ongoing projects at work. (This one's dependent on pitching after the talk line up has been announced).
-* If your company is looking to hire another documentarian, the job fair and networking at the event are an excellent resource.
-* Don't forget that one of the benefits to your attendance is that it raises the visibility of your company in the community. If your team wants a reputation for caring about their docs, having people at Write the Docs is a great way to do that.
-
-In addition, it can be useful to share some info about previous conferences. View the `main page overview </conf/{{shortcode}}/{{year}}/#schedule-overview>`_ explaining what is Write the Docs, history and schedule overview.
-
-Convince Your Community
------------------------
-
-Do you need help justifying why your community or employer should attend Write the Docs 
-and bring their project to Writing Day? 
-
-Don't worry, you're not alone. Based on the experiences of some of our previous attendees, 
-we've put together a sample email and list of resources below.
-
-Feel free to adapt and share with your community or employer to show them the many benefits of attending!
-
-Sample email
-^^^^^^^^^^^^
-
-Remember to change the things in `[brackets]`! You can edit this to work for more casual communication
-methods, such as Slack, Discord, etc.
-
-----
-
-  FROM: [your name]
-
-  TO: [your employer or community lead's name]
-
-  SUBJECT: Docs hackathon: Documentation Community Conference
-
-  I'd like to attend Write the Docs {{city}}, which takes place {{ date.main }}. This three-day 
-  event explores the art and science of documentation, and covers a diverse range of topics 
-  related to documentation in the software industry. I am particularly interested in Writing Day, 
-  I believe this event can positively impact our project and community.
-  
-  Writing Day is a community event modeled after the concept of “code sprints” or “hackathons”, 
-  which are common in open-source conferences. The idea is to get a bunch of people together 
-  and have them work towards a shared goal, in this case the goal is creating or improving 
-  documentation or other related projects.
-
-  Costs:
-
-  * Conference ticket
-
-  Writing Day Benefits:
-
-  * Introduce our project and community to a new audience and demographic in our industry
-  * Get highlighted as a project in the conference blog and announcements (`Submit online <https://www.writethedocs.org/conf/{{ shortcode }}/{{ year }}/news/call-for-projects-writing-day>`_ by *March 28, 2024* to be included)
-  * Onboard documentation enthusiasts to increase the likelihood of post-conference contributions
-  * Strategically tackle documentation tickets and requests
-  * Update existing documentation
-  * Peer review new and existing documentation
-
-  Conference Benefits:
-
-  * Exposure to the latest ideas, techniques, and tools for software docs
-  * Opportunity to learn from the best doc teams in the industry
-  * Building professional connections with other documentarians
-
-Bringing our project to Writing Day benefits us as a community. It gives us the opportunity to 
-improve our documentation and create a more inclusive project. Check out the `Call for Projects <https://www.writethedocs.org/conf/{{ shortcode }}/{{ year }}/call-for-projects-writing-day>`_ for more information.
-
-  Thanks in advance,
-  [your name]
-
-----
-
-Writing Day Resources
-^^^^^^^^^^^^^^^^^^^^^
-
-When discussing how to pitch Writing Day, a few helpful tips emerged:
-
-* Highlight a few specific projects that attended a previous Writing Day, such as `Writing Day, Portland 2023 <https://www.writethedocs.org/conf/portland/2023/writing-day/#project-listing>`_. 
-* If your community is looking for regular documentation contributions, Writing Day 
-  is a great place to onboard potential contributors and editors.
-* Don't forget that one of the benefits to your attendance is that it raises the 
-  visibility of your community and/or company in the Write the Docs community. 
-  If your project wants a reputation for caring about their docs, having people 
-  at Write the Docs is a great way to do that.
-
-You may find it useful to review the `tips and tricks for leading a project <https://www.writethedocs.org/conf/{{ shortcode }}/{{ year }}/writing-day/#lead-a-project>`_ at Writing Day.
-
-In addition, it can be useful to share some info about previous conferences. 
-View the `main page overview </conf/{{shortcode}}/{{year}}/#schedule-overview>`_ explaining what is Write the Docs, history, and schedule overview.
-
-
diff --git a/docs/conf/portland/2025/health.md b/docs/conf/portland/2025/health.md
index ffa4c0d2d5..c8a85c32e2 100644
--- a/docs/conf/portland/2025/health.md
+++ b/docs/conf/portland/2025/health.md
@@ -5,25 +5,24 @@ og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
 
 # Health and Safety Policy 
 
-**This policy is up to date as of December 2023.**
+**This policy is up to date as of December 2025.**
 
-## No Vaccination or Testing Requirement
+## Onsite Health and Safety Measures
 
-This year, we have removed our vaccination and testing mandate. We will not be requiring any specific COVID-related health measures to attend the event, however we will still provide a number of accommodations for people who have concerns.
+Please expect the following measures to be in place at the event:
 
-## Masks Provided
+- Physically-spaced audience seating on the 3rd level of the main auditorium
+- Event signage to allow for physical distancing
+- Plentiful hand sanitation stations and personal hand sanitizer onsite and available for participants
+- Antigen COVID tests available at registration, while supplies last
+- Masks available at registration, while supplies last
 
-We are not currently requiring that masks be worn in the venue. We will provide masks to attendees at our registration desk.
+## Mask Policy
 
-## Onsite health and safety measures
+Masks are optional. We are not currently requiring that masks be worn in the venue. 
 
-Please expect the following measures to be in place at the event:
+## No Vaccination or Testing Requirement
 
-* Physically-spaced audience seating on the 3rd level of the main auditorium
-* Additional event traffic flow signage to allow for physical distancing
-* Plentiful hand sanitation stations onsite
-* Personal hand sanitizer and wipes available for participants
-* Antigen COVID tests available at registration, while supplies last
-* Masks available at registration, while supplies last
+We will not be requiring any specific COVID-related health measures to attend the event.
 
-At a minimum, we will also be following all mandated venue and state guidelines. **This list, and all protocols, are subject to change if the COVID-19 situation changes. Changes to this policy will only add requirements, and will not remove requirements.**
+We will be following all mandated venue and state guidelines. **This list, and all protocols, are subject to change if the COVID-19 situation changes. Changes to this policy will only add requirements, and will not remove requirements.**
\ No newline at end of file
diff --git a/docs/conf/portland/2025/hike.md b/docs/conf/portland/2025/hike.md
new file mode 100644
index 0000000000..91df8321a7
--- /dev/null
+++ b/docs/conf/portland/2025/hike.md
@@ -0,0 +1,35 @@
+---
+template: {{year}}/generic.html
+og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
+banner: _static/conf/images/headers/hike.png
+---
+
+# Hike
+
+Every year we have a conference hike that kicks off the **unofficial** beginning of the conference. It has become a fantastic tradition and is a wonderful way to gather the day before the conference begins.
+
+We will be hiking in the amazing [Forest Park](https://forestparkconservancy.org/), the largest urban forested park in the country. It is conveniently located in Northwest Portland, and has a beautiful walk along a creek. 
+
+**The hike is around 5 miles long with 1,200 feet of elevation gain and is classified as a moderate hike. We’ll be going nice and slow so people can appreciate the views and forest.**
+
+It’s rained on us in the past, but we have faith it will be beautiful this year! We will hopefully see Mount Hood at the top :)
+
+## Schedule & Logistics
+
+- **Date: {{ hike.date }}** 
+- **Arrival:** Meet 15 minutes before the start time.
+- **Lunch (optional):** Join us at the [Nob Hill food carts](https://www.google.com/maps/place/Nob+Hill+Food+Carts/@45.5360531,-122.7007924,19.6z/data=!4m7!3m6!1s0x54950942eb34ca71:0xe277fed8c0cec152!8m2!3d45.5362156!4d-122.7000932!15sChZmb29kIGNhcnRzIG53IHBvcnRsYW5kkgEKZm9vZF9jb3VydOABAA!16s%2Fg%2F11vwhg4f9_?entry=tts) at 12:30pm for lunch. We'll leave for the trailhead at 1:40pm.
+- **Start:** [Lower Macleay Park](https://www.google.com/maps/place/Lower+Macleay+Park/@45.5336665,-122.7234215,16z/data=!4m7!3m6!1s0x549509e9f2adf02d:0x1b3668a7adc941d9!8m2!3d45.5359671!4d-122.7125142!15sChVNYWNsZWF5IFBhcmsgRW50cmFuY2VaFyIVbWFjbGVheSBwYXJrIGVudHJhbmNlkgEEcGFya5oBJENoZERTVWhOTUc5blMwVkpRMEZuU1VOb2RWQklaRzluUlJBQuABAA!16s%2Fg%2F11g7wcqxt9?coh=164777&entry=tt&shorturl=1). Meet at the pavilion at the park entrance.
+- **End:** Oregon Zoo around 5pm, where we will take the MAX back to town.
+- **Tickets:** Participating in the hike is free, but please register for your ticket so we can contact you in advance for day-of weather and logistics information.
+
+## What to Bring
+
+The temperature will likely be in the upper 50s and 60s, with a chance of rain. There is no predicting Portland Spring weather! Please bring:
+
+- **Comfortable shoes** that you are willing to get a bit muddy.
+- **Water!** There is water available halfway through the hike.
+- **Lightweight rain jacket** - it likely will not be too cold, but it might drizzle on you.
+- **High spirits!**
+
+We hope you will join us for this pre-conference activity!
diff --git a/docs/conf/portland/2025/hike.rst b/docs/conf/portland/2025/hike.rst
deleted file mode 100644
index 09142de79a..0000000000
--- a/docs/conf/portland/2025/hike.rst
+++ /dev/null
@@ -1,49 +0,0 @@
-:template: {{year}}/generic.html
-:banner: _static/conf/images/headers/hike.png
-:og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
-
-Hike
-====
-
-Every year we have a conference hike that kicks off the *unofficial* beginning of the conference. It has become a fantastic tradition and is a wonderful way to gather the day before the conference begins. 
-
-We will be hiking in the amazing `Forest Park <http://www.forestparkconservancy.org/>`__, the largest urban forested park in the country. It is conveniently located in Northwest Portland, and has a beautiful walk along a creek. 
-
-It's rained on us in the past, but we have faith it will be beautiful this year! We will hopefully see Mount Hood at the top :)
-
-Schedule & Logistics
---------------------
-
-- **Date:** **{{ hike.date }}**. Meet 15 minutes before the start time.
-- **Lunch:** (Optional) Join us at the `Nob Hill Food carts <https://maps.app.goo.gl/LFdYXc69v8daeKSG8>`_ at 12:30pm for lunch. Leaving for the trailhead at 1:40pm.
-- **Start:** Lower Macleay Park** (`Map link <https://goo.gl/maps/bU7MAMsKCJAbG3zFA>`__). Meet at the pavilion at the park entrance.
-- **End:** Oregon Zoo around 5pm, where we will take the MAX back to town.
-- **Tickets:** `Register your hike ticket <https://ti.to/writethedocs/write-the-docs-portland-2024/with/hike-ticket>`_
-
-Please register for your ticket so we can contact you in advance for day-of weather and logistics information.
-
-
-.. figure:: /_static/img/2015/hike/balch.jpg
-   :alt: Balch Creek
-
-   A view along the hike.
-
-What to Bring 
--------------
-
-The temperature will likely be in the upper 50s and 60s, with a chance of rain. There is no predicting Portland Spring weather! Please bring:
-
-- **Comfortable shoes**, that you are willing to get a bit muddy.
-- **Water!** There is water available halfway through the hike.
-- **Light rain jacket**. It likely will not be too cold, but it might drizzle on you.
-- **High spirits!**
-
-The Hike
---------
-
-The hike will be around 5 miles long, and have 1,200 feet of elevation gain. This classifies as a *moderate* hike. We'll be going nice and slow so people can appreciate the views and forest.
-
-We hope you will join us for this pre-conference activity!
-
-.. figure:: /_static/img/2015/hike/pittock.jpg
-   :alt: The view from Pittock Mansion
diff --git a/docs/conf/portland/2025/lightning-talks.md b/docs/conf/portland/2025/lightning-talks.md
new file mode 100644
index 0000000000..af29279eb6
--- /dev/null
+++ b/docs/conf/portland/2025/lightning-talks.md
@@ -0,0 +1,131 @@
+---
+template: {{year}}/generic.html
+og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
+banner: _static/conf/images/headers/2025/lightning-talks.jpg
+---
+
+# What is a Lightning Talk?
+
+A Lightning Talk is a brief presentation, lasting up to five minutes, where you share an idea, concept, or piece of information that you find interesting. These talks can cover technical or non-technical topics - whatever you are passionate about!
+
+Lightning Talks are a fantastic opportunity for first-time speakers. Regardless of your speaking experience, we invite you to submit a talk.
+
+**Supporting first-time speakers is important to us, so we have created two speaker categories:**
+
+- First-time speakers
+- Experienced speakers
+
+Our goal is to have a balance between first-time and experienced speakers. 
+
+## Schedule and Logistics
+
+**Date: Monday, May 5 and Tuesday, May 6 after lunch**
+
+Submit your Lightning Talk in person at the registration/check-in table.
+
+**Submissions are open:**
+
+- During Writing Day on Sunday
+- Monday morning, until the end of the last morning break
+- Monday afternoon, post-Monday Lightning Talks
+- Tuesday morning, until the end of the last morning break
+
+**Speaker selection and announcements:**
+
+The coordinator, with staff support, selects the speakers. The speakers are announced onstage after the final morning talk and before lunch on Monday and Tuesday. You do not have to be present to be selected, but it is helpful. The coordinator also contacts the speakers by phone to confirm their acceptance. 
+
+**Tech check:**
+- Fifteen minutes before Lightning Talks begin on Monday and Tuesday.
+- Speaking order is confirmed during tech check.
+- Speakers using tech, such as slides, etc, have the opportunity to test it.
+
+**Lightning Talks!**
+
+- Coordinator introduces and explains Lightning Talks to attendees.
+- Each speaker is introduced and given five minutes to present.
+- There is a countdown timer for each presentation. Speakers receive a signal when they have one minute remaining.
+- The coordinator stops speakers after five minutes.
+
+Exact times to be posted on our [Schedule](/conf/{{shortcode}}/{{year}}/schedule) page.
+
+![Lightning Talks](/_static/conf/images/pics/2025/lightning-talks.jpg)
+
+## Planning Your Lightning Talk
+
+A Lightning Talk is five minutes and intentionally designed to encourage speakers to be mindful in how they communicate their topic. Use the time to give an overview, provide insights, and ignite curiosity. 
+
+### 1. Choose a topic
+
+You are welcome to submit any topic you are passionate about. It does not have to be related to documentation. Some of our most popular Lightning Talk topics included legos, music, design software, and more.
+
+
+**Topic selection tips:**
+
+- A concept, process, or tool that you are learning or learned recently.
+- A retrospective overview, what went right/wrong during a project you are doing or finished.
+- Any relevant content that the audience might be interested in knowing more about.
+- Technical topics are wonderful and welcome but not mandatory.
+
+### 2. Create an outline
+
+- Who is your audience?
+- What is the goal of your talk?
+- What points do you need to make to help the audience understand your goal?
+
+### 3. Choose points of interest
+
+- What could you use this for or when could you use it? Have you already used it? How?
+- When would it not be as useful? What are some contraindications to using it?
+- Resources related to the subject, including books, documentation, and URLs.
+- Are there any projects or companies that are using what you are sharing?
+- Is this something you’d like to collaborate with others on? Feel free to ASK!
+- What are some of the challenges related to using, building, or configuring what you’re showing?
+
+Remember how quickly five minutes goes by when choosing what to include!
+
+## Presentation Options
+
+While there is a short tech check to acclimate you to the stage, all technology is optional so proceed at your own risk!
+
+**Slides**
+
+
+- Use a platform you are familiar with - Microsoft Word, Keynote, a PDF, a website, etc. Even a terminal or console window where you enter commands can work well for presenting your ideas.
+- Don’t worry if it does not look polished; Lightning Talks do not need to be!
+- Keep in mind that the projector is lower resolution, typically 1024x768. Low-contrast slides don’t display well.
+- Remember to adjust your font! This is key for terminal or console examples, you need a large font so everyone can see what you’re typing.
+- If you plan to use code examples, have them written, debugged, and ready to go. Watching someone write code as they go can be great in a longer deep-dive type of talk, but it’s not very well-suited to a Lightning Talk.
+
+**Live demos**
+
+You may have the desire to do a live demonstration. It seems like an easy way to help the audience see your vision, and it is… if it works! In most cases, live demos rarely convey your goals and often fail.
+
+A derailed demo can distress even the most skilled presenters. If you choose to do a demo and it goes wrong, have a backup story to explain what the demo would have shown and revert to it if necessary.
+
+**Equipment**
+
+- Be self-sufficient. Bring everything you need to do your presentation - computer, cords, adaptors to connect to a monitor or projector, etc.
+- Download slides or load web pages you need into your browser beforehand. Do not rely on the internet as it has proven to drop the connection during talks.
+- Keep a backup copy of your presentation on a USB removable storage device.
+
+## Your Moment on Stage
+
+Take a deep breath and go for it. You are among friends and colleagues. We are excited for your presentation! Nobody minds if you make mistakes. We are here to support you.
+
+This may be something you do once, or maybe it will spark a love for presenting for you. Many folks begin their speaking career in the tech industry with Lightning Talks.
+
+Enjoy your five minutes; you are going to do great! :)
+
+## Create Opportunities for Follow Up
+Lightning Talks can create wonderful opportunities such as hallway conversations, Unconference sessions, and sometimes, future presentations.
+
+- Consider using the final moments of your presentation to let the audience know how to follow up with you.
+- If you plan to share your content, let them know how to access it.
+- Share your social media information (optional).
+- Host your own Unconference session (optional).
+- Be available to speak afterwards in the hallway (optional).
+
+## Acknowledgements
+Special thanks to the Portland Python Users Group for use of this content.
+
+Lightning Talks: A Guide for Beginners by Michelle Rowley of PDX Python is licensed under a [Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License](https://creativecommons.org/licenses/by-nc-sa/4.0/).
\ No newline at end of file
diff --git a/docs/conf/portland/2025/lightning-talks.rst b/docs/conf/portland/2025/lightning-talks.rst
deleted file mode 100644
index 2ad0578585..0000000000
--- a/docs/conf/portland/2025/lightning-talks.rst
+++ /dev/null
@@ -1,145 +0,0 @@
-:template: {{year}}/generic.html
-:og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
-
-Lightning Talks
-===============
-
-What is a Lightning Talk?
--------------------------
-
-A lightning talk is a short talk, up to 5 minutes, where you share an idea, concept, or a bit of information that you find interesting. The talks can cover technical or non-technical topics - whatever you are passionate about!
-
-Lightning talks are a fantastic opportunity for first time presenters. No matter what your speaking experience level is, you are invited to submit a talk.
-
-Creating opportunities for first time speakers is important to us, so we have created **two groups of speakers**:
-
-* First-time speakers
-* Experienced speakers
-
-Our goal is to have a mix of first-time and experienced speakers. You can let us know your group on your submission form.
-
-Schedule & Logistics
-----------------------
-
-**Date and time: Monday, April 15 & Tuesday April 16 after lunch**
-
-Submit your lightning talk in person at the registration/check-in table throughout the conference.
-
-**Submissions are open:**
-
--  During Writing Day.
--  Monday morning until the end of the last morning break.
--  Monday afternoon, post Monday Lightning Talks.
--  Tuesday morning until the end of the last morning break.
-
-**Speaker selection and announcements:**
-
-- The coordinator selects the tentative speakers.
-- The tentative speakers are announced on stage at the end of the last morning talk on Monday and Tuesday. You do not have to be present to be selected, but it is helpful. 
-- The coordinator also contacts the speakers to confirm their acceptance and inform them of the time and place for the tech check.
-
-**Tech check**: 
-
-- Ten minutes before lunch ends on the main stage on Monday and Tuesaday.
-- Speaking order is confirmed during tech check.
-- Speakers using tech, such as slides, etc, have the opportunity to test it.
-
-**Lightning Talks begin:**
-
-- The coordinator explains to attendees how Lightning Talks work.
-- Each speaker is introduced and they have 5 minutes to present.
-- There is a countdown timer for each presentation. Speakers receive a notice when they have 1 minute remaining.
-- The coordinator stops speakers at the 5 minute mark.
-
-Exact times to be posted on the :doc:`/conf/{{shortcode}}/{{year}}/schedule` page.
-
-
-Plan your Lightning Talk
-------------------------
-
-A lightning talk is no more than five minutes long! This is intentional and designed to encourage speakers to be tactile in how they present their topic. Use your time to give an overview, provide insights, and encourage curiosity. 
-
-Speakers can talk about anything, it does not have to be related to documentation. Some of our most popular lightning talk topics included legos, music, design software, to name a few.
-
-**1. Choose a topic**
-
-You are welcome to submit any topic you are passionate about and can pitch in your submission summary.
-
-**Topic selection tips:**
-
-- A concept, process, or tool that you are learning or learned recently.
-- A retrospective overview, what went right/wrong during a project you are doing or finished.
-- Any relevant content that the audience might be interested in knowing more about.
-
-Technical topics are wonderful and welcome but are not mandatory. We enjoy having a variety of topics to entice your fellow attendees.
-
-**2. Create an outline**
-
-- Consider the audience. 
-- What is the goal of your talk? 
-- What points do you need to make to help them understand your goal? 
- 
-**3. Choose points of interest**
-
-- What could you use this for or when could you use it? Have you already used it? How?
-- When would it not be as useful? What are some contraindications to using it?
-- Resources related to the subject, including books, documentation, and URLs.
-- Are there any projects or companies that are using what you are sharing?
-- Is this something you'd like to collaborate with others on? Feel free to ASK!
-- What are some of the challenges related to using, building, or configuring what you're showing?
-
-Remember how quickly five minutes goes by when choosing what to include!
-
-Presentation Options
---------------------
-
-While there is a short tech check to acclimate you to the stage... all technology is optional and at your own risk.
-
-**Slides**
-
-If you choose to use slides or similar presentation tools. Consider the following recommendations:
-
-- Use a platform you are familiar with - Microsoft Word, Keynote, a PDF, a website, to name a few. Even a terminal or console window where you enter commands can work well for presenting your ideas.
-- Don’t worry if it does not look polished; lightning talks do not need to be!
-- Keep in mind that the projector is lower resolution, typically 1024x768. Low-contrast slides don't display well.
-- Remember to adjust your font! This is key for terminal or console examples, you need a large font so everyone can see what you’re typing.
-- If you plan to use code examples, have them written, debugged, and ready to go. Watching someone write code as they go can be great in a longer deep-dive type of talk, but it's not very well-suited to a lightning talk.
-
-
-**Live demos**
-
-You may have the urge to do a live demonstration. It seems like an easy way to help the audience see your vision, and it is… if it works! In most cases, live demos rarely convey your goals and often, fail. 
-
-A derailed demo can distress even the most skilled presenters. If you choose to do a demo and it goes wrong, have a backup story to explain what the demo would have shown and revert to it if necessary.
-
-**Equipment**
-
-- Be self-sufficient. Bring everything you need to do your presentation - computer, cords, adaptors to connect to a monitor or projector, etc.
-- Download slides or load web pages you need into your browser beforehand. Do not rely on the internet as it has proven to drop the connection during talks.
-- Keep a backup copy of your presentation on a USB memory stick.
-
-Create Opportunities for Follow Up
-----------------------------------
-
-Lightning Talks can create wonderful opportunities such as hallway conversations, unconference sessions, and sometimes, future presentations.
-
-- Consider using the final moments of your presentation to let the audience know how to follow up with you. If you plan to share your content, let them know how to access it. 
-- Share your social media information (optional).
-- Host your own unconference session (optional).
-
-Your Time on Stage
-------------------
-
-Take a deep breath and go for it. You are among friends and colleagues. We are excited for your presentation! Nobody minds if you make mistakes; we are here to support you.
-
-This may be something you do once, or maybe it creates a love for presenting. Many folks begin their speaking career in the tech industry with lightning talks. 
-
-Enjoy your five minutes, you are going to do great! :)
-
-
-Acknowledgements
-----------------
-
-Special thanks to the Portland Python Users Group for use of this content.
-
-Lightning Talks: A Guide for Beginners by Michelle Rowley of PDX Python is licensed under a `Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License <http://creativecommons.org/licenses/by-nc-sa/4.0/>`__.
diff --git a/docs/conf/portland/2025/news/announcing-tickets.rst b/docs/conf/portland/2025/news/announcing-tickets.rst
new file mode 100644
index 0000000000..983fde60bd
--- /dev/null
+++ b/docs/conf/portland/2025/news/announcing-tickets.rst
@@ -0,0 +1,59 @@
+:template: {{year}}/generic.html
+:og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
+
+.. post:: Dec 16, 2024
+   :tags: {{shortcode}}-{{year}}, website, tickets, grants, volunteers, cfp, sponsors
+
+Tickets on Sale for Write the Docs Portland 2025
+================================================
+
+Happy December, documentarians!
+
+We’re thrilled to announce that `tickets are now available for Write the Docs Portland 2025 <https://www.writethedocs.org/conf/{{shortcode}}/{{year}}/tickets/>`_!
+
+Join us for our 13th annual conference in Portland. It's a great opportunity to meet fellow documentarians, learn new skills, and get inspired.
+
+We have some high-level information for you below.
+
+Full website is available
+-------------------------
+
+Our `full event website <https://www.writethedocs.org/conf/{{shortcode}}/{{year}}/>`_ is live with information about all the events and basic travel information.
+
+The website has lots of details about the conference events. Stay tuned for more updates on food, transportation and more.
+
+Opportunity Grants
+------------------
+
+Interested in attending but need extra financial support? We strive to provide an accessible conference for folks of all backgrounds to join. Our opportunity grant application is now open. 
+
+Visit our `Opportunity Grants page <https://www.writethedocs.org/conf/{{shortcode}}/{{year}}/opportunity-grants/>`_ for more information.
+
+Volunteers
+----------
+
+Our volunteers make the conference happen each year, and it's a great group of folks. Want to help out and attend for free? Volunteer with us this year!
+
+Visit our `volunteer page <https://www.writethedocs.org/conf/{{shortcode}}/{{year}}/volunteer/>`_ to learn more and sign up.
+
+Call for Proposals
+------------------
+
+Our Call for Proposals is still open, and we'd love for you to be part of the conference this year.
+
+Our `Call for Proposals <https://www.writethedocs.org/conf/{{shortcode}}/{{year}}/cfp/>`_ page has details, and all the information you need to submit a talk.
+
+**Submit your talk by {{ cfp.ends }}!**
+
+Thanks to our sponsors
+----------------------
+
+We appreciate the support of our sponsors. Thank you to the following companies:
+
+.. datatemplate::
+   :source: /_data/{{shortcode}}-{{year}}-config.yaml
+   :template: {{year}}/sponsors-simplelist.rst
+
+Your company can `become a sponsor <https://www.writethedocs.org/conf/{{shortcode}}/{{year}}/sponsors/prospectus/>`_ today!
+
+We're excited to see everyone in Portland.
\ No newline at end of file
diff --git a/docs/conf/portland/2025/opportunity-grants.md b/docs/conf/portland/2025/opportunity-grants.md
new file mode 100644
index 0000000000..14a3aef435
--- /dev/null
+++ b/docs/conf/portland/2025/opportunity-grants.md
@@ -0,0 +1,75 @@
+---
+template: {{year}}/generic.html
+og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
+banner: _static/conf/images/headers/2025/grants.jpg
+---
+
+# Opportunity Grants
+
+The grant program for Write the Docs Portland 2025 supports people who would otherwise not be able to attend the conference, by covering ticket and/or attendance costs. 
+
+## Eligibility
+
+Applications are open to anyone who wants to attend Write the Docs. We encourage anyone to apply who would otherwise have difficulty attending.
+
+You are welcome to apply regardless of your experience level, background, or reason making it difficult for you to cover the cost.
+
+You are welcome to apply, even if you have received a grant before from our conferences or any others.
+
+We prioritize applications based on the overall impact that granting an application will have on the applicant, the Write the Docs community, and the applicant’s wider community and country. However, there are no requirements for you to meet. In other words, if you’re unsure, please apply.
+
+Grant applicants, like all other participants in the Write the Documents community, are required to follow the [Code of Conduct](https://www.writethedocs.org/conf/portland/2025/code-of-conduct/).
+
+## Schedule
+
+- **Now - {{ grants.ends }}:** Grant applications open
+- **{{ grants.notification }}:** Grant recipients notified
+
+## What is Covered
+
+**All grants include a free conference ticket.** This is the most common and possible grant for us to award. View our [ticket page](https://www.writethedocs.org/conf/portland/2025/tickets/) for what is included with a conference ticket.
+
+We can assist with typical costs such as travel and accommodation, but you may request other costs you need covered to attend.
+
+This list can include, but is not limited to:
+
+- Travel (flights, gas, rideshare, etc.)
+- Accommodations
+- Meals
+- Additional expenses (childcare, loss of wages, etc.)
+
+The application form will ask for an estimate of your costs.
+
+## Grant Amounts
+
+The total amount of grant funds to be distributed is based upon sponsors and number of tickets sold. We will not know the full amount until we near the deadline. In 2024, $3,500 was distributed in grant funds. There is no limit on the amount you request, but please consider this amount when making your request. We rarely fund only one individual and aim to use our budget for two or more people. We do not award partial grants.
+
+## Are you part of a marginalized or underrepresented group in tech?
+
+We encourage and may prioritize applications from people who are part of a marginalized or underrepresented group in tech. 
+
+These groups include, but are not limited to:
+
+- Women and other gender minorities of all expressions and identities; for example trans, agender, and non-binary people 
+- People of color
+- Sexuality minorities, including asexual people
+- People with disabilities, both visible and invisible
+- Neurodivergent people
+- People with chronic illnesses or diseases
+- Religious and ethnic minorities
+- Age minorities (under ~21, over ~50)
+- People experiencing poverty
+- Homeless and home/food insecure people
+- Caregivers of children or other dependents
+- People who have experienced trauma and its aftermath (PTSD, anxiety, etc)
+- People living with or recovering from substance abuse
+
+You do not have to tell us which underrepresented group(s) you belong to.
+
+**Note:** Grant applications will be seen only by the conference team, and we will never publish grant applications or publicly name grant recipients. You are of course free to share if you applied or received a grant yourself.
+
+## Application
+
+<iframe src="{{ grants.url }}?embedded=true" width="760" height="850" frameborder="0" marginheight="0" marginwidth="0">Loading...</iframe>
+
+You can also view [the application form]({{ grants.url }}) in its own page.
diff --git a/docs/conf/portland/2025/opportunity-grants.rst b/docs/conf/portland/2025/opportunity-grants.rst
deleted file mode 100644
index 5eda2e8ec6..0000000000
--- a/docs/conf/portland/2025/opportunity-grants.rst
+++ /dev/null
@@ -1,92 +0,0 @@
-:template: {{year}}/generic.html
-:og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
-
-Opportunity grants
-==================
-
-The grant program for Write the Docs {{ name }} {{ year }} supports people who would not be able to attend the conference by covering ticket and/or attendance costs. Applications are open to anyone who wants to attend Write the Docs.
-
-{% if grants and grants.url %}
-To apply, fill in the form below.
-{% endif %}
-
-Who is Eligible
-----------------
-
-We encourage anyone to apply who would otherwise have difficulties attending the conference.
-
-You are welcome to apply, even if you have received a grant before from our conferences or any others.
-
-You are welcome to apply regardless of your experience level, background or reason making it difficult for you to cover the cost.
-
-We prioritize applications based on the overall impact that granting an application will have on the applicant, the Write the Docs community, and the applicant's wider community and country, compared to others. However, there are no requirements for you to meet. **In other words, if you're not sure, feel free to apply.**
-
-Grant applicants, like all other participants in the Write the Documents community, are required to follow the Code of Conduct: https://www.writethedocs.org/code-of-conduct/.
-
-*Please note: Grant applications will be seen only by the conference team, and we will never publish grant applications or publicly name grant recipients.*
-
-
-Schedule
-----------------
-
-* **Now - February 1:** Grant applications open
-* **February 14:** Grant recipients notified 
-
-What is covered
-----------------
-
-**All grants include a free conference ticket for the conference.** Note that this year, the conference ticket does not include meals.
-
-We can cover typical costs like travel and accommodation,
-but you may include other costs you need covered to be able to attend. 
-
-This list can include, but is not limited to:
-
-* Travel (flights, gas, rideshare, etc.)
-* Accommodations
-* Meals
-* Other costs (childcare, loss of wages, etc.)
-
-The application form will ask for an estimate of your costs.
-
-Are you part of a marginalized or underrepresented group in tech?
-------------------------------------------------------------------
-
-Our grant program is open to anyone who wants to attend Write the Docs.
-However, we may prioritise applications from people who are part of a marginalized or underrepresented group in tech. If you are not part of any of these groups, you are still welcome to apply.
-
-These groups include, but are not limited to:
-
-* women and other gender minorities of all expressions and identities;  for example trans, agender and non-binary people
-* people of color
-* sexuality minorities, including asexual people
-* people with disabilities, both visible and invisible
-* neurodivergent people
-* people with chronic illnesses or diseases
-* religious and ethnic minorities
-* age minorities (under ~21, over ~50)
-* people experiencing poverty
-* homeless and home/food insecure people
-* caregivers of children or other dependents
-* people who have experienced trauma and its aftermath (PTSD, anxiety, etc)
-* people living with or recovering from substance abuse
-
-You do not have to tell us which underrepresented group(s) you belong to.
-
-Grant Amounts
-----------------
-
-The total amount of grant funds to be distributed is based upon sponsors and number of tickets sold. We will not know the full amount until we near the deadline. In 2023, $4,000 was distributed in grant funds. There is no limit on the amount you request but please note, we do not award partial grants. Free conference tickets are the most possible for us to grant. 
-
-{% if grants and grants.url %}
-
-Submit your application
---------------------------
-
-.. raw:: html
-
-	<iframe src="{{ grants.url }}?embedded=true" width="760" height="850" frameborder="0" marginheight="0" marginwidth="0">Loading...</iframe>
-
-You can also view `the application form <{{ grants.url }}>`_ in its own page.
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/conf/portland/2025/schedule.rst b/docs/conf/portland/2025/schedule.rst
index feb3816317..acec159496 100644
--- a/docs/conf/portland/2025/schedule.rst
+++ b/docs/conf/portland/2025/schedule.rst
@@ -9,7 +9,7 @@ Each year we organize a wide range of events so that people can come together, c
 
 {% if not flaghasschedule %}
 
-**Full schedule will be released in March 2024.** See the `schedule overview </conf/{{shortcode}}/{{year}}/#schedule-overview>`_ for high level details.
+**Full schedule will be released closer to the conference.** See the `schedule overview </conf/{{shortcode}}/{{year}}/#schedule-overview>`_ for high level details.
 
 {% else %}
 
diff --git a/docs/conf/portland/2025/sponsor-expo.rst b/docs/conf/portland/2025/sponsor-expo.rst
deleted file mode 100644
index beac92be26..0000000000
--- a/docs/conf/portland/2025/sponsor-expo.rst
+++ /dev/null
@@ -1,19 +0,0 @@
-:template: {{year}}/generic.html
-:og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
-
-Sponsor Expo
-============
-
-Each year we invite our top sponsors to engage with our attendees throughout the conference and during our Sponsor Expo. Sponsors can participate in two ways:
-
-* **Hiring:** Companies that are hiring and can speak with attendees about work and available jobs.
-* **Products:** Companies that build products for docs folks, where attendees can learn more about what people are building.
-
-Write the Docs looks forward to facilitating constructive networking, connecting people with jobs and employers, and hearing more from some of our sponsors. 
-
-Schedule
---------
-
-Our sponsors will be available all day Monday & Tuesday.
-
-Exact times are posted on our :doc:`/conf/{{shortcode}}/{{year}}/schedule` page.
diff --git a/docs/conf/portland/2025/tickets.rst b/docs/conf/portland/2025/tickets.rst
index e43ced502c..935d0d5cbd 100644
--- a/docs/conf/portland/2025/tickets.rst
+++ b/docs/conf/portland/2025/tickets.rst
@@ -4,9 +4,6 @@
 Tickets
 =======
 
-Ticket Information
-------------------
-
 {% if flagticketsonsale %}
 
 **Tickets are on sale now!**
@@ -15,9 +12,6 @@ We're excited to invite you to our {{ year }} conference in {{ city }}.
 
 {% elif flagsoldout %}
 
-Ticket status
-~~~~~~~~~~~~~
-
 **Tickets are sold out!**
 
 {% else %}
@@ -26,13 +20,13 @@ Ticket status
 
 {% endif %}
 
-Ticket details
-~~~~~~~~~~~~~~
+Ticket Information
+------------------
 
 Write the Docs {{ name }} {{ year }} is an in-person conference. Each ticket includes:
 
 * Entry to all conference events and activities
-* Drinks and snacks on event days (Sunday-Tuesday)
+* Snacks and drinks on event days (Sunday-Tuesday)
 * Welcome Reception and Social Event with light snacks and drinks
 * Wifi throughout the event
 * Meeting lots of fantastic people in a spacious, inviting venue
diff --git a/docs/conf/portland/2025/unconference.md b/docs/conf/portland/2025/unconference.md
new file mode 100644
index 0000000000..16682a37f1
--- /dev/null
+++ b/docs/conf/portland/2025/unconference.md
@@ -0,0 +1,73 @@
+---
+template: {{year}}/generic.html
+og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
+banner: _static/conf/images/headers/2025/unconference.jpg
+---
+
+# What is an Unconference?
+
+The Unconference consists of attendee-driven sessions that provide the opportunity for anyone who is attending the conference to lead, contribute, share ideas, and discuss problems in an organized setting away from the main stage talks. Many attendees consider this one of their favorite aspects of the conference.
+
+**Who can lead an Unconference session?**
+
+Everyone! All attendees are invited to lead a session on a topic. Sessions can be organized around a presentation, group discussion or anything in between.
+
+**Who can attend an Unconference session?**
+
+![Unconference 1](/_static/conf/images/pics/2025/unconference.jpg)
+
+Everyone!
+
+## Schedule
+
+**Date: {{ unconf.date }}**
+
+- Morning and afternoon sessions
+- Each session is 40 minutes in length
+
+### Scheduling a Session
+- Sign up during Writing Day or the Welcome Reception on Sunday, and anytime during the conference on Monday and Tuesday.
+- Write the title and your name on a note. Select a time slot and table number and place the note on the large schedule. You can only sign up in person.
+- The online version will be updated periodically throughout the conference.
+
+Exact times to be posted on our [Schedule](/conf/{{shortcode}}/{{year}}/schedule) page.
+
+![Unconference 2](/_static/conf/images/pics/2025/unconference.jpg)
+
+## Leading a Session
+
+Sessions take place at tables and focus on small group interaction. There is no stage at an Unconference session.
+
+**How do I structure my Unconference session?**
+
+- **Group discussion:** Pick a topic and facilitate a discussion
+- **The semi-talk:** Use a short presentation to lead into a group discussion on a topic
+- **Show and tell:** Share your latest project, a new tool, or anything else that excites you
+- **Presentation:** Sessions are meant to be small and inclusive, so a presentation can be a difficult format. You will not have access to a large screen, so you cannot rely on slides. You may present a longer talk, but expect more interaction from others joining the session, and break often for questions and discussion.
+
+These ideas were borrowed from Scott Berkun. Read more of his [post on Unconference sessions](https://scottberkun.com/2006/how-to-run-a-great-unconference-session/).
+
+**Tips to keep in mind:**
+
+- **Good sessions emphasize group participation.** However, if you choose a format that includes a lot of your own ideas or material, be prepared to dial it back and use what you have as a starting point, not as the focal point.
+- **Aim to keep your sessions manageably small.** Most sessions are typically 5-12 people. 
+     - If your group is larger than this, split it into two groups if possible, reconfigure, or remove tables. Ask Unconference staff/volunteers for assistance. 
+     - If you’re leading a session on a popular topic (notably API docs in the past), consider scheduling an early time so there’s the possibility to schedule overflow sessions later in the day, or the following day.
+- **Whoever attends are the right people.** You can get great results with 5 or 30 people, and sometimes it’s better to have a smaller, but more engaged group.
+- **People may come and go during the session and that’s okay!**
+- **Keep an open mind.** Even though the session starts out with a topic, you may end up with a different outcome.
+- **Ask Unconference staff/volunteers for support to wrangle logistics.** The room can get crowded especially when a popular topic is scheduled.
+- **When it’s over, it’s over.** There are time slots to help organize the sessions but you can finish early or continue the discussion elsewhere.
+
+## Attending a Session
+
+- View the Session Schedule. This will be posted online and in the Unconference room during the conference only.
+- Find the table and have a seat. You can also join mid-session!
+- Listen or contribute to the discussion.
+- You're welcome to change sessions mid-slot! Please make sure you leave politely.
+
+**Enjoy the Unconference!**
+
+
+
+
diff --git a/docs/conf/portland/2025/unconference.rst b/docs/conf/portland/2025/unconference.rst
deleted file mode 100644
index 04827bc5cd..0000000000
--- a/docs/conf/portland/2025/unconference.rst
+++ /dev/null
@@ -1,79 +0,0 @@
-:template: {{year}}/generic.html
-:og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
-
-Unconference
-============
-
-What is an Unconference?
-------------------------
-
-The Unconference is attendee-driven sessions that provide the opportunity for anyone who is attending the conference to lead, contribute, share ideas and discuss problems in an organized setting away from the main stage talks. 
-
-**Who can lead an Unconference session?**
-
-Anyone! All attendees are invited to lead a session on a topic -- sessions can be organized around a presentation, group discussion or anything in between. 
-
-**Who can attend an Unconference session?** 
-
-Everyone! 
-
-.. figure:: /_static/img/2024/unconference-board.jpg
-
-   Above is an example of what the unconference signup board will look like.
-
-
-Unconference Schedule
----------------------
-
-**Date: Monday, April 15 & Tuesday, April 16**
-
-- Morning and afternoon sessions
-- Each session is 40 minutes in length 
-
-Exact times to be posted on our :doc:`/conf/{{shortcode}}/{{year}}/schedule` page. 
-
-
-Leading a Session
------------------
-
-There is no stage in an unconference. Sessions take place at tables and focus on small group interaction. 
-
-**How do I structure my unconference session?**
-
--  **Group discussion** - Pick a topic and facilitate a group discussion
--  **The semi-talk** - Use a short presentation to lead into a group discussion on a topic
--  **Show and tell** - Show off your latest project, a new tool, or anything else you are excited about
--  **Presentation** - Because sessions are meant to be small and inclusive, this is a difficult format for a session. You cannot rely on slides, because you will not have access to a large screen. Feel free to present a longer talk, but expect more interaction from others joining the session and break often for questions and discussion.
-
-These ideas were borrowed from Scott Berkun. Read more of his `post on unconference sessions <http://scottberkun.com/2006/how-to-run-a-great-unconference-session/>`_.
-
-**Tips to keep in mind:** 
-
-
-*  **Good sessions emphasize group participation.** However, if you choose a format that includes a lot of your own ideas or material, be prepared to dial it back and use what you have as a starting point, not as the focal point.
-*  **Aim to keep your sessions manageably small.** Most sessions are typically 5-12 people. If you're leading a session on a popular topic (notably API docs in the past), consider scheduling an early time so there's the possibility to schedule overflow sessions later in the day, or the following day.
-*  **Whoever attends are the right people.** You can get great results with 5 or 30 people, and sometimes it's better to have a smaller, but more engaged group. 
-*  **People may come and go during the session and that's okay!**
-*  **Keep an open mind.** Even though the session starts out with a topic, you may end up with a different outcome. 
-* **Ask unconf organizers for support to wrangle logistics.** The room can get crowded especially when a popular topic is scheduled.
-*  **When it's over, it's over.** There are time slots to help organize the sessions but you can finish early or continue the discussion elsewhere. 
-
-*Some above tips inspired by the "Open Space Technology" infographic.*
-
-Attending a Session
--------------------
-
-* View the Sessions Schedule. This will be posted online and in the unconf room during the conference only. 
-* Head to that table and have a seat. You can also join mid-session!
-* Feel free to listen or add your voice to the discussion. 
-* Don't be afraid to change sessions mid-slot! Please make sure you bow out politely.
-
-**Can't find a session you want to attend?** Perhaps this means you should add your own session to the schedule!
-
-
-Scheduling a Session
---------------------
-
-- The first opportunity to schedule a session is on Sunday at Writing Day and the welcome reception. Sign up anytime during the conference on Monday and Tuesday.
-- Write the title of your session on a note. Pick a time slot and table number on the large schedule. 
--  The schedule for the Unconference is posted in-person, but we have an online version that we update periodically throughout the conference. 
diff --git a/docs/conf/portland/2025/venue.md b/docs/conf/portland/2025/venue.md
index 51f7fbc66c..9218c8f7e0 100644
--- a/docs/conf/portland/2025/venue.md
+++ b/docs/conf/portland/2025/venue.md
@@ -6,142 +6,6 @@ og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
 
 # Venue
 
-## Revolution Hall
+Our conference will be held at [Revolution Hall](https://www.revolutionhall.com/), a beautiful venue located in the thriving inner east side of Portland. It was originally a high school, and was converted into the versatile space it is today, including an 800+ seat auditorium, coffee shop, bar/restaurant, rooftop bar, rooms to support events, and local businesses. It still has some lockers in the hallway for that extra ambiance.
 
-Our conference will be held at Revolution Hall, a beautiful venue
-located on the thriving inner east side of Portland. It was originally a
-high school, and converted into the versatile space it is today,
-including an 850-seat auditorium, coffee shop, bar/restaurant, rooftop
-bar, rooms to support events, and local businesses. It still has some
-lockers in the hallway for that extra ambiance.
-
-## Conference Layout
-
-### Registration and Welcome Wagon
-
-**Location:**
-
--   1st Floor: April 14
--   2nd Floor: April 15-16
-
-### Writing Day, Unconference, and Welcome Reception
-
-**Location:** 1st Floor: Library/Astoria Room
-
--   Parent Room in 1st floor Show Bar Green Room
-
-### Speaker Talks, Sponsor Expo, Catering, and Quiet Room
-
-**Location:** 2nd Floor Auditorium and surrounding spaces
-
--   Speaker Talks: Auditorium
--   Sponsor Expo: Hallway
--   Catering: Assembly Lounge
--   Quiet Room: Sunset Room
-
-### Other Venue Spaces (open to the public)
-
--   Martha's Coffee Shop
-    - 7:30am-3:00pm
--   Show Bar
-    -   3:00-11:00pm
--   Roof Deck
-    -   3:00pm-late, weather permitting
--   Outdoor seating and city park
-
-### Sunday Conference Map
-
-![Attendee map](/_static/conf/images/2024-map-sunday.png)
-
-### Monday & Tuesday Conference Map
-
-![Attendee map](/_static/conf/images/2024-map-monday.png)
-
-## Accessibility
-
-We are committed to hosting a conference that is accessible to everyone.
-This page contains accessibility information as well as links to other
-resources. If you have questions or require any additional
-accommodations, please email us at portland@writethedocs.org.
-
-### ADA Accessibility
-
-The venue has:
-
--   Wheelchair accessibility to all conference spaces
--   Step-free access to all areas of the conference
--   Elevator accessing the 2nd and 3rd floor, open and unlocked during
-    entire conference
--   Accessible, clearly labeled restrooms
-
-### Restrooms
-
--   1st floor bathrooms are gender-neutral, single, and multi-stall
--   2nd floor bathrooms (auditorium level) are gender-segregated and
-    multi-stall
-
-### Parking and Transportation
-
--   ADA spots (two) in the guest parking lot south of the venue
--   Street parking is east of the venue (15th Ave. and higher), allows
-    for all-day parking
--   Bus transit stops are located nearby the venue. All transit in
-    Portland announce stops verbally in English and most buses have a
-    visual display of upcoming stops. Refer to the [TriMet
-    website](https://trimet.org/access/index.htm) for more information.
-
-### Low Vision or Hard of Hearing
-
--   Live captioning: If you are Deaf, Hard of Hearing, or hearing
-    impaired, and unable to view the captions, a staff member can move
-    you to a closer seat.
--   Preferred seating: Please reach out to us so we can prioritize your
-    seating.
--   Lighting sensitivity: Please contact us and we will do our best to
-    accommodate.
-
-### Seating
-
--   People can sit anywhere they would like in the main stage auditorium
-    on the 2nd floor. Reserved seating will be available for those who
-    need to be close enough to view the live captioning. For distanced
-    seating, there is a 3rd floor balcony.
--   Additional seating and table space will be available for our
-    Unconference and Writing Day events. Catering will be located on the
-    2nd floor.
--   There are various places around Revolution Hall with seating and
-    tables including the Assembly Lounge, Show Bar, Quiet Room (no
-    laptops), Martha's (coffee shop), hallways, and the rooftop and
-    patio outside, if the weather is nice.
-
-### Service Animals
-
-Service Animals are welcome at our conference venue.
-
-### Quiet Room
-
-We have a clearly marked quiet room available, intended to be a calm
-place for anyone who needs a break from the bustle of the conference.
-This room will not be used for socializing.
-
-### Parents Room
-
-We have a dedicated parents room that is available as needed. Please
-check in with the Registration table for information on how to access.
-
-### Dietary Requirements
-
-We aim to provide snacks that meet varying dietary requirements
-including vegan, vegetarian, gluten-free, and dairy-free. Our catering
-menu and ingredients will be listed.
-
-### Did we miss something?
-
-Is there anything not mentioned that would make your attendance possible
-or improve your experience? Please email us portland@writethedocs.org,
-and we'll do what we can to provide it.
-
-### Thanks
-
-Thank you to [Djangocon US](https://2015.djangocon.us/) for inspiration
-on this page.
+More information will be shared in January regarding venue spaces and accessibility.
\ No newline at end of file
diff --git a/docs/conf/portland/2025/volunteer.md b/docs/conf/portland/2025/volunteer.md
index 7a6818edfd..e40b2fb677 100644
--- a/docs/conf/portland/2025/volunteer.md
+++ b/docs/conf/portland/2025/volunteer.md
@@ -1,62 +1,57 @@
 ---
 template: {{year}}/generic.html
 og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
+banner: _static/conf/images/headers/2025/volunteer.jpg
 ---
 
 # Volunteer Information
 
-Our Volunteer Application is open! We are looking for volunteers to provide support with a variety of conference roles - registration, writing day, unconference, stage support, catering, load out, and more.
+Our volunteer application is open! We are looking for volunteers to provide support with a variety of conference roles - registration, Writing Day, Unconference, stage support, catering, load out, and more.
 
-Completing this form gives us an idea of what days and roles you are interested in volunteering. Another form will be sent out once the speaker schedule is released in early March.
+Completing this form signs you up to volunteer. We will close the form once volunteer capacity is reached. Another form will be sent out once the speaker schedule is released mid-February.
 
-Each individual who volunteers for two or more 3-4 hour shifts receives a **free ticket** to the conference.
+Each individual must volunteer two assigned 3-4   for two or more 3-4 hour shifts receives a **free ticket** to the conference.
 
-## Apply today
+## Apply to Volunteer
 
-**Timeline:**
-
--   Now until March 1 (or volunteer capacity is reached): Volunteer application open
--   March 1: Volunteer sign-up form emailed with specific timed shifts
--   March 15: Volunteer schedule emailed
-
-**[Sign up today! View the Volunteer Application form for more information.](https://docs.google.com/forms/d/e/1FAIpQLSfvU7kB_miEAPmHKiIynJ1fh7zsUEpgM2Xsya6Bm20olo3mYw/viewform?usp=sf_link)**
+### [Sign up today! View the Volunteer Application form for more information.](https://docs.google.com/forms/d/e/1FAIpQLSeO5JMVVn1F2NN6keihd0qrLRnytaCMyBAefBjWGW_sz0Iwwg/viewform?usp=sf_link)
 
-![Volunteer photo](/_static/img/2024/volunteer.jpg)
+![Volunteer](/_static/conf/images/pics/2025/volunteer.jpg)
 
-## FAQs
-
-### How many shifts am I required to volunteer?
-
-Each volunteer must work two assigned shifts 3-4 hours in length. Each individual who volunteers for two shifts receives a free ticket to the conference. If you want to volunteer more shifts, please contact katie@writethedocs.org.
+**Timeline:**
 
-### What volunteer roles do you have?
+- Now - February 14: Volunteer applications open
+- February 14 - March 26: Volunteer schedule sign up open
+- End of March: Volunteer schedule emailed
+  
+## Volunteer Roles
 
-#### Writing Day
+### Writing Day
 
 - Assist the Writing Day coordinator, direct attendees to specific tables, and support writing day project leads with logistical questions.
 
-#### Registration
+### Registration
 
-Check in attendees, provide general information inquiries, answer venue questions, and field other requests or direct individuals to the correct staff member who can provide support.
+- Check in attendees, provide general information inquiries, answer venue questions, and field other requests or direct individuals to the correct staff member who can provide support.
 
-#### Stage Support
+### Stage Support
 
 - Assist presenters while on stage - troubleshoot issues with slides, video, or audio portions of their presentation. Please apply for this role if you have some A/V knowledge; it is not required, but experience with different operating systems is a plus!
 
-#### Unconference
+### Unconference
 
-- Assist the Unconference coordinator, help folks sign up to host a session, maintain an updated schedule, direct individuals and groups to their tables, and minimal clean up of tables.
+- Assist the Unconference coordinator, help folks sign up to host a session, maintain an updated schedule, direct individuals and groups to their tables, and keep tables looking neat.
 
-#### Catering
+### Catering
 
 - Set up catering, replenish beverages and snacks, and notify venue staff of coffee refills and cleaning needs.
 
-#### Venue Load Out
+### Venue Load Out
 
 - What's more fun than setting things up? Taking them down! Load out conference set up and leave the conference hall better than we found it.
 
-### Will travel assistance be provided?
+## Will travel assistance be provided?
 
-Unfortunately, we cannot offer travel assistance to volunteers. We encourage you to apply for the Opportunity Grant. Deadline is February 1. [Apply here today!](https://www.writethedocs.org/conf/{{ shortcode }}/{{ year }}/opportunity-grants/) 
+Unfortunately, we cannot offer travel assistance to volunteers. We encourage you to apply for the Opportunity Grant. [View grant application here!](https://www.writethedocs.org/conf/{{ shortcode }}/{{ year }}/opportunity-grants/) 
 
-Contact katie@writethedocs.org with any additional questions.
\ No newline at end of file
+Contact katie@writethedocs.org with any additional questions.
diff --git a/docs/conf/portland/2025/writing-day.md b/docs/conf/portland/2025/writing-day.md
new file mode 100644
index 0000000000..59c77bfd2e
--- /dev/null
+++ b/docs/conf/portland/2025/writing-day.md
@@ -0,0 +1,94 @@
+---
+template: {{year}}/generic.html
+og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
+banner: _static/conf/images/headers/2025/writing-day.jpg
+---
+
+# What is Writing Day?
+
+Writing Day is modeled after the concept of “sprints” or “hackathons”, which are common in open-source software (OSS) conferences.
+
+On the first day of the conference, Sunday, attendees are encouraged to bring and lead a project, or contribute to another attendee's project.
+
+The primary goal is to bring interested individuals into the same room, sharing their passions and aspirations while collaborating to develop creative solutions to solve a problem or issue.
+
+If you have a project, we encourage you to submit it before the conference! This is a great way to build momentum and get other attendees excited to participate in your project. We’ll open project submissions in February/March. As usual, day-of projects are always welcome too - you'll have the option to sign up onsite and announce it during Writing Day.
+
+![Writing Day](/_static/conf/images/pics/2025/writing-day.jpg)
+
+## How to participate in Writing Day:
+
+- **Project Lead:** You bring an idea, content, or OSS project to work on with contributors.
+- **Contributors:** You are looking to contribute to various hosted projects.
+
+**Here are examples of projects that you might see at the conference:**
+
+- Open-source software documentation
+- General documentation writing
+- Best practices manual (for your company, or the world)
+- Resume, cover letter, and portfolio reviews
+- Blog posts
+- Tips and tricks
+- Great works of fiction
+- Love letters
+- The Documentarian Manifesto
+
+Find specific examples on the [Portland Writing Day 2023 project list](https://www.writethedocs.org/conf/portland/2023/writing-day/#project-listing).
+
+## Schedule
+
+**Date: {{ writing_day.date }}**
+
+Writing Day is an all day event designed with flexibility in mind. Feel free to check out as many projects as make sense for you and your schedule!
+
+- **Morning Session:** 
+    - Welcome and overview
+    - Project announcements: Leads give a 2 minute summary
+    - Projects and co-working begins
+- **Lunch Break**
+- **Afternoon Session**
+    - Project announcements: Leads give a 2 minute project summary, starting with the afternoon-only projects
+    - Projects and co-working reconvenes
+- **Writing Day ends at 5pm**
+
+Exact times to be posted on our [Schedule](/conf/{{shortcode}}/{{year}}/schedule) page.
+
+## How to Prepare
+
+Come with the following tools:
+
+- Laptop, tablet, or other device
+- GitHub account (you may also want a GitLab account)
+- Text editor of your choice for coding or content creation
+
+![Writing Day 2](/_static/conf/images/pics/2025/writing-day-2.jpg)
+
+## Lead a Project
+
+Leading a project at Writing Day is a wonderful opportunity to engage with documentarians from a variety of backgrounds, experience, and expertise. Their collective wealth of experience can upgrade your documentation and create a more inclusive project. This empowers all of us to work together to create opportunities for each other and bigger, better communities.
+
+**Tips to create and lead a new project effectively:**
+
+- **Provide a project overview with a specific focus or goals:** Your overview is a 2 minute pitch that describes your project and clearly defines a focus area or goal.
+- **Pre-label tasks and issues:** Create a specific event label and label documentation tasks and issues. This empowers new contributors to find tasks that interest them.
+- **Create a task filter:** This helps contributors find issues more easily and see which issues have been assigned.
+- **Clear onboarding:** Ensure your ReadMe, contribution guidelines, or onboarding instructions are accurate and up to date.
+- **Project experts:** We recommend having 1-2 project experts on your project. We love our developer advocates, community managers, and subject matter experts! You’re welcome to ask for virtual reinforcements from your community as well.
+- **Flexibility and understanding:** Reminder that attendees may need additional info to be successful in onboarding to your project.
+- **Submit your Writing Day before the conference:** Projects submitted by April 17, 2025, are featured in our pre-conference blog post and email. Many attendees have shared that their curiosity for specific projects motivated them to attend. Project submissions open in February/March.
+
+These are suggestions and not requirements. It is perfectly valid to show up to Writing Day, tell us about your project day of, and ask for attendee contribution! It’s been done before and it will be done again.
+
+## Contribute to a Project
+
+
+Writing Day is the perfect opportunity to participate and learn about new projects and technologies. You are welcome to stay with one project all day, or project hop. Do what feels right to you.
+
+**Tips to contribute to a project:**
+
+- **Regardless of your experience level, you are welcome here!** We're excited to have you. Even if you feel you lack the right skills, experiences, or have never attended an event like Writing Day before, you’ll be surprised at how much you can contribute.
+- **Explore our guide to writing documentation!** Our [beginner’s guide](https://www.writethedocs.org/guide/writing/beginners-guide-to-docs/) is designed to help you get started and spark ideas for how you can contribute to a project.
+- **Ask questions!** If you encounter challenges with new concepts and tools, you are in a room surrounded by friendly people from diverse backgrounds and experiences. You can always ask the Welcome Wagon or Registration staff and volunteers. We will help you connect with the right person!
+- **View the project list.** Check out the projects that have been submitted in advance. Keep in mind that some attendees choose to announce their projects during Writing Day itself, so these projects might not appear on the list in advance.
+
+**We're excited to have another wonderful Writing Day!**
\ No newline at end of file
diff --git a/docs/conf/portland/2025/writing-day.rst b/docs/conf/portland/2025/writing-day.rst
deleted file mode 100644
index c7472855a3..0000000000
--- a/docs/conf/portland/2025/writing-day.rst
+++ /dev/null
@@ -1,213 +0,0 @@
-:template: {{year}}/generic.html
-:og:image: _static/conf/images/headers/{{shortcode}}-{{year}}-opengraph.jpg
-
-Writing Day
-===========
-
-What is Writing Day? 
---------------------
-
-Writing Day is modeled after the concept of "sprints" or “hackathons”, which are common in open-source (OSS) conferences. 
-
-Held on Sunday, the first day of the conference, attendees are encouraged to bring a project or contribute to someone else’s project. 
-
-The main goal is to get interesting people in the same room, sharing their passion and goals and collaborating to find creative solutions to solve a problem or issue.
-
-Attendees are invited to submit their project pre-conference! It's a great way to get other attendees excited about contributing. We'll open project submissions in February/March.
-
-**There are two main types of Writing Day attendees:**
-
-- Project leads: Attendees bringing ideas, content, or OSS projects to work on with contributors.
-- Contributors: Attendees looking to contribute to various content projects.
-
-**Here are examples of projects that you might see at the conference:**
-
--  Open-source software documentation
--  General documentation writing
--  Best practices manual (for your company, or the world)
--  Resume, cover letter, and portfolio reviews
--  Blog posts
--  Tips and tricks
--  Great works of fiction
--  Love letters
--  The Documentarian Manifesto
-
-If you find specific examples helpful, check out the `Portland Writing Day 2023 project list <https://www.writethedocs.org/conf/portland/2023/writing-day/#project-listing>`_.
-
-Writing Day Schedule 
---------------------
-
-**Date: Sunday, April 14, 9am-5:00pm PST** 
-
-Writing Day is an all day event that is designed with flexibility in mind. Feel free to check out as many projects as make sense for you and your schedule!
-
--  Morning Introduction: The coordinator welcomes everyone and gives a Writing Day overview.
--  Project announcements: Project leads are invited to give a 2 minute project summary.
--  Session 1: Projects and co-working begins.
--  Lunch Break
--  Project announcements: Project leads are invited to give a 2 minute project summary, starting with the afternoon-only projects.
--  Session 2: Projects and co-working reconvene.
--  Writing Day ends at 5:00pm.
-
-Exact times to be posted on our :doc:`/conf/{{shortcode}}/{{year}}/schedule` page. 
-
-Logistics
----------
-
-**Come prepared with the following tools:**
-
--  Laptop, tablet, or other device 
--  `GitHub account <https://github.com/>`_ (you may also want a `GitLab account <https://about.gitlab.com/>`_)
--  Text editor of your choice for coding or content creation
-
-
-Lead a Project
---------------
-
-Leading a project at Writing Day is a wonderful opportunity to engage with documentarians from a variety of backgrounds, experience, and expertise. Their collective wealth of experience can help upgrade your documentation and create a more inclusive project. This empowers all of us to work together to create opportunities for each other and bigger, better communities.
-
-
-**Tips to create and lead a new project effectively:** 
-
--  **Provide a project overview with a specific focus or goals:** Your project overview is a 2 minute pitch that describes your project and clearly defines a focus area or goal. Here’s a good example from Writing Day 2022, the `Open Web Docs project <https://www.writethedocs.org/conf/portland/2022/writing-day/#open-web-docs>`_.
--  **Pre-label tasks and issues:** Create a specific event label and label documentation tasks and issues. This empowers new contributors to find tasks that interest them.
--  **Create a task filter:** This  helps contributors find issues more easily and see which issues have been assigned.
--  **Clear onboarding:** Ensure your ReadMe, contribution guidelines, or onboarding instructions are accurate and up to date.
--  **Submit your Writing Day Project:** Adding your project to the Writing Day project list promotes your project to our attendees before the event. Many attendees have told us that their curiosity about certain projects incentivised their attendance.
--  **Project Experts:** We recommend having 1-2 project experts on your project. We love our developer advocates, community managers, and subject matter experts! You’re welcome to call for virtual reinforcements from your community as well.
--  **Flexibility and Understanding:** Reminder that attendees may need additional info to be successful in onboarding to your project.
-
-These are suggestions and not requirements. It is perfectly valid to show up to Writing Day, tell us about your project day of, and ask for volunteers! It’s been done before and it will be done again.
-
-Contribute to a Project
------------------------
-
-Writing Day is the perfect opportunity to learn about new projects and technologies. Some attendees stay at one table all day, others table hop. Do what feels right to you.
-
-Check out the project list! Keep in mind that some attendees choose to announce their projects during Writing Day and the information is not available on the project list.
-
-**Tips to contribute to a project:**
-
--  **No matter your experience level, you are welcome!** We are glad you’re here. Even if you `feel <http://en.wikipedia.org/wiki/Impostor_syndrome>`__ as though you don't have the right skills or experience or have never attended an event like Writing Day before, you’ll be surprised how much you can share.
--  **Check out our guide to writing documentation.** Our `beginners guide <https://www.writethedocs.org/guide/writing/beginners-guide-to-docs/>`_ will help you get started, and give you some ideas for how you can contribute to a project.
--  **Ask people for help if you have a question.** If at any time you get stuck with new concepts and tools, you are in a room full of friendly people from diverse backgrounds and experiences.  If you are not sure who to ask, ask the Welcome Wagon or Registration staff or volunteers. We will help you find someone!
-
-Call for Project Submissions
-----------------------------
-
-Based on the positive response to Writing Day during Portland 2023, we strongly recommend that you `submit your Writing Day project in advance <https://forms.gle/5WPN8MGCKzKqZBWU6>`__! **Projects submitted by March 28, 2024 are promoted in our pre-conference Writing Day blog post and email.**
-
-Learn more in our `Call for Project Announcement <https://www.writethedocs.org/conf/portland/{{year}}/news/call-for-projects-writing-day>`_.
-
-As usual, walk-on projects are always welcome. All attendees always have the option to bring a project, sign up on site, and announce it during Writing Day.
-
-If you need additional information to advocate for Writing Day in your community or organization, see the `Convince Your Community <https://www.writethedocs.org/conf/portland/{{year}}/convince-day-manager/#convince-your-community>`_ resource.
-
-Project List
-------------
-
-Docs as Tests & Doc Detective: Help us test your docs!
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Project organizer Manny Silva, he/him.
-
-`Doc Detective <https://doc-detective.com/>`__ is back at Writing Day again, this time with our friends, `Docs as Tests <https://www.docsastests.com>`__. Does your project or product have a UI? APIs? SDKs? We can help you test them and keep your docs accurate.
-
-Docs as Tests is a tool-agnostic strategy for validating doc content by performing documented tasks directly in your products using automation. By validating that doc contents work as written, you can: 
-
-* Prevent broken docs.
-* Ensure consistent UX between docs and products.
-* Build user trust.
-
-Our Writing Day goal is to test at least 10 docs sets! We want every writer to be confident in their docs. 
-
-Come by our table, and we'll help you set up Docs as Tests with whatever tools (such as Doc Detective) or strategies (like unit testing code snippets) are appropriate. Establish a zero-trust relationship between your docs and product, catching bugs in both as you go.
-
-Mutual Aid for Tech Writer/Documentarian Job Hunters
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Coordinated by Kenzie Woodbridge, they/them. 
-
-Let's help each other get ready for our job searches! Are you thinking of applying for a new or different tech writer/documentarian jobs and would appreciate feedback on your resume? Or, are you responsible for hiring and know what you're looking for in a resume and application? 
-
-Let's get together and offer each other some feedback on the important documentation we're using to move our careers forward.
-
-Meet the new GitBook (Sponsor)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Project organizer Addison Schultz, he/him.
-
-Our mission at `GitBook <https://gitbook.com/>`__ is to help you harness your team's knowledge!
-
-Our Writing Day goal is to teach you how to use your team's internal knowledge to the fullest. Documenting internal knowledge is often the last task in a sprint and most likely to be skipped or forgotten. This leads to knowledge gaps that can slow the progress towards your team's ultimate goals and reduce efficiency. GitBook is here to help you combat the knowledge gap and make docs effortlessly epic!
-
-That's not all, GitBook is bringing three Writing Day challenges. No matter your experience level, these challenges are designed to guide you through the tasks necessary to publish your first, but hopefully not last, GitBook knowledge site! The content on your knowledge site is up to you, it can be documentation, a company knowledge base, or something to help you plan the rest of your sprint. GitBook staff will be around to answer any questions you have.
-
-Writing Day challenges:
-
-- Publish your first site with GitBook
-- Install the Slack Integration and capture your first snippet
-- Import your docs from an existing repo or an open source project
-
-It gets better! For every challenge completed, you'll receive one (1) entry for our raffle to win an epic swag box! That means if you complete all 3 challenges, you'll get three (3) entries. More information about the raffle entry is available during each session.
-
-Already familiar with GitBook? We're looking for people like you to brainstorm features as. Help us make the ultimate documentation platform!
-
-Use OpenAPI with the Museum API
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Project organizer Heather Cloward, she/her. The `Museum API <https://github.com/Redocly/museum-openapi-example/tree/main>`__ was built by Redocly for educational purposes.
-
-The Museum API is a sample OpenAPI description. It offers a set of endpoints to interact with a museum's services -- such as retrieving museum hours, managing special events, and purchasing tickets.
-
-Our Writing Day goal is to onboard contributors and improve the Museum API definition. Help us create more complex use case examples like discriminator, webhooks, oneOf, allOf, etc. 
-
-The Museum API was built specifically to teach OpenAPI concepts and to create a better developer experience. The more realistic and complex the Museum API is, the better it can demonstrate all that OpenAPI has to offer.
-
-Write the Docs Documentation Salary Survey
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Project Organizer Kay Smoljak, she/her. Afternoon only session.
-
-The WTD Salary Survey has been running annually since 2019, with the goal of identifying appropriate salary ranges and providing a basis for pay negotiations. It has sparked discussions on other topics such as remote work, pay transparency, and job satisfaction.
-
-The 2023 results - which will be announced before Writing Day - are drawn from the largest respondent pool yet, and for the first time include structured as well as freeform feedback on the survey itself.
-
-Our Writing Day project centers on updating the survey site content and question text on GitHub. We'll go over the: 
-
-* Constraints of the project.
-* Feedback we have received.
-* Areas we think are most in need of attention.
-
-Our Writing Day goal is to improve the clarity, inclusivity, neutrality, and relevance of the questions, the instructions, and the general flow of the survey. The format, questions, and instructions have evolved each year, based on the submitted responses and feedback from the community, but it's largely been a one-person effort.
-
-We're particularly interested in: 
-
-* Better catering to contractors, freelancers and self-employed people.
-* Addressing potential privacy concerns.
-* Exploring ways to expand the respondent base.
-
-This is where we need you the most! Everyone who works in documentation is a subject matter expert on this topic, and we want your ideas on how to make the survey better benefit the community as a whole.
-
-Tabletop game rules writing workshop
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Project Organizer Ryan Macklin, he/they. Afternoon only session.
-
-Tabletop game rules are a neat and weird form of technical documentation! 
-
-If you're working on writing tabletop game rules or are interested in learning about that, join me during the Writing Day afternoon session. You can bring your own work-in-progress rules documents, and I'll have some work-in-progress rules as well. 
-
-The purpose for this Writing Day workship is to help:
-
-* Technical writers turning their craft toward game rules writing
-* Tabletop game writers understand that their skills are applicable to technical writing as a career
-
-**Note**: This is not a game design or playtesting session, purely a session about helping one another with the difficult task of rules writing.
-
-*More projects coming, get excited!*
-
-Contact Us
-----------
-
-Email us at portland@writethedocs.org with any questions.