Unify related project sites with a visible “Part of ShakaStack” journey

[justin808]

Parent: #45

Why

React on Rails, Shakapacker, E2E on Rails, ShakaPerf, and Control Plane Flow can still feel like separate properties. Visitors should understand the family relationship and the next logical step without being forced back to a search engine.

Scope

Define the canonical cross-site navigation and messaging in ShakaStack.com, then create or link follow-up work in each affected repository.

Potential shared element:

Part of ShakaStack — Build → Test → Prove → Deploy

Contextual next steps:

• React on Rails → bundle with Shakapacker
• Shakapacker → test with E2E on Rails
• E2E on Rails → prove performance and visual stability with ShakaPerf
• ShakaPerf → deploy a validated version with Control Plane Flow
• every project → return to the complete ShakaStack overview

Acceptance criteria

• Inventory the canonical domains, repositories, and current cross-links for all five projects.
• Define consistent project names, phase names, descriptions, and ShakaStack URL targets.
• Add an unobtrusive “Part of ShakaStack” treatment to ShakaStack.com's project outbound experience.
• Specify a reusable cross-site navigation/footer pattern.
• Keep each project's primary documentation task dominant; the family navigation must not become a marketing obstruction.
• File or link implementation issues in each related repository rather than treating external-site changes as completed here.
• Avoid cross-site circular links that provide no useful next step.
• Verify all links and mobile/accessibility behavior.