Guides

Overall, I think the Kit docs are very nice, and I really appreciate that they are correct and factual and explaining.
In this particular issue, my feeling is: "Why do I have to go to Advanced > Hooks > handleFetch in order to figure this out?".
A) This shouldn't be under "Advanced", since this is basic information that is required to produce a functioning result.
B) If you don't know what the solution is, then you don't know that you should be looking at "Hooks".
Ideally, it would be good to have more docs that are complete step-by-step guides that include everything needed to achieve a certain result. But I know that this takes much more work to write and maintain.
As an example, the Django docs organization is often cited as a best-in-class example of this: https://docs.djangoproject.com/en/5.2/#how-the-documentation-is-organized

Btw, I made a mistake in my previous comment, it seems like ORIGIN is also needed in my case. Thanks for the info on that!

Originally posted by @thnee in #8314

I think the comment referenced has a point, we could do with more guides. An example of this is https://docs.astro.build/en/getting-started/ that is more focused on "how do I do X" rather than "we have X Y Z". I think there's room for both rather than one or the other but we are lacking in guides

Start by reviewing the existing Advanced > Hooks > handleFetch documentation and the referenced SvelteKit issue comment. Compare the current organization with Django's documentation structure and Astro's getting-started guides; done requires an agreed scope and new step-by-step guides for selected workflows, but this issue does not identify which workflows or files to change.