Skip to content

Redirects RFC#145

Open
jonnyjohannes wants to merge 1 commit into
masterfrom
redirects-rfc
Open

Redirects RFC#145
jonnyjohannes wants to merge 1 commit into
masterfrom
redirects-rfc

Conversation

@jonnyjohannes

Copy link
Copy Markdown
Collaborator

Compiles design notes into rfcs/0001: redirect flow, infra options (static GitHub-native vs FastAPI backend), click-logging choices, link permanence, target-rot fallback, and a recommendation.

<|°_°|>

Compiles design notes into rfcs/0001: redirect flow, infra options
(static GitHub-native vs FastAPI backend), click-logging choices,
link permanence, target-rot fallback, and a recommendation.

<|°_°|>

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jonnyjohannes jonnyjohannes changed the title Add URL redirect system RFC Redirects RFC Jul 8, 2026
- **Minting:** the existing cron job, when it posts a pet, also **generates a
redirect page** (`docs/r/<slug>/index.html`) and **commits it to the repo**,
then posts `cutepetsboston.com/r/<slug>` to socials.
- **Mapping store (D3):** the committed redirect pages (and/or a `redirects.json`)

@jonnyjohannes jonnyjohannes Jul 14, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

considerations here:

  • self-committing to the repo is making people feel weird
  • possibly a dedicated repo for the metadata storage
  • potentially the same pattern of wiiiiiiiith

Engagement metrics

  • new pipeline that redeploys the web app wiiiiiiiiiiith the retrieved data.

then posts `cutepetsboston.com/r/<slug>` to socials.
- **Mapping store (D3):** the committed redirect pages (and/or a `redirects.json`)
— **in git, permanent, versioned, backed up, free.** Explicitly *not* an artifact.
- **Redirect (D2):** static meta-refresh + JS on the interstitial page.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we prob think we DO NOT need to keep these forever

@jonnyjohannes

Copy link
Copy Markdown
Collaborator Author

We converged on:

  • we're ok with using current infra: github artifact or commit (depending on the complexity of plugging the workflow-and-the-pages together)
  • we'll graduate to a more sophisticated backend when the need(s) arise
  • we can ttl these links, and then old links just bring people back to cutepetsboston.com
  • tableau > js for data analytics, for potentially analytics and exploratory purposes

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