React Native Maps & Pathfinding Knowledge Book

A Markdown-first, seven-day revision book for a React Native developer with 4–5 years of experience. It focuses on maps, location, routing, pathfinding, performance, and the native-module knowledge expected in interviews.

The repository uses VitePress to turn the Markdown chapters into a searchable, mobile-friendly static site.

Current status

• The knowledge-first production plan is ready.
• Parts 0–4 are complete: usage guide, React Native foundations, native modules, map SDK integration, and location/permissions.
• Parts 5–10 and the appendix remain planned for incremental writing.
• The finished book targets approximately 22,000–26,000 words across about 57 pages.
• Version-sensitive sources were last reviewed on 2026-08-02.

Requirements

• Node.js 24 or newer
• npm

Local development

npm ci
npm run docs:dev

The development server normally runs at http://localhost:5173.

Production build

npm run docs:build
npm run docs:preview

The generated static site is written to docs/.vitepress/dist and is intentionally excluded from Git.

Content workflow

1. Follow docs/production-plan.md.
2. Write one planned part as self-contained revision knowledge.
3. Keep it within its word budget and mobile-reading structure.
4. Include decision guidance, common failure modes, answered interview questions, and a pocket summary.
5. Finish with version-matched official documentation and its review date.
6. Run the content audit and npm run docs:build before committing.

GitHub Pages

The workflow in .github/workflows/deploy.yml builds and deploys the site whenever main is pushed.

1. Create an empty GitHub repository.
2. Add it as the remote and push the local main branch.
3. Open Settings → Pages in GitHub.
4. Choose GitHub Actions as the publishing source.
5. Re-run the workflow or push another commit if needed.

The VitePress configuration derives the project-site base path from GITHUB_REPOSITORY during GitHub Actions builds. User or organization repositories named <owner>.github.io use /; regular project repositories use /<repository-name>/.

Repository boundaries

• Never commit API keys, tokens, signing material, or private candidate information.
• Paraphrase concepts in original language and link official sources instead of copying documentation.
• Do not represent hypothetical project work as production experience.