Deployment

CoolAdmin runs on static hosting. Its frontend examples need your backend for authentication, persistence, payments, or email.

Prepare a deployment

If you edit source, use Node >=22.12 and run npm ci then npm run check. If you use the ready-built release, no Node runtime is required.

Publish root HTML plus css/, js/, vendor/, fonts/, images/, media/, required screenshots, and license notices. Exclude .git, node_modules, credentials, test fixtures, and build tooling from the public directory. The template uses relative URLs and works under a subdirectory when you keep its folder structure.

Built files can be uploaded to Cloudflare Pages, GitHub Pages, Netlify, Vercel, object storage behind a static-serving CDN, or conventional hosting. Configure each host to serve actual files rather than replacing missing pages with the dashboard homepage.

Existing Colorlib destinations

• Demo: R2 colorlib-preview, prefix theme/cooladmin/.
• Download ZIP: R2 colorlib-downloads, key theme/cooladmin.zip.
• This website/docs: Cloudflare Pages project cooladmin-colorlib from the separate landing-page source.

The publication and rollback checklist is in the repository deployment guide. Shared buckets must be updated only within the CoolAdmin prefix/key.

Caching and external assets

Refresh HTML and unversioned JS/CSS when deploying. Versioned vendor filenames can use longer caches; keep the old files until cached old HTML expires. CDN or Worker caching may override object metadata, so invalidate only affected URLs and verify normal requests after deployment.

Bootstrap, Chart.js, FullCalendar, Font Awesome, and Poppins are local assets. Inter loads from rsms.me, Leaflet CSS/JS from unpkg.com on the map page, and map tiles from external services. Self-host or replace these dependencies if your deployment must work offline. Preserve upstream licenses.

Verify and recover

Open all affected pages on desktop/mobile. Check console/network errors, calendar views, chart rendering and repeated refresh, command palette, accent themes, and mobile navigation. Verify the download archive has the release version and contains no secrets or Node modules.

Keep a backup of the current runtime and archive before publication. Restore the saved files or redeploy the prior Pages build if verification fails, invalidate the affected URLs, and check the restored version.