@jahia/agentic 0.2.0 → 0.4.0

package/dist/opencode/.agents/skills/jahia-orchestrate/SKILL.md

@@ -0,0 +1,148 @@
+---
+name: jahia-orchestrate
+description: Orchestrates building a Jahia module from a task description. Writes a build plan, delegates development and review to subagents in a loop, and exits cleanly. Keeps the orchestrator context lean — reads only small status files, never source code.
+---
+
+You are the Jahia build orchestrator. Your role is coordination, not execution. You keep your context lean by delegating all code work to subagents and communicating only through small status files.
+
+**Max iterations: 3.** If the reviewer still reports NEEDS_WORK after 3 cycles, proceed anyway with the best available state.
+
+---
+
+## Step 1 — Parse the task
+
+Read the task description from your context. Identify:
+- The module being built (site name, company type, pages, components)
+- The module path (working directory, or check `PLAN.md` if already set up)
+- Any efficiency rules already provided
+
+Determine the module path:
+```bash
+pwd
+ls package.json 2>/dev/null && cat package.json | grep '"name"' | head -1
+```
+
+---
+
+## Step 2 — Write PLAN.md
+
+Write `PLAN.md` in the project root with the full build spec. Use the format:
+
+```
+# Build Plan — Round 1
+
+## Module
+- Path: <absolute path from pwd>
+- Site key: <inferred from package.json name or task description>
+- Namespace: <infer from task, e.g. "forsure">
+
+## Pages
+<list from task description>
+
+## Page Template
+- `src/templates/<ModuleName>Template/default.server.tsx` — root layout with `<header>` (nav), `<main>` (areas), `<footer>`, and `<title>` tag
+- Build this FIRST before any page-specific components
+
+## Components
+<list from task description with field descriptions>
+
+## Efficiency Rules
+- ONE build+deploy at the end — do not deploy after each component
+- Skip UI validation in Page Builder
+- Write CND directly — load cnd reference files from .claude/agents/ for patterns
+- Use MCP tools for all content operations
+
+## Done when
+- Page template built with header/nav/main/footer
+- All components have definition.cnd + default.server.tsx + component.module.css
+- yarn build && yarn jahia-deploy succeeded
+- All pages created via MCP and published
+- pages.json written as array of public URLs
+```
+
+---
+
+## Step 3 — Development cycle
+
+Set `round = 1`.
+
+**3a. Spawn the developer worker:**
+
+Use the Agent tool to spawn `@jahia-dev-worker`. Pass this prompt:
+
+> "Read PLAN.md in the current directory. You are the Jahia developer worker — follow the instructions in your agent file. Module path: <absolute path>."
+
+Do NOT read the agent's returned output. After the agent completes, proceed to 3b.
+
+**3b. Read DEV_STATUS.md:**
+
+```bash
+cat DEV_STATUS.md
+```
+
+If Status is FAILED and the failure is unrecoverable (e.g. Jahia never started), stop here and report the failure. Otherwise continue.
+
+---
+
+## Step 4 — Review cycle
+
+**4a. Spawn the code reviewer:**
+
+Use the Agent tool to spawn `@jahia-reviewer`. Pass this prompt:
+
+> "Read REVIEW.md (if it exists) for round context, then review the current source code. Write REVIEW.md with your findings for round <round>."
+
+Do NOT read the agent's returned output. After the agent completes, proceed to 4b.
+
+**4b. Read REVIEW.md:**
+
+```bash
+cat REVIEW.md
+```
+
+---
+
+## Step 5 — Decide: loop or finish
+
+- If REVIEW.md says `Verdict: PASS` → proceed to Step 6.
+- If `Verdict: NEEDS_WORK` and `round < 3`:
+  - Increment round.
+  - Append a "## Round N Fix-Ups" section to `PLAN.md` with the critical issues from REVIEW.md.
+  - Return to Step 3.
+- If `Verdict: NEEDS_WORK` and `round >= 3`:
+  - Log "Max iterations reached — proceeding with current state."
+  - Proceed to Step 6.
+
+---
+
+## Step 6 — Verify pages.json and page quality
+
+```bash
+cat pages.json 2>/dev/null || echo "MISSING"
+```
+
+If missing, spawn `@jahia-dev-worker` once more:
+> "Deploy is already done. Only create content via MCP, verify all pages render correctly, and write pages.json. Read PLAN.md for the page list."
+
+If present, verify every URL actually renders real content — a file that exists but points to error pages is a failed run:
+
+```bash
+node scripts/verify-pages.mjs
+```
+
+If any URL shows `ERROR_PAGE` or a non-200 status, spawn `@jahia-dev-worker` with:
+> "Pages are failing. Read DEV_STATUS.md and REVIEW.md for context, investigate the render errors, fix them, redeploy, and re-verify all pages. Do not update pages.json unless all pages pass."
+
+---
+
+## Step 7 — Done
+
+Report the outcome:
+
+```
+Orchestration complete.
+- Rounds: N
+- Dev status: <from DEV_STATUS.md>
+- Review verdict: <from REVIEW.md>
+- pages.json: <present/missing>
+```

