aem-eds-kit 0.4.4 → 0.4.9

package/CHANGELOG.md

@@ -6,6 +6,54 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [0.4.9] - 2026-10-08
+
+### Added
+- `eds migrate component` now pulls the component's **clientlib CSS** off disk
+  into the block's CSS (auto-detected, or `--clientlib <dir>`): honours
+  `css.txt` ordering + `#base=`, concatenates the `.css`, and flags any
+  LESS/SCSS that needs a build. A starting point to review and scope under
+  `.<block>` (the faithful, rendered-CSS path comes in a later phase).
+
+## [0.4.8] - 2026-10-07
+
+### Added
+- **`eds migrate component <dir>`** - start migrating a classic AEM component to
+  EDS. Phase 1 (deterministic, no agent/network): parses the Touch UI dialog
+  (`_cq_dialog/.content.xml`) and maps its Granite/Coral fields onto the 17
+  Universal Editor field types - selects keep their options, multifields become
+  repeatable containers, tabs are preserved - then writes `blocks/<name>/` with
+  a UE model, a decorator stub, and a scoped CSS file to fill from the clientlib
+  or rendered page. Also in the `eds` menu.
+
+## [0.4.7] - 2026-10-07
+
+### Changed
+- Consistent "no EDS project markers found" message across every command.
+
+## [0.4.6] - 2026-10-07
+
+### Added
+- **`eds init`** - adapt a freshly cloned EDS boilerplate to your authoring model
+  in one interactive wizard: pick Universal Editor (crosswalk), DA (da.live),
+  Google Drive or SharePoint; set the project name (package.json + boilerplate
+  placeholders); generate `fstab.yaml` only when the model needs it; scaffold the
+  crosswalk config + `paths.json` for UE; optionally add the CI workflow; then
+  walk the external steps (code-sync, content share, Sidekick) as a clickable
+  checklist. Also in the `eds` menu. Flags: `--name`, `--authoring`,
+  `--mountpoint`, `--org`, `--site`, `--no-ci`, `--yes`.
+
+## [0.4.5] - 2026-10-07
+
+### Fixed
+- Project-root detection no longer requires `fstab.yaml`. Universal Editor /
+  crosswalk and Document Authoring projects often don't have one, which made
+  every command (and the generated CI) fail with "Not inside an EDS project".
+  A root is now any ancestor with `fstab.yaml`, `head.html`, `scripts/scripts.js`,
+  `scripts/aem.js`, `component-definition.json`, `paths.json` or `helix-query.yaml`.
+- `eds doctor` treats a missing `fstab.yaml` as a warning, not a hard failure,
+  so `scaffold ci`'s doctor step doesn't break CI for fstab-less projects.
+
 ## [0.4.4] - 2026-10-07
 
 ### Added
@@ -132,7 +180,12 @@ harness, gradient ANSI logo. Not published (superseded by 0.3.0).
 Initial CLI scaffold: `block create`, `block from-figma`, `block list`,
 `figma setup`, `doctor`, `preview`, `publish`. Not published.
 
-[Unreleased]: https://github.com/piotrgodycki/aem-eds-kit/compare/v0.4.4...HEAD
+[Unreleased]: https://github.com/piotrgodycki/aem-eds-kit/compare/v0.4.9...HEAD
+[0.4.9]: https://github.com/piotrgodycki/aem-eds-kit/releases/tag/v0.4.9
+[0.4.8]: https://github.com/piotrgodycki/aem-eds-kit/releases/tag/v0.4.8
+[0.4.7]: https://github.com/piotrgodycki/aem-eds-kit/releases/tag/v0.4.7
+[0.4.6]: https://github.com/piotrgodycki/aem-eds-kit/releases/tag/v0.4.6
+[0.4.5]: https://github.com/piotrgodycki/aem-eds-kit/releases/tag/v0.4.5
 [0.4.4]: https://github.com/piotrgodycki/aem-eds-kit/releases/tag/v0.4.4
 [0.4.3]: https://github.com/piotrgodycki/aem-eds-kit/releases/tag/v0.4.3
 [0.4.2]: https://github.com/piotrgodycki/aem-eds-kit/releases/tag/v0.4.2

package/README.md

@@ -41,6 +41,9 @@ A full A-Z reference of every command lives on the docs page: **https://piotrgod
 ```bash
 eds                              # interactive menu
 
+# Just cloned an EDS boilerplate? Set it up for your authoring model
+eds init
+
 # One-time: configure Figma MCP for your AI agent
 eds figma setup
 
@@ -60,6 +63,37 @@ eds doctor
 
 ## Commands
 
+### `eds init`
+
+Adapt a freshly cloned EDS boilerplate to your setup in one interactive wizard. Pick the authoring model - **Universal Editor (crosswalk), DA (da.live), Google Drive or SharePoint** - and `eds` sets the project name (`package.json` + boilerplate placeholders), writes `fstab.yaml` **only when the model needs it** (UE/crosswalk doesn't), scaffolds the crosswalk config + `paths.json` for UE, optionally adds the CI workflow, then walks the **external steps** (AEM Code Sync app, content-source share, Sidekick) as a clickable checklist.
+
+```bash
+eds init                                           # interactive
+eds init --name my-site --authoring da --org my-org --site my-site --yes
+```
+
+| Flag | Description |
+|---|---|
+| `--name <name>` | Project name (kebab-case) |
+| `--authoring <model>` | `ue` \| `da` \| `gdrive` \| `sharepoint` |
+| `--mountpoint <url>` | Content source URL (document models) |
+| `--org <org>` / `--site <site>` | DA org / site (`--authoring da`) |
+| `--no-ci` | Skip the GitHub Actions workflow |
+| `--yes` | Skip prompts; apply with flags/defaults |
+
+### `eds migrate component [dir]`
+
+Start migrating a **classic AEM component** to EDS. Phase 1 is deterministic (no agent, no network): it parses the component's Touch UI dialog (`_cq_dialog/.content.xml`) and maps its Granite/Coral fields onto the **17 Universal Editor field types** - selects keep their options, multifields become repeatable containers, tabs are preserved - then writes `blocks/<name>/` with a UE model (`_<name>.json`), a `decorate()` stub (port the HTL logic), and a scoped CSS file to fill from the component's clientlib or its rendered page.
+
+It also pulls the component's **clientlib CSS** off disk into the block's CSS when it can find one (auto-detected, or `--clientlib <dir>`): it honours `css.txt` ordering (and `#base=`), concatenates the `.css`, and flags any LESS/SCSS that needs a build. Treat it as a starting point - review the selectors and scope them under `.<block>`.
+
+```bash
+eds migrate component /path/to/apps/myproject/components/hero
+eds migrate component ./components/hero --name hero --clientlib ./ui.apps/.../hero/clientlib --yes
+```
+
+Dialogs map cleanly because Granite's `sling:resourceType` set is finite. The most faithful CSS actually comes from the **rendered page** (resolves LESS vars + cascade) - that capture lands in a later phase; for now the clientlib source gets you most of the way.
+
 ### `eds block create <name>`
 
 Scaffolds `blocks/<name>/` with `<name>.js`, `<name>.css`, **and a Universal Editor model `_<name>.json` by default** - so the block is authorable in UE the moment it's created. Validates kebab-case naming and checks for collisions.