caramelo-astro-adaptation

Adapt an Astro static build for WordPress release packaging by generating a Caramelo-ready release with manifest.json, HTML entry mapping, and proper _astro asset handling. This enforces Caramelo's strict release contract boundaries while avoiding SSR or runtime dependencies inside WordPress.

Manifest.json entry mapping when converting Astro sites to WordPress is the process of linking public URLs like index or campanha/verao to specific HTML entries. This creates a structured manifest that Caramelo uses to route and serve the adapted static build correctly.

No, you cannot use server-side rendering with Astro builds for Caramelo WordPress releases. The adaptation enforces strict static build boundaries and avoids SSR or runtime dependencies inside WordPress, ensuring only static assets and HTML entries are packaged.

Package an Astro site into a ZIP release for Caramelo import by running the adaptation workflow on your Astro source project. This generates the required manifest.json, applies page-to-entry URL mapping, and bundles the _astro assets into a Caramelo-ready release package.

The best way to handle _astro assets when adapting Astro builds for Caramelo is to enforce a clean asset strategy that maintains strict separation between Astro source-project changes and WordPress-runtime changes. This ensures assets are correctly packaged and mapped in the release.