Core AI integration for Etherpad: authorship analysis, LLM client, access control.
- Etherpad plugin framework (hooks declared in
ep.json) - EJS templates rendered server-side via
eejsBlock_*hooks - html10n for i18n (
locales/<lang>.json,data-l10n-idin templates)
ep_ai_core/
├── AGENTS.md
├── CONTRIBUTING.md
├── accessControl.js
├── admin.js
├── authorship.js
├── ep.json
├── i18n.js
├── index.js
├── llmClient.js
├── locales/
│ ├── en.json
├── package.json
├── static/
│ ├── tests/
├── templates/
│ ├── admin.html
None — ep_plugin_helpers is not a dependency. Adoption is part of the helpers-adoption sweep (Phase 4).
To be audited in the helpers-adoption sweep (Phase 4).
ep_ai_core runs inside Etherpad's test harness. From an etherpad checkout that has installed this plugin via pnpm run plugins i --path ../ep_ai_core:
# Backend (Mocha) — harness boots its own server
pnpm --filter ep_etherpad-lite run test
# Playwright — needs `pnpm run dev` in a second terminal
pnpm --filter ep_etherpad-lite run test-ui- PRs target
main. Linear commits, no merge commits. - Every bug fix includes a regression test in the same commit.
- All user-facing strings in
locales/. No hardcoded English in templates. - No hardcoded
aria-labelon icon-only controls — etherpad's html10n auto-populatesaria-labelfrom the localized string when (a) the element has adata-l10n-idand (b) no author-suppliedaria-labelis present. Adding a hardcoded Englisharia-labelblocks that and leaves it untranslated. (Seeetherpad-lite/src/static/js/vendors/html10n.ts:665-678.) - No nested interactive elements (no
<button>inside<a>). - LLM/Agent contributions are explicitly welcomed by maintainers.
- Server:
loadSettings,init_ep_ai_core,expressCreateServer
When adding a hook, register it in both ep.json and the matching exports.<hook> = ... in the JS file.