package/dist/opencode/.agents/skills/jahia-orchestrate/scripts/verify-pages.mjs

@@ -0,0 +1,59 @@
+#!/usr/bin/env node
+import { readFileSync, writeFileSync } from "node:fs";
+import { execSync } from "node:child_process";
+import { tmpdir } from "node:os";
+import { join } from "node:path";
+
+const pagesFile = "pages.json";
+let urls;
+try {
+  urls = JSON.parse(readFileSync(pagesFile, "utf8"));
+} catch {
+  console.error(`MISSING: ${pagesFile} not found or invalid JSON`);
+  process.exit(1);
+}
+
+if (!Array.isArray(urls) || urls.length === 0) {
+  console.error(`EMPTY: ${pagesFile} contains no URLs`);
+  process.exit(1);
+}
+
+const tmp = join(tmpdir(), "jahia_pg_verify.html");
+let allOk = true;
+
+for (const url of urls) {
+  let code, body;
+  try {
+    code = execSync(`curl -s -o "${tmp}" -w "%{http_code}" "${url}"`, { encoding: "utf8" }).trim();
+    body = readFileSync(tmp, "utf8");
+  } catch {
+    console.log(`ERROR [unknown] ${url}`);
+    allOk = false;
+    continue;
+  }
+  const titleMatch = body.match(/<title>([^<]*)<\/title>/i);
+  const title = titleMatch ? titleMatch[1].trim() : "";
+  const hasError =
+    body.includes("error details are shown in development mode") ||
+    body.includes("pl.touk.throwing");
+
+  let status;
+  if (hasError) {
+    status = "ERROR_PAGE";
+  } else if (code !== "200") {
+    status = `HTTP_${code}`;
+  } else {
+    const mainMatch = body.match(/<main[^>]*>([\s\S]*?)<\/main>/i);
+    if (mainMatch) {
+      const mainText = mainMatch[1].replace(/<[^>]+>/g, "").replace(/\s+/g, " ").trim();
+      status = mainText.length < 150 ? "INCOMPLETE" : "OK";
+    } else {
+      status = "OK";
+    }
+  }
+
+  console.log(`${status} [${title}] ${url}`);
+  if (status !== "OK") allOk = false;
+}
+
+process.exit(allOk ? 0 : 1);

package/dist/opencode/.opencode/agents/cnd-child-nodes.md

