Skip to content

Commit a2be68c

Browse files
authored
feat: add sponsor us page (#842)
1 parent fe2b885 commit a2be68c

4 files changed

Lines changed: 241 additions & 0 deletions

File tree

_data/navigation.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,8 @@ main:
5151
url: "https://www.pyopensci.org/handbook/"
5252
- title: "Support Us"
5353
sub-nav:
54+
- title: "Ways to Give"
55+
url: "/ways-to-give.html"
5456
- title: "Volunteer"
5557
url: "/volunteer.html"
5658
- title: "Donate"

_pages/ways-to-give.md

Lines changed: 152 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,152 @@
1+
---
2+
layout: splash
3+
classes: flowing
4+
title: "Invest in the Future of Scientific Open Source"
5+
author_profile: false
6+
published: true
7+
site-map: true
8+
permalink: /ways-to-give.html
9+
header:
10+
overlay_color: "#33205c"
11+
overlay_filter: 0.3
12+
---
13+
14+
<div class="content padding" markdown="1">
15+
16+
By supporting pyOpenSci, you are directly investing in the sustainability of the
17+
open-source Python ecosystem that modern businesses, universities, and
18+
researchers rely on. A healthy, diverse open-source community is critical to
19+
ensuring the long-term health and accessibility of the fundamental tools that
20+
enable productivity and innovation at scale.
21+
22+
Whether you are a company looking to align your brand with industry leaders, or
23+
an individual funder passionate about open science, we offer clear pathways for
24+
you to support our mission.
25+
26+
<figure class="full">
27+
<picture>
28+
<source srcset="/images/people/scipy-sprint-2026.webp" type="image/webp">
29+
<img src="/images/people/scipy-sprint-2026.png" alt="A group of contributors sitting at a table at a pyOpenSci sprint working on their laptops and talking to each other.">
30+
</picture>
31+
</figure>
32+
33+
## For companies: corporate sponsorship
34+
35+
By sponsoring pyOpenSci, your company directly expands high-impact, expert-led
36+
training programs that build a stronger pipeline of diverse talent in the
37+
scientific open-source space. Your support enables us to deliver rigorously
38+
reviewed educational resources, ultimately fostering a more resilient and
39+
informed ecosystem that scales scientific discovery.
40+
41+
### Benefits of contributing
42+
43+
<ul class="benefits-list">
44+
<li>
45+
<i class="fa-solid fa-seedling" aria-hidden="true"></i>
46+
<strong>Long-term impact.</strong>
47+
Open source development and the critical infrastructure it supports are
48+
rapidly evolving due to the impacts of generative AI. pyOpenSci is uniquely
49+
positioned to address these challenges, and our sponsors will be at the
50+
forefront of this evolution, directly supporting a mission that shapes the
51+
future of open source tools.
52+
</li>
53+
<li>
54+
<i class="fa-solid fa-bullhorn" aria-hidden="true"></i>
55+
<strong>Brand awareness.</strong>
56+
Your brand will benefit from multi-channel promotion integrated directly into
57+
our evolving content strategy, which spans our primary website,
58+
organizational and personal social platforms, dedicated mailing lists, and
59+
an upcoming asynchronous course platform tailored for universities.
60+
</li>
61+
<li>
62+
<i class="fa-solid fa-people-arrows" aria-hidden="true"></i>
63+
<strong>Target audience.</strong>
64+
Expose your brand to practitioners who don't just use tools—they have high
65+
visibility to those who develop them, teach them, and shape how research
66+
communities adopt new workflows.
67+
</li>
68+
</ul>
69+
70+
Sponsorship funds directly support our mission to make scientific Python more
71+
accessible. From special programs to scholarships, your sustained support
72+
ensures our scientific infrastructure remains a crucial, valuable resource.
73+
74+
### Example sponsorship tiers
75+
76+
Tiers vary by organization; the table below illustrates how support can align
77+
with different goals. Contact us to design a package that fits your team.
78+
79+
| Tier | Example focus | Example visibility &amp; benefits |
80+
| --- | --- | --- |
81+
| **Ecosystem catalyst** | Companies ready to lead in supporting open source research software | Premier placement across channels; tailored activations such as mentored sprints and dedicated office hours; strategic collaboration with pyOpenSci leadership |
82+
| **Momentum driver** | Teams growing their scientific Python footprint | Sustained visibility on the website and in mailings; alignment with webinars and community programs; connection to our cross-disciplinary network |
83+
| **Foundation builder** | Organizations beginning to invest in open science education | Recognition alongside training and course materials; support for scholarships and learner access; pathway to deeper partnership |
84+
85+
<a href="mailto:media@pyopensci.org?subject=pyOpenSci%20corporate%20sponsorship%20inquiry"
86+
class="btn btn--info btn--large">Inquire to learn more</a>
87+
88+
</div>
89+
90+
{% comment %}
91+
<div class="pyos-section purple" markdown="1">
92+
<div class="content padding-wide" markdown="1">
93+
94+
### A learner perspective
95+
96+
<div class="highlight-quote-split" markdown="0">
97+
<figure class="highlight-quote-split__photo">
98+
<img src="/images/people/leah-wasser/headshot.jpg" width="180" height="180" loading="lazy" alt="Portrait placeholder for the learner testimonial; replace with the contributor photo when available.">
99+
</figure>
100+
{% include pyos-blockquote.html quote="Absolutely honored to have had the opportunity to contribute to the amazing pyOpenSci open-source project at my first-ever #PyConUS24 back in May! 🙌 As a total newbie, I was blown away by how warm and welcoming the pyOpenSci team was—they made diving into my first open-source contribution so much less intimidating (even if it was just documentation)! 😅 It's been an incredible experience to see firsthand how collaboration can drive innovation in the Python community, and I'm excited to keep learning and contributing." author="Brianne Wilhelmi" event="Software Engineer" class="highlight purple wide highlight-quote--split" %}
101+
</div>
102+
</div>
103+
</div>
104+
{% endcomment %}
105+
106+
<div class="pyos-section" markdown="1">
107+
<div class="content padding" markdown="1">
108+
109+
## For funders &amp; community: direct donations
110+
111+
The scientific research community is experiencing unparalleled challenges. From
112+
shifting federal and grant funding to the rise of generative AI, the need to
113+
support science and the tools that drive innovation at scale has never been
114+
greater.
115+
116+
Every donation—whether a one-time gift or a recurring contribution—directly
117+
empowers the individuals and structures propelling open science forward.
118+
119+
### What your investment enables
120+
121+
<ul class="benefits-list">
122+
<li>
123+
<i class="fa-solid fa-gears" aria-hidden="true"></i>
124+
<strong>Sustaining core operations.</strong>
125+
Your funding directly supports our infrastructure, community support, and
126+
the leadership required to run our programs.
127+
</li>
128+
<li>
129+
<i class="fa-solid fa-hand-holding-heart" aria-hidden="true"></i>
130+
<strong>Rewarding volunteer contributions.</strong>
131+
We provide volunteer stipends that keep our vital open-source software peer
132+
review running.
133+
</li>
134+
<li>
135+
<i class="fa-solid fa-book-open" aria-hidden="true"></i>
136+
<strong>Developing trusted training materials.</strong>
137+
We build rigorously reviewed tutorials and training materials that support
138+
better software development.
139+
</li>
140+
<li>
141+
<i class="fa-solid fa-universal-access" aria-hidden="true"></i>
142+
<strong>Expanding access.</strong>
143+
Your donations fund scholarships to our asynchronous courses, expanding
144+
access to world-class education while sustaining pyOpenSci's mission.
145+
</li>
146+
</ul>
147+
148+
<a href="https://give.communityin.org/pyopensci_2024"
149+
class="btn btn--info btn--large">Donate today</a>
150+
151+
</div>
152+
</div>

_sass/minimal-mistakes/_pyos-flowing-page.scss

Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,11 @@
1818
position: relative;
1919
margin-top: 4rem;
2020
}
21+
22+
// Extra bottom padding when the learner / split quote sits in this band
23+
&.purple:has(.highlight-quote-split) {
24+
padding-bottom: 1.5rem;
25+
}
2126
}
2227

