Test

.env.example

@@ -4,5 +4,5 @@ PUBLIC_CONTENTSTACK_API_KEY=your_api_key_here
 PUBLIC_CONTENTSTACK_DELIVERY_TOKEN=your_delivery_token_here
 PUBLIC_CONTENTSTACK_PREVIEW_TOKEN=your_preview_token_here
 PUBLIC_CONTENTSTACK_ENVIRONMENT=preview
-PUBLIC_CONTENTSTACK_REGION=EU # Options: EU or NA
+PUBLIC_CONTENTSTACK_REGION=EU # Options: NA, EU, AU, AZURE-NA, AZURE-EU, GCP-NA, GCP-EU
 PUBLIC_CONTENTSTACK_PREVIEW=true # Set to true to enable preview

.github/workflows/sca-scan.yml

@@ -5,6 +5,9 @@ on:
 jobs:
   security-sca:
     runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: write
     steps:
       - uses: actions/checkout@master
       - name: Run Snyk to check for vulnerabilities

README.md

@@ -1,12 +1,12 @@
-# Contentstack Kickstart: Astro SSR
+# Contentstack Kickstart: Astro
 
 Contentstack Kickstarts are the minimum amount of code needed to connect to Contentstack.
 This kickstart covers the following items:
 
 - SDK initialization
 - Live preview and Visual building setup
 
-> This example has Contentstack Live preview set up SSR mode turnt on. Which means Contentstack adds query parameters to the URL which we grab in the code and give to the Live Preview SDK intance. Contentstack refreshes the browser on content edit each time.
+> This example uses Astro's default static output and runs Contentstack Live Preview in client-side (CSR) mode. Pages are rendered at build time with published content; inside the Visual Builder the Live Preview SDK re-fetches the entry in the browser and re-renders the page on every edit — no server and no iframe refresh needed.
 
 More details about this codebase can be found on the [Contentstack docs](https://www.contentstack.com/docs/developers).
 
@@ -75,6 +75,19 @@ PUBLIC_CONTENTSTACK_ENVIRONMENT=preview
 PUBLIC_CONTENTSTACK_PREVIEW=true
 ```
 
+### How live preview updates work
+
+Live preview runs in client-side (CSR) mode: the Live Preview SDK is initialized with `ssr: false`, changes arrive in the browser via postMessage, and the page re-fetches the entry with the Delivery SDK and re-renders client-side — no iframe refresh. See `src/lib/renderPage.ts` for the client-side renderer.
+
+### Timeline support
+
+[Timeline](https://www.contentstack.com/docs/content-managers/timeline/preview-content-across-a-timeline) (previewing your site as it will look at a future date, with scheduled Releases applied) works out of the box:
+
+- Timeline loads the site with `preview_timestamp` and `release_id` query params. The Delivery SDK picks these up automatically and sends them as headers to the Preview API, and `syncPreviewParams` in `src/lib/contentstack.ts` keeps them applied on every client-side re-fetch.
+- Timeline's compare view (diff highlighting) relies on the `data-cslp` edit tags, which the client-side renderer preserves.
+
+To use it, enable Timeline for your stack and schedule content with Releases. No code changes needed.
+
 ## Turn on Live Preview
 
 Go to Settings > Live Preview. Click enable and select the `Preview` environment in the drop down. Hit save.
@@ -102,3 +115,43 @@ Go to `http://localhost:4321`.
 Go to Entries and select the only entry in the list.
 In the sidebar, click on the live preview icon.
 Or, see your entry in the visual builder
+
+## Regions and endpoint configuration
+
+Set `PUBLIC_CONTENTSTACK_REGION` to the value matching your Contentstack account region:
+
+| Region | Value |
+|---|---|
+| North America (default) | `NA` or `US` |
+| Europe | `EU` |
+| Australia | `AU` |
+| Azure North America | `AZURE-NA` |
+| Azure Europe | `AZURE-EU` |
+| GCP North America | `GCP-NA` |
+| GCP Europe | `GCP-EU` |
+
+The app uses `getContentstackEndpoint` from `@contentstack/utils` to resolve the correct API hostnames for your region automatically. The following endpoint keys are resolved:
+
+| Key | NA value |
+|---|---|
+| `contentDelivery` | `cdn.contentstack.io` |
+| `preview` | `rest-preview.contentstack.com` |
+| `application` | `app.contentstack.com` |
+| `graphqlDelivery` | `graphql.contentstack.com` |
+| `graphqlPreview` | `graphql-preview.contentstack.com` |
+| `images` | `images.contentstack.io` |
+| `assets` | `assets.contentstack.io` |
+| `contentManagement` | `api.contentstack.io` |
+| `auth` | `auth.contentstack.io` |
+
+### Custom or dedicated environments
+
+If you are on a dedicated or private cloud Contentstack instance, you can override the resolved endpoints via environment variables:
+
+```
+PUBLIC_CONTENTSTACK_CONTENT_DELIVERY=your-custom-cdn.example.com
+PUBLIC_CONTENTSTACK_PREVIEW_HOST=your-custom-preview.example.com
+PUBLIC_CONTENTSTACK_CONTENT_APPLICATION=your-custom-app.example.com
+```
+
+These override values take precedence over the region-resolved endpoints.

astro.config.mjs

@@ -1,16 +1,10 @@
 // @ts-check
 import { defineConfig } from "astro/config";
 import tailwindcss from "@tailwindcss/vite";
-import node from "@astrojs/node";
 
 // https://astro.build/config
 export default defineConfig({
-  output: "server",
-  adapter: node({
-    mode: "standalone"
-  }),
   vite: {
-    // @ts-ignore - tailwindcss plugin type compatibility
     plugins: [tailwindcss()],
     resolve: {
       extensions: ['.js', '.mjs', '.ts', '.jsx', '.tsx', '.json'],