chore: drop OpenTalk references from connext page#33
Conversation
We are no longer supporting OpenTalk as an integrated ExApp, so remove it from the platform overview, the ExternalAppShelf, and the app-downloads dataset. Rewrites the 'Why through the app store?' paragraph to keep the Nextcloud Talk pitch without the OpenTalk-on- Matrix alternative.
Review — chore: drop OpenTalk references from connext pageVerdict: 🟢 APPROVE — Clean sweep — alle OpenTalk-verwijzingen weg uit drie targetbestanden, JSON-validiteit bevestigd, NL/EN-pariteit klopt, CI volledig groen. Wat goed gaatVolledige cleanup-PR: drie bestanden raken alle OpenTalk-references in één keer. PR body bevat een nette scope-note over de design-system follow-up en een concrete test plan. NL- en EN-pariteit klopt (NL had alleen de IntegratedApps-entry, en die is geraakt). CI is volledig groen. Findings1. 🟢 Minor — Design-system follow-up correct uit-scope —
|
MWest2020
left a comment
There was a problem hiding this comment.
Zie consolidated review comment voor complimenten, findings en suggested fixes.
Summary
/connextExternalAppShelf, and theapp-downloads.jsondataset (both EN and NL connext pages)Scope note
Website-only sweep. The design-system repo still ships an
opentalkIntegrationIcon registry entry, brand SVG, taalgebruik glossary line, and preview pages (ExternalAppShelf / platform-overview / landing). Those will need a follow-up if/when the design-system content flows back into the live site.Test plan
npm run buildsucceeds (Docusaurus)/connext(EN) renders without the OpenTalk card in the integrated apps list/connext(EN) ExternalAppShelf no longer shows OpenTalk/connext(EN) "Why through the app store?" paragraph reads cleanly without the OpenTalk-on-Matrix sentence/nl/connextrenders without the OpenTalk carddata/app-downloads.jsonremains valid JSON