Use one asset library across apps and environments
Publish shared logos, fonts, documents, media and build assets once, then reference them from multiple apps, previews, CMS projects and production environments.
The problem
Shared assets often end up copied into each app, CMS, preview environment or deployment folder. Over time, every place can drift into a slightly different version of the same file.
That makes brand updates, legal documents, shared media and design-system files harder to publish consistently across environments.
Duplicate logos and fonts
Different files in staging and production
CMS and app assets managed separately
Manual updates across multiple projects
No shared release URL for asset sets
Solution
Smooth Bundle gives the shared asset set its own project. Apps and environments consume CDN URLs from that project instead of each carrying private copies of the same files.
1
Define the shared asset project
Put shared files in a folder structure that matches how apps will consume them. Use a release project when environments need pinned versions.
{
"project": "Shared Brand Assets",
"projectSlug": "shared-brand-assets",
"type": "versioned",
"version": "2.3.0",
"sources": [
"./brand/**/*.{svg,png,webp,avif}",
"./fonts/**/*.{woff2,woff}",
"./docs/**/*.{pdf,json}"
],
"replacePath": {
"/brand/": "/brand/",
"/fonts/": "/fonts/",
"/docs/": "/docs/"
}
}2
Publish the shared release
Run the same publish flow locally or from CI. Publishing the version also updates the project's latest pointer.
npm run build
sbundle create-version
sbundle push
sbundle publish-version3
Reference the same assets everywhere
Production can pin a version. Previews, internal apps or CMS templates can use latest when they should follow the active shared release.
<link
rel="preload"
href="https://cdn.smoothbundle.com/acme/shared-brand-assets/2.3.0/fonts/inter.woff2"
as="font"
/>
<img
src="https://cdn.smoothbundle.com/acme/shared-brand-assets/latest/brand/logo.svg"
alt="Acme"
/>Result
Multiple apps and environments can reference the same published asset project. Teams update the asset set once, then choose whether each consumer follows latest or stays pinned to an explicit version.