Skip to content

Split tech section by audience: organiser tooling vs Global Team infrastructure#207

Open
drmowinckels wants to merge 1 commit into
mainfrom
split-tech-organisers-vs-infra
Open

Split tech section by audience: organiser tooling vs Global Team infrastructure#207
drmowinckels wants to merge 1 commit into
mainfrom
split-tech-organisers-vs-infra

Conversation

@drmowinckels

Copy link
Copy Markdown
Member

Summary

The /organizers/tech/ section mixed two unrelated audiences: chapter organisers needing Slack/Meetup/email setup, and Global Team members maintaining the build pipeline, PATs, deploy keys, and API credentials. Six of the ten pages were org-owner-only runbooks no chapter organiser would ever act on.

This PR splits them by audience:

content/organizers/tech/ keeps the four chapter-facing tooling pages:

  • accounts/ (Slack, Meetup, GitHub chapter repos, Posit Cloud)
  • email/
  • security/
  • updated _index.en.md with a pointer to the new infrastructure section

content/global-team/infrastructure/ (new) holds the six runbooks, ordered so Build Architecture is the entry point:

  • build-architecture/ (the cross-repo map)
  • github-pat/ (GLOBAL_GHA_PAT rotation)
  • github-admin-token/ (ADMIN_TOKEN rotation)
  • ssh-deploy-keys/
  • airtable-api-key/ (renamed from airtable/ to distinguish from the existing global-team/airtable/ usage guide; added a cross-link between the two)
  • meetup-api/

Every moved page kept its /organization/tech/<x>/ alias and gained a new /organizers/tech/<x>/ alias, so no external links break. All moves use git mv so history is preserved.

The organizers/tech/brand/ stub (already just a 4-line redirect to /branding/) is deleted; its aliases live on content/branding/_index.en.md now, and the two outbound links pointing at it (in content/global-team/meetup/index.en.md and content/organizers/online-presence/social-media/index.en.md) were updated to point at /branding/ directly.

Test plan

  • hugo builds cleanly (only pre-existing jinx shortcode warnings, unrelated)
  • 76 aliases generated; spot-checked /organizers/tech/build-architecture//global-team/infrastructure/build-architecture/ redirect works
  • Spot-checked /organization/tech/brand//branding/ redirect works
  • Review the navigation on the rendered preview: confirm the slimmer Tooling menu reads correctly for organisers and that Infrastructure shows up under Global Team in the expected order

🤖 Generated with Claude Code

…astructure

The /organizers/tech/ section mixed two unrelated audiences: chapter
organisers needing Slack/Meetup/email setup, and Global Team members
maintaining the build pipeline, PATs, deploy keys, and API credentials.
Six of the ten pages were org-owner-only runbooks no organiser would
ever act on.

Moves six pages to a new /global-team/infrastructure/ section:
build-architecture, github-pat, github-admin-token, ssh-deploy-keys,
airtable (renamed to airtable-api-key to distinguish from the existing
global-team/airtable/ usage guide), and meetup-api. Each moved page
keeps its old /organization/tech/ alias and gains an /organizers/tech/
alias so external links still resolve.

The brand/ stub (already just a 4-line redirect) is deleted; its
aliases moved onto content/branding/_index.en.md and the two outbound
links updated to point at /branding/ directly.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@drmowinckels drmowinckels requested a review from a team as a code owner May 28, 2026 19:29
@drmowinckels drmowinckels requested a review from reshamas May 28, 2026 19:29
@jinx-familiar

jinx-familiar Bot commented May 28, 2026

Copy link
Copy Markdown

Broken Link Check

✅ No broken links found.

Updated: 2026-05-28T19:29:29.955Z

@jinx-familiar

jinx-familiar Bot commented May 28, 2026

Copy link
Copy Markdown

i18n Coverage

Content pages missing translations

