Skip to main content

Change Log (Platform)

Index of larger product and system deliveries — for review by the team, editorial, and operations. Technical details are available on the linked pages.

(New entries at the top; format as per .cursor/rules/documentation-narrative-and-ops.mdc.)

2026-06-04 — Social Caption AI: Platform Rules & Center Context​

What: Caption generator utilizes platform-specific hashtag rules (Facebook without tags; Instagram 3–5; FB+IG optional first comment). Prompts in social-caption-prompts.ts; API loads shops, events, offers, news from the database according to the brief.

Why: Hashtags only where they are effective; better texts through real center data instead of generic phrases.

Links: Social Media Approval

2026-06-04 — Alert Variants (Dashboard, Round 7)​

What: Wayfinding SVG upload, shop mapping list, center profile (team & workflows), offers AI, header/footer colors, property automation, integration suites, notifications, file upload, theme upload.

Why: Further standardization of the notification UI in the dashboard.

Links: Mall-OS UI — Notifications

2026-06-04 — Alert Variants (Dashboard, Round 6)​

What: Admin setup, center page sync, app settings modal, homepage tiles, emergency manager, wayfinding, embed chat, reservations, plugin migration. PageContainer for Services Quick Setup and organization details.

Why: Continuation of a unified notification UI and page shell.

Links: Mall-OS UI — Notifications

2026-06-04 — Alert Variants (Dashboard, Round 5)​

What: Dispatch details, MEC import (media notice), shop mapping map, domains, WordPress connect/import, center plan Google Maps notice, chatbot analytics, reviews sentiment. Digital experience theme pages on PageContainer.

Why: Further UI standardization without manual color overrides.

Links: Mall-OS UI — Notifications

2026-06-04 — Alert Variants instead of Color Overrides (Dashboard, Round 4)​

What: About 20 additional locations: Social editor/approval board, QR management, Google Places, CM apps settings, workflow rejection, website settings (digital experience) including PageContainer + DNS notice as Alert.

Why: Continuation of UI standardization; fewer manual color classes.

Links: Mall-OS UI — Notifications

2026-06-04 — Alert Variants instead of Color Overrides (Dashboard)​

What: About 50 locations with manual border-*-200 bg-*-50 changed to Alert/Card to Alert variants (default, warning, destructive, success). Hub cards (settings, system) use normal Card + --shadow-card-hover. New variant success in @mall-os/ui.

Why: Uniform notification design without duplicated Tailwind colors.

Links: Mall-OS UI — Notifications

2026-06-04 — News Performance (Umami/DB/OpenAI) & Card Shadows​

What: News detail shows real views (Umami per news URL, fallback DB), shares from DB, SEO/readability scores (rule-based, optionally OpenAI). Central --shadow-card token for all Card components.

Why: No more placeholder metrics; cards clearly stand out from the page background.

Links: Mall-OS UI · API: GET/POST /api/content/news/{id}/performance

2026-06-04 — Dashboard: Settings & WP Content Areas (PageContainer)​

What: Users (New/Edit), Roles, Feedback Detail, Communication Redirect, WP Content Areas Detail/Edit on PageContainer. Design tokens in community and WordPress hub.

Why: Uniform dashboard shell in admin and WordPress areas.

2026-06-04 — Dashboard: Edit Routes & PageContainer (Continuation)​

What: Content editing under canonical path /content/{type}/{id}/edit (Offers, Shops, Services, Jobs, Hot Picks, Shop Chains, Shop Locations, Centers); old edit/[id] URLs redirect. Integration, WordPress Content Areas on PageContainer; scheduling/broadcast/content areas: gray-*/blue-* → Design tokens.

Why: Uniform URLs and visual shell as with events/news; fewer hardcoded colors.

2026-06-04 — Dead Code Cleanup (Dashboard)​

