Search Results

Duster

Duster The Duster Service provides template rendering using the LinkedIn Dust.js template engine. The Duster Service loads output templates for you, executes Dust across them and outputs markup like HTML and JSON. It allows you to build full web sites or custom APIs using a powerful template engine. Tags The Cloud CMS Application Server provides a library of * Dust Tags available out of the box. These are listed in more detail on the left-hand side menu. Fragment Caching Some Dust ta

Score: 10.96097

Overview

Overview The Application Server provides the runtime for the Cloud CMS Web Content Management solution. Web Content Management is a term that enterprise vendors have been using for years to distinguish between the role that a CMS (content management system) plays for an organization - it may be used to collaborate around your internal documents, legal records, digital assets and many other content items in addition to your web and mobile content. Cloud CMS provides a Web Content Management so

Score: 10.512517

Authentication

Authentication Cloud CMS supports OAuth2 for server authorization. OAuth2 provides a secure and robust method for authenticating clients and users to the server. It's become well-adopted across the industry by other vendors including Facebook, Twitter and Salesforce. We feel that OAuth2 is a best practice authorization mechanism for the applications that our customers build. As we move forward, we intend to support additional authorization schemes as they are requested. However, we find that

Score: 9.867885

Overview

Overview The Cloud CMS Application Server offers an easy way for customers to assemble powerful, front-end custom APIs and web sites for Cloud CMS. It is completely free and runs on top of the popular Node.js technology stack. With Cloud CMS, customers have a choice of using any front-end presentation technology they wish. In many cases, customers already have a technology investment (such as C#, PHP, Java or Ruby) and thus a preference for continuing to build on that technology stack. H

Score: 9.553046

Server Tags

Server Tags Model Variables The framework keeps track of specific model variables which are accessible within your templates: user - information about the current user page - information about the current page selected - information about the currently selected content item session - information about the current user application session history - information about the navigation history request - information about the request Here is an example template that displays the user's click

Score: 9.36801

Proxy API calls

Whenever a resulting URL looks something like:

https://api.cloudcms.com/repositories/f0fb4efd3de07c54420a/branches/9bcdbfea8f2d900f0387/nodes/<nodeId>/attachments/thumb.jpg
 
It works great as an API URL but not necessarily as one that can be resolved by the end user's browser.  In a typical Node.js-based architecture, you have the 
  • User’s browser
  • Node.js application server
  • Cloud CMS backend API
The URL gene

Score: 9.254982

Definitions for Date format

Our definitions are based on JSON schema and, as such, the default is to use strings for dates. The date controls in our forms engine let you customize the format string so that you can store ISO 8601 or other formats (perhaps simplified formats) as per your preference. The advantage here is simplicity with these controls and compatibility with JSON schema. The disadvantage is that MongoDB provides a lot of very powerful capabilities for range query and sorting that do not play as nicely with

Score: 9.147393

@resource

@resource Used to create a browser-ready and cache-sensitive URI to a resource within the application. Parameters uri Examples When rendered in the browser, this may look like: Where 817284192131 is a hash of the file. The hash changes when the file contents change. The has is automatically filtered out of the URI upon request so that the original file is returned. It guarantees that the browse

Score: 8.783312

How does Cloud CMS work with a CDN

There are a few places where this either occurs automatically if you're using our hosted service or can occur optionally if you're either running within Docker containers on your own or integrating to custom CDN endpoints.

First, the API itself can be fronted by a CDN that supports fallback lookup to an origin server.  In this case, we recommend Amazon CloudFront with short-lived TTLs on cache headers.  More specifically, you can use Amazon's API Gateway to get caching coverage across

Score: 8.569005

Node URLs

Node URLs The Application Server supports retrieval of nodes and node attachments via URLs and takes responsibility for setting headers and cache state for optimal performance. This method is the preferred method for dealing with binary payloads as it ensures compatibility with CDN edge caching. In addition, binary and JSON files that are retrieved from the Cloud CMS API are cached on the Application Server itself so that subsequent requests benefit from having a local copy. A notification

Score: 7.8740664