@cplace/mcp-server 1.3.14

package/dist/widget-specifications/cf.platform.files/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.platform.files",
+  "Description": "{\"en\":\"Allows you to upload files to the page and lists all attachments in a table.\",\"de\":\"Ermöglicht das Hochladen von Dateien in die Seite und listet alle Dateianhänge tabellarisch auf.\"}",
+  "Localized Name": "{\"en\":\"Files\",\"de\":\"Dateien\"}",
+  "Icon": "fa-upload",
+  "Plugin": "cf.cplace.platform",
+  "App": "cf.cplace.platform",
+  "Localized App Name": "{\"en\":\"cplace Basis\",\"de\":\"cplace Basis\"}",
+  "Repository": "cplace",
+  "* Details DE": null,
+  "* Details EN": "<p><strong>More Details</strong></p>\n\n<p>The 'Files' widget allows you to upload and attach files to a cplace page or to an attribute of the type of the page. All uploaded file attachments of a page are then displayed in a tabular form.</p>\n\n<p><strong>Prerequisites</strong></p>\n\n<p>A table must be embedded in the page.</p>\n\n<p><strong>Settings</strong></p>\n\n<p>// * Title: Bilingual text.</p>\n\n<p>// * Table:</p>\n\n<p>// * Attribute to attach files to. Leave empty to attach to embedding page.</p>\n\n<p>&nbsp;</p>\n\n<p>&nbsp;</p>"
+}

package/dist/widget-specifications/cf.platform.files/_meta.json

