Overview page

docs/guides/cdn-links-list.md

@@ -55,11 +55,11 @@ The `[version_number]` specifies `major.minor` version of the package, for examp
 Separate skin files are available in v6.0 and earlier.
 Starting from v7.0, all skins are included in `dhtmlxscheduler.css` and selected via `scheduler.skin`/`scheduler.setSkin()`, please check the [Migration guide](migration.md) for more details.
 
-- Terrace: https://cdn.dhtmlx.com/scheduler/6.0/skins/dhtmlxscheduler_terrace.css
-- Flat: https://cdn.dhtmlx.com/scheduler/6.0/skins/dhtmlxscheduler_flat.css
-- Contrast Black: https://cdn.dhtmlx.com/scheduler/6.0/skins/dhtmlxscheduler_contrast_black.css
-- Contrast White: https://cdn.dhtmlx.com/scheduler/6.0/skins/dhtmlxscheduler_contrast_white.css
-- Material: https://cdn.dhtmlx.com/scheduler/6.0/skins/dhtmlxscheduler_material.css
+- Terrace: https://cdn.dhtmlx.com/scheduler/6.0/dhtmlxscheduler_terrace.css
+- Flat: https://cdn.dhtmlx.com/scheduler/6.0/dhtmlxscheduler_flat.css
+- Contrast Black: https://cdn.dhtmlx.com/scheduler/6.0/dhtmlxscheduler_contrast_black.css
+- Contrast White: https://cdn.dhtmlx.com/scheduler/6.0/dhtmlxscheduler_contrast_white.css
+- Material: https://cdn.dhtmlx.com/scheduler/6.0/dhtmlxscheduler_material.css
 
 ## Particular Scheduler version, Uncompressed
 
@@ -82,8 +82,8 @@ Starting from v7.0, all skins are included in `dhtmlxscheduler.css` and selected
 
 Uncompressed skin files:
 
-- Terrace: https://cdn.dhtmlx.com/scheduler/8.0/sources/skins/dhtmlxscheduler_terrace.css
-- Flat: https://cdn.dhtmlx.com/scheduler/8.0/sources/skins/dhtmlxscheduler_flat.css
-- Contrast Black: https://cdn.dhtmlx.com/scheduler/8.0/sources/skins/dhtmlxscheduler_contrast_black.css
-- Contrast White: https://cdn.dhtmlx.com/scheduler/8.0/sources/skins/dhtmlxscheduler_contrast_white.css
-- Material: https://cdn.dhtmlx.com/scheduler/8.0/sources/skins/dhtmlxscheduler_material.css
+- Terrace: https://cdn.dhtmlx.com/scheduler/6.0/sources/skins/dhtmlxscheduler_terrace.css
+- Flat: https://cdn.dhtmlx.com/scheduler/6.0/sources/skins/dhtmlxscheduler_flat.css
+- Contrast Black: https://cdn.dhtmlx.com/scheduler/6.0/sources/skins/dhtmlxscheduler_contrast_black.css
+- Contrast White: https://cdn.dhtmlx.com/scheduler/6.0/sources/skins/dhtmlxscheduler_contrast_white.css
+- Material: https://cdn.dhtmlx.com/scheduler/6.0/sources/skins/dhtmlxscheduler_material.css

docs/integrations/angular/installation.md

