blog: fix links

[pftg]

Summary by CodeRabbit

Release Notes

• Chores
  • Updated contact page navigation links across blog articles to point to the new contact-us endpoint. All call-to-action links directing users to contact the team now use the updated URL.

[coderabbitai]

Walkthrough

This PR systematically updates call-to-action (CTA) links across 19 blog post markdown files, changing navigation endpoints from /contact to /contact-us. All changes are link-target updates with no modifications to content, logic, or structure.

Changes

Cohort / File(s)

Summary

Blog CTA Link Updates content/blog/2025/code-quality-evaluation-non-technical-founders.md, content/blog/2025/fractional-cto-roi-calculator-startup-decision-framework.md, content/blog/2025/hiring-developers-contractors-budget-guide-founders.md, content/blog/2025/infrastructure-spending-evaluation-founders.md, content/blog/2025/kamal-2-deployment-complete-guide.md, content/blog/2025/remote-team-accountability-non-technical-founders.md, content/blog/2025/ruby-on-rails-development-cost-guide-2025.md, content/blog/building-rag-applications-rails-pgvector/index.md, content/blog/building-scalable-rails-apis-architecture-design-patterns.md, content/blog/cost-optimization-llm-applications-token-management/index.md, content/blog/internal-product-teams-cost-center-to-profit-driver.md, content/blog/langchain-memory-systems-conversational-ai/index.md, content/blog/langgraph-workflows-state-machines-ai-agents/index.md, content/blog/production-scaling-langchain-crewai-enterprise/index.md, content/blog/rails-7-upgrade-guide-step-by-step-migration.md, content/blog/rails-performance-optimization-15-proven-techniques.md, content/blog/ruby-memory-management-best-practices-large-applications.md, content/blog/ruby-on-rails-testing-strategy-unit-tests-integration.md, content/blog/testing-monitoring-llm-applications-production/index.md

Updated CTA link targets from /contact or /contact/ endpoints to /contact-us or /contact-us/ across all blog posts; only URL paths changed, no content modifications

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

The changes are highly homogeneous and repetitive—a consistent link-target update pattern applied uniformly across 19 files with no logic alterations, structural changes, or new functionality.

Possibly related PRs

• posts: new posts #263: Directly modifies the same blog post files with CTA link updates, indicating coordinated navigation endpoint changes.
• adds new posts #252: Touches overlapping blog files (e.g., kamal-2-deployment-complete-guide.md), suggesting related content maintenance.
• Adds some posts and cleanups #246: Updates the same building-scalable-rails-apis-architecture-design-patterns.md file with consistent CTA link changes.

Poem

🐰 Links hop from contact to contact-us today,
Nineteen blog posts find their new way,
No logic bent, no content swayed,
Just navigation—neatly remade! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "blog: fix links" is directly related to the actual changeset, which updates call-to-action links across approximately 20 blog post files from /contact (or /contact/) to /contact-us (or /contact-us/). The title correctly identifies that the pull request affects blog files and involves fixing/updating links. While the title is somewhat generic and could be more specific about the nature of the fix (e.g., specifying the contact link endpoint change), it does convey meaningful information and accurately represents the primary activity in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-links

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bd6a0cf and f91d43d.

📒 Files selected for processing (19)

• content/blog/2025/code-quality-evaluation-non-technical-founders.md (1 hunks)
• content/blog/2025/fractional-cto-roi-calculator-startup-decision-framework.md (1 hunks)
• content/blog/2025/hiring-developers-contractors-budget-guide-founders.md (1 hunks)
• content/blog/2025/infrastructure-spending-evaluation-founders.md (1 hunks)
• content/blog/2025/kamal-2-deployment-complete-guide.md (1 hunks)
• content/blog/2025/remote-team-accountability-non-technical-founders.md (1 hunks)
• content/blog/2025/ruby-on-rails-development-cost-guide-2025.md (1 hunks)
• content/blog/building-rag-applications-rails-pgvector/index.md (1 hunks)
• content/blog/building-scalable-rails-apis-architecture-design-patterns.md (1 hunks)
• content/blog/cost-optimization-llm-applications-token-management/index.md (1 hunks)
• content/blog/internal-product-teams-cost-center-to-profit-driver.md (1 hunks)
• content/blog/langchain-memory-systems-conversational-ai/index.md (1 hunks)
• content/blog/langgraph-workflows-state-machines-ai-agents/index.md (1 hunks)
• content/blog/production-scaling-langchain-crewai-enterprise/index.md (2 hunks)
• content/blog/rails-7-upgrade-guide-step-by-step-migration.md (1 hunks)
• content/blog/rails-performance-optimization-15-proven-techniques.md (1 hunks)
• content/blog/ruby-memory-management-best-practices-large-applications.md (1 hunks)
• content/blog/ruby-on-rails-testing-strategy-unit-tests-integration.md (1 hunks)
• content/blog/testing-monitoring-llm-applications-production/index.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build_and_deploy / build

🔇 Additional comments (4)

content/blog/2025/remote-team-accountability-non-technical-founders.md (1)

1318-1318: Link update approved: /contact → /contact-us

The call-to-action link has been correctly updated from the legacy endpoint to the new contact page. The markdown syntax is valid, and the link text is appropriate.

content/blog/production-scaling-langchain-crewai-enterprise/index.md (1)

2907-2907: Lead magnet and consultation links updated: /contact → /contact-us

Two call-to-action links have been correctly updated to point to the new contact endpoint:

• Line 2907: Enterprise AI Architecture Blueprint download link
• Line 2930: Free Architecture Consultation scheduling link

Both markdown syntax validations pass, and the link text alignment is appropriate for each CTA context.

Also applies to: 2930-2930

content/blog/ruby-memory-management-best-practices-large-applications.md (1)

1317-1317: Consultation link updated: /contact/ → /contact-us/

The closing call-to-action link has been correctly updated with full URL format and trailing slash preservation. Markdown syntax is valid, and the link text contextually matches the memory optimization consultation offer.

content/blog/rails-7-upgrade-guide-step-by-step-migration.md (1)

436-436: Rails upgrade consultation links updated: /contact → /contact-us

Two call-to-action links have been correctly updated:

• Line 436: "Let's talk about your Rails upgrade project" link
• Line 444: "Contact us today for a free Rails upgrade consultation" link

Both use the full URL format with trailing slash, maintaining consistency. Markdown syntax passes validation, and link text appropriately contextualizes each CTA within the upgrade guide narrative.

Also applies to: 444-444

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}