Split the pages

Author: AA-Turner

src/content/sprints/cpython-documentation.md

@@ -0,0 +1,32 @@
+---
+title: "Python Documentation"
+numberOfPeople: "TBA"
+pythonLevel: "Any"
+contactPerson:
+  name: "Adam Turner"
+  github: AA-Turner
+links:
+  - title: "Start Documenting"
+    url: "https://devguide.python.org/documentation/start-documenting/"
+  - title: "Helping with Documentation"
+    url: "https://devguide.python.org/documentation/help-documenting/"
+  - title: "Easy Issues"
+    url: "https://github.com/python/cpython/issues?q=is%3Aissue%20is%3Aopen%20label%3Adocs%20label%3Aeasy"
+  - title: "Code of Conduct"
+    url: "https://policies.python.org/python.org/code-of-conduct/"
+---
+
+Help us improve the Python documentation!
+
+We'll be working on all parts of the documentation, so all any any changes are
+welcome -- from fixing a spelling error to documenting a new feature.
+
+1. Read
+   ['what to expect'](https://pycon.blogspot.com/2025/04/pyconus-sprints.html)
+   for a briefing on what happens at sprints in general. This was written for
+   the PyCon US sprints, but a lot applies here!.
+1. Fork and clone the [repository](https://github.com/python/cpython/fork)
+   **before** arriving at the sprints, to get started faster.
+1. Use the
+   [Python Developer's Guide](https://devguide.python.org/getting-started/setup-building/)
+   to set up an environment for contributing to the documentation.

src/content/sprints/cpython.md

@@ -1,32 +1,22 @@
 ---
-title: "CPython Core & Python Documentation"
+title: "CPython Core
 numberOfPeople: "TBA"
-pythonLevel: "Any"
+pythonLevel: "Intermediate
 contactPerson:
   name: "Petr Viktorin"
   email:
 links:
   - title: "CPython's Developer Guide"
     url: "https://devguide.python.org/"
-  - title: "Setup & Building [CPython core]"
+  - title: "Setup & Building"
     url: "https://devguide.python.org/getting-started/setup-building/"
-  - title: "Start Documenting [Python documentation]"
-    url: "https://devguide.python.org/documentation/start-documenting/"
-  - title: "Helping with Documentation [Python documentation]"
-    url: "https://devguide.python.org/documentation/help-documenting/"
   - title: "Code of Conduct"
     url: "https://policies.python.org/python.org/code-of-conduct/"
   - title: "Easy Issues"
     url: "https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+label%3Aeasy"
 ---
 
-Come sprint on CPython and work on Python 3.14 and 3.15, or Python's
-documentation!
-
-##### CPython Core
-
-Contacts: **Petr Viktorin, Adam Turner** \
-Experience Level: **Intermediate or Advanced**
+Come sprint on CPython and work on Python 3.14 and 3.15!
 
 Sprints will focus on release candidate fixes to Python 3.14 (to be released
 this October), with some limited new feature work for 3.15 (final version in
@@ -40,23 +30,3 @@ October 2026).
    wifi :)
 4. Use the [Python Developer's Guide](https://devguide.python.org/) to go
    through the initial build on you machine.
-
-##### Python Documentation
-
-Contacts: **Adam Turner** \
-Experience Level: **Any**
-
-Help us with Python's documentation!
-
-We'll be working on all parts of the documentation, so all any any changes are
-welcome -- from fixing a spelling error to improving an entire page.
-
-1. Read
-   ['what to expect'](https://pycon.blogspot.com/2025/04/pyconus-sprints.html)
-   for a briefing on what happens at sprints in general. This was written for
-   the PyCon US sprints, but a lot applies here!.
-1. Fork and clone the [repository](https://github.com/python/cpython/fork)
-   **before** arriving at the sprints, to get started faster.
-1. Use the
-   [Python Developer's Guide](https://devguide.python.org/getting-started/setup-building/)
-   to set up an environment for contributing to the documentation.