What: Removed: API .backup files, api/_disabled/**, WordPress *.old pages, unused Unified Website Builder, dev route test-bunny, dead nav configs. Demo stubs /dashboard/events|shops|jobs → redirects to /dashboard/content/*. Marketing/community links corrected.

Why: Less confusion, no duplicated/obsolete UIs in the repo. Remaining React page builder paths are documented in deprecated-navigation.ts.

2026-06-04 — Content Forms & Dashboard Page Layout​

What: News, Events, and Offers (New and Edit) use the same 3-step pattern (Content → Publish → Optional). Additional dashboard pages on PageContainer: Center plans (Overview + New), Team Management, Scheduling, Video Scheduling, Broadcast Messages, WordPress Hub.

Why: Unified editorial workflow; fewer disparate special layouts and hardcoded colors.

Links: Content Creator Manual

2026-06-04 — Dashboard UI: Tabs, Website Navigation, News Form​

What: Uniform tab styles via design tokens (@mall-os/ui, no more hex overrides). Website tab: collapsible main groups + search in the sidebar. New News: form in three steps (Content → Publish → Optional).

Why: Reduced visual inconsistency and cognitive load for editors in daily operations.

Who: Editorial, Center Operations (Dashboard).

Links: Website Tab Navigation · Content Creator Manual → News

Testing: Any page with tabs (e.g., Social) → active tab uses primary color. Center → Website → expand/collapse groups, search. Content → News → New → navigate through three tabs, save.

2026-06 — Documentation Target Audiences (Guideline) & Dev Start​

What: Mandatory classification Editorial / Decision Makers / Developers; Start Development for Cursor/MCP; homepage docs separated by target audience.

Why: One documentation for three completely different uses — without guidelines, v0 onboarding and API contracts mix.

Links: Documentation Target Audiences · Start Editorial · Start Development

2026-06 — Documentation: Appearance, Homepage, EN Workflow​

What: Homepage with three target audience cards; streamlined CSS (navbar, tables, sidebar); instructions Multilingual Documentation with docusaurus-i18n + npm run docs:translate.

Why: Clearer entry point; EN for international partners — OpenAI as in the cockpit, translations versioned in i18n/en/.

Links: Documentation i18n · Documentation Target Audiences

2026-06 — Investors & Partners (Platform Proof)​

What: A dedicated area for executive level (owners, operators, partners, VCs): decision maker page, maturity & operations, due diligence checklist. Navbar/footer Platform leads there.

Why: Editorial documentation alone does not convey "fundable platform" — investors need architecture, maturity, and market arguments without technical overload.

Links: Investors & Partners · Due Diligence

2026-06 — Editorial: Start here & Onboarding Short Paths​

What: Start here (New to the Team) page plus short paths for Center Website (v0), Social (Outstand) and Claude/MCP (later). Editorial sidebar: first checklists, details collapsed. References from intro, topic finder, and long-form pages.

Why: Main users are newcomers — v0, MCP, and Outstand should not be mentioned together; clear sequence instead of 80-link tree.

Who: New editors, team leadership onboarding.

Links: Start here · Website v0 Short Path · Social Introduction

2026-06 — Documentation Navigation (Sidebar by Role)​

What: Docusaurus navbar with sections Editorial, Dashboard, Center Website, Signage & Apps, Developers, Templates, Platform — each with a separate, short sidebar. Start hub now only has intro, topic finder, and platform overview.

Why: The previous mainSidebar with 80+ entries was confusing for editorial (dev/MEC checklists mixed in the same tree).

Who: All users of the documentation at docs.cockpit-os.de.

Links: Start · Maintenance: cockpit-docs/sidebars.ts, docusaurus.config.ts

2026-06 — Dashboard Control Center & Social Cockpit (Module)​

What: Homepage /dashboard as an operational control center (Task Inbox, Planner, Center Status, API GET /api/dashboard/home). Social Cockpit as its own sidebar module with hub, approvals (/dashboard/social/approvals), engage, and reporting — separate from the website workflow. Separation Center Website (CockpitOS) vs. WordPress (Plugin) in the navigation.

Why: Faster daily operations per center; social not mixed with website drafts in one list.

Who: Editorial, Center Manager, Org Marketing (Dashboard); operations unchanged towards Outstand/Env.

Links:

Testing: Select center in the switcher → /dashboard (counter clickable) → Social Cockpit → Approvals; website draft only under workflow.

2026-05-22 — Social Cockpit Shell & Hub "Today"​

What: Uniform SocialPageShell with subnav on all core pages; hub shows Today for you (KPIs + quick actions) instead of just tiles. API GET /api/social/hub.

Why: Social feels like a coherent cockpit module within the CockpitOS universe — orientation without feature overload.

Who: Editorial, Center Manager, Marketing.

Links: Social Media Approval, Navigation

2026-05-21 — Social / Outstand (Webhooks, Metrics, Publish)​

What: Outstand integration expanded: channel status in approvals, webhooks (post.published, post.error, account.token_expired), first comment after going live, reels/carousel publish, daily metric sync via cron.

Why: More reliable publishing (including images via containers[].media), faster error detection and reporting without manual updates in Outstand.

Who: Editorial/Social (Approval UI), Operations/IT (Env, Webhook, Cron).

Links:

Operation: OUTSTAND_API_KEY, optional OUTSTAND_WEBHOOK_SECRET, CRON_SECRET; webhook URL POST …/api/webhooks/outstand.

2026-05 — Platform Overview & Documentation Rules​

What: Platform page (DE/EN context overview), mandatory cursor rules for system documentation and this change log.

Why: A common "reference" for what CockpitOS is and what has changed when — not just developer API lists.

Links: Platform Overview

Older deliveries to be added gradually as a page is worked on anyway — no big-bang backfill necessary.

Nutzungsstatistik: Seitenaufrufe werden anonymisiert erfasst. Im Umami-Dashboard nach diesem Pfad filtern: /en/plattform/changelog