> ## Documentation Index
> Fetch the complete documentation index at: https://docs.avrxt.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Learning paths for small web projects

> Follow a practical reading sequence to build a personal site, understand an API, launch consent-based email, or contribute a small fix.

Choose a path by its outcome. Each route ends with something you can demonstrate, not a claim that reading several pages makes a project production-ready. Work in a local or preview environment until the result is reviewable.

## Build your first personal website

1. Read [working principles](https://docs.avrxt.dev/notes/working-principles.md) and choose one purpose for the site.
2. Start from the [static-site starter](https://docs.avrxt.dev/notes/starters.md), replacing example content with your own.
3. Review [accessibility](https://docs.avrxt.dev/notes/accessibility.md), including keyboard focus and mobile forms.
4. Follow [static hosting](https://docs.avrxt.dev/technical/static-hosting.md) and inspect a preview before changing DNS.
5. Use the [performance worksheet](https://docs.avrxt.dev/notes/performance-lab.md) to record a baseline.

**Done when:** a direct visit to every public page works, mobile navigation is usable, no private data is in the output, and you know how to restore the previous release.

## Understand a small API

1. Read [API debugging](https://docs.avrxt.dev/notes/api-debugging.md) and inspect a safe read response.
2. Use the [JSON recipes](https://docs.avrxt.dev/notes/command-line.md) to inspect a saved non-sensitive fixture.
3. Implement [pagination](https://docs.avrxt.dev/notes/recipe-pagination.md) in a local example.
4. Compare [caching and rate limits](https://docs.avrxt.dev/notes/recipe-cache.md) and explain their different purposes.
5. Read the [AVRXT API reference](https://docs.avrxt.dev/api-reference/overview.md) as a concrete contract example.

**Done when:** invalid input, an empty result, a timeout, and a rate-limit response all have deliberate behavior.

## Add domain email and a newsletter

1. Separate inbound mail from outbound sending with [Cloudflare routing](https://docs.avrxt.dev/technical/email-routing.md).
2. Read the [Gmail alias change](https://docs.avrxt.dev/technical/gmail-smtp.md) before relying on an older setup.
3. Design [confirmation and retries](https://docs.avrxt.dev/notes/recipe-forms.md) before connecting a sender.
4. Review [email maintenance](https://docs.avrxt.dev/maintaining/email.md) and unsubscribe handling.

**Done when:** a controlled test address can confirm and unsubscribe, repeated confirmation is safe, and you can investigate an ambiguous send without sending duplicates. Do not test against a real audience without authorization.

## Make a first contribution

Pick a project from the [open-source directory](https://docs.avrxt.dev/notes/open-source.md), follow [contribution guidance](https://docs.avrxt.dev/notes/contributing.md), and prepare a [reproducible report](https://docs.avrxt.dev/notes/bug-reports.md). A small documentation improvement is a valid outcome. Follow the target project’s license and review process.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.