Skip to content

Commit c748ad1

Browse files
LauraLangdonLauraLangdon
committed
add welcome packet pages, hidden from nav
1 parent b9a34c4 commit c748ad1

10 files changed

Lines changed: 177 additions & 4 deletions

File tree

‎about/get-involved/first-meetup.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: First meetup
3+
---
4+
5+
> This section is still being drafted. It will cover: format options (in-person, virtual, hybrid), who you're trying to reach, what makes a good kick-off (lessons from the existing six campuses), a planning checklist, and how to plug into the network's all-campus virtual meetups vs. running your own.
6+
7+
:::{div}
8+
:class: page-nav
9+
10+
[← Mailing list](./mailing-list.md)
11+
12+
[Connecting with local stakeholders →](./local-stakeholders.md)
13+
:::

about/get-involved.md renamed to about/get-involved/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,12 +15,12 @@ No matter how you're joining the community—as an individual or as a new instit
1515
### Attend events
1616

1717
- **All-Campus Virtual Meetups**: First Thursday of every month at 10am. Each campus takes turns hosting.
18-
- **Coworking & Office Hours**: Tuesdays at 10am, Thursdays at 1pm ([see the events calendar](../events/index.md)).
19-
- **Campus Meetups**: Some campuses hold their own local events. Check the [events calendar](../events/index.md) or ask in Slack.
18+
- **Coworking & Office Hours**: Tuesdays at 10am, Thursdays at 1pm ([see the events calendar](../../events/index.md)).
19+
- **Campus Meetups**: Some campuses hold their own local events. Check the [events calendar](../../events/index.md) or ask in Slack.
2020

2121
There's no minimum attendance requirement. Come to what interests you, when you can.
2222

23-
See our [Contact page](contact.md) for campus-specific contacts and mailing lists.
23+
See our [Contact page](../contact.md) for campus-specific contacts and mailing lists.
2424

2525
---
2626

‎about/get-involved/local-stakeholders.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: Connecting with local stakeholders
3+
---
4+
5+
> This section is still being drafted. It will cover: research computing, library, faculty senate / academic governance, Innovation Ventures / TTO. Patterns from the existing six campuses—what worked and what didn't.
6+
7+
:::{div}
8+
:class: page-nav
9+
10+
[← First meetup](./first-meetup.md)
11+
12+
[Connecting with the network →](./network-connection.md)
13+
:::

‎about/get-involved/mailing-list.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: Mailing list
3+
---
4+
5+
> This section is still being drafted. It will cover: platform options at UC (Sympa via campus IT, alternatives), and how to bootstrap your first subscribers.
6+
7+
:::{div}
8+
:class: page-nav
9+
10+
[← Web presence](./web-presence.md)
11+
12+
[First meetup →](./first-meetup.md)
13+
:::

‎about/get-involved/network-connection.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: Connecting with the network
3+
---
4+
5+
> This section is still being drafted. It will cover: Slack,, recurring meetings + working groups (OLG, Education, Discovery, Sustainability, Sharable), all-campus virtual meetups (first Thursdays, starting 2026-07-02), and how to plug into existing initiatives.
6+
7+
:::{div}
8+
:class: page-nav
9+
10+
[← Connecting with local stakeholders](./local-stakeholders.md)
11+
12+
[Where to go from here →](./next-steps.md)
13+
:::

‎about/get-involved/next-steps.md‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
title: Where to go from here
3+
---
4+
5+
> This section is still being drafted. It will cover: first-30-days suggestions, first-90-days suggestions, and when to ask the community manager or other network folks for help.
6+
7+
:::{div}
8+
:class: page-nav-prev-only
9+
10+
[← Connecting with the network](./network-connection.md)
11+
:::

