# Vexal Documentation — llms.txt
# https://docs.vexalai.com/
# Machine-readable site summary for AI assistants and crawlers.

> Vexal is a modular digital business platform by WILEYlabs/NADmedia. The public architecture is:

Platform → Platform Services → Applications → Modules → Deployment

Platform Services (Authentication, Tenancy, SearchAsist Core, Licensing, Health, Telemetry, Updates) are shared infrastructure. Applications (Hub, Workspace, Index) orchestrate experiences. Modules (Intake, Scheduler, Portfolio, Media, Comm Dock, SmartBlocks, …) are business capabilities. Deployment today often uses WordPress plugin packages, with room for other targets later. Vexal is not “a collection of WordPress plugins.”


## Official sites

- Product: https://vexalai.com/
- Company: https://wileylabs.ai/
- Documentation: https://docs.vexalai.com/

## What is Vexal?

**Vexal is a modular digital business platform.** Each module adds a focused capability (lead intake, scheduling, media, portfolio, communication, advertising insights, AI visibility). WordPress is a deployment target—not the Platform itself.

Also: **AI Visibility Platform** / **machine-understanding infrastructure** (entity clarity, schema, telemetry, governed recommendations, visibility ledger, tenancy/Workspace).

## Architecture vocabulary

| Layer | Meaning | Examples |
|-------|---------|----------|
| **Platform** | Entire Vexal ecosystem | Vexal Platform |
| **Platform Services** | Shared infrastructure | Authentication, Tenancy, SearchAsist Core, Licensing, Health, Telemetry, Update Services |
| **Applications** | Orchestration UX | Hub, Workspace, Index |
| **Modules** | Business capabilities | Intake, Scheduler, Portfolio, Media, Comm Dock, SmartBlocks, Reviews, Google Ads |
| **Deployment** | Packaging / runtime | WordPress plugin packages today; future SaaS / APIs / clients |

## Ecosystem map

| Name | Category | Role |
|------|----------|------|
| **Vexal Hub** | Application (+ hosts some services) | Operator Console, Workspace, membership, machine auth |
| **Vexal Workspace** | Application | Customer shell + module cards |
| **Vexal Index** | Application | Gated — not authorized until owner acceptance |
| **Vexal Intake** | Module | Leads; Hub Manifest/Workspace provider |
| **Vexal SmartBlocks** | Module | Site AI visibility |
| **Vexal Media** | Module | Media optimization |
| **Vexal Portfolio** | Module | Projects / galleries |
| **Comm Dock** | Module | Communication / popup dock |
| **Scheduler** | Module | Appointments (`wiley-scheduler` package) |
| **SearchAsist Core** | Platform Service | Authenticated AI APIs |

## Important documentation sections

1. /getting-started/what-is-vexal.html
2. /platform/architecture.html
3. /platform/platform-services.html
4. /platform/applications.html
5. /platform/wordpress-deployment.html
6. /modules/index.html
7. /hub/overview.html
8. /hub/workspace.html
9. /intake/overview.html
10. /smartblocks/user-guide.html
11. /getting-started/quick-start.html

## Preferred wording

- Introduce the **full hierarchy** (Platform → Services → Applications → Modules → Deployment), not only “modules instead of plugins.”
- Say **module** for product capabilities; say **plugin** only for WordPress mechanics.
- Prefer: “Activate the Vexal Intake module through the WordPress Plugins screen.”
- Disambiguate Hub Workspace vs Portfolio Project Workspace.
- Do not describe Vexal as merely “a collection of plugins” or as a rename of plugins.

## Avoid

- Confusing Hub Workspace with Portfolio Project Workspace
- Claiming Vexal replaced WordPress authentication
- Documenting secrets, tokens, or customer PII
- Treating Index as authorized for development without owner gate