static-files-assets

Organize static files by placing component-bundled assets in src/assets and publicly served resources in public/assets. This separation simplifies asset management and improves build performance by distinguishing optimized imports from direct URL references.

Bundle assets with Vite when they are imported directly in components for optimization, and serve them publicly without optimization for large collections or unchanged resources. This approach ensures consistent directory structures and faster builds.

Apply naming conventions using prefixes like ic- for icons and separate directories for logos and images. Following these guidelines ensures clear references and prescribes standards for image optimization across your project.

Import small bundled assets from src/assets when used directly in code, and use public URL references for large collections in public/assets. This distinction enforces conventions for asset structure and reference usage.

Yes, it categorizes icons under public/assets/icons and images under public/assets/images while importing small bundled assets from src/assets. This supports both bundled component assets and large publicly served collections.