Search Results

API / Actions / Create Thumbnail

Create Thumbnail ID: createThumbnail { "title": "Create Thumbnail(s)", "properties": { "attachmentId": { "title": "Attachment ID", "type": "string", "default": "default" }, "thumbnails": { "type": "array", "items": { "type": "object" } } } }

Score: 18.361626

API / Data Types / Billing Provider Configuration

Billing Provider Configuration Type billingProviderConfiguration Datastore Type application Supports authorities, permissions, transfer If this sounds familiar, it's because it's exactly what Cloud CMS uses to supports its own subscription plans for Cloud CMS customers. Just as we bill our customers for metered usage of the platform, you are free to pass those costs downstream to your own clients. And you can use the very same technical capabilities and facilities to do so. Cloud CMS offers bill

Score: 5.368211

UI Guide / Customize / Dashboard

Dashboard You can customize dashboard in Platform and Project. Find the "Config Dashboard" button at the top right area of the platform/project home page, and you will be able to customize dashboards for different pages. In this example, we will customize the dashboard for Platform. In the following screenshot, there are 5 dashlets (My Projects, My Favorites, My Recent Edits, My Tasks, and Recent Activities). We can Change the layout Add/remove a dashlet Configure each dashlet Lock configuration

Score: 4.160034

API / Features / Thumbnailable

Thumbnailable QName: f:thumbnailable Configures a node to automatically generate thumbnails for the node content or attachments. With this feature applied, one or more thumbnail images will be generated based on the node's JSON or attachment content. These thumbnails can be of various sizes and are automatically generated when the node's content is created, updated or deleted or its relevant attachment is updated. Thumbnail generation is always synchronous. Thumbnails are generated when the node

Score: 3.7687721

Docker Guide / Kits / Overview

Overview Cloud CMS ships a number of pre-built kits containing Docker configuration files to help you get start. These kits are built from customer feedback to provide the most commonly requested scenarios. They can be used straight away or at the very least can serve as a useful reference. To download the Cloud CMS Docker Kits, please visit our Docker download page. Kits All of the Docker kits utilize Docker and Docker Compose. In each kit, you'll find a docker-compose.yml file which describes

Score: 3.7450924

Application Server / Services / Cache

Cache Service that is responsible for providing an application server cache that all processes, whether local or distributed, have access to for non-transactional caching. Objects stored in the cache are eventually available to other members of the cluster (if there are any), no matter whether running on the same server or on other servers in the cluster. Modes The Cloud CMS Application Server can run in one of three modes: single node cluster multiple nodes (on a single process) sticky-cluster

Score: 3.3730283

UI Developer Guide / UI Configuration / Overview

Overview Customized changes to the user interface configuration can be introduced through the use of UI Config documents. UI Config documents are JSON documents that contain one or more configuration blocks. The UI Config configuration blocks are loaded after the standard configuration document and therefore have the opportunity to either extend or override the base configuration. UI Configs are scoped either to the platform or to the project. As such, you can use UI Config objects to customize

Score: 3.347159

UI Developer Guide / UI Configuration / Config Service

Config Service The configuration service evaluates a series of conditional configuration blocks and determines which blocks to keep in composing a final configuration document for the user interface. The configuration document consists of blocks that define JSON structures that are to be merged into a final JSON configuration that powers the user interface. The configuration service executes two phases - evaluate and merge. It essentially looks like this: [block1] --> --> [config1]

Score: 3.320156

API / Behaviors / Overview

Overview Cloud CMS lets you wire in behaviors behind your content models so that rules automatically execute when your content is touched. Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors. In this way, the developers can wire up behaviors and the editorial team never needs to know about it. Furthermore, be

Score: 3.30061

API / Forms / References

References Forms may use a $ref variable to pull in or include the configuration of another Cloud CMS form (or sub-section of a form). This capability is designed to be compatible with the use of $ref within JSON schema for pulling in alternate schemas or definitions. $ref within schemas Cloud CMS allows you to use the $ref variable within your schemas or definitions to pull in JSON schema blocks from other definitions on the same branch. This is typically done using a QName loader and generally

Score: 3.192247