It is built for block themes and full site editing, where it reads the presets your theme.json<\/code> defines and resolves its own tokens through them. It also runs on classic themes, but falls back to its own default token values, since there is no theme.json<\/code> to sync with.<\/p><\/dd>\nDoes Blicks replace my theme's design system?<\/h3><\/dt>\nNo. Blicks keeps its own catalogue of token slugs, and their values alias your theme's preset variables where the theme defines them. Where it defines none \u2014 a shadow scale, say \u2014 Blicks supplies its own, so a control is never empty.<\/p><\/dd>\n
Will it slow down my site?<\/h3><\/dt>\nBlicks enqueues one stylesheet, 13,301 bytes gzipped, on requests that render a block. There is no per-block <style><\/code> tag and no per-request CSS generation for token and utility values. Per-instance rules \u2014 pseudo-elements, container queries, keyframes \u2014 are collected and deduplicated into a single block in the footer.<\/p><\/dd>\nWhat happens to my content if I deactivate Blicks?<\/h3><\/dt>\nBlocks save static HTML, so the markup stays in the post. The runtime stylesheet stops loading, so the styling it carries goes with it.<\/p><\/dd>\n
What happens to my data if I delete the plugin?<\/h3><\/dt>\nBy default, nothing is removed \u2014 your tokens, themes, animations and settings survive a delete and reinstall. If you want Blicks to clean up after itself, set On uninstall<\/strong> to \"Delete all Blicks data\" in Blicks \u2192 Settings<\/strong> before deleting the plugin.<\/p><\/dd>\nCan I add my own CSS, JavaScript or PHP through Blicks?<\/h3><\/dt>\nNo. There is no stylesheet field, no script field and no snippet runner. Blicks never evaluates anything you type, and you cannot write a CSS rule, a selector or an at-rule anywhere in it.<\/p>\n\n
Two places do accept typed input. Some controls take a typed value rather than offering a picker \u2014 a length like 800px<\/code>, a transform like translateX(10px)<\/code>, a shape like polygon(0 0, 100% 0, 100% 100%)<\/code>. Each of those is the value of one named property that the control itself chooses; you cannot write the property, a selector or a rule. Every value is validated whole against a closed list of permitted characters and CSS functions before it is used, so a value cannot end its own declaration or start another one. Anything that does not validate is dropped.<\/p>\n\nThe custom animation editor (Blicks \u2192 Design System \u2192 Animations<\/strong>, administrators only) works the same way. Each keyframe step is a form row: you pick a property from a fixed list of animatable properties (opacity, transform, color and similar), and type its value, which is validated exactly as above. You cannot name any other property, write a selector or add an at-rule; Blicks generates the @keyframes<\/code> rule and its name itself.<\/p><\/dd>\nCan I paste in HTML from somewhere else?<\/h3><\/dt>\nYes. Import HTML<\/strong> in the editor's options (\u22ee) menu opens a one-way importer: you paste a block of markup, Blicks maps each element to the closest Blicks block, and inserts the result into the post.<\/p>\n\nIt reads each element's inline style<\/code> attribute only \u2014 not <style><\/code> blocks, not stylesheets, not <script><\/code>. A declaration is kept only where its property matches an existing Blicks control that takes a plain value; it then becomes an ordinary block attribute, validated exactly like any value you would have typed into that control yourself. Everything else \u2014 every property with no matching control, and every structured control that would need reshaping \u2014 is dropped, and the import report names each one so nothing is silently discarded.<\/p>\n\nThe pasted text itself is never stored and never rendered. No pasted CSS reaches the front end unvalidated, and pasted <script><\/code> is parsed as text, never executed.<\/p><\/dd>\nCan I use my own images as backgrounds?<\/h3><\/dt>\nYes, via the media library. Background image URLs are restricted to your own site's uploads or an ordinary http(s)<\/code> address; javascript:<\/code> and data:<\/code> URLs are rejected.<\/p><\/dd>\nDoes Blicks respect reduced motion?<\/h3><\/dt>\nYes. Rules that carry a keyframe animation are emitted inside @media (prefers-reduced-motion: no-preference)<\/code>, so a visitor who has asked for reduced motion never gets them.<\/p><\/dd>\nHow can I contribute?<\/h3><\/dt>\n