When using Kuroco as a content management system for your site, there are two locations for storing static files:
- Storing them in the source files (e.g. the static directory in Nuxt.js)
- Storing them in KurocoFiles
We will explain the recommended usage for each option.
Recommended usage for storing files in the source files
- For files (images, CSS, JS, etc.) used in the site design
Recommended usage for storing files in KurocoFiles
- For files that will be frequently updated
- For files with large file sizes (e.g. images over 30MB)
Pros of using KurocoFiles
By storing large files in KurocoFiles, the overall file size of the source files can be reduced. When the source file size is smaller, the Build & Deploy time using GitHub Actions is shortened.
Cons of using KurocoFiles
One disadvantage is that KurocoFiles does not have version control. Therefore, if you upload CSS or JS files to KurocoFiles, those files cannot be version-controlled.
For more detailed usage information, refer to How to correctly use KurocoFiles and KurocoFront to manages images & files.