# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [React Code Along from Scratch](https://reactjs.koida.tech/react-fundamentals/react-code-along-from-scratch.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 3 - What is ReactJS - How it Works](https://reactjs.koida.tech/react-fundamentals/lesson-3-what-is-reactjs-how-it-works.md)
- [Lesson 2: How to set up a new Next.js project](https://reactjs.koida.tech/backend-frameworks-next.js/lesson-2-how-to-set-up-a-new-next.js-project.md)
- [Lesson 1. React+Vite+TS+Shadcn Project](https://reactjs.koida.tech/deployment-and-web-hosting/lesson-1.-react+vite+ts+shadcn-project.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/react-fundamentals/react-code-along-from-scratch.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., `/react-fundamentals/react-code-along-from-scratch.md`).

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