Staying Current: Updates and Long-Term Support
How AstroWEBTheme separates reusable core from project files so updates stay safe, what astroweb update checks before changing anything, and what Pro and Agency licenses include.
A theme is only as useful as its upgrade path. If every customization makes future updates risky, the free-to-start promise stops meaning much. AstroWEBTheme is built around a clear boundary between reusable core and project-owned files specifically to keep updating safe.
Core versus project files
core/ contains reusable theme internals — layouts, generators, build tooling — that astroweb update can refresh. Project-specific content, configuration, styling, and components live under src/site/, src/components/, and src/layouts/, which updates are designed to leave alone. Theme Update & Core Boundaries documents exactly which paths fall into each zone.
A plan before a change
astroweb update defaults to a dry-run: it shows what a theme-core update would change before anything is written. Running astroweb update --apply --latest or --apply --tag <tag> only after reviewing that plan keeps upgrades deliberate rather than automatic.
What the license periods cover
Pro and Agency are one-time purchases for the version released at the time of purchase. During the license period, updates and installation support are included; after it lapses, the purchased version keeps working, and renewing restores ongoing updates and support rather than being required to keep the site running.
Monitoring beyond the theme itself
Keeping a production Astro website current is not only about theme updates — it also means watching Cloudflare configuration, dependency security advisories, and deployment health over time. That ongoing work is outside what a license covers on its own.
Want someone to own monitoring, upgrades, and small changes month to month? NViewsWEB offers Astro Website Care plans for exactly that.
