v1.1.0 — Theme-Aware Styling & UX Polish

v1.1.0 — Theme-Aware Styling & UX Polish

Highlights

This release brings full theme integration with @mieweb/ui brand system and a collection of UX improvements to the filter system, search bar, and production deployment.

---

What's New

Theme-Aware Node Styling

• Node border colors dynamically follow the active brand theme via --yc-color-primary
• Node card borders update in real-time when switching themes — no page reload required
• Highlighted nodes retain distinct pink stroke for visibility

Theme Persistence

• Selected brand theme now persists across page reloads using localStorage
• Works in both development and production builds

Filter System Improvements

• Fixed empty filter dropdown: Field selector now properly populates options on focus
• Themed filter badges: Selected filter values display with a tinted background matching the active brand color instead of neutral grey
• Search results positioning: Suggestions dropdown no longer covers the search input — now positioned absolutely below the search bar

POI Selector Polish

• Removed distracting border from POI (Person of Interest) selector
• Added subtle grey background for better visual distinction
• Overrides applied with sufficient specificity to beat Tailwind utility classes

CSS Variable Integration

• Shadow DOM :host variables now bridge to --color-primary for seamless @mieweb/ui integration
• Full variable chain: brand token → --color-primary → --yc-color-primary → node rendering

Production Build Sync

• production.html updated with correct brand color values from @mieweb/ui source files
• Theme selector in production now includes persistence and live chart re-render
• Fixed brand palette: BlueHive, MIE Web, Enterprise Health, Waggleline, WebChart

---

Files Changed

• src/d3-org-chart.js — Theme-aware default node stroke
• src/ychartEditor.ts — Filter UX, badge theming, CSS variable bridging, node card borders
• src/main.ts — Theme persistence and live re-render on theme change
• src/styles/mieweb-ui-overrides.css — POI selector styling overrides
• production.html — Correct brand colors, persistence, re-render
• package.json — Version bump to 1.1.0

---

Full Changelog: v1.0.7...v1.1.0

v1.0.7

Release v1.0.7 - Scoped library styles to container

v1.0.6

Release v1.0.6

v1.0.5

What's Changed since v1.0.3

✨ Features

• Multiple Root Nodes Support: YChart now fully supports multiple root nodes (e.g., holding company with subsidiaries). The chart renderer already handled this via virtual root, but the editor linter was incorrectly flagging them as errors. Added a new 'Multiple Roots (Holding Company)' example demonstrating three independent subsidiaries.

• Version Console Log: Displays YChart Editor v1.0.5 initialized successfully in the browser console when the editor loads, with styled branding.

🐛 Bug Fixes

• POI (Person of Interest) Improvements for Multi-Root Scenarios:
  • Reset button now clears POI entirely to show all roots (instead of selecting first root)
  • Root nodes in multi-root scenarios now show 'expand siblings' button to reveal other root hierarchies
  • Root node siblings are properly counted for the expand button
  • All roots are visible by default on page load (no auto-selection of first root as POI)

♻️ Refactoring

• CSS Scoping: All YChart library styles are now scoped under .ychart-container class to prevent interference with host page styles when integrating in production. This allows YChart to be embedded in existing pages without affecting or being affected by the host page's CSS.
  • Created modular SCSS architecture with _ychart-lib.scss (scoped library styles) and _demo.scss (demo-only styles)
  • CSS variables remain global (--yc-* prefix) but all selectors are scoped

📁 New Files

• src/styles/_ychart-lib.scss - Scoped library styles
• src/styles/_demo.scss - Demo page only styles
• examples/multiple-roots/orgchart.yaml - Multiple roots example data

Full Changelog: v1.0.3...v1.0.5

v1.0.4

What's Changed since v1.0.3

✨ Features

• Multiple Root Nodes Support: YChart now fully supports multiple root nodes (e.g., holding company with subsidiaries). The chart renderer already handled this via virtual root, but the editor linter was incorrectly flagging them as errors. Added a new 'Multiple Roots (Holding Company)' example demonstrating three independent subsidiaries.

• Version Console Log: Displays YChart Editor v1.0.4 initialized successfully in the browser console when the editor loads, with styled branding.

🐛 Bug Fixes

• POI (Person of Interest) Improvements for Multi-Root Scenarios:
  • Reset button now clears POI entirely to show all roots (instead of selecting first root)
  • Root nodes in multi-root scenarios now show 'expand siblings' button to reveal other root hierarchies
  • Root node siblings are properly counted for the expand button
  • All roots are visible by default on page load (no auto-selection of first root as POI)

♻️ Refactoring

• CSS Scoping: All YChart library styles are now scoped under .ychart-container class to prevent interference with host page styles when integrating in production. This allows YChart to be embedded in existing pages without affecting or being affected by the host page's CSS.
  • Created modular SCSS architecture with _ychart-lib.scss (scoped library styles) and _demo.scss (demo-only styles)
  • CSS variables remain global (--yc-* prefix) but all selectors are scoped

📁 New Files

• src/styles/_ychart-lib.scss - Scoped library styles
• src/styles/_demo.scss - Demo page only styles
• examples/multiple-roots/orgchart.yaml - Multiple roots example data

Full Changelog: v1.0.3...v1.0.4

v1.0.2

What's Changed

• Updated README with npm installation and CDN usage instructions
• Added jsDelivr and unpkg CDN examples

Full Changelog: v1.0.1...v1.0.2

v1.0.1

What's Changed

• Added npm publishing workflow for automated releases
• Renamed package to @mieweb/ychart
• Added NPM_PUBLISHING.md documentation
• Configured Node.js 24+ requirement

Full Changelog: v1.0.0...v1.0.1