Skip to content

docs: no longer mention favicon.ico in static #15087

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
benmccann merged 3 commits into from
Dec 24, 2025
Merged

docs: no longer mention favicon.ico in static #15087

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
69efcd8
Update static assets description in project structure
sacrosanctic Dec 23, 2025
94bf9f6
Fix link formatting in project structure documentation
sacrosanctic Dec 23, 2025
6dae53f
Update documentation/docs/10-getting-started/30-project-structure.md
sacrosanctic Dec 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion documentation/docs/10-getting-started/30-project-structure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ If you added [Vitest](https://vitest.dev) when you set up your project, your uni

### static

Any static assets that should be served as-is, like `robots.txt` or `favicon.png`, go in here.
Any static assets that should be served without any alteration to the name — such as `robots.txt` — go in here. It's generally preferable to minimize the number of assets in `static/` and instead `import` them. Using an `import` allows [Vite's built-in handling](images#Vite's-built-in-handling) to give a unique name to an asset based on a hash of its contents so that it can be cached.

### tests

Expand Down
Loading