WCH Documentation
- 301 Redirects The 301 Redirects page shows every permanent redirect set up for your site in one place and lets you download the full list as a CSV or JSON file for audits, backups, or moving them to your production host.
- AWS Production Deployment A recommended AWS setup for hosting a WCH project: a private S3 bucket receives the WCH archive, CodePipeline or Lambda extracts it, and CloudFront serves the site.
- AWS S3 Authentication An AWS S3 destination can authenticate to your bucket three ways: Assume Role, Resource Policy, or Access Key. This page explains each one, what to set up on the AWS side, and how to fill in the destination in WCH.
- Azure: Basic Implementation Set up an Azure Storage container that receives the WCH archive, choose how WCH authenticates to it, and unpack the zip with an Azure Function.
- GitHub: Basic Implementation Connect a GitHub repository as a destination and WCH commits your published site to it. Every publish becomes one commit and one tag, so your repository history doubles as a publish history.
- Pagination Webflow's CMS pagination and Load more rely on Webflow hosting, so they stop working on a WCH-hosted site. Use Slater Data for a client-side list with load more, search, and filters, or use WCH's legacy static pagination to generate one page per paginated state.
- Publishing modes Publishing mode controls how WCH finds the pages on your site when you publish. Most sites use Sitemap and never need to change it, but two other modes give you more control when you work with Webflow CMS content.
- Removing Dead Files During an S3 Publish Update a static website in S3 without temporarily breaking pages, while safely removing files that are no longer part of the latest WCH publish.
- Search Webflow's built-in site search needs Webflow hosting, so it stops working on a WCH-hosted site. Use Slater global site search instead: one search box across every CMS collection and static page, wired up with attributes in the Webflow Designer.
- Steps to Publishing in WCH Publishing takes your Webflow site, rebuilds it inside WCH, and sends the finished files to the hosting you control.
- Substitutions Substitutions find a piece of text and replace it with different text every time your project publishes. Use them to swap staging URLs for production URLs, fix a recurring typo, or update a brand name across your whole site at once.
- WCH Go-Live Checklist A practical go-live checklist covering staging review, production setup, SEO, redirects, DNS cutover, and post-launch validation. Use it to catch common migration issues before they become production problems.
- WCH Publishing Publishing turns your Webflow site into a static website that WCH hosts on a staging URL and delivers to your own hosting, such as an S3 bucket, an Azure container, or a GitHub repository.
- Webhooks Webhooks let a publish in Webflow start a publish in WCH automatically, so you never have to click Publish twice. WCH has two kinds: publishing webhooks for whole-site publishes, and CMS webhooks for single collection item changes.