@@ -0,0 +1,10 @@
+{
+  "tags": [
+    "files",
+    "media",
+    "inline-edit",
+    "drag-drop",
+    "detail-view"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/cf.platform.files/_overview.md

@@ -0,0 +1,74 @@
+## Overview
+
+Allows you to upload files to the page and lists all attachments in a table.
+
+The Files widget provides file attachment and management functionality for any cplace page. It enables users to upload, view, and manage files associated with a page through a simple list interface.
+
+**Use when**: You need to let users attach, view, or manage files on a page. This is the standard approach for any file handling needs.
+
+**Alternatives**: For visual presentation of documents with thumbnails and preview capabilities, consider the Image Gallery widget, which displays the same files in a more visual format.
+
+## Use Cases
+
+### Document Collection
+Pages that serve as repositories for related documents benefit from a files widget. Examples include project documentation pages, meeting minutes with supporting materials, or specification pages with technical attachments.
+
+### Supporting Materials
+When the primary content is something other than files (like a description, table, or diagram), but users still need to attach supporting materials, the files widget provides this capability without dominating the layout.
+
+### Upload Entry Point
+In layouts where users primarily interact with files through a visual gallery, the files widget often serves as the upload mechanism, with the gallery providing the viewing experience.
+
+## Behavior and Capabilities
+
+The Files widget operates on the page's built-in attachment system. Unlike table widgets that require data source configuration, the files widget automatically displays all files attached to the page where it's placed.
+
+**Automatic Scoping**: The widget is inherently scoped to its embedding page. There's no need to configure filters or references - it simply shows the current page's files.
+
+**List-Based Display**: Files appear in a list format showing filename and relevant metadata. This is efficient for many files but doesn't provide visual previews.
+
+**Upload Capability**: Users with write permission can upload files directly through the widget. This is always available and doesn't require configuration.
+
+**Immediate Synchronization**: When files are uploaded or removed, changes reflect immediately across any widgets displaying the same files (such as a paired gallery widget).
+
+## Design Considerations
+
+### When Files Widget Works Well
+
+- Pages where file management is a supporting feature rather than the primary focus
+- Situations requiring straightforward upload and list functionality
+- Layouts where space is limited and a compact file list is preferable to visual thumbnails
+
+### When to Consider Alternatives
+
+- When visual document preview is important (pair with or use gallery widget)
+- When files need to be categorized or filtered by type (consider separate pages or structured attributes)
+- When files relate to multiple items and need relationship tracking (consider a document management type with proper references)
+
+### Layout Positioning
+
+The files widget doesn't require full width since it displays a simple list. Half-width or narrower placements work well, leaving room for other content. Common patterns include:
+
+- Pairing with comments in a utilities section at page bottom
+- Placing alongside a document gallery (smaller widget for upload, larger gallery for viewing)
+- Using in a dedicated attachments tab for pages with many files
+
+### Single Instance Principle
+
+One files widget per layout is sufficient. Multiple instances would show the same files, creating redundancy without adding value.
+
+### Permission Dependency
+
+Upload functionality depends on the user having write permission on the page. Read-only users can view and download files but cannot add or remove them.
+
+## Related Widgets
+
+### Image Gallery
+The gallery widget displays the same page attachments with visual thumbnails and preview capabilities. Files and gallery widgets are complementary:
+- Files widget: List format, upload functionality, compact
+- Gallery widget: Visual format, preview capability, requires more space
+
+Many layouts pair both widgets, using the files widget for upload and management while the gallery provides the visual browsing experience.
+
+### Comments Widget
+Files and comments are often paired in a utilities section. Both represent page-level features (attachments and discussion) that support the main content. An equal-width split is common, though layouts may favor one or the other based on relative importance.

package/dist/widget-specifications/cf.platform.files/_summary.md

@@ -0,0 +1 @@
+Allows you to upload files to the page and lists all attachments in a table. Use when users need to upload, view, and manage files in a simple list interface.

package/dist/widget-specifications/cf.platform.iframe/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.platform.iframe",
+  "Description": "{\"en\":\"Embed content from any website (as iframe)\",\"de\":\"Inhalt einer beliebigen Webseite (als iframe) einbinden.\"}",
+  "Localized Name": "{\"en\":\"Inline Frame\",\"de\":\"Inlineframe\"}",
+  "Icon": "fa-laptop",
+  "Plugin": "cf.cplace.platform",
+  "App": "cf.cplace.platform",
+  "Localized App Name": "{\"en\":\"cplace Basis\",\"de\":\"cplace Basis\"}",
+  "Repository": "cplace",
+  "* Details DE": null,
+  "* Details EN": "<p><strong>More Details</strong></p>\n\n<p>The 'Inlineframe' widget can be used to embed content from any other website into a cplace page by means of an iframe element.</p>\n\n<p><strong>Settings</strong></p>\n\n<p>// * Source URL*:</p>\n\n<p>// * Title*: Bilingual text.</p>\n\n<p>// * Height:</p>\n\n<p>&nbsp;</p>\n\n<p>&nbsp;</p>"
+}

package/dist/widget-specifications/cf.platform.iframe/_meta.json

@@ -0,0 +1,9 @@
+{
+  "tags": [
+    "media",
+    "read-only",
+    "dashboard",
+    "detail-view"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/cf.platform.iframe/_overview.md

@@ -0,0 +1,77 @@
+## Overview
+
+Embed content from any website (as iframe). The Inline Frame widget embeds external web content directly into a cplace page using an HTML iframe. It displays content from a fixed URL specified during widget configuration, allowing users to view and interact with external websites or web applications without leaving the cplace interface.
+
+This is a **static embedding widget** - the URL is defined once during configuration and remains the same regardless of which page displays the widget. For context-dependent URLs that change based on page attributes, use the Dynamic Inline Frame widget instead.
+
+## Use Cases
+
+### External Documentation Integration
+Embed user manuals, help documentation, or tutorials from external documentation systems directly in cplace pages. Users can access reference materials without leaving their workflow.
+
+### Dashboard Embedding
+Display real-time analytics, reports, or metrics from BI tools or monitoring systems. This creates a consolidated view where users can see data from multiple systems in one place.
+
+### Third-Party Tool Integration
+Show content from Jira, Confluence, or other third-party tools that the organization uses alongside cplace. This enables seamless integration with existing tools in the organizational ecosystem.
+
+### Map Display
+Embed maps from services like OpenStreetMap or Google Maps to show office locations, project sites, or geographic data with visual representation.
+
+### Custom Internal Applications
+Integrate specialized internal tools or custom web applications hosted within the organization. This provides a unified interface for accessing various organizational tools.
+
+### Static Hosted Content
+Display custom HTML/JavaScript visualizations or tools served from within the cplace instance using relative URLs (e.g., `/static/custom-widgets/visualization.html`).
+
+## Design Considerations
+
+### When to Use Inline Frame
+
+- **Fixed content**: The embedded content is the same for all pages and users
+- **Company-wide resources**: General documentation, shared dashboards, or common tools
+- **Simple configuration**: Just need to enter a URL without complex attribute mapping
+- **Static external content**: Content that doesn't depend on page context
+
+### When to Use Dynamic Inline Frame Instead
+
+- URLs need to include values from page attributes (e.g., project IDs, external system references)
+- Different pages should show different external content based on their data
+- The embedded content needs to be filtered or parameterized by page context
+
+### Browser and Network Requirements
+
+- External sites must allow iframe embedding (not blocked by X-Frame-Options or Content-Security-Policy headers)
+- Users must have network access to the target URL
+- HTTPS URLs are recommended to avoid mixed content warnings
+- Corporate firewalls may affect access to external URLs
+
+### Security Validation
+
+The widget includes built-in security measures:
+- JavaScript URLs are blocked to prevent XSS attacks
+- Data URLs are not allowed
+- URLs are validated against tenant-specific security policies
+- Relative URLs are automatically converted to absolute URLs using the tenant's external URL
+
+## Common Pitfalls
+
+- **External site blocks embedding**: Many websites set X-Frame-Options headers that prevent iframe embedding. If content doesn't display, check the browser console for frame-blocking errors. Consider using the Dynamic Inline Frame widget in "button mode" as an alternative.
+
+- **Mixed content warnings**: When cplace runs on HTTPS but the embedded content uses HTTP, browsers may block the content or show warnings. Always use HTTPS URLs when available.
+
+- **Network access issues**: Users may not be able to access external URLs due to corporate firewalls or VPN requirements. Verify that all intended users have network access to the embedded content.
+
+## Alternatives
+
+| Alternative | When to Consider |
+|-------------|-----------------|
+| **Dynamic Inline Frame** | URL needs to change based on page attributes |
+| **Rich String with Links** | External site blocks iframe embedding; simple link is sufficient |
+| **Low-Code Widget** | Need full control over rendering or API-based integration instead of iframe |
+
+## Related Patterns
+
+- **Documentation portal** - Use Inline Frame widgets on landing pages to embed company-wide documentation or training materials
+- **Dashboard consolidation** - Place multiple Inline Frame widgets on a dashboard page to aggregate views from different systems
+- **Tool integration hub** - Create a page with iframe widgets linking to various external tools the team uses

package/dist/widget-specifications/cf.platform.iframe/_summary.md

@@ -0,0 +1 @@
+Embed content from any website (as iframe). Use for displaying company-wide documentation, dashboards, or third-party tools without requiring users to navigate away from cplace.

package/dist/widget-specifications/cf.platform.incomingLinks/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.platform.incomingLinks",
+  "Description": "{\"en\":\"If available, this widget displays incoming links from other cplace pages.\",\"de\":\"Falls vorhanden, werden eingehende Links aus anderen cplace Seiten angezeigt.\"}",
+  "Localized Name": "{\"en\":\"Incoming Links\",\"de\":\"Eingehende Links\"}",
+  "Icon": "fa-link",
+  "Plugin": "cf.cplace.platform",
+  "App": "cf.cplace.platform",
+  "Localized App Name": "{\"en\":\"cplace Basis\",\"de\":\"cplace Basis\"}",
+  "Repository": "cplace",
+  "* Details DE": null,
+  "* Details EN": "<p><strong>More Details</strong></p>\n\n<p>The 'Incoming Links' widget lists all cplace pages having set a link to the current page in a text widget.</p>\n\n<p>// * The links are sorted by categories such as:</p>\n\n<p>// Text pages in</p>"
+}

package/dist/widget-specifications/cf.platform.incomingLinks/_meta.json

@@ -0,0 +1,10 @@
+{
+  "tags": [
+    "references",
+    "list",
+    "read-only",
+    "navigation",
+    "metadata"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/cf.platform.incomingLinks/_overview.md

@@ -0,0 +1,83 @@
+## Overview
+
+If available, this widget displays incoming links from other cplace pages. The Incoming Links widget displays all pages that reference the current page through hyperlinks in rich text fields (like description fields, comments, or other formatted text content). It provides "backlinks" functionality similar to wiki systems, helping users understand which other pages reference the current page and enabling reverse navigation through interconnected content.
+
+The widget automatically scans hyperlinks in rich text content and groups incoming links by source page type and attribute, showing the count of links from each source.
+
+## Use Cases
+
+### Content Navigation & Discovery
+Enables users to see all pages that reference the current page, helping discover related content that might not be connected through formal relationships. Supports reverse navigation from a page back to its referencing pages, creating a graph-like navigation experience through interconnected content.
+
+### Knowledge Management & Wiki-Style Usage
+Provides "What links here" functionality similar to wikis, supporting organic content organization through hyperlinks. Ideal for knowledge bases and documentation pages where discoverability through natural hyperlinks is important.
+
+### Impact Analysis
+Before deleting or archiving a page, users can see what other pages link to it. Helps understand the reach and importance of a page based on how many places reference it and identifies dependencies between content items.
+
+### Relationship Visualization
+Complements outgoing links by showing the "other side" of hyperlink relationships. Provides context about how a page fits into the broader information architecture and helps identify pages that serve as hubs with many incoming links.
+
+### Master Data & Reference Pages
+Particularly useful on pages that are frequently referenced by other content, such as products, projects, requirements, or other master data entities that other pages naturally reference in their descriptions and notes.
+
+## Design Considerations
+
+### When to Use This Widget
+
+- On pages that are frequently referenced by other content through hyperlinks
+- In knowledge management scenarios where discoverability through natural linking is important
+- For master data pages (products, projects, requirements) that other pages reference in descriptions
+- When tracking informal content relationships created through natural hyperlinks
+- To complement structured relationships with organic linking patterns
+
+### When NOT to Use This Widget
+
+- If your content model relies primarily on formal reference attributes (use Incoming References widget instead)
+- On pages where hyperlinks in rich text fields are rarely used
+- If the widget consistently shows no results (indicating no incoming links exist)
+- When only structured, schema-defined relationships are needed
+
+## Operating Behavior
+
+### Automatic Detection
+The widget requires no manual configuration and automatically scans `RichStringLink` entities where the current page is the target. It only displays links that the current user has permission to see, respecting cplace's security model.
+
+### Display Format
+Links are grouped by source page type and the attribute name where the link appears. Each group shows:
+- Source entity type with the attribute name containing the link
+- Workspace/space information if the link comes from a different space
+- Count of incoming links for each group
+
+Example display:
+```
+Project as "Related Projects" (3)
+Task as "Description" in Product Space (5)
+Meeting Notes (2)
+```
+
+### Visibility Rules
+- Shows "No incoming links found" message if no links exist
+- Only displays links from pages the user can access
+- Indicates when links come from different workspaces
+- Respects attribute restrictions based on security extensions
+
+## Related Widgets
+
+### Incoming References Widget (`cf.platform.incomingReferences`)
+Tracks formal reference attributes rather than hyperlinks. Use when you need to display structured relationships defined through reference fields in your data model. The Incoming Links widget and Incoming References widget serve complementary purposes and can coexist on the same page.
+
+**Key Differences**:
+- **Incoming Links**: Tracks hyperlinks in rich text content (informal, user-created)
+- **Incoming References**: Tracks formal reference attributes (structured, schema-defined)
+
+## Common Pitfalls
+
+### Expecting Formal References
+This widget only shows hyperlinks created in rich text fields, not formal reference attributes. If you need to display structured relationships, use the Incoming References widget instead.
+
+### Empty Widget on New Pages
+Newly created pages will show no incoming links until other pages create hyperlinks pointing to them. This is normal behavior and the widget will populate as content is created.
+
+### Confusion with Bidirectional Relationships
+This widget shows who links TO the current page (incoming), not who the current page links to (outgoing). The directionality is from other pages pointing at this page.

package/dist/widget-specifications/cf.platform.incomingLinks/_summary.md

@@ -0,0 +1 @@
+If available, displays incoming links from other cplace pages through hyperlinks in rich text fields. Enables wiki-style navigation and relationship discovery for knowledge bases, documentation pages, and impact analysis.

package/dist/widget-specifications/cf.platform.incomingReferences/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.platform.incomingReferences",
+  "Description": "{\"en\":\"If available, this widget displays references associated with other cplace pages.\",\"de\":\"Falls vorhanden, werden zugehörige Referenzen mit anderen cplace Seiten angezeigt.\"}",
+  "Localized Name": "{\"en\":\"Incoming References\",\"de\":\"Eingehende Referenzen\"}",
+  "Icon": "fa-external-link fa-rotate-90",
+  "Plugin": "cf.cplace.platform",
+  "App": "cf.cplace.platform",
+  "Localized App Name": "{\"en\":\"cplace Basis\",\"de\":\"cplace Basis\"}",
+  "Repository": "cplace",
+  "* Details DE": null,
+  "* Details EN": "<p><strong>More Details</strong></p>\n\n<p>The 'Incoming References' widget lists all references to other cplace pages.</p>\n\n<p>&nbsp;</p>"
+}

package/dist/widget-specifications/cf.platform.incomingReferences/_meta.json

@@ -0,0 +1,10 @@
+{
+  "tags": [
+    "references",
+    "list",
+    "read-only",
+    "detail-view",
+    "navigation"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/cf.platform.incomingReferences/_overview.md

@@ -0,0 +1,48 @@
+## Overview
+
+If available, this widget displays references associated with other cplace pages. The Incoming References widget provides a "backlinks" view showing where the current entity is referenced in the data model through structured reference attributes. It queries the database to identify all custom reference relationships pointing to the entity and presents them grouped by source type, attribute name, and workspace. The widget distinguishes between references with actual values (entities currently referencing this one) and available reference types without values (configured but unused references).
+
+## Use Cases
+
+- **Dependency Discovery**: Understand what depends on an entity before making changes or deletions (e.g., view a Product entity and see which Projects reference it)
+- **Impact Analysis**: Review incoming references before performing destructive operations to prevent broken references and data inconsistencies
+- **Bidirectional Relationship Navigation**: Navigate from a referenced entity back to referring entities without manual searching
+- **Data Model Analysis**: Visualize actual usage of reference attributes in the system and understand relationship patterns
+- **Cross-Space Visibility**: Identify and understand cross-workspace dependencies when entities in one workspace are referenced by entities in other workspaces
+
+## Design Considerations
+
+### When to Use This Widget
+
+Use this widget when:
+- Your data model includes formal reference attributes between entity types
+- You need to track which entities reference a particular entity
+- You want to provide users with impact analysis capabilities
+- You need bidirectional relationship navigation
+- Your content model has complex interdependencies
+
+Do NOT use this widget when:
+- You only need to display outgoing references (use attribute widgets instead)
+- You want to track wiki-style hyperlinks in rich text (use `cf.platform.incomingLinks` instead)
+- The entity type is Person (use the dedicated "myElements" widget instead)
+
+### Display Organization
+
+The widget automatically organizes references into two sections:
+- **With Values** (expanded by default): Shows reference types that have at least one referring entity
+- **Without Values** (collapsed by default): Shows configured reference types with zero referring entities, useful for discovering potential relationship opportunities
+
+### Typical Layout Patterns
+
+**Basic Relationship Discovery**: Place the widget after core attributes to show who references the current entity.
+
+**Complete Relationship View**: Combine with `cf.platform.incomingLinks` to show both formal data model relationships and informal wiki-style links.
+
+**Impact Analysis Dashboard**: Pair with embedded search widgets and connected charts to visualize relationship patterns.
+
+## Related Patterns
+
+- `cf.platform.incomingLinks` - For tracking informal rich text hyperlinks rather than formal reference attributes. Use both widgets together for complete relationship visibility.
+- `cf.platform.singleAttribute` / `cf.platform.connectedSingleAttribute` - For displaying outgoing reference attributes (what this entity references)
+- `cf.platform.embeddedSearchAsList` / `cf.platform.embeddedSearchAsTable` - For displaying filtered entity lists based on relationships
+- `cf.platform.connectedMatrix` - For visualizing two-dimensional relationships between entity types

package/dist/widget-specifications/cf.platform.incomingReferences/_summary.md

@@ -0,0 +1 @@
+If available, displays references associated with other cplace pages through formal reference attributes, organized by source type, attribute, and workspace. Use for dependency discovery, impact analysis, and bidirectional relationship navigation.

package/dist/widget-specifications/cf.platform.makeover.attributes/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.platform.makeover.attributes",
+  "Description": "{\"en\":\"Displays all attributes of the page and allows editing.\",\"de\":\"Zeigt alle Attribute der Seite an und erlaubt ihre Bearbeitung.\"}",
+  "Localized Name": "{\"en\":\"Attributes (new)\",\"de\":\"Attribute (neu)\"}",
+  "Icon": "fa-list-alt",
+  "Plugin": "cf.cplace.platform",
+  "App": "cf.cplace.platform",
+  "Localized App Name": "{\"en\":\"cplace Basis\",\"de\":\"cplace Basis\"}",
+  "Repository": "cplace",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/cf.platform.makeover.attributes/_meta.json

@@ -0,0 +1,9 @@
+{
+  "tags": [
+    "attributes",
+    "form",
+    "inline-edit",
+    "detail-view"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/cf.platform.makeover.attributes/_overview.md

@@ -0,0 +1,48 @@
+## Overview
+
+Displays all attributes of the page and allows editing. The Makeover Attributes widget is a redesigned version of the original `cf.platform.attributes` widget, providing the same core functionality with enhanced visual styling and improved user experience. It displays all attributes of a page and allows inline editing, making it the primary widget for viewing and modifying entity properties.
+
+This widget is part of the UIX (User Interface eXperience) modernization initiative and requires a feature flag to be enabled.
+
+## Use Cases
+
+### Entity Detail Pages
+Embed the widget on pages to show all properties of an entity (projects, tasks, documents, etc.) in a comprehensive, editable view.
+
+### Inline Editing Workflows
+Allow users to modify entity attributes directly within the page view without navigating to separate forms.
+
+### Data Review
+Provide a complete view of all entity data in one location for quick review and verification.
+
+## Design Considerations
+
+### Feature Flag Requirement
+This widget requires the feature flag `cplace.uix.newAttributesWidgetEnabled` to be set to `true`. When disabled, the widget cannot be embedded and will not appear in widget selection.
+
+### Entity Type Restriction
+The widget can only be embedded in `CustomEntity` page types. It cannot be used with system entities or type definitions.
+
+### Single Instance Rule
+Only one attributes widget (either this or the original) can be embedded per page to prevent duplicate attribute displays.
+
+### Migration Strategy
+The original `cf.platform.attributes` widget remains available, ensuring backward compatibility. Organizations can migrate to the makeover version when ready by enabling the feature flag.
+
+## When to Choose This Widget
+
+**Choose the makeover version when:**
+- You want the modern, improved UI for displaying attributes
+- The feature flag is enabled in your cplace instance
+- You're building new pages and want to use the latest UI components
+
+**Choose the original widget when:**
+- The makeover version is not enabled
+- You need consistency with existing pages using the old design
+- The feature flag is not yet available in your cplace version
+
+## Alternatives
+
+- `cf.platform.attributes` - The original attributes widget with classic styling
+- `cf.platform.attributesGroup` - Displays attributes organized into groups
+- `cf.platform.singleAttribute` - Displays a single attribute instead of all attributes

package/dist/widget-specifications/cf.platform.makeover.attributes/_summary.md

@@ -0,0 +1 @@
+Displays all attributes of the page and allows editing. A modernized version of the attributes widget with enhanced styling and improved UI/UX for inline viewing and editing of page properties.

package/dist/widget-specifications/cf.platform.modificationInfo/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.platform.modificationInfo",
+  "Description": "{\"de\":\"Zeigt Nutzer und Zeitpunkt der letzten Änderung an der Seite.\",\"en\":\"Shows users and the time of the last change made to the page.\"}",
+  "Localized Name": "{\"en\":\"Version Info\",\"de\":\"Versionsinformation\"}",
+  "Icon": "fa-info",
+  "Plugin": "cf.cplace.platform",
+  "App": "cf.cplace.platform",
+  "Localized App Name": "{\"en\":\"cplace Basis\",\"de\":\"cplace Basis\"}",
+  "Repository": "cplace",
+  "* Details DE": null,
+  "* Details EN": "<p><strong>More Details</strong></p>\n\n<p>The 'Version Info' widget displays the name of the user who last modified the current cplace page and the date on which this modification was made.</p>"
+}

package/dist/widget-specifications/cf.platform.modificationInfo/_meta.json

@@ -0,0 +1,9 @@
+{
+  "tags": [
+    "metadata",
+    "read-only",
+    "detail-view",
+    "collaboration"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/cf.platform.modificationInfo/_overview.md

@@ -0,0 +1,27 @@
+## Overview
+
+Shows users and the time of the last change made to the page. The Modification Info widget displays version tracking metadata for pages, providing transparency about content changes and enabling users to track page activity without requiring any configuration.
+
+The widget automatically pulls data from the platform's built-in modification tracking system, displaying the timestamp and a clickable link to the modifier's profile.
+
+## Use Cases
+
+- **Content Transparency**: Show when documentation, policies, or process descriptions were last updated so users can assess currency and relevance
+- **Collaboration Tracking**: Help teams identify who made recent changes and when the page was last touched
+- **Audit Trail**: Provide traceability for tracking page ownership, verifying when critical information was updated, and monitoring activity
+- **Content Management**: Enable administrators to identify stale content and monitor which team members are actively maintaining pages
+
+## Design Considerations
+
+This widget is designed to be unobtrusive:
+- Renders without a frame or padding
+- Typically placed at the bottom of page layouts (footer area) or in metadata sections
+- Only one instance allowed per page (enforced by the platform)
+- No configuration options - the display is standardized and automatic
+
+The minimalist design allows flexible positioning without visual clutter, making it ideal for footer areas or compact layout sections.
+
+## Related Patterns
+
+- **Attribute History Widget** (`cf.platform.attributeHistory`): Use together when you need both page-level modification tracking AND detailed attribute-level change history. Attribute History tracks changes to specific attributes over time, while Modification Info shows overall page-level last modification.
+- **Comments Widget**: Related collaboration widget for explicit user feedback and discussion, whereas Modification Info passively tracks system-generated metadata.

package/dist/widget-specifications/cf.platform.modificationInfo/_summary.md

@@ -0,0 +1 @@
+Shows users and the time of the last change made to the page, providing transparency about when and by whom page content was updated.

package/dist/widget-specifications/cf.platform.myElements/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.platform.myElements",
+  "Description": "{\"en\":\"Widget available only on the personal dashboard that displays all pages that have a relation to the current user.\",\"de\":\"Nur auf dem persönlichen Dashboard verfügbares Widget, das alle Seiten anzeigt, die eine Relation zum aktuellen Nutzer haben.\"}",
+  "Localized Name": "{\"en\":\"My Elements\",\"de\":\"Meine Elemente\"}",
+  "Icon": "fa-user",
+  "Plugin": "cf.cplace.platform",
+  "App": "cf.cplace.platform",
+  "Localized App Name": "{\"en\":\"cplace Basis\",\"de\":\"cplace Basis\"}",
+  "Repository": "cplace",
+  "* Details DE": null,
+  "* Details EN": "<p><strong>More Details</strong></p>\n\n<p>// The 'My Elements' widget ...</p>"
+}

package/dist/widget-specifications/cf.platform.myElements/_meta.json

@@ -0,0 +1,10 @@
+{
+  "tags": [
+    "references",
+    "list",
+    "read-only",
+    "detail-view",
+    "dashboard"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/cf.platform.myElements/_overview.md

@@ -0,0 +1,69 @@
+## Overview
+
+Widget available only on the personal dashboard that displays all pages that have a relation to the current user. The My Elements widget displays incoming references for Person entities, showing all cplace pages that reference or are associated with a specific user. It is the Person-specific variant of the Incoming References widget (`cf.platform.incomingReferences`), designed exclusively for Person pages and type definitions that apply to Person.
+
+This widget automatically scans and presents all pages where the Person is referenced through formal reference attributes, providing users with a complete picture of their involvement across the system. The standard Incoming References widget explicitly forbids embedding in Person pages with the message "Not embeddable in person; use myElements widget instead."
+
+## Use Cases
+
+### Personal Dashboard
+Display all pages and entities that reference a specific user on their profile page, giving users immediate visibility into their associations.
+
+### User Activity Overview
+Show projects, tasks, documents, and other entities associated with a person, helping them understand their scope of involvement.
+
+### Accountability Tracking
+Identify all items where a person is mentioned, assigned, or referenced, useful for workload assessment and responsibility mapping.
+
+### Relationship Visualization
+Help users understand their connections across the cplace system, revealing how they relate to various entities and workflows.
+
+## Design Considerations
+
+### When to Use This Widget
+
+- On Person profile pages to show user involvement across the system
+- On type definitions that apply to Person entities
+- When building personal dashboards or user-centric views
+- To provide accountability and relationship visibility for users
+- As the standard (and only) way to display incoming references on Person entities
+
+### When NOT to Use This Widget
+
+- On non-Person entities (the widget enforces Person entity restrictions)
+- If you need to customize how references are displayed (this widget has no configuration options)
+- When you need to show hyperlinks from rich text fields rather than formal reference attributes (use Incoming Links widget)
+
+### Technical Constraints
+
+- **Single Instance Only**: Cannot be embedded multiple times on the same Person page
+- **Person Entities Only**: Enforced at the widget definition level; only embeddable in Person or applicable type definitions
+- **No Configuration**: Works out-of-the-box without user-configurable options
+- **Read-Only**: Displays references but does not provide editing capabilities
+- **Widget Embedding Only**: Cannot be embedded in other embedding contexts
+
+## Related Widgets
+
+### Incoming References Widget (`cf.platform.incomingReferences`)
+The standard incoming references widget for non-Person entities. It explicitly prohibits embedding in Person pages. Both widgets share the same underlying rendering mechanism (`incomingReferences()` template function).
+
+**Key Differences**:
+- **My Elements**: Person-specific, no configuration options
+- **Incoming References**: General-purpose for non-Person entities, more configuration options available
+
+### Incoming Links Widget (`cf.platform.incomingLinks`)
+Tracks hyperlinks in rich text content rather than formal reference attributes. Can be used alongside My Elements on a Person page to show both types of relationships - formal references (My Elements) and informal hyperlinks (Incoming Links).
+
+### Wiki Widget (`cf.platform.wiki`)
+Often used alongside My Elements on Person pages to display descriptive content. While My Elements shows references, Wiki provides rich text content.
+
+## Common Pitfalls
+
+### Using Incoming References Instead
+The standard Incoming References widget explicitly blocks embedding on Person pages. If you need to show incoming references for a Person, you must use My Elements.
+
+### Expecting Configuration Options
+This widget has no configurable attributes. It automatically displays all incoming references to the Person entity without filtering or customization.
+
+### Multiple Widget Instances
+Attempting to add the widget multiple times to the same page will fail. The widget enforces single-instance embedding.

package/dist/widget-specifications/cf.platform.myElements/_summary.md

@@ -0,0 +1 @@
+Widget available only on the personal dashboard that displays all pages that have a relation to the current user. Use on Person profile pages as the Person-specific variant of the Incoming References widget.