aem-eds-kit 0.4.7 → 0.4.9

package/CHANGELOG.md

@@ -6,6 +6,31 @@ 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
@@ -155,7 +180,10 @@ 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.6...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

package/README.md

@@ -81,6 +81,19 @@ eds init --name my-site --authoring da --org my-org --site my-site --yes
 | `--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.