Skip to content
This repository was archived by the owner on May 29, 2026. It is now read-only.

feat(openregister): retell integrations in consumer language#54

Merged
rubenvdlinde merged 1 commit into
developmentfrom
feature/openregister-integrations-consumer
May 18, 2026
Merged

feat(openregister): retell integrations in consumer language#54
rubenvdlinde merged 1 commit into
developmentfrom
feature/openregister-integrations-consumer

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Collaborator

Summary

The 'How OpenRegister plugs into the workspace' Showcase used internal vocabulary ('leaves', category names like 'Core/Communication/Knowledge/Workflow/External') and described the integration as just a sidebar surface. Rewrite for commercial readers.

  • Eyebrow: 'Integrations'. 'Leaves' stays in product docs and ADRs only; commercial copy uses 'integrations'.
  • Title: 'Apps that truly work together.' Frame the story as turning an office suite into a workspace.
  • Lede names all three integration levels: sidebar tabs, dashboard widgets, and the shared service layer that lets one app call another's data.
  • Item titles describe outcomes, not category names:
    • 'Your CRM uses your real contacts and calendar.'
    • 'Open a ticket or lead straight from a Talk message.'
    • 'Project knowledge, attached to the project.'
    • 'Outside systems, in the same fabric.'
  • Each summary leads with a concrete app-to-app use case (mail-to-project, lead-from-Talk, CRM-reads-Contacts) before naming the underlying Nextcloud apps.

Test plan

  • Local dev server: /apps/openregister/#integrations renders new titles
  • Default-open item shows the files/mail/shares story with the right CTA
  • Lede mentions sidebar / widget / service layer

Previous Showcase used internal vocabulary ("leaves", "core/communication/
knowledge/workflow/external") and described the integration as just a
sidebar surface. Rewrite for commercial readers:

- Eyebrow: 'Integrations' (the term consumers use; 'leaves' stays in
  product docs and ADRs only).
- Title: 'Apps that truly work together.' Frame the story as turning an
  office suite into a workspace.
- Lede: name all three integration levels (sidebar tabs, dashboard
  widgets, shared service layer that lets one app call another's data).
- Item titles describe outcomes, not category names: 'Your CRM uses your
  real contacts and calendar', 'Open a ticket or lead straight from a
  Talk message', 'Project knowledge, attached to the project', 'Outside
  systems, in the same fabric'.
- Each summary leads with a concrete app-to-app use case (mail-to-
  project, lead-from-Talk, CRM-reads-Contacts) and explains the
  integration without naming the internal slot.
@rubenvdlinde rubenvdlinde merged commit 4f4a207 into development May 18, 2026
3 checks passed
@rubenvdlinde rubenvdlinde deleted the feature/openregister-integrations-consumer branch May 18, 2026 05:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant