# Maintenance

> The work that remains once your website runs.

There are no servers or runtimes to maintain. Some work remains, so plan for it:

- **Review and merge dependency update pull requests.** Fixes to goodnight-web arrive in your repository as pull requests from [Dependabot](https://goodnight-web.dev/docs/glossary.md#dependabot). They are not merged automatically; you review and merge them.
- **Update the website's own dependencies**, such as Astro and Tailwind CSS. These also arrive as Dependabot pull requests.
- **Keep up with Cloudflare changes**, such as a new `compatibility_date` or a change to a free plan limit.
- **Keep your repository private.** Also keep your Worker secrets safe.
- **Have a professional review your privacy policy** before you publish it.

You do not write server code. The contact API and the admin screen come from an npm package that you do not edit, so its fixes reach you as the update pull requests above.

## Related pages

- [Distribution and updates](https://goodnight-web.dev/docs/distribution.md): what comes from the npm package, how Dependabot opens update pull requests, and how to tell an official update from other changes.
- [Database](https://goodnight-web.dev/docs/database.md): how schema changes reach your website and are applied before the new code goes live.
- [Security model](https://goodnight-web.dev/docs/security.md): what protects the admin screen and the contact form, and what goodnight-web does not protect against.
- [Privacy notes](https://goodnight-web.dev/docs/privacy.md): what the privacy policy template covers.