@@ -131,6 +131,8 @@ Search the project for any remaining mentions of `@dhtmlx/trial-angular-schedule
 npm token create --registry=https://npm.dhtmlx.com
 ~~~
 
+npm will prompt for a password. Use the same password that was used to log in to the private repository, which is the password from the Client Area.
+
 The token is printed once in the terminal output - copy it before closing the session, since it cannot be retrieved later. Then expose it through an `.npmrc` file that the build can read:
 
 

docs/integrations/google-calendar/google-calendar-sync.md

@@ -35,7 +35,7 @@ The complete source code is [available on GitHub](https://github.com/DHTMLX/sche
 ## Demo repository
 
 A complete working project that matches this guide is available on GitHub:
-- https://github.com/DHTMLX/scheduler-google-auth-demo
+- https://github.com/DHTMLX/scheduler-google-calendar-demo
 
 The guide explains the key steps and shows the integration code that matters. The repository is the "full runnable reference".
 
@@ -50,8 +50,8 @@ Do one of the following:
 - Clone the repository:
 
 ~~~bash title="Terminal"
-git clone https://github.com/DHTMLX/scheduler-google-auth-demo.git
-cd scheduler-google-auth-demo
+git clone https://github.com/DHTMLX/scheduler-google-calendar-demo.git
+cd scheduler-google-calendar-demo
 ~~~
 
 If your project installs `@dhx/*` packages from the private registry, configure npm:
@@ -164,7 +164,7 @@ In this step you will separate responsibilities so Scheduler stays a UI componen
 A typical structure:
 
 ~~~text title="Project structure"
-scheduler-google-auth-demo/
+scheduler-google-calendar-demo/
   client/
     index.ejs
     main.ts

docs/integrations/react/starhive-integration.md

@@ -103,7 +103,7 @@ Go to **Settings → API Connectors**. Select the `Scheduler` space, set the lan
 Extract the zip, locate the `starhive` folder under `project/src/io/`, and copy it into `lib/starhive/` in your Next.js project. The generated files contain workspace-specific UUIDs, so you'll repeat this step whenever the schema changes or you switch workspaces.
 
 :::note
-At the time of writing, the Starhive TypeScript generator produces output that does not pass strict TypeScript: a missing `Sla.ts` reference, a missing `visitSlaAttribute` implementation in the inline `AttributeVisitor` literal, and a `client.request<T>` call against an `any`-typed field (TS2347). The companion demo repo ships three minimal patches that work around these; see [`lib/starhive/PATCHES.md`](https://github.com/DHTMLX/react-scheduler-starhive-demo/blob/main/lib/starhive/PATCHES.md) for the diffs. Re-apply the same patches whenever you regenerate the schema, until Starhive ships a fix.
+At the time of writing, the Starhive TypeScript generator produces output that does not pass strict TypeScript: a missing `Sla.ts` reference, a missing `visitSlaAttribute` implementation in the inline `AttributeVisitor` literal, and a `client.request<T>` call against an `any`-typed field (TS2347). The companion demo repo ships three minimal patches that work around these; see [`lib/starhive/PATCHES.md`](https://github.com/DHTMLX/react-scheduler-starhive-demo/blob/main/lib/starhive/) for the diffs. Re-apply the same patches whenever you regenerate the schema, until Starhive ships a fix.
 :::
 
 ## Step 5. Configure the Starhive client
@@ -449,7 +449,7 @@ Open `http://localhost:3000`, drag an event to a new time, edit its text, and de
 ## Notes on Starhive integration
 
 - **Server-side credentials only.** `STARHIVE_API_TOKEN` and `STARHIVE_WORKSPACE_ID` are read inside Route Handlers (`getStarhiveClient`); they never reach the browser bundle. Don't move the Starhive client into a Client Component or expose the token via a `NEXT_PUBLIC_*` variable.
-- **Schema regeneration.** Whenever you add or rename attributes in Starhive, regenerate the TypeScript schema and replace `lib/starhive/`. Re-apply the patches in [`lib/starhive/PATCHES.md`](https://github.com/DHTMLX/react-scheduler-starhive-demo/blob/main/lib/starhive/PATCHES.md) if `next build` complains about the same upstream issues.
+- **Schema regeneration.** Whenever you add or rename attributes in Starhive, regenerate the TypeScript schema and replace `lib/starhive/`. Re-apply the patches in [`lib/starhive/PATCHES.md`](https://github.com/DHTMLX/react-scheduler-starhive-demo/blob/main/lib/starhive/) if `next build` complains about the same upstream issues.
 - **No realtime sync.** Unlike the Firebase integration, Starhive doesn't push changes to connected clients. Multiple users editing the same Scheduler will overwrite each other's changes. For multi-user scenarios, add polling on the client - or wire up Starhive webhooks to push invalidation events through SSE / WebSockets and refresh `events` state on remote changes.
 - **Dynamic loading for larger datasets.** The `/api/load` route loads every event in the workspace. For production, accept `from` / `to` query parameters in the GET handler, filter on `start_date` / `end_date`, and call `scheduler.setLoadMode("day")` on the client so only the visible range is fetched.
 - **Reference attributes carry arrays.** `Events.getResourceId()` returns `string[] | undefined` because Starhive's reference attributes are multi-valued. The demo flattens via `?.[0] || null`. If you allow events to belong to multiple resources, change the timeline view's `y_property` resolution and the normalize / builder calls accordingly.

docs/integrations/react/state/valtio.md

@@ -15,7 +15,7 @@ By the end, you will have a Scheduler with:
 - snapshot-based undo/redo (events + config)
 
 :::note
-The complete source code is [available on GitHub](https://github.com/nicetip/react-scheduler-valtio-starter).
+The complete source code is [available on GitHub](https://github.com/DHTMLX/react-scheduler-valtio-starter).
 :::
 
 ## Prerequisites

docs/integrations/vue/installation.md

@@ -39,7 +39,7 @@ This build is fully functional, but shows a message indicating that the library
 ### Optional: Start a full evaluation period (recommended)
 
 Although the trial package installs without restrictions, you may also start an official evaluation through the website at
-[https://dhtmlx.com/docs/products/dhtmlxScheduler-for-Vuejs/download.shtml](https://dhtmlx.com/docs/products/dhtmlxScheduler-for-Vuejs/download.shtml).
+[https://dhtmlx.com/docs/products/dhtmlxScheduler/download.shtml](https://dhtmlx.com/docs/products/dhtmlxScheduler/download.shtml).
 
 Starting a formal evaluation gives you free technical support during the trial period.
 
@@ -115,6 +115,8 @@ Search your project for any remaining mentions of `@dhtmlx/trial-vue-scheduler`,
 npm token create --registry=https://npm.dhtmlx.com
 ~~~
 
+npm will prompt for a password. Use the same password that was used to log in to the private repository, which is the password from the Client Area.
+
 The token is printed once in the terminal output - copy it before closing the session, since it cannot be retrieved later. Then expose it through an `.npmrc` file that the build can read:
 
 

i18n/de/docusaurus-plugin-content-docs/current/guides/cdn-links-list.md

@@ -1,63 +1,89 @@
 ---
 title: "Vollständige Liste der CDN-Links"
-sidebar_label: "Vollständige Liste der CDN-Links"
+sidebar_label: "CDN-Links"
 ---
 
 # Vollständige Liste der CDN-Links
 
-Dieser Artikel bietet eine vollständige Sammlung von Links, um die Scheduler-Funktionalität über das CDN einzubinden. Jeder Abschnitt ist einer bestimmten Scheduler-Version gewidmet:
+Dieser Artikel führt CDN-Links auf, um **dhtmlxScheduler** in Ihrer Anwendung einzubinden.
 
-- Core-Dateien - die *dhtmlxscheduler.js*- und *dhtmlxscheduler.css*-Dateien, die die Hauptfunktionen enthalten
-- Skins - Links zu allen verfügbaren [Skins](guides/skins.md)
+Scheduler besteht aus zwei Kern-Dateien:
 
-:::note
-Ab Version v6.0 sind alle [Erweiterungen](guides/extensions-list.md) im *dhtmlxscheduler.js*-File gebündelt. Wenn Sie dhtmlxScheduler 5.3 oder älter verwenden, lesen Sie bitte den [Migrationsartikel](migration.md#53---60).
-:::
+- **JavaScript:** `dhtmlxscheduler.js`
+- **Styles:** `dhtmlxscheduler.css`
 
-## Neueste Scheduler-Version
 
-Um die neueste Version der Bibliothek zu verwenden, setzen Sie den Quellpfad auf **https://cdn.dhtmlx.com/scheduler/edge/...**
+## Neueste Scheduler-Version (edge)
 
-Core-Dateien: [JS](https://cdn.dhtmlx.com/scheduler/edge/dhtmlxscheduler.js), [CSS](https://cdn.dhtmlx.com/scheduler/edge/dhtmlxscheduler.css)
+Verwenden Sie:
 
-Skins: [Terrace](https://cdn.dhtmlx.com/scheduler/edge/dhtmlxscheduler_terrace.css),
-[Material](https://cdn.dhtmlx.com/scheduler/edge/dhtmlxscheduler_material.css),
-[Flat](https://cdn.dhtmlx.com/scheduler/edge/dhtmlxscheduler_flat.css),
-[Contrast Black](https://cdn.dhtmlx.com/scheduler/edge/dhtmlxscheduler_contrast_black.css),
-[Contrast White](https://cdn.dhtmlx.com/scheduler/edge/dhtmlxscheduler_contrast_white.css).
+`https://cdn.dhtmlx.com/scheduler/edge/...`
 
-## Neueste Scheduler-Version, Unkomprimiert
+### Kernel-Dateien
 
-Für unkomprimierte Quellen der neuesten Version verwenden Sie den Pfad **https://cdn.dhtmlx.com/scheduler/edge/sources/...**
+- JS: https://cdn.dhtmlx.com/scheduler/edge/dhtmlxscheduler.js
+- CSS: https://cdn.dhtmlx.com/scheduler/edge/dhtmlxscheduler.css
 
-Core-Dateien: [JS](https://cdn.dhtmlx.com/scheduler/edge/sources/dhtmlxscheduler.js), [CSS](https://cdn.dhtmlx.com/scheduler/edge/sources/dhtmlxscheduler.css)
 
-Skins: [Terrace](https://cdn.dhtmlx.com/scheduler/edge/sources/skins/dhtmlxscheduler_terrace.css),
-[Material](https://cdn.dhtmlx.com/scheduler/edge/sources/skins/dhtmlxscheduler_material.css),
-[Flat](https://cdn.dhtmlx.com/scheduler/edge/sources/skins/dhtmlxscheduler_flat.css),
-[Contrast Black](https://cdn.dhtmlx.com/scheduler/edge/sources/skins/dhtmlxscheduler_contrast_black.css),
-[Contrast White](https://cdn.dhtmlx.com/scheduler/edge/sources/skins/dhtmlxscheduler_contrast_white.css).
+## Neueste Scheduler-Version (edge), Unkomprimiert
+
+Verwenden Sie:
+
+`https://cdn.dhtmlx.com/scheduler/edge/sources/...`
+
+### Kern-Dateien
+
+- JS: https://cdn.dhtmlx.com/scheduler/edge/sources/dhtmlxscheduler.js
+- CSS: https://cdn.dhtmlx.com/scheduler/edge/sources/dhtmlxscheduler.css
+
 
 ## Bestimmte Scheduler-Version
 
-Um auf eine bestimmte Version der Bibliothek zu verweisen, setzen Sie den Quellpfad auf **https://cdn.dhtmlx.com/scheduler/[version_number]/...**
+Verwenden Sie:
+
+`https://cdn.dhtmlx.com/scheduler/[version_number]/...`
+
+Die `[version_number]` gibt die major.minor-Version des Pakets an, zum Beispiel **7.0**, **6.0**, **5.3** usw. Unser CDN stellt immer die neueste Patch-Version für jede major/minor-Veröffentlichung bereit.
+
+### Kern-Dateien
+
+- JS: https://cdn.dhtmlx.com/scheduler/7.0/dhtmlxscheduler.js
+- CSS: https://cdn.dhtmlx.com/scheduler/7.0/dhtmlxscheduler.css
+
+### Skins (nur für v6.0 und älter)
+
+Getrennte Skin-Dateien sind in v6.0 und älter verfügbar.
+Ab Version v7.0 sind alle Skins in `dhtmlxscheduler.css` enthalten und über `scheduler.skin`/`scheduler.setSkin()` auswählbar, bitte prüfen Sie den [Migrationsleitfaden](migration.md) für weitere Details.
+
+- Terrace: https://cdn.dhtmlx.com/scheduler/6.0/dhtmlxscheduler_terrace.css
+- Flat: https://cdn.dhtmlx.com/scheduler/6.0/dhtmlxscheduler_flat.css
+- Contrast Black: https://cdn.dhtmlx.com/scheduler/6.0/dhtmlxscheduler_contrast_black.css
+- Contrast White: https://cdn.dhtmlx.com/scheduler/6.0/dhtmlxscheduler_contrast_white.css
+- Material: https://cdn.dhtmlx.com/scheduler/6.0/dhtmlxscheduler_material.css
+
+## Bestimmte Scheduler-Version, Unkomprimiert
+
+Verwenden Sie:
+
+`https://cdn.dhtmlx.com/scheduler/[version_number]/sources/...`
+
+Die `[version_number]` gibt die major.minor-Version des Pakets an, zum Beispiel **7.0**, **6.0**, **5.3** usw. Unser CDN liefert immer die neueste Patch-Version für jede major/minor-Veröffentlichung.
+
+### Kern-Dateien
 
-Core-Dateien: [JS](https://cdn.dhtmlx.com/scheduler/4.3/dhtmlxscheduler.js), [CSS](https://cdn.dhtmlx.com/scheduler/4.3/dhtmlxscheduler.css)
+- JS: https://cdn.dhtmlx.com/scheduler/7.0/sources/dhtmlxscheduler.js
+- CSS: https://cdn.dhtmlx.com/scheduler/7.0/sources/dhtmlxscheduler.css
 
-Skins: [Terrace](https://cdn.dhtmlx.com/scheduler/5.0/dhtmlxscheduler_terrace.css),
-[Material](https://cdn.dhtmlx.com/scheduler/5.0/dhtmlxscheduler_material.css),
-[Flat](https://cdn.dhtmlx.com/scheduler/5.0/dhtmlxscheduler_flat.css),
-[Contrast Black](https://cdn.dhtmlx.com/scheduler/5.0/dhtmlxscheduler_contrast_black.css),
-[Contrast White](https://cdn.dhtmlx.com/scheduler/5.0/dhtmlxscheduler_contrast_white.css).
 
-## Bestimmte Scheduler-Version, Unkomprimiert 
+### Skins (nur für v6.0 und älter)
 
-Um unkomprimierte Quellen einer bestimmten Version zu verwenden, setzen Sie den Pfad auf **https://cdn.dhtmlx.com/scheduler/[version_number]/sources/...**
+Getrennte Skin-Dateien sind in v6.0 und älter verfügbar.
+Ab Version v7.0 sind alle Skins in `dhtmlxscheduler.css` enthalten und über `scheduler.skin`/`scheduler.setSkin()` auswählbar, bitte prüfen Sie den [Migrationsleitfaden](migration.md) für weitere Details.
 
-Core-Dateien: [JS](https://cdn.dhtmlx.com/scheduler/4.3/sources/dhtmlxscheduler.js), [CSS](https://cdn.dhtmlx.com/scheduler/4.3/sources/skins/dhtmlxscheduler.css)
+Unkomprimierte Skin-Dateien:
 
-Skins: [Terrace](https://cdn.dhtmlx.com/scheduler/5.0/sources/skins/dhtmlxscheduler_terrace.css),
-[Material](https://cdn.dhtmlx.com/scheduler/5.0/sources/skins/dhtmlxscheduler_material.css),
-[Flat](https://cdn.dhtmlx.com/scheduler/5.0/sources/skins/dhtmlxscheduler_flat.css),
-[Contrast Black](https://cdn.dhtmlx.com/scheduler/5.0/sources/skins/dhtmlxscheduler_contrast_black.css),
-[Contrast White](https://cdn.dhtmlx.com/scheduler/5.0/sources/skins/dhtmlxscheduler_contrast_white.css).
+- Terrace: https://cdn.dhtmlx.com/scheduler/6.0/sources/skins/dhtmlxscheduler_terrace.css
+- Flat: https://cdn.dhtmlx.com/scheduler/6.0/sources/skins/dhtmlxscheduler_flat.css
+- Contrast Black: https://cdn.dhtmlx.com/scheduler/6.0/sources/skins/dhtmlxscheduler_contrast_black.css
+- Contrast White: https://cdn.dhtmlx.com/scheduler/6.0/sources/skins/dhtmlxscheduler_contrast_white.css
+- Material: https://cdn.dhtmlx.com/scheduler/6.0/sources/skins/dhtmlxscheduler_material.css

i18n/de/docusaurus-plugin-content-docs/current/guides/initialization.md

@@ -21,15 +21,15 @@ Dieser Leitfaden beschreibt die Initialisierung von dhtmlxScheduler in reinem JS
     </div>
   </a>
 
-  <a className="framework-card" href="../../integrations/angular/howtostart-angular/">
+  <a className="framework-card" href="../../integrations/angular/quick-start/">
     <FrameworkIcon name="angular" className="framework-icon" />
     <div className="framework-title">Angular</div>
     <div className="framework-desc">
       In Angular-Projekten den Scheduler mithilfe einer dünnen Wrapper-Schicht integrieren.
     </div>
   </a>
 
-  <a className="framework-card" href="../../integrations/vue/howtostart-vue/">
+  <a className="framework-card" href="../../integrations/vue/quick-start/">
     <FrameworkIcon name="vue" className="framework-icon" />
     <div className="framework-title">Vue</div>
     <div className="framework-desc">

i18n/de/docusaurus-plugin-content-docs/current/integrations/google-calendar/google-calendar-sync.md

@@ -35,7 +35,7 @@ Der vollständige Quellcode ist auf GitHub verfügbar: [https://github.com/DHTML
 ## Demo-Repository
 
 Ein vollständiges, funktionsfähiges Projekt, das dieser Anleitung entspricht, ist auf GitHub verfügbar:
-- https://github.com/dhtmlx/scheduler-google-auth-demo
+- https://github.com/DHTMLX/scheduler-google-calendar-demo
 
 Die Anleitung erläutert die wichtigsten Schritte und zeigt den relevanten Integrationscode. Das Repository ist die „voll funktionsfähige Referenz“.
 
@@ -50,8 +50,8 @@ Führen Sie eine der folgenden Optionen aus:
 - Das Repository klonen:
 
 ~~~bash title="Terminal"
-git clone https://github.com/dhtmlx/scheduler-google-auth-demo.git
-cd scheduler-google-auth-demo
+git clone https://github.com/dhtmlx/scheduler-google-calendar-demo.git
+cd scheduler-google-calendar-demo
 ~~~
 
 Wenn Ihr Projekt `@dhx/*`-Pakete aus dem privaten Registry installiert, konfigurieren Sie npm:
@@ -164,7 +164,7 @@ In diesem Schritt trennen Sie die Verantwortlichkeiten, sodass Scheduler eine UI
 Eine typische Struktur:
 
 ~~~text title="Project structure"
-scheduler-google-auth-demo/
+scheduler-google-calendar-demo/
   client/
     index.ejs
     main.ts