@exdst-sitecore-content-sdk/astro 1.0.1 → 1.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +3 -3
  2. package/package.json +2 -2
  3. package/src/editing/utils.ts +1 -1
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Sitecore Content SDK for Astro
2
2
 
3
- `@exdst-sitecore-content-sdk/astro` provides Astro components and integration for the [Sitecore Content SDK](https://doc.sitecore.com/xmc/en/developers/content-sdk/index.html), letting you build SitecoreAI / XM Cloud websites with [Astro](https://astro.build/). It follows the same patterns as the official Next.js Content SDK and supports running Astro locally as a rendering host with metadata editing mode for the SitecoreAI Pages editor.
3
+ `@exdst-sitecore-content-sdk/astro` provides Astro components and integration for the [Sitecore Content SDK](https://doc.sitecore.com/xmc/en/developers/content-sdk/index.html), letting you build SitecoreAI(XM Cloud) websites with [Astro](https://astro.build/). It follows the same patterns as the official Next.js Content SDK and supports running Astro locally as a rendering host with metadata editing mode for the SitecoreAI Pages editor.
4
4
 
5
5
  ## Installation
6
6
 
@@ -16,7 +16,7 @@ npx @exdst-sitecore-content-sdk/create-astro@latest
16
16
 
17
17
  ## Why Astro
18
18
 
19
- Astro renders to HTML by default and only hydrates the islands that actually need JavaScript. Measured against the same demo on Next.js with the Content SDK, the Astro build delivers **+30 Lighthouse points (mobile)**, **3.2s faster LCP**, and **858 ms less main-thread blocking** — read the [case study](https://exdst.com/case-studies/sitecore-astro-sdk).
19
+ Astro renders to HTML by default and only hydrates the islands that actually need JavaScript. Measured against the same demo on Next.js with the Content SDK, the Astro build delivers higher Lighthouse scores on mobile, faster LCP, and less main-thread blocking — read the [case study](https://exdst.com/case-studies/sitecore-astro-sdk).
20
20
 
21
21
  ## Learn more
22
22
 
@@ -25,4 +25,4 @@ Astro renders to HTML by default and only hydrates the islands that actually nee
25
25
  * Repository root: [jss-astro-public](../../../README.md)
26
26
  * Initializer: [`@exdst-sitecore-content-sdk/create-astro`](../create-astro-content-sdk-app/)
27
27
 
28
- Sponsored by [EXDST](https://exdst.com/)
28
+ Made by [EXDST](https://exdst.com/)
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@exdst-sitecore-content-sdk/astro",
3
- "version": "1.0.1",
4
- "description": "Astro Content SDK for Sitecore AI (XM Cloud)",
3
+ "version": "1.0.2",
4
+ "description": "Astro Content SDK for SitecoreAI(XM Cloud)",
5
5
  "keywords": [
6
6
  "sitecore",
7
7
  "astro",
package/src/editing/utils.ts CHANGED
@@ -291,7 +291,7 @@ export const isDesignLibraryPreviewData = (
291
291
  * 1. `config.sitecoreInternalEditingHostUrl` (explicitly set in config)
292
292
  * 2. Environment variable `SITECORE_INTERNAL_EDITING_HOST_URL`
293
293
  * 3. Fallbacks:
294
- * - For XM Cloud deployments → `'http://localhost:3000'`
294
+ * - For SitecoreAI(XM Cloud) deployments → `'http://localhost:3000'`
295
295
  * - For all other cases → use the request `Host` header
296
296
  * Note we use https protocol on Vercel due to serverless function architecture.
297
297
  * In all other scenarios, including localhost (with or without a proxy e.g. ngrok)