- What is goldnead/statamic-flow-canvas used for?
- Flow Canvas is a Statamic addon that adds a visual canvas to the control panel for building and managing flow-based content. Editors can arrange connected nodes, map relationships, and store structured data without leaving the CMS. It works with existing content models and templates, making it useful for node-based layouts, diagrams, and reusable flow structures.
- How do I install Flow Canvas in a Laravel Statamic project?
- Install the addon with Composer using goldnead/statamic-flow-canvas, then rebuild your frontend assets and complete the package configuration. The overview describes installation and configuration as simple, but v1.6.1 is frontend-asset sensitive, so clear cached views and stale compiled assets after updating. Pin v1.6.1 in a development branch and verify the canvas in both light and dark modes before promoting to production.
- Which Laravel and Statamic versions does Flow Canvas support?
- The provided context does not list exact Laravel or Statamic version constraints, so check the package composer.json and release notes before upgrading. Because it is a Statamic addon, it runs inside a Laravel application and should be tested against your project's Statamic and Laravel versions. Validate compatibility in a development branch rather than assuming support from the package name alone.
- Does Flow Canvas require Tailwind CSS in my Laravel app?
- In v1.6.1, seven shared UI components no longer depend on host-generated Tailwind utilities for core layout and colour. They now use package-owned fc- classes and scoped style blocks, reducing the need for your Tailwind build to scan those package paths. However, the package is not fully Tailwind-independent because remaining Tailwind utilities exist outside the listed components, so hosts may still need Tailwind for those parts.
- Why did Flow Canvas styles change after upgrading to v1.6.1?
- v1.6.1 changes the styling contract for Canvas, AdderNode, ControlBar, InsertableEdge, NodeCard, NodeLibrary, and PropertiesSection. Those components moved from host-generated Tailwind utilities to fc- classes, scoped style blocks, and CSS variables. If your custom theme overrode Tailwind utility classes on those elements, replace those overrides with rules against the new fc- classes or CSS variables and rebuild your assets.
- How does dark mode work in Flow Canvas?
- The migrated components use dark-mode colours via :global(.dark) and CSS variables instead of hard-coded hex values. Your host application still needs to provide the expected .dark ancestor class for dark mode to apply. After upgrading, inspect all seven affected components in both light and dark modes and confirm that your theme supplies the required ancestor contract.
- Are the fc- CSS classes and CSS variables public API?
- The technical assessment recommends treating the fc- class names and CSS variables as versioned public API. Hosts that override them should rely on documented names and fallback values, because undocumented changes would create upgrade friction. Pin the package version and audit custom CSS overrides before each upgrade to avoid visual regressions.
- Can I use Flow Canvas with a strict Content Security Policy?
- Scoped style blocks can interact with CSP policies, so strict environments may block or restrict them and cause visual regressions. The assessment suggests extracting or nonce-enabling inline and scoped styles if your policy requires it. Test CSP behavior in staging after upgrading to v1.6.1 rather than assuming the package's default styles will pass every policy.
- How should I test the v1.6.1 upgrade before production?
- Pin v1.6.1 in a development branch, run the package's JavaScript test suite including tests/js/plain-css.test.js, and perform visual regression checks on all seven affected components. Validate light and dark modes, confirm CSP behavior for scoped style blocks, and audit any custom CSS overrides that targeted Tailwind utilities. Then promote to staging and production only after those checks pass.
- Does upgrading Flow Canvas require database migrations or PHP changes?
- No database migration or PHP API change is indicated for v1.6.1; the release is primarily a frontend CSS isolation change. The main work is updating the Composer dependency, rebuilding assets, and verifying custom styling overrides against the new fc- classes and CSS variables. Because stale compiled assets, cached views, or CDN-cached CSS can mask the change, clear those during rollout.