Add PSF/PyLadiesCon workflow (#214)

* Add PSF/PyLadiesCon workflow

* port to nested structure

---------

Co-authored-by: Ege Akman <me@egeakman.dev>

Author: cmaureir

src/content/docs/sponsorship/psf_pyladiescon_workflow.md

@@ -0,0 +1,32 @@
+---
+title: "PSF/PyLadies Sponsorship Invoicing Workflow"
+meta_title: "PSF/PyLadiesCon Sponsorship Workflow"
+description: "The process when a company wants to sponsor the conference"
+section: "sponsorship"
+draft: false
+---
+
+1. PyLadies works with Company/Organization to determine sponsorship
+   level/benefits
+2. PyLadies enters sponsor information into the **Sponsor Tracking Sheet** and
+   adds a comment with a tag to accounting@python.org with the following
+   information:
+    * Company name
+    * Company address
+    * Contact name
+    * Email
+    * Sponsorship level
+    * Sponsorship benefits
+    * Amount
+    * Event or Sponsorship Term Start and end dates
+    * P.O. number if required by company
+
+3. PSF Accounting generates Sponsorship Agreement and sends to company contact,
+   PyLadies Sponsorship person, and PSF signor with Adobe EchoSign
+4. Sponsorship Agreement is fully executed when all parties sign
+5. PSF Accounting generates and sends invoice in accordance with Sponsorship
+   Agreement
+6. Sponsor submits payment to PSF
+7. PSF Accounting records payment in Sponsor Tracking Sheet and credits
+   PyLadies account.  PSF Accounting tags PyLadies sponsor email to let them
+   know benefits delivery can start.

src/lib/utils/docsHelpers.ts

@@ -12,9 +12,10 @@ const SECTION_LABELS: Record<string, string> = {
   volunteers: "Volunteer Guides",
   speakers: "Speaker Guides",
   resources: "Resources",
+  sponsorship: "Sponsorship Guides"
 };
 
-const SECTION_ORDER = ["speakers", "volunteers", "resources"] as const;
+const SECTION_ORDER = ["speakers", "volunteers", "sponsorship", "resources"] as const;
 
 const resolveSectionKey = (doc: CollectionEntry<"docs">): string => {
   // use explicit section if available