Settings: Replace plugin jargon with feature names #921

Open
opened 2026-10-02 17:40:09 +00:00 by kayg · 0 comments
Owner

Rule: use plugin only when needed, and explain it. Settings should use plain names.

Findings and proposed copy:

  • apps/web/src/routes/settings/sections.ts:131,135,147,152: Plugins / Optional plugins → Features / Optional Features.
  • apps/web/src/routes/settings/plugins/PluginsSection.svelte:132: Enable optional plugins for this instance. → Turn on optional features for this Instance.
  • :134-135,143,145: Core and Optional plugins → Built-in Features and Optional Features.
  • :96,165,169: change plugin state, Loading plugins…, Retry loading plugins, and No plugins are available on this server. → use feature wording, for example change feature status, Loading features…, Retry loading features, and No optional features are available on this Instance.
  • :175-176,191: Disable plugin?, Disable plugins, and {name} is required by these enabled Plugins → Turn off this feature?, Turn off features, and This feature needs these features to stay on: {names}.
  • apps/web/src/lib/components/search-dialog.svelte:893: enable the AI plugin → turn on AI in Settings.
  • apps/web/src/lib/composer/Composer.svelte:673: The Calendar plugin is off → Calendar is turned off.
  • apps/web/src/routes/money/+page.svelte:92: Money is off for this Instance. Ask an Admin to enable Money in Settings → Plugins. → Money is turned off for this Instance. Ask an Admin to turn it on in Settings → Features.

Expected: Settings names and related messages describe features the User can turn on. Keep the current access controls and feature behavior.

Test idea: check the Settings navigation, feature list, disable confirmation, Search no-options state, Calendar composer error and Money empty state. Check that no visible message uses plugin without a plain explanation.

Rule: use `plugin` only when needed, and explain it. Settings should use plain names. Findings and proposed copy: - `apps/web/src/routes/settings/sections.ts:131,135,147,152`: `Plugins` / `Optional plugins` → `Features` / `Optional Features`. - `apps/web/src/routes/settings/plugins/PluginsSection.svelte:132`: `Enable optional plugins for this instance.` → `Turn on optional features for this Instance.` - `:134-135,143,145`: `Core` and `Optional plugins` → `Built-in Features` and `Optional Features`. - `:96,165,169`: `change plugin state`, `Loading plugins…`, `Retry loading plugins`, and `No plugins are available on this server.` → use `feature` wording, for example `change feature status`, `Loading features…`, `Retry loading features`, and `No optional features are available on this Instance.` - `:175-176,191`: `Disable plugin?`, `Disable plugins`, and `{name} is required by these enabled Plugins` → `Turn off this feature?`, `Turn off features`, and `This feature needs these features to stay on: {names}.` - `apps/web/src/lib/components/search-dialog.svelte:893`: `enable the AI plugin` → `turn on AI in Settings`. - `apps/web/src/lib/composer/Composer.svelte:673`: `The Calendar plugin is off` → `Calendar is turned off`. - `apps/web/src/routes/money/+page.svelte:92`: `Money is off for this Instance. Ask an Admin to enable Money in Settings → Plugins.` → `Money is turned off for this Instance. Ask an Admin to turn it on in Settings → Features.` Expected: Settings names and related messages describe features the User can turn on. Keep the current access controls and feature behavior. Test idea: check the Settings navigation, feature list, disable confirmation, Search no-options state, Calendar composer error and Money empty state. Check that no visible message uses `plugin` without a plain explanation.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal#921
No description provided.