@@ -0,0 +1,74 @@
+# CND Child Nodes
+
+## Syntax
+
+```cnd
++ childName (ns:type)            // named child — exactly one
++ childName (ns:type) multiple   // named child — list
++ * (ns:type)                    // any-name child of a specific type
++ * (jmix:droppableContent)      // open container — any droppable component
+```
+
+## When to use child nodes vs `weakreference multiple`
+
+| Use child nodes when… | Use `weakreference multiple` when… |
+|---|---|
+| Each item has multiple properties (label + link) | Each item is just a reference (a page, an image) |
+| Items have no life outside the parent | Items are managed elsewhere and reused |
+| You always create them together | Editors need to pick from existing content |
+
+## Repeatable CTA pattern
+
+**NEVER put `ctaText + ctaLink/ctaUrl` on the parent type as flat properties.**
+Model CTAs as child nodes — editors can then add multiple CTAs.
+
+```cnd
+// ✅ Correct — supports multiple CTAs
+[ns:heroSection] > jnt:content, nsmix:component, mix:title
+ - subtitle (string, richtext) i18n
+ - backgroundImage (weakreference, picker[type='image']) < jmix:image
+ + * (ns:heroCallToAction)
+
+[ns:heroCallToAction] > jnt:content, nsmix:component
+ - label (string) i18n mandatory
+ - j:linkType (string, choicelist[linkTypeInitializer]) mandatory
+
+// ❌ Wrong — forces exactly one CTA, editors can't add more
+[ns:heroSection] > jnt:content, nsmix:component
+ - ctaText (string) i18n
+ - ctaLink (string) i18n       // also wrong type for links
+```
+
+## Ordering
+
+Add `orderable` to the parent type when editors need to reorder children:
+
+```cnd
+[ns:featureList] > jnt:content, nsmix:component orderable
+ + * (ns:featureItem)
+```
+
+## Hidden structural nodes
+
+Child nodes that editors should never add manually (structural containers, auto-created nodes):
+
+```cnd
+[ns:heroSection] > jnt:content, nsmix:component, mix:title
+ + ctaContainer (ns:ctaContainer) autocreated
+
+[ns:ctaContainer] > jnt:content, jmix:hiddenType orderable
+ + * (ns:callToAction)
+```
+
+`jmix:hiddenType` hides a type from the Page Builder component picker.
+**Never use `jmix:studioOnly`** — it causes silent rendering issues.
+
+## Open container (accept any droppable)
+
+```cnd
+[ns:gridRow] > jnt:content, nsmix:component
+ - columns (long) = '3' autocreated mandatory < '1', '2', '3', '4'
+ + * (jmix:droppableContent)
+```
+
+`+ * (jmix:droppableContent)` accepts any component the editor can drop.

package/dist/opencode/.opencode/agents/cnd-jahia-mixins.md

@@ -0,0 +1,113 @@
+# Jahia Native Mixins & Types
+
+Source: https://github.com/Jahia/jahia/tree/master/war/src/main/webapp/WEB-INF/etc/repository/nodetypes
+Fetch this URL to verify before using any mixin not listed here.
+
+## Base types — always extend these
+
+| Type | Purpose |
+|---|---|
+| `jnt:content` | Base for all user content nodes — **always include** |
+| `jnt:page` | Page node — only for `jmix:mainResource` full-page types |
+| `jnt:file` | File node — for file references |
+
+## Mixins by use case
+
+### `mix:title` — preferred over a raw title property
+
+Adds `jcr:title` (string). Jahia's UI, breadcrumbs, SEO, and sitemap generation all read `jcr:title`.
+**Extend this instead of declaring `- title (string) i18n mandatory`.**
+
+```cnd
+[ns:article] > jnt:content, nsmix:component, mix:title
+```
+
+Access in view: `props["jcr:title"]`
+
+### `jmix:mainResource` — full-page content types only
+
+Makes a node accessible at its own URL. Use **only** for content that needs both a listing card AND a detail page (e.g. blog posts, team members, events). Do not add to navigation or visual composition types.
+
+```cnd
+[ns:blogPost] > jnt:content, mix:title, jmix:mainResource, nsmix:component
+```
+
+### `jmix:image` — image constraint for weakreference
+
+Use as the type constraint on image weakreference properties:
+
+```cnd
+- backgroundImage (weakreference, picker[type='image']) < jmix:image
+```
+
+**Never use `< 'jnt:file'`** (quoted string form) — it does not enforce image type correctly.
+
+**Never declare `imageAlt (string) i18n`** alongside an image weakreference. The referenced image node already has `jcr:title` (from `mix:title`). Use that as the alt text in the view:
+
+```tsx
+const imageAlt = props.image?.getPropertyAsString("jcr:title") ?? "";
+```
+
+Remove any `imageAlt` property — it forces editors to enter duplicate data.
+
+### `jmix:droppableContent` — never extend directly
+
+Always define a module-level component mixin and extend that:
+
+```cnd
+// In settings/definitions.cnd
+[nsmix:component] > jmix:droppableContent, jmix:accessControllableContent mixin
+```
+
+Then all component types extend `nsmix:component`.
+
+### `jmix:hiddenType` — hide from Page Builder picker
+
+Structural/container types editors should not add manually:
+
+```cnd
+[ns:ctaContainer] > jnt:content, jmix:hiddenType orderable
+```
+
+**Never use `jmix:studioOnly`** — it causes silent rendering issues in some contexts.
+
+### `jmix:accessControllableContent` — per-component access control
+
+Add to your base module mixin so all components support it:
+
+```cnd
+[nsmix:component] > jmix:droppableContent, jmix:accessControllableContent mixin
+```
+
+### `jmix:link` — built-in link type
+
+Provides `j:linkType`, `j:linknode`, `j:url`, `j:linkTitle`. Extend this mixin as an alternative to declaring `j:linkType` directly on a type that needs only link behavior and nothing else.
+
+## picker[] selector
+
+| Selector | Use |
+|---|---|
+| `picker[type='image']` | Image assets only |
+| `picker[type='file']` | Any file asset |
+
+```cnd
+- backgroundImage (weakreference, picker[type='image']) < jmix:image
+- attachment (weakreference, picker[type='file']) < jnt:file
+```
+
+## Two-tier component mixin system
+
+If the module uses custom area types (see `jahia-dev-create-page-template`):
+
+```cnd
+[nsmix:component]     > jmix:droppableContent, jmix:accessControllableContent mixin
+[nsmix:pageComponent] > nsmix:component mixin
+```
+
+| Component will be… | Extend |
+|---|---|
+| Dropped in page areas | `nsmix:pageComponent` |
+| Child of another component | `nsmix:component` |
+| Listed programmatically | `nsmix:component` |
+
+A component extending only `nsmix:component` **cannot** be dropped in areas that use `nsmix:pageComponent`.

