@cplace/test-mcp-server 1.0.0 → 1.1.0

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

@@ -0,0 +1,39 @@
+## Overview
+
+Shows the content of a Rich String attribute and enables you to edit this content using a WYSIWYG editor.
+
+The Custom Rich String Attribute widget renders formatted text content stored in RichString attributes of custom entities. It displays the attribute value with all HTML formatting intact, including bold, italic, lists, links, headings, and other rich text elements.
+
+The widget offers two display modes: framed (with a visible border and the attribute's localized name as the title) or frameless (for seamless content integration into the page layout).
+
+## Use Cases
+
+- **Formatted descriptions** - Display project descriptions, requirement documentation, or detailed explanations with preserved formatting
+- **Rich text notes** - Show user-entered notes that include styling like lists, links, and emphasis
+- **Content sections** - Present detailed information that benefits from headings, bullet points, and structured formatting
+- **Inline documentation** - Embed formatted explanatory text within page layouts
+
+## Design Considerations
+
+### When to Use
+
+- The attribute contains formatted text that loses meaning without its formatting
+- You want to display a single RichString attribute prominently
+- The content should be read-only (no direct editing from the widget)
+
+### Frame vs Frameless
+
+- **With frame** (`showFrame: true`): Creates visual separation, displays the attribute's localized name as a title. Best when the content is a distinct section.
+- **Frameless** (`showFrame: false`): Content integrates seamlessly into the page. Best for inline content where visual boundaries are unwanted.
+
+### Limitations
+
+- Only works with attributes that have a RichString constraint
+- Must be embedded within a custom entity context
+- Read-only display; does not support inline editing
+
+## Related Patterns
+
+- **Single Attribute Widget** (`cf.platform.singleAttribute`) - More generic widget for various attribute types; consider when you need to display non-rich-text attributes or want editing capabilities
+- **Connected Single Attribute Widget** (`cf.platform.connectedSingleAttribute`) - Use when the attribute value should come from a table selection rather than the embedding entity
+- **Attributes Widget** (`cf.platform.attributes`) - Use when you need to display multiple attributes together in a group

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

@@ -0,0 +1 @@
+Shows the content of a Rich String attribute and enables you to edit this content using a WYSIWYG editor. Provides optional frame display for visual separation or seamless frameless integration.

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

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.platform.embeddedSearchAsList",
+  "Description": "{\"en\":\"Generates a list of search results sorted alphabetically.\",\"de\":\"Erzeugt eine alphabetisch sortierte Liste aus Suchresultaten.\"}",
+  "Localized Name": "{\"en\":\"List\",\"de\":\"Liste\"}",
+  "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": "<p><strong>More Details</strong></p>\n\n<p>The 'List' widget displays an alphabetically sorted list generated from search results.</p>\n\n<p><strong>Settings</strong></p>\n\n<p>// * Search*:</p>\n\n<p>// * Title: Bilingual text.</p>\n\n<p>// * Sort criterion:</p>\n\n<p>// * Sort order: Ascending/descending.</p>\n\n<p>// * Height:</p>\n\n<p>&nbsp;</p>"
+}

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

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

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

@@ -0,0 +1,66 @@
+## Overview
+
+Generates a list of search results sorted alphabetically.
+
+The Embedded Search as List widget executes a configured search query and displays the results as a simple unordered list of clickable page links. It provides a lightweight alternative to table-based widgets when you only need to show page names without additional columns or complex formatting.
+
+The widget automatically sorts results alphabetically when no custom sort is specified and no full-text search is used. Full-text searches use relevance scoring by default.
+
+## Use Cases
+
+### Navigation Lists
+- Quick navigation menus based on dynamic queries
+- Recently modified pages
+- Favorited or tagged items
+- Pages within a specific workspace
+
+### Related Content Display
+- Child pages of the current page
+- Related documents or tasks
+- Team members or stakeholders
+- Items in a specific category
+
+### Embedded Dynamic Content
+- Include dynamic lists within documentation
+- Show related references in description fields
+- Embed contextual search results in rich text content
+
+### Lightweight Result Display
+- When only page names and links are needed
+- Mobile-friendly simple lists
+- Filtered content views by status, category, or type
+
+## Design Considerations
+
+### Result Limitations
+The widget displays up to 1000 results. When results exceed this limit, an informational message indicates that only the first 1000 results are shown. For larger datasets requiring pagination, consider the table widget instead.
+
+### Sorting Behavior
+- Custom sort column and order can be configured
+- Without custom sort and without text search: alphabetical sorting applied
+- With text search: relevance-based sorting preserved
+
+### Empty State Handling
+When the search returns no results, a "No results" message is displayed.
+
+## Common Pitfalls
+
+- Using this widget for datasets exceeding 1000 items where users need to see all results
+- Choosing this widget when multiple attributes per result need to be displayed
+- Expecting interactive filtering capabilities (use connected table filter pattern instead)
+
+## Alternatives
+
+| Scenario | Recommended Widget |
+|----------|-------------------|
+| Need column-based data display | `cf.platform.embeddedSearchAsTable` |
+| Need user-controlled filtering | `cf.platform.embeddedSearchAsTable` with `cf.platform.connectedTableFilter` |
+| Need to show backlinks to current page | `cf.platform.incomingReferences` |
+| Large datasets requiring pagination | `cf.platform.embeddedSearchAsTable` |
+| Visual data representation | Chart widgets (pie, bar) |
+
+## Related Patterns
+
+- **Search-based widgets**: Part of a family including table, chart, and matrix variants that share search configuration but differ in presentation
+- **Rich text embedding**: Can be embedded within rich string attributes for inline dynamic content
+- **Master-detail**: Unlike the table widget, this widget does not support selectable items for master-detail patterns

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

