feat: rename /workflow to /spec-driven-development for SEO#449
Conversation
- Route: /workflow → /spec-driven-development (with redirect from old URL) - Page title: "Spec-Driven Development with Semantic Anchors" - Nav label: "Spec-Driven Dev" (EN + DE) - AsciiDoc h1 updated in both EN and DE versions - All cross-links updated (brownfield pages, sitemap, prerender) - Old /workflow URL redirects automatically via navigate() Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
WalkthroughDas Pull Request benennt die Workflow-Seite von der Route Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 0/1 reviews remaining, refill in 51 minutes and 52 seconds.Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@scripts/prerender-routes.js`:
- Around line 44-49: The new route replaced the old '/workflow' URL so a static
file for dist/workflow/index.html is no longer generated; add an explicit legacy
redirect entry in scripts/prerender-routes.js that preserves the old path by
creating a route object with path: '/workflow' (or a small redirect fragment)
which generates a static page at dist/workflow/index.html that redirects (via
meta-refresh and/or JS) to '/spec-driven-development' and reuses the same
fragment/title/description values (or points to docs/spec-driven-workflow.html)
so direct visits to /workflow on GitHub Pages are routed to the new URL.
In `@website/src/main.js`:
- Around line 149-150: The legacy redirect from the '/workflow' route uses
navigate('/spec-driven-development') which internally calls pushState and causes
a history back-loop; change the '/workflow' route handler registered via
addRoute to perform a replace navigation (use the navigate API or
history.replace variant that replaces the current entry) instead of pushing a
new history entry so that addRoute('/workflow', ...) replaces the current
history state with '/spec-driven-development' rather than pushing it.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro
Run ID: b24fb626-cc24-49f5-b57c-33d86782638f
📒 Files selected for processing (11)
docs/brownfield-workflow.adocdocs/brownfield-workflow.de.adocdocs/spec-driven-workflow.adocdocs/spec-driven-workflow.de.adocscripts/generate-sitemap.jsscripts/prerender-routes.jswebsite/src/components/header.jswebsite/src/main.jswebsite/src/translations/de.jsonwebsite/src/translations/en.jsonwebsite/src/utils/router.js
Update trailing-slash URL test to use /spec-driven-development/ and expect the new page title. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…lback - Use replaceState instead of pushState for /workflow → /spec-driven-development redirect to prevent back-button loop - Add static redirect page at dist/workflow/index.html for direct URL access on GitHub Pages (meta http-equiv refresh + canonical link) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Summary
/workflowto/spec-driven-developmentfor better SEO discoverability/workflowURL redirects automaticallyTest plan
/spec-driven-development— page loads with new title/workflow— redirects to/spec-driven-development/spec-driven-development<title>tag🤖 Generated with Claude Code
Summary by CodeRabbit
Release Notes
Documentation
Chores