Blicks

FAQ

Does Blicks work with my theme?

It’s built for block themes and full site editing, where it reads your theme.json directly. It also runs on classic themes, but falls back to its own default token values since there’s no theme.json to read.

What happens to my data if I delete the plugin?

By default, nothing is removed — your tokens, themes, animations, and settings survive a delete and reinstall. If you want Blicks to clean up after itself, set On uninstall to “Delete all Blicks data” in Blicks → Settings before deleting the plugin.

Can I add my own CSS, JavaScript, or PHP through Blicks?

No. 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.

Two places do accept typed input, and both are described below.

Some controls take a typed value rather than offering a picker — a length like 800px, a transform like translateX(10px), a shape like polygon(0 0, 100% 0, 100% 100%). 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.

The custom animation editor (Blicks → Design System → Animations, 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 rule and its name itself.

Can I paste in HTML from somewhere else?

Yes. Import HTML in the editor’s options (⋮) 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.

It reads each element’s inline style attribute only — not <style> blocks, not stylesheets, not <script>. 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 — every property with no matching control, and every structured control that would need reshaping — is dropped, and the import report names each one so nothing is silently discarded.

The pasted text itself is never stored and never rendered. No pasted CSS reaches the front end unvalidated, and pasted <script> is parsed as text, never executed.

Does Blicks let me use my own images as backgrounds?

Yes, via the media library. Background image URLs are restricted to your own site’s uploads or an ordinary http(s) address; javascript: and data: URLs are rejected.