@@ -0,0 +1 @@
+Generates a list of search results sorted alphabetically. Ideal for navigation lists, related items, and embedded dynamic content where tabular formatting is unnecessary.

package/dist/widget-specifications/cf.platform.embeddedSearchAsList/search.md

@@ -0,0 +1,8 @@
+**Warning**: Do not manually construct search JSON!
+
+**Correct Usage**: Use the cplaceJson field from cplace_search_pages response
+
+**Workflow**:
+1. Call cplace_search_pages with your desired filter
+2. Take the cplaceJson field from the response
+3. Use that value for the search configuration

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

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.platform.embeddedSearchAsTable",
+  "Description": "{\"en\":\"Generates a table of search results.\",\"de\":\"Erzeugt eine Tabelle aus Suchergebnissen.\"}",
+  "Localized Name": "{\"en\":\"Table\",\"de\":\"Tabelle\"}",
+  "Icon": "fa-table",
+  "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 'Table' widget can be used to display the results of a search in tabular form.</p>\n\n<p><strong>Settings</strong></p>\n\n<p>// * Search*:<br>\n// * Title: Bilingual text.<br>\n// * Columns:<br>\n// * Filters<br>\n// * Connected table:<br>\n// * Single spaced display*:<br>\n// * Show actions*:<br>\n// * Show header*:<br>\n// * Disable links in name column*:<br>\n// * Hide names*:<br>\n// * Sorting<br>\n// * Show \"New\" button*:<br>\n// * Height:</p>\n\n<p><strong>Key Benefits</strong></p>\n\n<p><strong>Examples</strong></p>"
+}

package/dist/widget-specifications/cf.platform.embeddedSearchAsTable/_implementation.md

@@ -0,0 +1,10 @@
+**Configuration Modes**:
+- `search`: Query pages via embedded search (most common)
+  - Requires: `search` attribute with cplaceJson from `cplace_search_pages`
+- `connectedTable`: Display data from another table widget on the page
+  - Requires: `connectedTableWidgetId` pointing to the source widget
+
+**Typical Configuration Workflow**:
+1. Configure either `search` or `connectedTableWidgetId`
+2. Define visible columns via `columns` attribute
+3. Optionally configure sorting (`multiSortColumns`), filtering (`filters`), and grouping (`groupColumn`)

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

@@ -0,0 +1,11 @@
+{
+  "tags": [
+    "table",
+    "searchable",
+    "filterable",
+    "sortable",
+    "selectable",
+    "navigation"
+  ],
+  "requiredApp": null
+}

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

