Ask sponnsor #8
Merged
Ask sponnsor #8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Created a comprehensive guide to help PyTexas community members advocate for their companies to sponsor the conference. The new page provides persona-specific outreach strategies, email templates, and objection handling for individuals who want their employer to sponsor but don't control purchasing decisions. Changes: - Add docs/sponsors/asking-for-sponsorship.md with 5 decision-maker personas (DevRel, Recruiting, Marketing, Engineering Leadership, Sales) - Include expandable email templates using MkDocs Material admonitions - Add objection handling guide and internal champion tips - Provide copy-paste one-pager template for internal use - Update mkdocs.yml navigation to include new "Ask Your Company" page under Sponsors section - Add descriptive titles to existing sponsor navigation items The guide emphasizes PyTexas's 20th anniversary, day-one sponsorship sale for urgency, and provides ready-to-use templates to reduce friction for internal advocates.
Streamlined the community member sponsorship guide by removing redundant content and clarifying language to improve readability and effectiveness. Changes: - Remove "Quick Context for Your Pitch" section (talking points already present in email templates) - Remove "Tips for Internal Champions" section (content overlapped with role-specific sections and objection handling) - Simplify closing line in all email templates: changed "I'm also happy to answer any questions you may have about my experience with them" to "I'm happy to discuss this opportunity further if helpful" (removes assumption of personal attendance) - Clarify CFP reference in Engineering Leadership template: changed "The [CFP] is currently open" to "The speaker submission period is currently open" (removes jargon) - Fix typos: remove double "for" in all "How to Find Them" sections - Fix punctuation: add missing dash in "first day - popular tiers will sell out" Result: Document reduced from 325 to 281 lines (~14% shorter) while maintaining all core functionality. Email templates remain intact with full bullet points. The guide is now more focused and likely to be read completely by community members.
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
thejcannon
reviewed
Nov 2, 2025
thejcannon
reviewed
Nov 2, 2025
dijital20
approved these changes
Nov 2, 2025
dijital20
left a comment
dijital20
left a comment
There was a problem hiding this comment.
Looks alright to me. I don't have any notes above what @thejcannon has already posted.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.