package/dist/opencode/.opencode/agents/cnd-numbers-dates.md

@@ -0,0 +1,61 @@
+# CND Numeric, Date & Boolean Properties
+
+## Types
+
+| Type | Editor widget | Notes |
+|---|---|---|
+| `long` | Integer number input | Counts, limits, columns |
+| `double` | Decimal number input | Coordinates, prices, ratios |
+| `boolean` | Checkbox | Feature flags, toggles |
+| `date` | Date picker | ISO 8601 stored, string in TypeScript |
+| `date, datepicker` | Date + time picker | Same storage, richer widget |
+
+## Default values with `autocreated`
+
+Always combine `autocreated` with `= 'value'`:
+
+```cnd
+- columns (long) = '3' autocreated mandatory < '1', '2', '3', '4'
+- isHighlighted (boolean) = 'false' autocreated
+- country (string, choicelist[country]) = 'US' autocreated mandatory
+```
+
+## Range constraints
+
+```cnd
+// Numeric range — inclusive brackets
+- latitude (double) mandatory < "[-90,90]"
+- longitude (double) mandatory < "[-180,180]"
+- rating (long) mandatory < "[1,5]"
+```
+
+**Star ratings always need a range constraint.** Never write `rating (long)` without `< "[1,5]"`:
+
+```cnd
+// WRONG
+- rating (long) = 5 indexed=no
+
+// CORRECT
+- rating (long) = '3' autocreated mandatory < "[1,5]"
+```
+
+## Date range constraints
+
+Parentheses = exclusive bound, brackets = inclusive. Leave a side empty for open-ended:
+
+```cnd
+// Any date after 2020-01-01 (exclusive)
+- eventDate (date, datepicker) < '(2020-01-01T00:00:00.000,)'
+
+// Bounded campaign window
+- campaignDate (date, datepicker) < '(2020-01-01T00:00:00.000,2030-12-31T00:00:00.000)'
+```
+
+## TypeScript mapping
+
+| CND type | TypeScript |
+|---|---|
+| `long` | `number` |
+| `double` | `number` |
+| `boolean` | `boolean` |
+| `date` | `string` (ISO 8601) |

package/dist/opencode/.opencode/agents/cnd-string-selectors.md

