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.<\/p>\n\n
Create a component once, insert it with a shortcode or the Gutenberg Velox Component block, and manage its code from one focused interface.<\/p>\n\n
Velox automatically wraps rendered components and scopes their CSS selectors to that wrapper. This reduces accidental style collisions between unrelated customizations.<\/p>\n\n
CSS scoping can be disabled per component when global styles are intentional, such as a CSS-only component targeting theme or page-builder markup.<\/p>\n\n
Velox discovers the components needed by a page and combines their code into cache-friendly static assets under the WordPress uploads directory.<\/p>\n\n
The Used On index shows which content references each component. Velox understands normal shortcodes, the Gutenberg Velox Component block, and Avada Fusion Code content.<\/p>\n\n
Safety checks warn before removing referenced components and identify inactive, trashed or missing component references.<\/p>\n\n
Create manual backups or schedule daily, weekly or monthly snapshots with configurable retention. Backups cover Velox components and relevant Velox settings.<\/p>\n\n
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.<\/p>\n\n
Export\/Import and Backup\/Restore serve different purposes: exports are for portability between sites; backups are recovery snapshots for the current Velox installation.<\/p>\n\n
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.<\/p>\n\n
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.<\/p>\n\n
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.<\/p>\n\n\n
\/wp-content\/plugins\/<\/code>.<\/li>\n- Activate Velox Component Manager.<\/li>\n
- Open Velox Components > Add New.<\/li>\n
- Add your HTML, CSS and optional JavaScript, then save the component.<\/li>\n
- Insert the generated shortcode wherever WordPress shortcodes are supported, or use the Velox Component block in Gutenberg.<\/li>\n<\/ol>\n\n
Example shortcode:<\/p>\n\n
[velox_component slug=\"homepage-feature\"]\n<\/code><\/pre>\n\n\n\nDoes Velox Component Manager run PHP snippets?<\/h3><\/dt>\nNo. The plugin is deliberately limited to front-end HTML, CSS and JavaScript. PHP execution has a different security and failure profile and is outside the plugin's purpose.<\/p><\/dd>\n
Why is CSS scoping enabled by default?<\/h3><\/dt>\nScoping helps prevent generic selectors such as .card<\/code>, .title<\/code> or .button<\/code> in one component from changing another component. Disable scoping only when the CSS intentionally needs to target markup outside the component wrapper.<\/p><\/dd>\nWhat HTML can a component render?<\/h3><\/dt>\nRendered component HTML is filtered through WordPress KSES. Standard post markup plus common form and SVG elements are supported. Script\/style blocks and inline event-handler attributes are removed; put styling in the CSS tab and executable behaviour in the JavaScript tab.<\/p><\/dd>\n
Can I use it with Avada or Elementor?<\/h3><\/dt>\nYes. The shortcode is builder-independent and can be used anywhere the builder processes WordPress shortcodes. Avada Fusion Code references are also understood by the Used On index. No dedicated builder integration is required.<\/p><\/dd>\n
Why does Live Preview look different from my real page?<\/h3><\/dt>\nThe preview intentionally renders the component in an isolated sandbox and does not load your theme or page-builder styles. It is designed to verify the component itself. The live page remains authoritative when a component relies on theme-specific CSS.<\/p><\/dd>\n
What is the difference between Export and Backup?<\/h3><\/dt>\nExport creates portable component JSON for moving or sharing components. Backup creates a recovery snapshot of components and relevant Velox settings for the current installation.<\/p><\/dd>\n
What happens if I uninstall the plugin?<\/h3><\/dt>\nVelox preserves components, groups, settings and stored backups by default. This avoids silently destroying custom code simply because the plugin was removed. Disposable scheduled\/runtime state is cleaned up.<\/p><\/dd>\n
Does the plugin send data to Velox Plugins?<\/h3><\/dt>\nNo. Velox Component Manager has no telemetry, tracking or remote-service dependency.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.1<\/h4>\n\n\n- Fixed CodeMirror layout in initially hidden CSS and JavaScript tabs so the gutter and line numbers no longer overlap or clip code text.<\/li>\n
- Routed preview and late-discovered component CSS\/JavaScript through WordPress enqueue APIs.<\/li>\n
- Sanitized rendered component HTML through a WordPress KSES allow list and limited the filesystem fallback notice to Velox admin screens.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial public release.<\/li>\n
- Create reusable front-end components that keep HTML, CSS, optional JavaScript and notes together.<\/li>\n
- Scoped CSS by default with conditional hashed static asset delivery and site-wide asset support.<\/li>\n
- Insert components with shortcodes or the Gutenberg Velox Component block.<\/li>\n
- Track usage across WordPress content, custom fields and Avada Fusion Code.<\/li>\n
- Includes Groups, bulk actions, Live Preview, revisions, recovery drafts, JSON portability and backup\/restore.<\/li>\n
- Includes safety checks for referenced, inactive, trashed and missing components.<\/li>\n<\/ul>","raw_excerpt":"Keep custom HTML, CSS and JavaScript together as reusable, isolated WordPress components.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/364070","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=364070"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/veloxplugins"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=364070"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=364070"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=364070"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=364070"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=364070"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=364070"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}