Velox Component Manager organizes front-end customizations as self-contained components instead of scattered snippets. Each component keeps its HTML, CSS, optional JavaScript, notes, status and usage information together.

Create a component once, insert it with a shortcode or the Gutenberg Velox Component block, and manage its code from one focused interface.

Component-first workflow

Keep HTML, CSS and optional JavaScript together.
Activate or deactivate the whole component.
Organize components with lightweight Groups.
Duplicate components safely; duplicates start inactive.
Select multiple components and apply common management actions in bulk.
Export one component or all components as portable JSON.
Imported components start inactive so imports cannot immediately change the public site.

Scoped CSS by default

Velox automatically wraps rendered components and scopes their CSS selectors to that wrapper. This reduces accidental style collisions between unrelated customizations.

CSS scoping can be disabled per component when global styles are intentional, such as a CSS-only component targeting theme or page-builder markup.

Conditional static assets

Velox discovers the components needed by a page and combines their code into cache-friendly static assets under the WordPress uploads directory.

One page-level CSS bundle when CSS is required.
One page-level JavaScript bundle when JavaScript is required.
Hashed filenames for cache busting.
Site-wide asset mode for intentionally global customizations.
Graceful inline fallback when static files cannot be written.

Know where components are used

The Used On index shows which content references each component. Velox understands normal shortcodes, the Gutenberg Velox Component block, and Avada Fusion Code content.

Safety checks warn before removing referenced components and identify inactive, trashed or missing component references.

Editing and recovery

WordPress CodeMirror syntax highlighting.
Sandboxed live preview for unsaved HTML, CSS and JavaScript.
WordPress-backed revision history.
Browser-local recovery drafts for unsaved editor work.
Ctrl/Cmd + S support and unsaved-change warnings.

Backup and restore

Create manual backups or schedule daily, weekly or monthly snapshots with configurable retention. Backups cover Velox components and relevant Velox settings.

Restore operations validate the snapshot first, create a pre-restore safety backup, and attempt an automatic rollback if a restore fails after making partial changes.

Export/Import and Backup/Restore serve different purposes: exports are for portability between sites; backups are recovery snapshots for the current Velox installation.

Focused by design

Velox Component Manager does not execute PHP snippets and does not include analytics, tracking pixels, cloud libraries, AI code generation, account systems, telemetry or remote services.

Privacy

Velox Component Manager does not collect, transmit or sell visitor or administrator data. It does not contact Velox Plugins or any other external service during normal operation.

Component code, usage information, settings and backups remain within the WordPress installation. Browser-local recovery drafts are stored in the administrator’s browser local storage and are not transmitted to Velox Plugins.