TextQL Workshops

Hands-on workshop guides for the TextQL platform — self-paced sites a customer can walk through alone, or that an FDE/AE can use to lead a guided session.

Each workshop is a self-contained index.html (plus a local assets/ folder for screenshots) — no build step, no dependencies. Open it from a double-click, host it anywhere, or serve the whole repo via GitHub Pages.

Catalog

Workshop	Audience	Time	Status
Self-Service Analytics	Business users — no SQL, no data background	~2 hours	✅ Ready (screenshots pending — see SHOT_LIST)
Dashboards & Reporting	Anyone who turns analysis into something others consume	~2 hours	✅ Ready
Automation Deep-Dive	Analysts/operators automating recurring analysis	~2 hours	✅ Ready
TextQL for Sales & GTM	Sellers, sales leaders, RevOps, CS	~90 min	✅ Ready
Connect Your Data	Data engineers, platform admins	~2.5 hours	✅ Ready
Ontology Operations	Data teams running an ontology in production	~2 hours	✅ Ready
Admin & Governance	Workspace administrators	~2.5 hours	✅ Ready
Developer Workshop — API & MCP	Developers and technical integrators	~2 hours	✅ Ready
Build Your Ontology, End to End	Data teams	Half day	✅ Ready
Implement the Healthcare Starter Pack	HCLS data teams	~2.5 hours	✅ Ready
TextQL for Finance Teams	FP&A, controllers, finance ops	~2 hours	✅ Ready
TextQL for Customer Success	CSMs, CS leaders, CS ops	~90 min	✅ Ready
TextQL for Executives	C-suite & VPs	45 min	✅ Ready
Migrate from Your BI Tool	Analytics engineers, BI admins	~2.5 hours	✅ Ready
POC in a Week	Data team + champion running an evaluation	5 days	✅ Ready
Data Quality & Validation Deep-Dive	Data & analytics engineers	~2 hours	✅ Ready
Embed TextQL in Your Product	Developers & product teams	~2.5 hours	✅ Ready
Deploy TextQL in Your VPC	Platform & infra teams	~2.5 hours	✅ Ready
The Context Stack — Personal, Role & Org Context	Platform owners, admins, enablement	~2 hours	✅ Ready

The repo root index.html is a catalog landing page listing all workshops.

Using a workshop

• Send to a customer: share the hosted link, or the workshop folder (the HTML works offline; screenshots load from its assets/). Everything is account-agnostic and safe to share.
• Run a guided session: the facilitator shares their screen on the guide while attendees follow hands-on in their own TextQL workspace.
• Learner progress (checkpoints + progress bar) persists in the browser via localStorage.

Adding a new workshop

1. Copy _template/ to a new kebab-case folder (e.g. data-team-onboarding/).
2. Follow the HOW TO USE THIS TEMPLATE comment inside — set the title, a unique WS_KEY, and replace the placeholder <section class="page"> blocks.
3. Add screenshots to the workshop's assets/ and keep a SHOT_LIST.md (placeholders render as "coming soon" until the file exists).
4. Add a card to the catalog in the root index.html and a row to the table above.
5. Keep it account-agnostic: no customer names, no real data, synthetic examples only. Run the sanitizer before publishing if content derives from a real engagement.

Questions or contributions: contact the TextQL team.

Conventions

• One folder per workshop; one self-contained index.html + assets/ per workshop. The HTML is the single source of truth — no parallel markdown copies to drift.
• Customer-facing only — facilitator guides, playbooks, and account context live internally, never here.
• Non-technical voice for business-user workshops: every step gives the exact prompt to type, followed by a "You'll see" panel; modules end with outcome-based checkpoints.