These changed content directories are missing translations:

  • content/branding (es)
  • content/global-team/infrastructure (es)
  • content/global-team/infrastructure/airtable-api-key (es)
  • content/global-team/infrastructure/build-architecture (es)
  • content/global-team/infrastructure/github-admin-token (es)
  • content/global-team/infrastructure/github-pat (es)
  • content/global-team/infrastructure/meetup-api (es)
  • content/global-team/infrastructure/ssh-deploy-keys (es)
  • content/global-team/meetup (es)
  • content/organizers/online-presence/social-media (es)
  • content/organizers/tech (es)

Translations are recommended for all configured languages. Missing language files fall back to the default content language.

Updated: 2026-05-28T19:30:50.658Z

drmowinckels added a commit that referenced this pull request May 29, 2026
Adds an infrastructure runbook for the Cloudflare account that owns
rladies.org DNS, hosts the Jinx runtime (Workers, KV, Vectorize,
Workers AI), and runs Cloudflare Web Analytics. Covers the shared
admin role-mailbox pattern (credentials in 1Password),
`CLOUDFLARE_API_TOKEN` rotation via `gh secret set` and Wrangler
secret management, navigation paths for DNS, Web Analytics, Worker
logs, and billing, plus the quarterly DNS audit cadence and recovery
when 2FA breaks.

Aliases the page from `/website/admin_guide/cloudflare/`,
`/website/admin_guide/domain-management/`, and `/website/admin_guide/dns/`
so it is reachable from the website-admin URL space.

Stacks on #207.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
drmowinckels added a commit that referenced this pull request May 29, 2026
Adds an infrastructure runbook for the OSS-plan 1Password account
that holds RLadies+'s shared credentials. Covers the leadership-as-
admins model, the admin console URL and navigation, first-time
activation flow for new admins (email → master password → Secret
Key → Emergency Kit → app install), daily credential retrieval
(vault selector, search, copy icon, clipboard auto-clear), the
Emergency Kit habit as the one operational practice that genuinely
matters, recovery scenarios (lost device, forgotten master password,
suspected compromise, primary holder transfer), the chapter-vs-
Global-Team distinction, and the six-monthly admin audit cadence.

Stacks on #207.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
drmowinckels added a commit that referenced this pull request May 29, 2026
Adds a five-page subsection covering the org-level GitHub setup that
the existing PAT, Admin Token, and SSH Deploy Keys runbooks sit on
top of:

- `_index.en.md` — overview (Team plan paid through a leadership
  member's faculty account, the open Free-for-OSS upgrade question
  framed honestly, billing-lapse failure mode)
- `org-membership.md` — owners, teams, member invitations via the
  `global-team` onboarding workflows, offboarding via
  `offboarding-finalise.yml`, literal click paths for demoting an
  owner and removing collaborators, four-step periodic review checklist
- `core-repositories.md` — the eight repos that matter for day-to-day
  operations with cross-links to where each is documented further
- `branch-protection.md` — convention enforced on `main` across the
  core repos, the bypass identities (`ADMIN_TOKEN`, `push-to-protected`)
  framed as operational debt, literal Settings → Rules → Rulesets
  navigation
- `apps-and-bots.md` — Jinx as the headline GitHub App with a paste-
  ready `actions/create-github-app-token@v3` adoption snippet,
  Dependabot, the deliberately-short integration list

Stacks on #207.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
drmowinckels added a commit that referenced this pull request May 29, 2026
Adds a five-page subsection covering the Workspace Nonprofit tenant
that owns rladies.org email:

- `_index.en.md` — overview: plan, what we actually use Workspace
  for (email + the occasional shared doc), and the shared super-admin
  role-mailbox pattern
- `admin-console.md` — operational runbook: how to reach
  admin.google.com, the menu paths that matter for our small
  footprint, the six-monthly review cadence, sign-in troubleshooting,
  and step-by-step click paths for the common admin tasks (chapter
  mailbox provisioning, alias provisioning, suspend/delete/transfer
  with the decision tree, password reset)
