Fix quick start guide app init wording

[volfpeter]

Summary by CodeRabbit

• Documentation
  • Updated Quick Start Guide to clarify that App() discovers and registers layouts/pages based on the folder structure, not individual files.
  • Improved wording for clearer guidance on project organization and discovery behavior.
  • No functional changes; content aligns documentation with current behavior to reduce confusion for new users.

[coderabbitai]

Walkthrough

Updated documentation in docs/quick-start-guide.md to state that App() registers layouts/pages based on folder structure instead of file structure. No code or control-flow changes.

Changes

Cohort / File(s)	Change Summary
Docs wording update docs/quick-start-guide.md	Revised phrasing: App() discovery described as based on folder structure rather than file structure. No functional changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my whiskers, pages rearranged,
From files to folders, the wording’s changed.
No code to hop, no routes to chase—
Just tidy trails in the docs’ neat place.
Thump-thump! I sign, with carrot pen,
“Structure set—onward again!” 🥕

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 succinctly describes the change to the quick start guide’s app initialization wording and directly reflects the documentation update without extraneous detail.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/quick-start-guide-app-init

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between 43b1e42 and a0035da.

📒 Files selected for processing (1)

• docs/quick-start-guide.md (1 hunks)

🔇 Additional comments (1)

docs/quick-start-guide.md (1)

39-39: Clarified discovery wording reads well

The updated sentence accurately reflects the folder-based discovery behavior and aligns with the examples in this guide.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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