# blogwright > Full operations for a blog site on AWS: S3 + CloudFront hosting with builds in a Lambda MicroVM, PR previews, GitHub-OIDC CI deploys, and standard.site (AT Protocol) publishing. One CLI, no CloudFormation, no Terraform, no CDK. Every documentation page is available as Markdown by appending `.md` to its URL path (e.g. https://blogwright.iamstan.dev/reference/cli.md). ## Getting started - [Introduction](https://blogwright.iamstan.dev/getting-started/introduction.md): What blogwright is, who it's for, and how a deploy actually works. - [Installation](https://blogwright.iamstan.dev/getting-started/installation.md): Install blogwright as a dev dependency and point it at your AWS credentials. - [Quickstart](https://blogwright.iamstan.dev/getting-started/quickstart.md): From an empty AWS account to a live site in three commands. ## Guides - [Deploying](https://blogwright.iamstan.dev/guides/deploying.md): What happens between `blogwright deploy` and your changes going live, step by step. - [Environments & configuration files](https://blogwright.iamstan.dev/guides/environments.md): How blogwright selects an environment, resolves its JSONC config file, isolates AWS resources per environment, and tags everything it creates. - [Custom domains](https://blogwright.iamstan.dev/guides/custom-domains.md): Serve the site from your own domain with a DNS-validated ACM certificate and a CloudFront alias — your DNS can stay wherever it is hosted. - [CI deploys with GitHub OIDC](https://blogwright.iamstan.dev/guides/ci-github-oidc.md): Let GitHub Actions deploy your site with a short-lived OIDC role — no AWS keys stored anywhere. - [PR previews](https://blogwright.iamstan.dev/guides/pr-previews.md): Serve every pull request at its own URL from one shared CloudFront distribution — deploy on open, destroy on close. - [Publishing to standard.site](https://blogwright.iamstan.dev/guides/publishing-standard-site.md): Mirror your posts to your own AT Protocol PDS as standard.site records, reconciled automatically after every production deploy. - [Beyond Astro: SPAs & monorepos](https://blogwright.iamstan.dev/guides/non-astro-sites.md): Deploy any static site that builds via pnpm build — SvelteKit or Vite SPAs, monorepo subdirectories, and sites with pre-built artifacts. - [Day-2 operations](https://blogwright.iamstan.dev/guides/operations.md): Inspect drift, audit deploy history, read build logs, roll back, and tear the stack down. - [Troubleshooting](https://blogwright.iamstan.dev/guides/troubleshooting.md): Symptom, cause, and fix for the errors and warnings blogwright actually raises. ## Reference - [CLI reference](https://blogwright.iamstan.dev/reference/cli.md): Every blogwright command, positional, and flag — synopsis, behavior, output modes, and exit codes. - [Configuration reference](https://blogwright.iamstan.dev/reference/configuration.md): Every config key blogwright reads — types, defaults, validation rules, and what each one controls. - [Architecture](https://blogwright.iamstan.dev/reference/architecture.md): How blogwright models, provisions, and operates your AWS infrastructure under the hood. - [rkey subpath export](https://blogwright.iamstan.dev/reference/rkey.md): Deterministic, URL-derived AT Protocol record keys for standard.site documents, exported as blogwright/rkey so your site and the sync share one implementation.