docs: Identify top 10 how-to docs, add deployment guide (#4701)

<!-- One very short sentence on the WHAT and WHY of the PR. E.g. "Remove
pathHash attribute because it is confirmed unused." or "Add DNS round
robin to improve load distribution." -->
Add a comprehensive how-to guide for deploying TanStack Router to
production and establish a multi-PR process for future documentation.

---------

Co-authored-by: Cursor Agent <[email protected]>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>

Author: 3 people

docs/router/framework/react/how-to/README.md

@@ -1,22 +1,34 @@
 # How-To Guides
 
-This directory contains terse, step-by-step instructions for common TanStack Router tasks. Each guide is designed to be:
+This directory contains focused, step-by-step instructions for common TanStack Router tasks. Each guide is designed to be:
 
-- **Bite-sized**: Focused on a single, specific task
-- **Actionable**: Step-by-step instructions you can follow immediately
-- **Concise**: No extra explanation, just the essential steps
-- **Targeted**: Easy for both users and AI to find exactly what they need
+- **Task-focused**: Covers one specific goal from start to finish
+- **Self-contained**: All necessary steps included, no prerequisites assumed
+- **Copy-paste ready**: Working code examples you can use immediately
+- **Problem-solving oriented**: Addresses real-world scenarios and common issues
 
 ## Available Guides
 
 - [Install TanStack Router](./install.md) - Basic installation steps
+- [Deploy to Production](./deploy-to-production.md) - Deploy your app to hosting platforms
+
+## Using These Guides
+
+Each guide follows a consistent structure:
+
+1. **Quick Start** - Brief overview of what you'll accomplish
+2. **Step-by-step instructions** - Platform-specific or scenario-specific guidance
+3. **Production checklist** - Verification steps (where applicable)
+4. **Common problems** - Troubleshooting for typical issues
+5. **Common next steps** - Optional related tasks you might want to tackle
 
 ## Contributing
 
 When adding new how-to guides:
 
-1. Keep each guide focused on one specific task
-2. Use numbered steps for clarity
-3. Include prerequisites if needed
-4. Provide next steps or related guides
-5. Check existing documentation for duplicate content and update references accordingly
+1. Focus on a single, well-defined task
+2. Use clear headings and numbered steps
+3. Include complete, working code examples
+4. Address the most frequent problems at the end
+5. Comment out "Common next steps" links until those guides are created
+6. In "Related Resources", link to specific relevant resources, not generic documentation