Skip to content

docs: position ralphify as the loop engineering runtime#54

Merged
kasperjunge merged 1 commit into
mainfrom
docs/loop-engineering-positioning
Jun 8, 2026
Merged

docs: position ralphify as the loop engineering runtime#54
kasperjunge merged 1 commit into
mainfrom
docs/loop-engineering-positioning

Conversation

@kasperjunge

Copy link
Copy Markdown
Collaborator

What

Weaves "loop engineering" through the README, MkDocs docs, and the ralphify.co landing page so ralphify is discoverable as the runtime for loop engineering — the emerging paradigm popularized by Peter Steinberger and Boris Cherny ("I don't prompt Claude anymore. My job is to write loops").

The consistent framing across every surface: the ralph loops format is how you write a loop, ralphify is how you run it.

Why

"Loop engineering" is a brand-new, low-competition, high-demand search term, and ralphify is built for exactly this. This is a land-grab: own the term before anyone else does, and use it as the on-ramp to the existing "ralph loop" content.

Changes

Positioning copy

  • README + docs/index.md: bridge line under the tagline; "Why loops" → "Why loop engineering works"
  • docs/getting-started.md + docs/how-it-works.md: loop-engineering framing in the intros

Landing page (website/index.html)

  • New <title>, meta description, Open Graph + Twitter cards
  • Hero badge + subhead, "Why loop engineering wins" heading
  • New first FAQ: "What is loop engineering?" (rich-snippet candidate)

SEO keywords

  • Added "loop engineering" to keyword lists on index, getting-started, how-it-works, agents, cookbook
  • Retitled How it Works → "How Loop Engineering Works"
  • Updated mkdocs.yml site description

Cleanup

  • Removed outdated agr install references; reframed sharing around plain git

Notes

  • Docs build passes mkdocs build --strict.
  • Landing page changes need a redeploy (just website-build → Cloudflare Worker) to go live.
  • Follow-up (not in this PR): add loop-engineering to the GitHub repo topics + About description.

🤖 Generated with Claude Code

…n the new trend

Weave "loop engineering" through the README, docs, and landing page so
ralphify is discoverable as the runtime for the emerging loop-engineering
paradigm (Steinberger/Cherny). Consistently frame it as: the ralph loops
format is how you write a loop, ralphify is how you run it.

- README + docs/index: bridge line under the tagline; "Why loop engineering works"
- landing page: new title/meta/OG/Twitter, hero badge + subhead, "What is loop
  engineering?" FAQ, "Why loop engineering wins" heading
- SEO keywords: add "loop engineering" to index, getting-started, how-it-works,
  agents, cookbook; retitle How it Works
- remove outdated agr install references, reframe sharing around plain git

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
ralphify-co 62f12cf Commit Preview URL

Branch Preview URL
Jun 08 2026, 05:50 PM

@kasperjunge kasperjunge merged commit 6698187 into main Jun 8, 2026
6 checks passed
@kasperjunge kasperjunge deleted the docs/loop-engineering-positioning branch June 8, 2026 17:51
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