# Page Not Found

The URL `files/nTpyG2kFdde7R4VpfI24` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Multi-Page React Application](https://reactjs.koida.tech/multi-page-applications-mpas/multi-page-react-application.md)
- [Lesson 1 - Pulling Book Data from a Different Data File](https://reactjs.koida.tech/react-state-and-styling/lesson-1-pulling-book-data-from-a-different-data-file.md)
- [Lesson 6 - React Project File and Folder Walkthrough](https://reactjs.koida.tech/react-fundamentals/lesson-6-react-project-file-and-folder-walkthrough.md)
- [Lesson 9 - Props and One-Way Data Flow - Overview](https://reactjs.koida.tech/react-fundamentals/lesson-9-props-and-one-way-data-flow-overview.md)
- [Level 2 Team Project](https://reactjs.koida.tech/final-term-project/level-2-team-project-1.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://reactjs.koida.tech/multi-page-applications-mpas/multi-page-react-application.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://reactjs.koida.tech/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://reactjs.koida.tech/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/multi-page-applications-mpas/multi-page-react-application.md`).

You may also use `Accept: text/markdown` header for content negotiation.