Epic: Migrate peterp.org to RedwoodSDK
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github-actions, react, vite
- Domain
- build-system, devops, full-stack
Research direction
Start with the current index.html and the RedwoodSDK quick-start and Cloudflare Workers references. Review sub-issues #4–#9 and #20 to understand the migration sequence, using pnpm for package management. Done means the existing site is represented in the RedwoodSDK app with local development, Worker configuration, CI deployment, and validation covered by the listed sub-issues.
Written by the indexing model from the issue text.
Description
Goal
Rewrite the current single-file index.html site as a RedwoodSDK (rwsdk) application — a Vite-based React framework that runs on Cloudflare Workers.
Why
- Move off a static one-pager toward a structured app we can grow (RSC, server functions, realtime).
- Aligns the personal site with the same stack used elsewhere.
Scope
This epic covers only the framework migration (code). Hosting move and domain registrar transfer are tracked separately.
Sub-issues
- #4 Scaffold new RedwoodSDK project
- #5 Port index.html content into RedwoodSDK routes/components
- #6 Port styles to RedwoodSDK app
- #7 Verify local dev for rwsdk app
- #8 Add wrangler.toml / Worker config
- #9 Add CI deploy workflow (GitHub Actions \u2192 Cloudflare Workers)
- #20 Install agent-ci for local GitHub Actions validation
Tooling
Use pnpm for all package management and scripts (not npm/yarn).
Out of scope
- Domain registrar transfer (#3)
- Cutting traffic over from GitHub Pages (#2)
References
- Dominant language
- HTML
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from peterp/peterp.github.io
-
infrastructure
Difficulty 1/5 Under an hour Newbie friendliness 78/100
peterp/peterp.github.io#19 ·
-
infrastructure migration
Difficulty 1/5 Under an hour Newbie friendliness 68/100
peterp/peterp.github.io#14 ·
-
infrastructure migration
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
peterp/peterp.github.io#12 ·
-
infrastructure migration
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
peterp/peterp.github.io#11 ·
-
infrastructure migration
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
peterp/peterp.github.io#10 ·
All issues in peterp/peterp.github.io
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
bjverde/adianti-fork-template#103 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
gfx-rs/wgpu-native#636 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day