Roadmap
-
Create a default Critical CSS configuration
- Add support for a global default Critical CSS entity that applies to all pages when no specific context matches.
- Provide an admin UI to manage and edit the default CSS.
- Ensure fallback priority order:
node:ID → node:bundle → default. - Allow enabling/disabling the default Critical CSS independently.
-
Integrate CodeMirror (or similar) for CSS editing
- Add syntax highlighting for better editing experience.
- Include basic CSS validation/linting in the editor.
- Load editor assets only on relevant forms to maintain performance.
-
Drush commands for Critical CSS export/import
- Create commands to export Critical CSS entities as YAML files.
- Create commands to import YAML definitions back into the site.
- Help support configuration workflows and CI/CD environments.
-
Integrate a Critical CSS generator service (API provider)
- Provide a service interface for generating Critical CSS programmatically.
- Allow integration with external tools or APIs (e.g., Penthouse, Critical PHP wrapper).
- Support both automatic and manual generation per entity or route.
- Allow alternative providers via pluggable service architecture.
Issue fork critical_css_ui-3558157
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
diegodz commentedComment #3
diegodz commentedComment #5
diegodz commented