GuideCustomize

Assets & Icons

Organize product assets, use local SVG icons, and prevent missing files across root and subpath deployments.

6 min readCustomizeUpdated for Nexus 0.1
On this page 4

What you will learn

  • Add stable public assets.
  • Reuse the icon system.
  • Verify asset paths below a base path.

Public assets

Keep browser-served images, fonts, and documents under public. Group new product assets by purpose instead of mixing them with demo assets.

text
public/brand/
public/images/products/
public/images/avatars/
public/documents/

Base-path-safe references

Next.js basePath does not automatically rewrite arbitrary hard-coded asset strings in every context. Verify public assets in both root and subpath builds, especially CSS backgrounds and manually constructed URLs.

  • Images load at the root URL.
  • Images load below NEXT_BASE_PATH.
  • No mixed-content warning occurs.
  • Meaningful images include alternative text.

Icons

The template uses local SVG React components, keeping stroke size and color under CSS control. Reuse an existing icon before adding another shape.