Releases: Daiosity/Lenviqa
Releases · Daiosity/Lenviqa
Release list
Lenviqa v0.3.0 - Reliability Beta
Lenviqa v0.3.0 is a reliability and release-discipline update for the validated beta core. It does not broaden the product scope.
Improvements
- Clear API configuration errors instead of unresolved starter placeholders
- 15-second request timeouts instead of indefinite loading states
- Aligned failure behavior across the Vite app, exported starter, and lite frontend
- Reusable PHP, metadata, JSON, and starter-parity validation
- GitHub Actions checks for the frontend build and plugin ZIP
- Refreshed frontend dependencies with zero npm audit findings at release time
- Correct project, author, version, and Update URI metadata
Validation
- Route scenarios: passed
- Gutenberg scenarios: passed
- Preview guardrails: passed
- Package and install/runtime validation: passed
- Public GitHub Actions build: passed
The beta still does not promise universal Gutenberg/theme fidelity, WooCommerce, ACF, Elementor, third-party blocks, or WordPress-JS-dependent interactive blocks.
See docs/release-notes-v0.3.0.md and docs/beta-scope.md for the full boundary.
Lenviqa v0.2.0 - Beta Core
Lenviqa is a WordPress plugin and starter frontend setup for developers who want WordPress as the CMS and React as the public frontend.
This v0.2.0 release is the first public beta-core release. The focus is a smaller, validated bridge promise that developers can evaluate honestly.
What is working
- Route resolution for home, standard pages, nested hierarchical pages, standard posts, unresolved routes, and basic path normalization
- Gutenberg-aware rendering for common layout patterns including nested groups, columns, media-text, cover sections, galleries, and button groups
- Preview-flow foundations with valid preview token resolution and honest invalid or expired preview failure
- Packaging, install, and runtime confidence checks for ZIP structure, activation defaults, starter export hook presence, deactivation, and uninstall cleanup
Beta-safe scope
See the beta scope document for the validated boundary:
Intentionally out of scope
- WooCommerce as a solved core feature
- ACF integration
- Elementor compatibility
- Theme-specific CSS fidelity
- Pixel-perfect Gutenberg parity with the active WordPress theme
- Third-party or custom block ecosystem support
- Interactive blocks that require WordPress frontend JS
Feedback wanted
Useful beta feedback includes:
- route-resolution failures on normal WordPress content
- preview-flow failures or confusing preview behavior
- Gutenberg layouts that break structurally instead of failing safely
- install, package, or runtime issues on real WordPress environments
- onboarding friction where the validated path is still unclear