wheels packages add wheels-basecoat…or manually:
mkdir -p vendor
cp -r packages/basecoat vendor/wheels-basecoat
wheels reloadThe package ships basecoat-css 0.3.11 + basecoat-js + a CSP-safe shim under vendor/wheels-basecoat/assets/. Publish them to your app's public/ directory:
cp -r vendor/wheels-basecoat/assets/basecoat public/assets/basecoatThis is a one-shot operation. If you upgrade the package later (wheels packages update wheels-basecoat), re-run the copy to refresh the bundled CSS+JS.
Why a manual copy? Wheels'
PackageLoaderactivates the helpers automatically, but it doesn't expose the package'sassets/directory at any URL. Publishing topublic/assets/basecoatis the simplest path that works on every host. Most modern frameworks (Rails, Django, Phoenix) use a similar copy-or-symlink pattern.
In app/views/layout.cfm's <head>:
<cfoutput>
#basecoatThemeScript()#
#csrfMetaTags()#
#basecoatIncludes()#
</cfoutput>…and just before </body>:
<cfoutput>#basecoatFlashToasts()#</cfoutput>Drop the controller + view + route from examples/showcase/ into your app to get a live /basecoat-showcase URL. See examples/showcase/README.md for the three-step install.
wheels reloadVisit /wheels/packages/wheels-basecoat to confirm the package is loaded (you'll see the docs page). Visit /basecoat-showcase if you mounted the showcase to see every helper rendered live.
wheels packages update wheels-basecoat
cp -r vendor/wheels-basecoat/assets/basecoat public/assets/basecoat
wheels reloadThe asset copy step refreshes the bundled CSS+JS to match the new package version.
If anything renders unstyled, check:
- The bundled CSS is published —
ls public/assets/basecoat/basecoat.min.cssshould exist. basecoatIncludes()is in your layout's<head>.- Reload the app:
wheels reload. - Check the package loaded:
application.wheels.packagesshould containwheels-basecoat.
For more, see .ai/PITFALLS.md.