- `chapter-emails.md` — short signpost to the existing organiser-
  facing email/accounts pages
- `shared-drive.md` — Global Team meeting notes context with a literal
  Shared Drives → Members → role-picker walkthrough
- `organisation-and-policies.md` — target-state recommendation: OU
  structure (with one worked end-to-end policy-on-OU example), Groups
  strategy with per-group access types and ownership convention,
  chapter mailbox 12/24-month lifecycle, alias offboarding Day 0/90,
  SPF/DKIM/DMARC verification via external inspector plus admin
  console, six-monthly recovery drill, seven-step migration plan with
  per-step verification

Stacks on #207.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
drmowinckels added a commit that referenced this pull request May 29, 2026
Adds a Netlify management runbook at
`content/website/admin_guide/netlify/`. Covers the account's two
sites (rladies.github.io preview deploys + guide.rladies.org), the
three secrets that connect them (`NETLIFY_AUTH_TOKEN`,
`NETLIFY_SITE_ID`, `RLADIESGUIDE` deploy hook), custom-domain TLS
recovery, and literal click paths for rotating the auth token (with
verification step), rotating the deploy hook, adding collaborators,
rolling back to a previous deploy, locking production during
incidents, and configuring deploy notifications.

Alias from `/global-team/infrastructure/netlify/` keeps any in-flight
references resolving.

Stacks on #207.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
drmowinckels added a commit that referenced this pull request May 29, 2026
Adds an infrastructure runbook for the shared Zoom account that
hosts chapter events. Covers grant-funded billing, the "request a
host" model with the alternative-host convention as the click-path
follow-up, recording posture with the recommended account-level
auto-delete to enforce retention, integrations (Calendly + Meetup +
Workspace) including the Meetup auto-Zoom-link disable path,
shared admin role-mailbox access via 1Password, literal click paths
for adding/removing host licenses, configuring defaults, pulling
participant reports, and the mid-event panic-mode recovery when a
host link fails minutes before an event.

Stacks on #207.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
drmowinckels added a commit that referenced this pull request May 29, 2026
Adds an infrastructure runbook for the Calendly account used for
mentoring sessions, office hours, and other bookable slots. Covers
per-member-seat structure, Zoom/Calendar/Slack integrations including
the per-member Calendar re-authorisation pattern after Workspace
password rotations, shared admin role-mailbox access via 1Password,
literal click paths for adding/removing members, creating shared
event types, connecting calendars, pulling reports, double-booking
recovery, and the post-member-removal pending-bookings sweep. Includes
the standing recommendation that the RLadies+ Code of Conduct link
belongs in every confirmation email.

Stacks on #207.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
drmowinckels added a commit that referenced this pull request May 29, 2026
Adds a runbook for the two RLadies+ Slack workspaces — the organisers
workspace (invitations via chapter onboarding) and the community
workspace (invitations via Airtable form + Jinx webhook). Covers plan
tradeoffs (Slack Free vs the open Pro for Nonprofits question),
leadership-as-owners admin model with shared admin role-mailbox login
in 1Password, channel conventions, Jinx as the headline installed
app, and literal click paths for channel-creation permissions,
workspace export (with Free vs Pro caveat), app review and
revocation, 2FA enforcement, audit log location, retention policy,
and owner-recovery when the only owner leaves.

Stacks on #207.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
drmowinckels added a commit that referenced this pull request May 29, 2026
Adds `content/global-team/social-media-management/buffer.md`
documenting how RLadies+ posts to Bluesky, Mastodon, LinkedIn,
Instagram, and YouTube through a single shared Buffer account. The
page exists because Buffer's connection to each platform breaks
silently occasionally, and re-authorising is the operation a new
social-media volunteer most needs to know.

