CRXDE Lite
Purpose: Use CRXDE Lite effectively and safely — the in-browser IDE for the repository.
Who this page is for
| Audience | Why it matters to you |
|---|---|
| All engineers | Daily inspection tool |
What it is
/crx/de — a browser IDE over the JCR: tree navigation, property editing, script editing, an access-control tab and a query tool. Think Redux DevTools with write access to production state — powerful and dangerous in equal measure.
Daily moves
| Task | How |
|---|---|
| Find where a page's content lives | Navigate /content/…/jcr:content, expand component nodes |
| Check a component's implementation | Follow the node's sling:resourceType into /apps |
| Test a query | Tools → Query, JCR-SQL2 or XPath |
| Check effective type hierarchy | Node's sling:resourceSuperType chain |
| Quick property fix on a dev box | Edit property → Save All |
Safety rules
- Never hand-edit /apps or /libs on shared environments — it drifts from source control and is lost on redeploy. CRXDE edits are for local experiments and inspection.
- /libs is Adobe's product code: read it freely (it is the best documentation), never modify it — overlay into /apps instead.
- On production, CRXDE should be blocked at the dispatcher and access restricted; treat any prod CRXDE access as break-glass.
Reading /libs as documentation
The fastest way to learn any product component: find it under /libs, read its HTL and dialog. Example: how does the product page component include clientlibs? Read /libs/core/wcm/components/page/… and follow the scripts.