+++
title = "[TRIAGE] Cloudflare Pages SPA routing — 404 fallback config for client-side Yew router"
priority = 8
status = "todo"
ticket_type = "task"
dependencies = ["25c413"]
+++

<context>
This is a triage decision ticket. It must be resolved before dependent implementation tickets can proceed.
</context>

<question>
Cloudflare Pages SPA routing: Yew uses client-side routing. A direct URL to `/browse` or `/quotes/:id` will 404 on Cloudflare Pages unless a fallback is configured.
</question>

<options>
1. **\_redirects file** — add a `_redirects` file to the `dist/` directory: `/* /index.html 200`. Cloudflare Pages supports this.
2. **\_headers file** — configure headers; does not fix routing by itself.
3. **Cloudflare Pages custom 404 page** — set `404.html` to be the same as `index.html`. Less clean.
</options>

<resolution>
1. Research the options above and choose the best approach for this project.
2. Add a `_redirects` file (or equivalent) to the Trunk build output. Update ticket ae886f (Pages resource) and ticket dc3d2b (Trunk.toml) if the file needs to be included in the build.
3. Mark this ticket done with a note on the chosen approach in the body or a comment.
</resolution>

<commit>
`chore(quotesdb): resolve triage — cloudflare-pages-spa-routing-404-fallback-config-for-clients`
</commit>