docs: add clarification for assets/static

[fry69]

This adds a short clarification how imported assets vs. static files get handled now with Vite to the existing documentation for static files.

[CAYdenberg]

I tried this out based on the issue mentioned in #3482 and it didn't seem to work. A font referenced from a CSS url() wasn't found by Vite when running deno task dev, but it did work when running deno task build. Maybe I'm doing something wrong.

[fry69]

@CAYdenberg This works for me with deno task dev and in a production build (using the demo app with Tailwind enabled):

/* assets/styles.css */
@import "tailwindcss";

@font-face {
  font-family: "Roboto";
  src: url("/Roboto-Regular.ttf") format("truetype");
  font-weight: normal;
  font-style: normal;
}

body {
  font-family: "Roboto", sans-serif;
}

The Roboto-Regular.ttf is inside static/. I can turn the font on and off in the browser inspector.

[CAYdenberg]

I think my confusion stems from:

Files imported in code (CSS, fonts, icons, etc.) → Place outside static/

In this case though, the fonts themselves (not the CSS referring to the fonts) should be in static

[fry69]

@CAYdenberg Should be fixed now

[CAYdenberg]

This LGTM (but I'm not a real reviewer).

🚀