@@ -0,0 +1,94 @@
+# CND String & Selector Properties
+
+## String type variants
+
+| Type declaration | Editor widget | When to use |
+|---|---|---|
+| `(string)` | Single-line text input | Short labels, IDs, slugs |
+| `(string, textarea)` | Multi-line text area | Paragraphs, descriptions |
+| `(string, richtext)` | Rich text editor (TinyMCE) | Body content, formatted text |
+| `(string) multiple` | Tag input / list | Lists of plain strings |
+
+## Fixed-choice dropdowns
+
+Use `(string, choicelist)` + `< 'val1', 'val2'` for a dropdown with a hard-coded list.
+**Never use `choicelist[val1,val2]`** — the bracket syntax is for initializer keywords, not values.
+
+```cnd
+- difficulty (string, choicelist) i18n < 'beginner', 'intermediate', 'advanced'
+- variant (string, choicelist) < 'primary', 'secondary', 'ghost'
+```
+
+## `mix:title` instead of a title string property
+
+**NEVER write `- title (string) i18n mandatory`.**
+Extend `mix:title` instead — it adds `jcr:title`, which Jahia's UI, breadcrumbs, and search use natively.
+
+```cnd
+// ✅ Correct
+[ns:heroSection] > jnt:content, nsmix:component, mix:title
+
+// ❌ Wrong — duplicates what mix:title already provides
+[ns:heroSection] > jnt:content, nsmix:component
+ - title (string) i18n mandatory
+```
+
+Access in the view as `props["jcr:title"]`.
+
+## Link picker — `choicelist[linkTypeInitializer]`
+
+**NEVER use `(string)` for a link, URL, href, or path.**
+Use `choicelist[linkTypeInitializer]` — it renders an internal/external/none picker in the editor.
+
+**Declare ONLY `j:linkType` in the CND. Do NOT add `j:linknode` or `j:url` — Jahia injects them automatically.**
+
+```cnd
+// ✅ Correct — bare minimum
+[ns:callToAction] > jnt:content, nsmix:component
+ - label (string) i18n mandatory
+ - j:linkType (string, choicelist[linkTypeInitializer]) mandatory
+
+// ❌ Wrong — do not declare companion fields
+ - j:linknode (weakreference)   // injected by Jahia — remove this
+ - j:url (string)               // injected by Jahia — remove this
+```
+
+TypeScript discriminated union for the view:
+
+```ts
+import type { JCRNodeWrapper } from "org.jahia.services.content";
+export type Props =
+  | { label?: string; "j:linkType": "none" }
+  | { label?: string; "j:linkType": "internal"; "j:linknode"?: JCRNodeWrapper }
+  | { label?: string; "j:linkType": "external"; "j:url"?: string; "j:linkTitle"?: string };
+```
+
+In the view, switch on `props["j:linkType"]`.
+
+## Other `choicelist[...]` initializers
+
+| Initializer | What it renders |
+|---|---|
+| `choicelist[country]` | Country selector (ISO codes, localized labels) |
+| `choicelist[resourceBundle]` | Labels from `.properties` file keys |
+| `choicelist[nodes=/path;type=jnt:content]` | Nodes under a JCR path |
+| `choicelist[componentTypes=jnt:page]` | Registered views of a node type |
+| `choicelist[menus]` | Site menus |
+
+## Regex constraints on strings
+
+```cnd
+- contactEmail (string) < '^$|[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}'
+- slug (string) < '^[a-z0-9-]+$'
+- externalUrl (string) < '^https?://'
+```
+
+## Common attributes
+
+| Attribute | Meaning |
+|---|---|
+| `i18n` | Translatable per language — **default to always on user-facing fields** |
+| `mandatory` | Required |
+| `multiple` | List of values |
+| `primary` | Highlighted field in editor (one per type) |
+| `autocreated` | Auto-created on node creation — always combine with `= 'defaultValue'` |

package/dist/opencode/.opencode/agents/jahia-cnd-author.md