@@ -0,0 +1,109 @@
+## Overview
+
+Generates a table of search results.
+
+The Embedded Search Table displays a filtered list of pages in a tabular format. It is the most versatile and commonly used widget for presenting collections of data in cplace.
+
+**Use when you need to:**
+- Show a list of pages matching certain criteria
+- Enable users to browse, sort, and select from a collection
+- Create master-detail interactions between widgets
+- Display related entities on a page detail view
+
+**Alternatives:**
+- **New Table Widget** - Modern alternative with different feature set
+- **Embedded Search as List** - Simpler card-based display without columns
+
+## Operating Modes
+
+### Standalone Mode
+
+The table operates independently, showing results based on its own search criteria. This is the simplest mode—define what pages to show, and the table displays them.
+
+**Typical scenarios:**
+- A list of all active projects in a workspace
+- Showing open tasks assigned to the current user
+- Displaying recent documents matching a category
+
+### Master Mode
+
+The table serves as a selection source for other widgets. When a user selects a row, connected widgets update to show related information.
+
+**Typical scenarios:**
+- Project list where selecting a project updates charts and detail panels
+- Resource list driving a capacity timeline view
+- Category browser controlling what appears in detail tables
+
+### Detail Mode
+
+The table reacts to selections made in another widget. Its contents filter dynamically based on what the user selected elsewhere.
+
+**Typical scenarios:**
+- Showing tasks belonging to a selected project
+- Displaying team members assigned to a selected department
+- Listing documents related to a selected category
+
+### Embedding Context Mode
+
+When placed on a page detail layout, the table can automatically filter to show entities related to that specific page. The table "knows" which page it's embedded on and uses that context.
+
+**Typical scenarios:**
+- On a Project page: showing all tasks belonging to this project
+- On a Person page: showing all assignments for this person
+- On a Category page: showing all items in this category
+
+## Design Considerations
+
+### When to Use Master-Detail
+
+Master-detail patterns work well when:
+- Users need to explore relationships between entities
+- The detail view would be too cluttered without context
+- There's a clear parent-child or one-to-many relationship
+
+Avoid master-detail when:
+- Each table serves an independent purpose
+- Users need to see all information simultaneously
+- The relationship between data sets isn't intuitive
+
+### Scoping to Workspace
+
+Tables should almost always be scoped to the current workspace. This prevents data leakage across workspaces and ensures users only see relevant content. Cross-workspace tables are rare and require explicit justification.
+
+### Showing Multiple Types
+
+A single table can display pages of different types. This is useful for unified views (e.g., "all requests and responses") but requires careful column selection since different types have different attributes. Include a type indicator column so users can distinguish between row types.
+
+### Negation Filters
+
+Sometimes it's easier to define what you *don't* want rather than what you do. Negation filters exclude matching items, which is useful for:
+- Showing "everything except active items" (catches future status values automatically)
+- Excluding specific categories without listing all included ones
+- Creating complementary table pairs (active vs. inactive)
+
+## Connection Patterns
+
+### Driving Charts and Visualizations
+
+Tables can drive chart widgets. When users select rows in the table, charts update to reflect that selection. This creates interactive dashboards where the table serves as a data navigator.
+
+### Cascading Detail Tables
+
+Multiple tables can form a hierarchy: Table A drives Table B, which drives Table C. This enables drill-down exploration through data relationships (e.g., Portfolio → Projects → Tasks).
+
+### Coordinated Height
+
+When tables appear side-by-side in master-detail layouts, matching their heights creates visual harmony and makes the relationship between them clearer.
+
+## Common Pitfalls
+
+- **Missing connection setup** - Detail tables need both the connection reference and the appropriate search filter; one without the other won't work
+- **Overly broad searches** - Forgetting to scope to workspace can surface unexpected data from other contexts
+- **Column mismatch** - Specifying columns that don't exist on the searched type results in empty columns
+- **Inconsistent visual treatment** - Master and detail tables with different heights or density settings look disconnected
+
+## Related Patterns
+
+- **Lifecycle Status Split** - Pair of tables showing active vs. inactive items
+- **Dashboard Context Scoping** - All widgets on a dashboard filtering relative to the dashboard page's attributes
+- **Hierarchical Drill-Down** - Cascading master-detail through multiple levels

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

@@ -0,0 +1 @@
+Generates a table of search results. Use for listing collections of data with support for master-detail interactions, column configuration, and user-driven sorting.

package/dist/widget-specifications/cf.platform.embeddedSearchAsTable/columns.md

@@ -0,0 +1,14 @@
+**JSON Format**:
+```json
+[
+  {"name": "'cf.cplace.myType.attributeName'", "visible": true},
+  {"name": "'cf.cplace.myType.otherAttribute'", "visible": false},
+  {"name": "name", "visible": true}
+]
+```
+
+**Important**:
+- **Custom attributes** require single quotes around the attribute name: `"'cf.cplace.myType.attributeName'"`
+- **Builtin attributes** (e.g., `name`, `createdAt`, `creator`, `modifiedAt`, `modifier`, `owner`) are specified without quotes: `"name"`
+
+**Note**: Order in array determines column display order. Hidden columns (`visible: false`) can still be used for sorting/filtering.

package/dist/widget-specifications/cf.platform.embeddedSearchAsTable/multiSortColumns.md

@@ -0,0 +1,16 @@
+**JSON Format**:
+```json
+[
+  {"sortColumn": "'cf.cplace.myType.attribute1'", "sortOrder": "asc", "sortingPriorityIndex": 1},
+  {"sortColumn": "'cf.cplace.myType.attribute2'", "sortOrder": "desc", "sortingPriorityIndex": 2},
+  {"sortColumn": "name", "sortOrder": "asc", "sortingPriorityIndex": 3}
+]
+```
+
+**Valid sortOrder values**: `"asc"`, `"desc"`
+
+**Important**:
+- **Custom attributes** require single quotes around the attribute name: `"'cf.cplace.myType.attributeName'"`
+- **Builtin attributes** (e.g., `name`, `createdAt`, `creator`, `modifiedAt`, `modifier`, `owner`) are specified without quotes: `"name"`
+
+**Note**: `sortingPriorityIndex` determines which sort applies first (lower = higher priority).

package/dist/widget-specifications/cf.platform.embeddedSearchAsTable/search.md

@@ -0,0 +1,8 @@
+**Warning**: Do not manually construct search JSON!
+
+**Correct Usage**: Use the cplaceJson field from cplace_search_pages response
+
+**Workflow**:
+1. Call cplace_search_pages with your desired filter
+2. Take the cplaceJson field from the response
+3. Use that value for the search configuration

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
+}