docs(introduction): add headings

[gxres042]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

I have added some headings into the introduction, and re-categorize content.

This PR may improve the reading and comprehension experience.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[vercel]

@gxres042 is attempting to deploy a commit to the Nitro Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

📝 Walkthrough

Walkthrough

The file docs/1.docs/1.index.md was restructured: the single introductory paragraph was replaced with multiple labeled sections and subsections covering Nitro’s role (Vite extension and standalone server), production server, API routes, SSR, deployment targets, integrations, performance, built-in functions (KV, Cache, SQL), and a "Try it now" section.

Changes

Cohort / File(s)

Summary

Documentation Restructuring docs/1.docs/1.index.md

Replaced monolithic intro with organized headings and blocks. Added sections: "Production-ready server", "API Routes", "Server-Side Rendering", "Deploy to anywhere", "Integrate with other frameworks", "Optimal Performance", "Built-in functions" (KV Storage, Cache, SQL Database), "Try it now", and clarified Nitro as both a Vite extension and standalone server. No public API or export declarations changed.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'docs(introduction): add headings' follows conventional commits format with correct scope and description.
Description check	✅ Passed	The description clearly explains the changes: adding headings to introduction documentation and re-categorizing content to improve readability and comprehension, which aligns with the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

🧪 Unit Test Generation v2 is now available!

We have significantly improved our unit test generation capabilities.

To enable: Add this to your .coderabbit.yaml configuration:

reviews:
  finishing_touches:
    unit_tests:
      enabled: true

Try it out by using the @coderabbitai generate unit tests command on your code files or under ✨ Finishing Touches on the walkthrough!

Have feedback? Share your thoughts on our Discord thread!

---

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.}

[pi0]

@gxres042 Why closed? Most of changed were looking good.

[gxres042]

@gxres042 Why closed? Most of changed were looking good.

I will * edit something when I have a better change than this 🤔
was planning to bring this up again when I had time 😂

[pi0]

i see 😄 Feel free to close then or keep open i can gladly take some time on it when could.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@docs/1.docs/1.index.md`:
- Line 61: Fix the typo in the user-facing sentence in docs/1.docs/1.index.md by
replacing "isn' t" with the correct contraction "isn't" in the line that reads
"When key-value storage isn' t enough, Nitro also includes a built-in SQL
database." Ensure the updated text reads exactly "When key-value storage isn't
enough, Nitro also includes a built-in SQL database."

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix typo in user-facing text.

“isn' t” has an extra space. Please correct to “isn't”.

✏️ Proposed fix

-When key-value storage isn' t enough, Nitro also includes a built-in SQL database.
+When key-value storage isn't enough, Nitro also includes a built-in SQL database.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	When key-value storage isn' t enough, Nitro also includes a built-in SQL database.
	When key-value storage isn't enough, Nitro also includes a built-in SQL database.

🤖 Prompt for AI Agents

In `@docs/1.docs/1.index.md` at line 61, Fix the typo in the user-facing sentence
in docs/1.docs/1.index.md by replacing "isn' t" with the correct contraction
"isn't" in the line that reads "When key-value storage isn' t enough, Nitro also
includes a built-in SQL database." Ensure the updated text reads exactly "When
key-value storage isn't enough, Nitro also includes a built-in SQL database."