Shared files
Runtime logic like profiles, focus behavior, language switching, persistence, and UI interaction should be reused across hosts.
This landing page is plain HTML, but it already runs your ADecksibility widget through the embed adapter. So the message is simple: WordPress stays stable, while the product starts growing beyond WordPress.
Yes, but only in the adapter layer. The shared engine should stay the same. WordPress-specific files handle hooks and settings. Universal files handle embed bootstrapping and host integration.
Runtime logic like profiles, focus behavior, language switching, persistence, and UI interaction should be reused across hosts.
These stay responsible for admin settings, enqueue flow, option loading, and output inside the plugin environment.
These handle asset loading, template mounting, remote config later on, and script-based installation on non-WordPress sites.
It is more than a pretty example. It is a working proof that your widget already has a future beyond the plugin wrapper.
You can now showcase the widget on a normal marketing page without needing WordPress as the host environment.
The page includes links, buttons, form fields, headings, and long-form copy so the widget can be tested on realistic content.
Once the embed contract feels stable, the next layer becomes tenant config, licensing, and a remote dashboard.
Use keyboard navigation, read aloud, visual adjustments, and profile presets on a realistic landing-page flow.
This line updates when the demo action is triggered.
With this page, you already have a cleaner story for investors, clients, or internal planning: ADecksibility is no longer mentally trapped as “only a WordPress plugin”.