Astro site, static or SSR
Content in Markdown or MDX inside the repository. Ideal for sites that change weekly, not hourly.
Content sites rebuilt on Astro — lighter pages, fewer moving parts, an editing experience your team chooses. Everything that isn’t simply content gets assessed on its own terms.
Content in Markdown or MDX inside the repository. Ideal for sites that change weekly, not hourly.
Editors keep a visual editing interface; the site is rendered by Astro. CMS chosen to fit your team.
When the “site” is really an application — accounts, transactions, workflows — it’s rebuilt as one, often beyond Astro.
These features carry business logic and data. Each needs its own functionality assessment before any outcome is recommended.
Typical outcomes for common plugins. Your site’s actual list is reviewed one by one before anything is recommended.
| WORDPRESS PLUGIN | AREA | IN ASTRO | PARITY |
|---|---|---|---|
| Yoast SEO / Rank Math | SEO | Metadata in content front-matter, sitemap and schema generated at build | FULL |
| Advanced Custom Fields | Content model | Typed content collections with validated schemas | FULL |
| Redirection | URLs | Redirect map maintained at the host or in config | FULL |
| Contact Form 7 / Gravity Forms | Forms | Rebuilt against a chosen form service; entries stored outside the site | PARTIAL |
| WPML / Polylang | Languages | Built-in i18n routing; translation workflow chosen per project | PARTIAL |
| Elementor / page builders | Layout | Layouts rebuilt as components; editors lose free-form drag-and-drop | REBUILD |
| Comments | Community | Third-party service or removed by agreement | PARTIAL |
| WooCommerce | Commerce | Separate assessment — kept, replaced by a platform, or rebuilt via php2modern | ASSESS |
| Memberships / bookings | Accounts | Separate assessment — needs a backend, not a static site | ASSESS |
Search visibility is protected by planning, not hoped for. Each item below is scoped and checked during the project.
With outcome B they get a headless CMS editor instead. With outcome A, editing happens in files or a Git-based editor. We choose together.
A conversation, then an Assessment of your site and plugins. Any migration follows as a separate Proposal and Contract.
A public URL and a list of plugins is enough for a first conversation. No admin access needed.
Review my WordPress siteAdd to your home screen
wordpress2astro: Open this site from your home screen, full screen, like an app.
Tap the Share button, then “Add to Home Screen”.
Open your browser menu, then “Add to Home screen” or “Install app”.