@ng-brutalism/ui 0.1.1 → 0.1.2

package/CHANGELOG.md

@@ -21,6 +21,15 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Portfolio journey map sync migrated to `toObservable + subscribe`.
 - Event handlers renamed to reflect actions rather than triggering events.
 
+## [0.1.2] — 2026-05-23
+
+### Changed
+
+- npm package `description` rewritten to lead with "neo-brutalist Angular UI library" and include "brutalist Angular components" and `ng add @ng-brutalism/ui` (T1/T2 keyword alignment).
+- npm `keywords`: added `ngbrutalism`, `ng-add`, `schematics`; removed generic `ui` and redundant `tailwind`.
+
+> Patch motivation: `@ng-brutalism/ui` was absent from npm's search index even for exact-name queries. Publishing a new version fires the registry event that triggers the search crawler.
+
 ## [0.1.1] — 2026-05-21
 
 ### Fixed

package/README.md

@@ -127,13 +127,13 @@ Full guides, component API tables, and live examples:
 Yes — it is built and tested against Angular 21. Earlier Angular versions are not supported.
 
 **Do I need Tailwind CSS v4?**
-Yes. ng-brutalism is built on Tailwind v4's token system. Tailwind v3 is not supported.
+Yes. ng-brutalism is built around Tailwind CSS v4 and CSS custom properties. It ships with an Angular CLI schematic that helps you get the required styling setup ready out of the box.
 
 **Can I use ng-brutalism without zoneless mode?**
-Yes — components are signal-driven and work in both zone.js and zoneless apps.
+Yes. Components are designed for modern Angular: standalone imports, signal-friendly internals, and zoneless-friendly interaction patterns. They work in zoneless apps and in apps that still run with zone.js.
 
 **Does ng-brutalism work with server-side rendering (SSR)?**
-Components are zoneless and avoid direct DOM access where possible, so SSR is expected to work — but it is not yet exhaustively verified at v0.1.0.
+The UI package avoids browser-only assumptions in core primitives where possible, and browser-dependent behavior is kept behind Angular platform checks when needed.
 
 **How customizable is the theme?**
 All visual tokens are exposed as CSS custom properties (`--nb-*`). A subset of tokens can also be configured from TypeScript via `provideNgBrutalism({ theme: ... })` at bootstrap.
@@ -141,6 +141,10 @@ All visual tokens are exposed as CSS custom properties (`--nb-*`). A subset of t
 **Is ng-brutalism ready for production?**
 It is pre-1.0. Component APIs are usable today, but minor versions may include breaking changes while the library settles.
 
+## Author
+
+Created by [Khang Tran](https://github.com/khangtrannn). MIT licensed. Source code is available on GitHub.
+
 ## Status
 
 `@ng-brutalism/ui` is pre-1.0. The component APIs are usable today, but minor

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@ng-brutalism/ui",
-  "version": "0.1.1",
-  "description": "Neo-brutalist Angular component library (ng-brutalism) with signals, zoneless, token-driven design, and Tailwind v4.",
+  "version": "0.1.2",
+  "description": "Neo-brutalist Angular UI library — brutalist Angular components with signals, zoneless, and Tailwind v4. Install: ng add @ng-brutalism/ui",
   "license": "MIT",
   "author": "Khang Tran <khangtrann8198@gmail.com>",
   "repository": {
@@ -14,6 +14,7 @@
   },
   "keywords": [
     "ng-brutalism",
+    "ngbrutalism",
     "neo-brutalism",
     "neo-brutalism-ui",
     "neobrutalism",
@@ -24,14 +25,14 @@
     "angular-ui",
     "angular-components",
     "angular-brutalism",
-    "ui",
     "ui-library",
     "component-library",
     "design-system",
-    "tailwind",
     "tailwindcss",
     "signals",
-    "zoneless"
+    "zoneless",
+    "ng-add",
+    "schematics"
   ],
   "peerDependencies": {
     "@angular/common": "^21.0.0",