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

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>

Author: drmowinckels

content/branding/_index.en.md

@@ -3,9 +3,11 @@ title: Branding
 weight: 6
 chapter: true
 linkTitle: Branding
+aliases:
+  - /organization/tech/brand/
+  - /organizers/tech/brand/
 ---
 
-
 ## Brand identity
 
 RLadies+ launched its new visual identity in March 2026, designed in collaboration with [Science Graphic Design](https://www.sciencegraphicdesign.com/) and shaped by community feedback.
@@ -18,13 +20,13 @@ The full visual identity guide is available as [Branding-guidelines.pdf](https:/
 
 ### Color palette
 
-| Role | Color | Hex code | Preview |
-|------|-------|----------|---------|
-| Main colour | Blue Violet | `#881ef9` | <span style="display:inline-block;width:20px;height:20px;background:#881ef9;border-radius:3px;vertical-align:middle;"></span> |
-| Accent | Dodger Blue | `#146af9` | <span style="display:inline-block;width:20px;height:20px;background:#146af9;border-radius:3px;vertical-align:middle;"></span> |
-| Accent | Brilliant Rose | `#ff5b92` | <span style="display:inline-block;width:20px;height:20px;background:#ff5b92;border-radius:3px;vertical-align:middle;"></span> |
-| Basic | Bastille Black | `#2f2f30` | <span style="display:inline-block;width:20px;height:20px;background:#2f2f30;border-radius:3px;vertical-align:middle;"></span> |
-| Basic | Lavender White | `#ededf4` | <span style="display:inline-block;width:20px;height:20px;background:#ededf4;border:1px solid #ccc;border-radius:3px;vertical-align:middle;"></span> |
+| Role        | Color          | Hex code  | Preview                                                                                                                                             |
+| ----------- | -------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Main colour | Blue Violet    | `#881ef9` | <span style="display:inline-block;width:20px;height:20px;background:#881ef9;border-radius:3px;vertical-align:middle;"></span>                       |
+| Accent      | Dodger Blue    | `#146af9` | <span style="display:inline-block;width:20px;height:20px;background:#146af9;border-radius:3px;vertical-align:middle;"></span>                       |
+| Accent      | Brilliant Rose | `#ff5b92` | <span style="display:inline-block;width:20px;height:20px;background:#ff5b92;border-radius:3px;vertical-align:middle;"></span>                       |
+| Basic       | Bastille Black | `#2f2f30` | <span style="display:inline-block;width:20px;height:20px;background:#2f2f30;border-radius:3px;vertical-align:middle;"></span>                       |
+| Basic       | Lavender White | `#ededf4` | <span style="display:inline-block;width:20px;height:20px;background:#ededf4;border:1px solid #ccc;border-radius:3px;vertical-align:middle;"></span> |
 
 The main colour (Blue Violet) should be used primarily, combined with the basic colours and/or accent colours.
 Accent colours should be used sparingly as supplements to the main colour.
@@ -43,12 +45,12 @@ Each colour also has 75%, 50%, and 25% tints for extended palette use — see th
 
 The official font is **Poppins**, available via [Google Fonts](https://fonts.google.com/specimen/Poppins).
 
-| Element | Weight |
-|---------|--------|
-| Main titles | Poppins Medium |
-| Headings | Poppins SemiBold |
-| Body text | Poppins Regular |
-| Emphasis | Poppins Bold (not italics or underline) |
+| Element     | Weight                                  |
+| ----------- | --------------------------------------- |
+| Main titles | Poppins Medium                          |
+| Headings    | Poppins SemiBold                        |
+| Body text   | Poppins Regular                         |
+| Emphasis    | Poppins Bold (not italics or underline) |
 
 The monospace font is **Inconsolata**.
 
@@ -58,14 +60,14 @@ Maintain visual hierarchy: main titles should be the largest text, headings size
 
 The RLadies+ logo is available in multiple variants:
 
-| Variant | Use case |
-|---------|----------|
-| Vertical (stacked) | Default — use for most cases |
-| Horizontal | When vertical space is limited |
-| Full colour | Light or white backgrounds |
-| Bastille Black | Light backgrounds (single-colour alternative) |
-| Lavender White | Dark or coloured backgrounds |
-| Pure Black / Pure White | High-contrast contexts |
+| Variant                 | Use case                                      |
+| ----------------------- | --------------------------------------------- |
+| Vertical (stacked)      | Default — use for most cases                  |
+| Horizontal              | When vertical space is limited                |
+| Full colour             | Light or white backgrounds                    |
+| Bastille Black          | Light backgrounds (single-colour alternative) |
+| Lavender White          | Dark or coloured backgrounds                  |
+| Pure Black / Pure White | High-contrast contexts                        |
 
 {{% notice warning %}}
 **Do not** edit the logo shapes, move the logo icon relative to its text, recreate the logo using a different font, change the logo's proportions (rotate, skew, stretch), or position the logo on a busy or discontinuous background. Leave enough space around the logo and text.
@@ -83,29 +85,29 @@ It contains the full colour palette (including tints), typography settings, and
 
 All official assets are in the [branding-materials repository](https://github.com/rladies/branding-materials):
 
-| Folder | Contents |
-|--------|----------|
-| `logos/horizontal/` | Horizontal logo in 5 colour variants |
-| `logos/vertical/` | Vertical (stacked) logo in 5 colour variants |
-| `logos/favicon/` | Favicon icons |
-| `logos/hex/` | Hex sticker logos (4 variants) |
-| `logos/social-media/` | Social media profile pictures |
-| `logos/circular/` | Circular logos (not for social media) |
-| `logos/quarto/` | Clean-named SVGs for Quarto and web projects |
-| `templates/slidedecks/` | PowerPoint and Google Slides templates |
-| `templates/documents/` | Document templates (with and without letterheads) |
-| `templates/certificates/` | Certificate templates (DOCX and PDF) |
+| Folder                    | Contents                                          |
+| ------------------------- | ------------------------------------------------- |
+| `logos/horizontal/`       | Horizontal logo in 5 colour variants              |
+| `logos/vertical/`         | Vertical (stacked) logo in 5 colour variants      |
+| `logos/favicon/`          | Favicon icons                                     |
+| `logos/hex/`              | Hex sticker logos (4 variants)                    |
+| `logos/social-media/`     | Social media profile pictures                     |
+| `logos/circular/`         | Circular logos (not for social media)             |
+| `logos/quarto/`           | Clean-named SVGs for Quarto and web projects      |
+| `templates/slidedecks/`   | PowerPoint and Google Slides templates            |
+| `templates/documents/`    | Document templates (with and without letterheads) |
+| `templates/certificates/` | Certificate templates (DOCX and PDF)              |
 
 Additional editable templates are available on [Google Drive](https://drive.google.com/drive/folders/1UV940p-KN9FWoHt4yrZnrc2oAczGw9QB?usp=sharing) and in the [RLadies+ Canva workspace](https://www.canva.com/folder/FAHCPq0DH3w).
 
 ## Tools and extensions
 
-| Tool | Description |
-|------|-------------|
-| [glamour](https://github.com/rladies/glamour) | Quarto extension — applies RLadies+ branding to documents and presentations |
-| [spellbind](https://github.com/rladies/spellbind) | R package with brand colours ([documentation](https://rladies.org/spellbind/)) |
-| [cloak](https://github.com/rladies/cloak) | pkgdown theme for R package websites |
-| [brand.yml](https://github.com/rladies/branding-materials/blob/rebrand/brand.yml) | Machine-readable brand definition for Quarto and Shiny |
+| Tool                                                                              | Description                                                                    |
+| --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
+| [glamour](https://github.com/rladies/glamour)                                     | Quarto extension — applies RLadies+ branding to documents and presentations    |
+| [spellbind](https://github.com/rladies/spellbind)                                 | R package with brand colours ([documentation](https://rladies.org/spellbind/)) |
+| [cloak](https://github.com/rladies/cloak)                                         | pkgdown theme for R package websites                                           |
+| [brand.yml](https://github.com/rladies/branding-materials/blob/rebrand/brand.yml) | Machine-readable brand definition for Quarto and Shiny                         |
 
 ## Legacy materials
 

content/global-team/infrastructure/_index.en.md

@@ -0,0 +1,11 @@
+---
+title: "Infrastructure"
+linkTitle: "Infrastructure"
+weight: 60
+chapter: false
+---
+
+Runbooks for the secrets, tokens, and deploy keys that keep the R-Ladies website, directory, and automation workflows running.
+These pages are for Global Team members with org-owner or repo-admin access — chapter organisers do not need to read them.
+
+Start with the [Build Architecture]({{% relref "build-architecture" %}}) page for the cross-repo map showing how everything connects, then drill into individual credentials as needed.

…ent/organizers/tech/airtable/index.en.md …rastructure/airtable-api-key/index.en.mdcontent/organizers/tech/airtable/index.en.md renamed to content/global-team/infrastructure/airtable-api-key/index.en.md content/organizers/tech/airtable/index.en.md renamed to content/global-team/infrastructure/airtable-api-key/index.en.md

@@ -1,22 +1,28 @@
 ---
-title: "Airtable API Key"
-linkTitle: "Airtable"
-weight: 7
+title: "Airtable API Key (AIRTABLE_API_KEY)"
+linkTitle: "Airtable API Key"
+weight: 40
 aliases:
   - /organization/tech/airtable/
+  - /organizers/tech/airtable/
 ---
 
 R-Ladies uses Airtable as the backend for directory submissions and Global Team membership data.
 Two repos connect to Airtable through a shared API key stored as `AIRTABLE_API_KEY`.
 
+{{% notice info %}}
+This page documents the `AIRTABLE_API_KEY` org secret used by GitHub Actions workflows.
+If you're looking for guidance on how Global Team members use the Airtable bases day-to-day, see the [Airtable guide]({{% relref "/global-team/airtable" %}}).
+{{% /notice %}}
+
 ## Airtable bases
 
 We maintain separate Airtable bases for different purposes:
 
-| Base ID | Purpose | Key tables | Used by |
-|---|---|---|---|
-| `appzYxePUruG9Nwyg` | Directory submissions | Submissions, Languages, Countries | `directory` |
-| `appZjaV7eM0Y9FsHZ` | Global Team | Members, Teams, Alumni | `rladies.github.io` |
+| Base ID             | Purpose               | Key tables                        | Used by             |
+| ------------------- | --------------------- | --------------------------------- | ------------------- |
+| `appzYxePUruG9Nwyg` | Directory submissions | Submissions, Languages, Countries | `directory`         |
+| `appZjaV7eM0Y9FsHZ` | Global Team           | Members, Teams, Alumni            | `rladies.github.io` |
 
 The `directory` repo pulls new member submissions every Friday via `airtable-update.yml` and deletes processed records after PRs merge via `airtable-delete.yml`.
 
@@ -31,14 +37,14 @@ Make sure the account that generates the token has at least Editor access on bot
 
 ## Creating a new token
 
-1. Log in to [airtable.com](https://airtable.com) with the R-Ladies Airtable account  
-2. Go to [airtable.com/create/tokens](https://airtable.com/create/tokens)  
-3. Create a new personal access token with these scopes:  
-   - `data.records:read` — read records from tables  
-   - `data.records:write` — create and update records  
-   - `schema.bases:read` — read base schema (needed by `airtabler`)  
-4. Under "Access", add both bases: the directory base and the Global Team base  
-5. Copy the generated token  
+1. Log in to [airtable.com](https://airtable.com) with the R-Ladies Airtable account
+2. Go to [airtable.com/create/tokens](https://airtable.com/create/tokens)
+3. Create a new personal access token with these scopes:
+   - `data.records:read` — read records from tables
+   - `data.records:write` — create and update records
+   - `schema.bases:read` — read base schema (needed by `airtabler`)
+4. Under "Access", add both bases: the directory base and the Global Team base
+5. Copy the generated token
 
 ## Storing the secret
 

…zers/tech/build-architecture/index.en.md …structure/build-architecture/index.en.mdcontent/organizers/tech/build-architecture/index.en.md renamed to content/global-team/infrastructure/build-architecture/index.en.md content/organizers/tech/build-architecture/index.en.md renamed to content/global-team/infrastructure/build-architecture/index.en.md

@@ -1,9 +1,10 @@
 ---
 title: "Cross-Repo Build Architecture"
 linkTitle: "Build Architecture"
-weight: 10
+weight: 1
 aliases:
   - /organization/tech/build-architecture/
+  - /organizers/tech/build-architecture/
 ---
 
 The R-Ladies website build is the most interconnected piece of our infrastructure.
@@ -14,12 +15,12 @@ This page maps out how everything fits together.
 
 When someone submits a new directory entry or blog post, the path to the live website looks like this:
 
-1. **Airtable** receives a new submission (directory entry) or a contributor opens a PR (blog)  
-2. **Source repos** (`directory` or `awesome-rladies-blogs`) process the data and create or update a PR  
-3. The source repo **triggers a preview build** on `rladies.github.io` via `workflow_dispatch`  
-4. **`rladies.github.io`** clones the source repos via SSH, builds the Hugo site, and deploys a preview to Netlify  
-5. The preview build **posts a comment** back to the originating PR with the preview link  
-6. Once the PR merges, the next **scheduled production build** (every 12 hours) picks up the changes  
+1. **Airtable** receives a new submission (directory entry) or a contributor opens a PR (blog)
+2. **Source repos** (`directory` or `awesome-rladies-blogs`) process the data and create or update a PR
+3. The source repo **triggers a preview build** on `rladies.github.io` via `workflow_dispatch`
+4. **`rladies.github.io`** clones the source repos via SSH, builds the Hugo site, and deploys a preview to Netlify
+5. The preview build **posts a comment** back to the originating PR with the preview link
+6. Once the PR merges, the next **scheduled production build** (every 12 hours) picks up the changes
 
 ## What connects to what
 
@@ -38,16 +39,16 @@ awesome-rladies-blogs                 ├── clones directory (SSH)
 
 Each connection in the diagram above requires a specific secret:
 
-| Connection | Secret | Stored in | Type |
-|---|---|---|---|
-| Source repo dispatches build | `GLOBAL_GHA_PAT` | Org secret | PAT |
-| Website clones `directory` | `ssh_directoryy_repo` | `rladies.github.io` | SSH deploy key |
-| Website clones `awesome-rladies-blogs` | `RLADIES_BLOGS_KEY` | `rladies.github.io` | SSH deploy key |
-| Website comments on source PR | `GLOBAL_GHA_PAT` | Org secret | PAT |
-| Website deploys preview to Netlify | `NETLIFY_AUTH_TOKEN` | `rladies.github.io` | API token |
-| Website identifies Netlify site | `NETLIFY_SITE_ID` | `rladies.github.io` | Site ID |
-| Global Team data pushed to main | `push-to-protected` | `rladies.github.io` | SSH deploy key |
-| Global Team data pushed to main | `ADMIN_TOKEN` | Org secret | PAT |
+| Connection                             | Secret                | Stored in           | Type           |
+| -------------------------------------- | --------------------- | ------------------- | -------------- |
+| Source repo dispatches build           | `GLOBAL_GHA_PAT`      | Org secret          | PAT            |
+| Website clones `directory`             | `ssh_directoryy_repo` | `rladies.github.io` | SSH deploy key |
+| Website clones `awesome-rladies-blogs` | `RLADIES_BLOGS_KEY`   | `rladies.github.io` | SSH deploy key |
+| Website comments on source PR          | `GLOBAL_GHA_PAT`      | Org secret          | PAT            |
+| Website deploys preview to Netlify     | `NETLIFY_AUTH_TOKEN`  | `rladies.github.io` | API token      |
+| Website identifies Netlify site        | `NETLIFY_SITE_ID`     | `rladies.github.io` | Site ID        |
+| Global Team data pushed to main        | `push-to-protected`   | `rladies.github.io` | SSH deploy key |
+| Global Team data pushed to main        | `ADMIN_TOKEN`         | Org secret          | PAT            |
 
 ## Production vs. preview builds
 
@@ -73,9 +74,9 @@ See the [GitHub PAT](../github-pat/), [Admin Token](../github-admin-token/), and
 We use two separate Netlify setups:
 
 - **Website previews** — `rladies.github.io` deploys preview builds to Netlify using `NETLIFY_AUTH_TOKEN` and `NETLIFY_SITE_ID` (stored as repo-level secrets).
-The preview URL is posted back to the originating PR.  
+  The preview URL is posted back to the originating PR.
 - **R-Ladies Guide** — `rladiesguide` is hosted on Netlify at `guide.rladies.org`.
-The `.github` org repo has a `RLADIESGUIDE` secret containing a Netlify deploy hook URL that triggers a rebuild whenever the org-level repo is updated.  
+  The `.github` org repo has a `RLADIESGUIDE` secret containing a Netlify deploy hook URL that triggers a rebuild whenever the org-level repo is updated.
 
 The Netlify account credentials and site ownership should be documented with the team.
 If you lose access to the Netlify account, preview deploys and the guide site will stop updating.