@@ -0,0 +1,130 @@
+---
+name: jahia-cnd-author
+description: Use when you need to write a Jahia CND content type definition and its TypeScript props interface. Receives a component spec and produces a per-component definition.cnd + types.ts with correct Jahia-specific syntax. Self-validates output before returning.
+allowed-tools: Read, Write, Edit, Bash
+tools:
+  Read: true
+  Write: true
+  Edit: true
+  Bash: true
+---
+
+You are a Jahia CND specialist. Your sole job is to write correct `definition.cnd` and `types.ts` files for a single component type. You have no MCP tools and should not perform content operations or deployments.
+
+## Your inputs
+
+You will receive a structured spec:
+
+```
+Component: <name>
+Namespace prefix: <ns>
+Module path: <path to module root>
+Fields:
+  - <field name>: <type description> [mandatory] [i18n] [multiple]
+Usage: <where this component appears>
+Children: <repeatable sub-items if any>
+```
+
+## Step 1 — Locate and load reference files
+
+Reference files live next to this agent file. First, discover where they are:
+
+```bash
+# Find the directory that contains the cnd-jahia-mixins reference file
+find . -maxdepth 4 -name "cnd-jahia-mixins*" 2>/dev/null | head -5
+```
+
+Then read the files you need (using whichever path the find command returned):
+
+- **Always read**: `cnd-jahia-mixins` (required — tells you which native mixins to extend)
+- **If text, link, or choice properties**: `cnd-string-selectors`
+- **If repeatable child items**: `cnd-child-nodes`
+- **If numbers, dates, or booleans**: `cnd-numbers-dates`
+
+Do not skip this step. These files contain the exact CND patterns you must use. If the find returns nothing, something is wrong with the harness installation — stop and report.
+
+## Step 2 — Resolve namespace and location
+
+```bash
+# Get namespace prefix
+grep "^<" <module-path>/settings/definitions.cnd | head -5
+
+# Check for two-tier mixin
+grep "pageComponent" <module-path>/settings/definitions.cnd
+
+# Find the right category directory
+ls <module-path>/src/components/
+```
+
+If `namespacemix:pageComponent` exists: use it for components dropped in page areas, use `namespacemix:component` for children of other components.
+
+**File locations — collocation is mandatory:**
+
+Each component type lives in its own file, next to its view. NEVER put all types in `settings/definitions.cnd`.
+
+```
+src/
+  components/
+    Sections/
+      HeroSection/
+        definition.cnd    ← one type per file, co-located here
+        default.server.tsx
+        types.ts
+    Cards/
+      TextCard/
+        definition.cnd    ← separate file per component
+        types.ts
+settings/
+  definitions.cnd          ← namespace declarations + shared mixins ONLY
+```
+
+## Step 3 — Write the CND
+
+Create `<module-path>/src/components/<Category>/<Name>/definition.cnd`.
+
+Rules from the reference files you loaded — apply all of them:
+1. **Links**: `j:linkType (string, choicelist[linkTypeInitializer]) mandatory` — never `(string)` for `*Url`, `*Href`, `*Link`
+2. **Titles**: extend `mix:title` — never `- title (string)` or `- jcr:title (string)`
+3. **Repeatable CTAs**: child nodes `+ * (ns:callToAction)` — never flat `ctaText + ctaUrl` on the parent
+4. **Images**: `(weakreference, picker[type='image']) < jmix:image` — never `(string)` for image URLs
+5. **i18n**: on every user-facing string/textarea/richtext property
+6. **Component mixin**: extend `namespacemix:component` or `namespacemix:pageComponent` — never `jmix:droppableContent` directly on a concrete type
+
+Each per-component `definition.cnd` must include the namespace declarations at the top:
+```cnd
+<ns = 'http://...'>
+<nsmix = 'http://...'>
+```
+
+## Step 4 — Write types.ts
+
+Create `<module-path>/src/components/<Category>/<Name>/types.ts`. All fields use `?:` even if mandatory in CND.
+
+For `j:linkType` properties, use the discriminated union from the reference file you loaded.
+
+## Step 5 — Self-validate
+
+```bash
+CND=<module-path>/src/components/<Category>/<Name>/definition.cnd
+
+# Error: raw string for a link/URL property
+grep -En "^[[:space:]]*-[[:space:]]+[a-zA-Z]*(Url|Href|Link)[[:space:]]+\(string" "$CND"
+
+# Error: title declared as raw property instead of mix:title
+grep -En "^[[:space:]]*-[[:space:]]+(title|jcr:title)[[:space:]]+\(string" "$CND"
+
+# Error: concrete type extends jmix:droppableContent directly
+grep -n "jmix:droppableContent" "$CND" | grep -v "mixin"
+
+# Error: image as plain string URL
+grep -En "^[[:space:]]*-[[:space:]]+[a-zA-Z]*(Image|Photo|Avatar|Logo)[[:space:]]+\(string" "$CND"
+```
+
+If any of these print matches, fix the issue and re-run before reporting.
+
+## Step 6 — Report
+
+- Files written: paths
+- Type name(s) defined
+- Self-validate result: PASS / fixed N errors
+- Any warnings not fixed and why