‎about/get-involved/web-presence.md‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
title: Web presence
3+
---
4+
5+
You need a place on the public web where people can find your OSPO. There are two patterns we've seen in the network:
6+
7+
**Path A: page(s) on ucospo.net.** The network site has space for every campus, and adding your page is a single PR. Examples in the network: [UCSB](../../santa-barbara/).
8+
9+
**Path B: page(s) on a campus URL.** Examples in the network: [UCSD](https://datanexus.ucsd.edu/ospo/), [UCSC](https://ucsc-ospo.github.io).
10+
11+
## What every page needs (regardless of path)
12+
13+
- **A short intro:** One to three sentences on what a campus OSPO is and how yours serves the campus community. Don't overthink this; it'll evolve as you go along. ("We support open-source contributors and maintainers at [Campus] across [departments/disciplines/units]." is enough to start.)
14+
- **How to reach you:**
15+
- Identify at least one person (probably you!) who people on your campus can reach out to with questions about your OSPO and the Network
16+
- Make it easy for people from your campus to get in touch—however that usually happens (email, your campus's Slack, office hours). You can also link to the [public UC OSPO Network Slack](https://join.slack.com/t/uc-ospo-network/shared_invite/zt-3ecp5b20z-ECL~4DkCUslB0t3mbH9xUg).
17+
<!-- TODO: governance pending—PI/department sponsor may become a required element. Revisit once the governance proposal is finalized. -->
18+
<!-- TODO: discuss in leadership group. No campus is currently listing specific projects on their page; reinstating this bullet effectively makes it network practice. -->
19+
<!-- - **Projects.** Projects you're supporting, stewarding, or affiliated with. If you don't have any yet, list aspirations ("we hope to support…") rather than leaving the section blank—it signals direction. -->
20+
- **News/events:** Upcoming meetups, workshops, talks. Even one upcoming event is enough; the section signals "we're alive." Link also to the [network events page](../../events/index.md).
21+
<!-- TODO: events/calendar handling needs its own page or major subsection. Team Up vs. campus Google Calendar push/pull direction TBD—verify how Santa Barbara is currently set up. Link to events calendar once it exists. -->
22+
- **Get involved:** Spell out concrete next steps for visitors—joining the [public UC OSPO Network Slack](https://join.slack.com/t/uc-ospo-network/shared_invite/zt-3ecp5b20z-ECL~4DkCUslB0t3mbH9xUg), subscribing to your campus mailing list, attending the next meetup. Even one of these is enough to start.
23+
24+
## Templates and resources
25+
26+
- **For Path A (page on ucospo.net):** the repo is at <https://github.com/UC-OSPO-Network/ucospo.net>. Look at existing campus directories for inspiration—clone one as a starting template, edit, open a PR. If you'd like help getting the first PR open, open an issue on the repo, or DM Laura (community manager) directly!
27+
- **For Path B (standalone site):** start the conversation with whoever handles web infrastructure for your unit (campus IT, your library, etc.). The network can share what's worked elsewhere—Laura (community manager) is happy to chat through CMS/framework choices before you commit, and we've seen a few different setups across the network. Link to [ucospo.net](https://ucospo.net) from your page, and open an issue (DM Laura if you need help!) so we can link back to you. Cross-linking is how the network shows up as a network rather than a list of isolated OSPOs.
28+
29+
:::{div}
30+
:class: page-nav
31+
32+
[← What it means to declare yourself an OSPO](./what-it-means.md)
33+
34+
[Mailing list →](./mailing-list.md)
35+
:::

‎about/get-involved/what-it-means.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: What it means to declare yourself an OSPO
3+
---
4+
5+
> This section is still being drafted. It will cover: what your campus is committing to (and what it isn't) when you stand up an OSPO, who to talk to first on your campus, and what "joining the network" actually looks like in practice.
6+
7+
:::{div}
8+
:class: page-nav
9+
10+
[← Get Involved](./)
11+
12+
[Web presence →](./web-presence.md)
13+
:::

‎myst.yml‎

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,22 @@ project:
1212
children:
1313
- file: about/about.md
1414
- file: about/services.md
15-
- file: about/get-involved.md
15+
- file: about/get-involved/index.md
16+
children:
17+
- file: about/get-involved/what-it-means.md
18+
hidden: true
19+
- file: about/get-involved/web-presence.md
20+
hidden: true
21+
- file: about/get-involved/mailing-list.md
22+
hidden: true
23+
- file: about/get-involved/first-meetup.md
24+
hidden: true
25+
- file: about/get-involved/local-stakeholders.md
26+
hidden: true
27+
- file: about/get-involved/network-connection.md
28+
hidden: true
29+
- file: about/get-involved/next-steps.md
30+
hidden: true
1631
- file: about/contact.md
1732
- file: about/guiding-themes/index.md
1833
children:

‎static/css/custom.css‎

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -809,3 +809,50 @@ figcaption,
809809
margin: 0 auto 1rem auto !important;
810810
}
811811
}
812+
813+
/* Per-page prev/next nav at the bottom of welcome-packet sequence pages.
814+
The site-wide footer prev/next is hidden via hide_footer_links: true
815+
in site.yml; these classes provide explicit nav on just the pages that
816+
want it. */
817+
818+
.page-nav {
819+
display: flex;
820+
justify-content: space-between;
821+
margin-top: 2.5rem;
822+
margin-bottom: 2.5rem;
823+
padding-top: 2rem;
824+
border-top: 1px solid #e5e7eb;
825+
}
826+
827+
.page-nav p {
828+
margin: 0;
829+
}
830+
831+
.page-nav-prev-only {
832+
margin-top: 2.5rem;
833+
margin-bottom: 2.5rem;
834+
padding-top: 2rem;
835+
border-top: 1px solid #e5e7eb;
836+
}
837+
838+
.page-nav-next-only {
839+
margin-top: 2.5rem;
840+
margin-bottom: 2.5rem;
841+
padding-top: 2rem;
842+
border-top: 1px solid #e5e7eb;
843+
text-align: right;
844+
}
845+
846+
.page-nav-prev-only p,
847+
.page-nav-next-only p {
848+
margin: 0;
849+
}
850+
851+
/* TEMPORARILY HIDDEN: while the packet pages themselves are hidden from
852+
nav (myst.yml), the prev/next links would just lead readers to draft
853+
stub pages. Remove this block when the packet ships. */
854+
.page-nav,
855+
.page-nav-prev-only,
856+
.page-nav-next-only {
857+
display: none;
858+
}

0 commit comments

Comments
 (0)