Ship on Launch
Take a Contentstack site from a manual deploy to a CI-driven Launch project with edge routing, edge functions and a cache strategy you can reason about.
- Step 1: GuideLevel: Advanced
Deploy from CI with the Launch CLI, REST API and deploy hooks
Trigger, monitor and roll back Contentstack Launch deployments from GitHub Actions with deploy hooks, the Launch CLI plugin and the Launch REST API.
Checkpoint: Your project deploys from CI using the Launch CLI or a deploy hook.
- Step 2: GuideLevel: Intermediate
Edge functions, redirects and caching on Launch
Control what happens to a request on Launch before it reaches your app. Redirects, rewrites, edge functions, CDN caching, revalidation and logs.
Checkpoint: Redirects, an edge function and cache revalidation run on your project.
- Step 3: BlogLevel: Intermediate
Revalidate, prime or redeploy? Picking the right cache lever on Launch
Launch gives you three ways to get fresh pages to visitors. Here is what each one costs, when to use it, and a decision flow for picking one.
Checkpoint: You can pick revalidation, priming or a redeploy for a given content change.
Path complete
Browse all learning paths