2328
// Wave dividers (div_purple_top.html / div_purple_bottom.html):
@@ -253,3 +258,85 @@
253258
}
254259

255260
}
261+
262+
// Opt-in layout: wide blockquote + photo (add .highlight-quote--split on blockquote)
263+
.highlight-quote-split {
264+
display: flex;
265+
flex-direction: column;
266+
align-items: center;
267+
gap: 1.5rem;
268+
// Clearance below "A learner perspective" so the opening quote mark does
269+
// not overlap the heading
270+
margin-top: 2.25rem;
271+
margin-bottom: 0.5rem;
272+
273+
@include breakpoint($medium) {
274+
flex-direction: row;
275+
align-items: flex-start;
276+
gap: 2rem;
277+
}
278+
}
279+
280+
.highlight-quote-split__photo {
281+
margin: 0;
282+
flex-shrink: 0;
283+
text-align: center;
284+
285+
img {
286+
display: block;
287+
width: 180px;
288+
height: 180px;
289+
object-fit: cover;
290+
border-radius: 50%;
291+
}
292+
}
293+
294+
// Class name uses BEM-style --; attribute selector avoids Sass minus ambiguity
295+
blockquote.highlight-quote.wide[class~="highlight-quote--split"] {
296+
flex: 1;
297+
min-width: 0;
298+
margin-top: 0;
299+
margin-bottom: 0;
300+
// Anchor decorative quotes so they stay inside the purple band
301+
position: relative;
302+
padding-top: 1.5rem;
303+
padding-bottom: 4rem;
304+
padding-right: 1.5rem;
305+
padding-left: 0.25rem;
306+
307+
// +10% leading vs .wide blockquote paragraph (base 2.2rem)
308+
p.quote {
309+
line-height: calc(2.2rem * 1.05);
310+
}
311+
312+
// Less upward shift than default -20px so the open quote clears the h3
313+
p.quote:before {
314+
top: -0.35rem;
315+
}
316+
317+
&:after {
318+
right: 1rem;
319+
bottom: 0.75rem;
320+
top: auto;
321+
margin-top: 0;
322+
}
323+
324+
> div.end {
325+
position: relative;
326+
display: block;
327+
min-height: 2.5rem;
328+
}
329+
330+
> div.end:after {
331+
right: 0.75rem !important;
332+
bottom: 0 !important;
333+
top: auto !important;
334+
margin-top: 0 !important;
335+
}
336+
337+
// With footer, close-quote also renders on .end — hide duplicate (must follow &:after)
338+
&:has(footer):after {
339+
content: none !important;
340+
display: none !important;
341+
}
342+
}
16.5 KB
Loading

0 commit comments

Comments
 (0)