Covers the Channels health dashboard, drafts vs scheduled vs queue
(the common cause of "I scheduled it but it didn't post"), posting
schedule configuration, per-platform reconnection runbooks (Bluesky
app passwords, Mastodon OAuth, LinkedIn Page Admin trap, Meta
Business chain for Instagram, Google Brand Account for YouTube),
adding and removing team members, the silent-posting-failure
diagnostic, reposting old content, analytics access, and the
six-monthly audit cadence.

Stacks on #207.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
drmowinckels added a commit that referenced this pull request May 29, 2026
Adds an infrastructure runbook for the RLadies+ Posit Cloud Team —
the Global Team members who process chapter workshop access
requests, create spaces, and manage the donated license. Covers the
license terms (10 Instructors / 440 Students / unlimited compute
hours / per-project caps), the request flow via the
rladies.org/form/posit-cloud-request form into the `posit-cloud`
Slack channel, the literal space-creation runbook with posit.cloud
click paths, member management, license utilisation review, the
two-week space cleanup cadence, troubleshooting for invitation and
compute-cap issues, and the watch list for license utilisation and
programme renewal.

Cross-links the existing organiser-facing usage docs in
`organizers/tech/accounts` rather than duplicating them.

Stacks on #207.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
drmowinckels added a commit that referenced this pull request May 29, 2026
Adds `content/global-team/social-media-management/buffer.md`
documenting how RLadies+ posts to Bluesky, Mastodon, LinkedIn,
Instagram, and YouTube through a single shared Buffer account. The
page exists because Buffer's connection to each platform breaks
silently occasionally, and re-authorising is the operation a new
social-media volunteer most needs to know.

Covers the Channels health dashboard, drafts vs scheduled vs queue
(the common cause of "I scheduled it but it didn't post"), posting
schedule configuration, per-platform reconnection runbooks (Bluesky
app passwords, Mastodon OAuth, LinkedIn Page Admin trap, Meta
Business chain for Instagram, Google Brand Account for YouTube),
adding and removing team members, the silent-posting-failure
diagnostic, reposting old content, analytics access, and the
six-monthly audit cadence.

Stacks on #207.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
drmowinckels added a commit that referenced this pull request May 29, 2026
Restructures `content/global-team/finance/` from a single page into
a Hugo section and adds three sub-pages for the actual financial
tools:

- `relay/` — primary USD operating account: sign-in, transactions
  and bookkeeping export, virtual cards per subscription, ACH
  transfers, user management, recovery
- `wise/` — international transfers: sending, receiving via local
  account details in multiple currencies, multi-currency reserves,
  sweep-to-Relay cadence
- `paypal/` — donation channel: nonprofit fee tier, donor refunds,
  receipt template, weekly sweep to Relay, donor-fee absorption
  policy

The `_index.en.md` preserves the existing donations policy with
light edits and cross-links into the tool sub-pages, into the
forthcoming nonprofit-administration section, and into 1Password
for credentials.

Stacks on #207.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
drmowinckels added a commit that referenced this pull request May 29, 2026
…eMailbox)

Adds a new section at `content/global-team/nonprofit-administration/`
covering the three external services that handle RLadies+'s
California-nonprofit corporate surface:

- `vcorp/` — California compliance partner: registered agent,
  biennial Statement of Information, annual Form 990, FTB
  correspondence, document forwarding. Includes the typical annual
  calendar and the "VCorp files but we decide" framing.
- `openphone/` — shared US phone number: voicemail with transcription,
  team SMS inbox, business hours/routing, call filtering, shared-inbox
  conventions.
- `anytime-mailbox/` — Oakland virtual business address: weekly
  mail-triage cadence, the four per-item action paths
  (Open/Scan/Shred, Open/Scan/Hold, Forward, Shred), authorised-
  recipient list maintenance, service-of-process routing to VCorp.

All three services share the same continuity pattern: credentials in
the 1Password Shared vault; recovery flows through the shared
leadership role mailbox.

Stacks on #207.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant