Replies: 1 comment
-
Nope. You should only put content-managed assets in your asset containers. Depending on your build process, site assets should either go in If Vite isn't picking up your site assets maybe you need to configure it to look in the right place? Or make sure you are using the Vite tag. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Short Version:
Are you guys creating an assets container for your site-wide resources (logos, backgrounds, icons) to link to from templates?
Long Version:
With the last CMS I worked with (this was MANY years ago), the equivalent to Assets was generally used only by content authors for article content. Resources for the site itself would go elsewhere in a regular directory, inaccessible from the control panel UI. I started building my first real Statamic site assuming that arrangement but keep finding little pain points (such as Vite not picking them up). I don't actually feel all that strongly about it either way, but I'm curious if there are community norms for a thing like this.
Beta Was this translation helpful? Give feedback.
All reactions