Found 41 results for "sdk"
The search executed in 6.15086E-4 seconds. That's fast.
Gitana / 3.2 / Guide / Guide / Docker / Container ServicesContainer Services In this chapter, we provide examples and guidance on how to instantiate the Gitana platform within a variety of container services. SDK For each of the frameworks listed below, you will find samples configuration files within the Gitana SDK. Gitana SDK - Container Framework Examples for Gitana 3.2 Frameworks Amazon ECS Kubernetes
Score: 9.719607
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / Content Model Builder / Extend Field TemplatesExtend Field Templates If you find the existing field templates still limited to your need, Modules allow you to add your own field template. In the following sample, we added a field template that provides a Summernote WYSIWYG editor. Default CKEditor WYSIWYG: Customized Summernote WYSIWYG: Get the code here in the SDK: https://github.com/gitana/sdk/tree/master/ui/modules/content-model/content-model-field
Score: 9.083817
|
|
Gitana / 4.0 / Content Engine / Content Models / Content Model Builder / Extend Field TemplatesExtend Field Templates If you find the existing field templates still limited to your need, Modules allow you to add your own field template. In the following sample, we added a field template that provides a Summernote WYSIWYG editor. Default CKEditor WYSIWYG: Customized Summernote WYSIWYG: Get the code here in the SDK: https://github.com/gitana/sdk/tree/master/ui/modules/content-model/content-model-field
Score: 9.083817
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / ModulesModules Common files that each module should have: module.json (where you give the module a name) install.js uninstall.js As soon as you have these files, the rest is up to you depending on what you would like to customize in the module. Take a look at some sample modules in our SDK Custom Modules One of the features that make CloudCMS super configurable is the ability to implement custom modules. Within a custom module, you can define new UI elements that your editorial team can use in their da
Score: 8.664646
|
|
Gitana / 4.0 / Developers / User Interface Customization / ModulesModules Common files that each module should have: module.json (where you give the module a name) install.js uninstall.js As soon as you have these files, the rest is up to you depending on what you would like to customize in the module. Take a look at some sample modules in the Gitana SDK Custom Modules One of the features that make CloudCMS super configurable is the ability to implement custom modules. Within a custom module, you can define new UI elements that your editorial team can use in t
Score: 8.664646
|
|
Gitana / 3.2 / Guide / Guide / Docker / Kits / MongoDB Replica SetMongoDB Replica Set The MongoDB Replica Set kit defines an environment with a 3 node MongoDB replica set and two Cloud CMS environments running against it The configuration files for this kit can be found in the Gitana SDK Running Start the mongo servers first and then initialize the cluster: docker login --username {docker-username} --password '{docker-password}' docker-compose up -d mongodb1 mongodb2 mongodb3 Initialize the replic set. only have to do this once since the mongo servers persist
Score: 7.912538
|
|
Gitana / 3.2 / Guide / Guide / Docker / UI ExtensionsUI Extensions The Docker-based Cloud CMS UI provides additional extension patterns beyond the AMD-driven mechanism for user interface components and screens. Since Docker allows you to run on-premise, you can use these extension patterns to influence more foundational changes to the way the application works. Environment Variables When the Cloud CMS user interface starts up, it looks to environment variables to tell it whether there are any extensions available to be loaded. Extensions are store
Score: 7.21579
|
|
Gitana / 4.0 / Self Managed / UI Extensions / OverviewUI Extensions The Docker-based Cloud CMS UI provides additional extension patterns beyond the AMD-driven mechanism for user interface components and screens. Since Docker allows you to run on-premise, you can use these extension patterns to influence more foundational changes to the way the application works. Environment Variables When the Cloud CMS user interface starts up, it looks to environment variables to tell it whether there are any extensions available to be loaded. Extensions are store
Score: 7.21579
|
|
The best way to enable content authoring with your JS frameworkNow that you’ve built that beautiful application in Angular, Aurelia, Ember, React - or the next big JavaScript framework - how do make your content authors happy? Easy: Think Headless. Never let a CMS dictate your presentation tier options. The field is too crowded and is changing too rapidly for pre-ordained “templates” to suffice. Instead, crank out that prototype in your desired framework(s) and utilise REST calls to query content a simple mockup will do returning JSON for each node Then go
Score: 7.042318
|
|
Gitana / 4.0 / Developers / Frameworks / cURLcURL Guide and References for connectivity to Cloud CMS Connecting to Cloud CMS From a command prompt, the curl command can be used to execute API calls to Cloud CMS. Connecting to the Cloud CMS API requires API Keys from your Cloud CMS project. This is done by default for the sample project. You can find these by going to Manage Project and clicking API Keys in the left hand menu. Several examples of using curl are available in our Gitana SDK For example, reading a node can be done with the fol
Score: 6.494724
|
|
Build your prototype website in 10 easy stepsGetting started with Cloud CMS for a website takes minimal setup: Fork a copy of https://github.com/gitana/sdk Note the URL of your repo; you’ll need this later… Login to your tenant or signup for a trial of Cloud CMS When prompted upon login create a Web Content Management starter project From the resulting Project Dashboard navigate to “Applications” in Manage Project Select “Sample Web Application” > Deployments Tick the radio button on the right Navigate to Selected > Undeploy (upper right)
Score: 6.494724
|
|
Finding sanity by losing your headThere was a lot of chatter last year regarding a “headless” or “decoupled” CMS design. Zeitgeist, maybe… countermovement, definitely. Since their inception, every expansion of content management software along the continuum from managing basic websites to full-on digital experiences drove CMSes further and further into the application’s presentation tier. In parallel, we witnessed the maturity of frameworks such as Angular, Ember, and Ionic (just to name a few) - all pushing development out to t
Score: 6.494724
|
|
Gitana / 3.2 / Guide / Guide / Docker / Container Services / KubernetesKubernetes Kubernetes, also known as K8s, is an open-source system for automating the deployment, scaling, and management of containerized applications. Kubernetes is open-source and adaptable to a number of cloud providers including Amazon, Google, Azure and others. It allows you to express your infrastructure configuration in such a way as to take advantage of on-premises and a diversity of hybrid and public cloud infrastructures. For information on Kubernetes, please visit https://kubernetes.
Score: 6.4753084
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Tags / @form@form A form can be rendered from Cloud CMS by identifying the definition and form key. Forms are rendered on the client-side using Alpaca Forms. For a working example, see: https://github.com/gitana/sdk/tree/master/app-server/appserver-form-sample Parameters parameter required description definition yes the type definition QName form yes the form key list no the data list to populate successUrl no the URL to redirect to upon success failureUrl no the URL to redirect to upon failure formId no ov
Score: 6.384404
|
|
Gitana / 4.0 / Developers / Application Server / Tags / @form@form A form can be rendered from Cloud CMS by identifying the definition and form key. Forms are rendered on the client-side using Alpaca Forms. For a working example, see: https://github.com/gitana/sdk/tree/master/app-server/appserver-form-sample Parameters parameter required description definition yes the type definition QName form yes the form key list no the data list to populate successUrl no the URL to redirect to upon success failureUrl no the URL to redirect to upon failure formId no ov
Score: 6.384404
|
|
Gitana / 3.2 / Guide / Guide / User Interface / Embed Media In CKEditor / Advanced Usages / Extend Media TypesExtend Media Types The out of the box media types on CloudCMS are Youtube, Vimeo, Brightcove and Soundcloud. However, we grant you the ability to introduce any other media types. Follow this tutorial to learn how. (Code is involved!) Create a xxx-link.js File Note: Take a look at these files to get a sense of it. getSchema() and getOptions() These two methods allow you to create a form with specific fields to configure for templates of this type. /** * @override */ getSchema: fun
Score: 6.2777705
|
|
Gitana / 4.0 / User Interface / Embedded Media / Advanced Usages / Extend Media TypesExtend Media Types The out of the box media types on CloudCMS are Youtube, Vimeo, Brightcove and Soundcloud. However, we grant you the ability to introduce any other media types. Follow this tutorial to learn how. (Code is involved!) Create a xxx-link.js File Note: Take a look at these files to get a sense of it. getSchema() and getOptions() These two methods allow you to create a form with specific fields to configure for templates of this type. /** * @override */ getSchema: fun
Score: 6.2777705
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Web HookWeb Hook Type: webhook This handler makes an HTTP(S) POST to a remote web service. It automatically passes along any relevant information about the workflow, task or transition so that your web service can get to work. The config for this handler looks like this: { "url": "http://myserver:port/controller" } In addition, you can supply username and password properties in support of Basic authentication to your listener endpoint: { "url": "http://myserver:port/controller", "username":
Score: 6.0748434
|
|
Gitana / 4.0 / Developers / Frameworks / Next.js
Next.js Generate static sites with Cloud CMS Building a static or hybrid-server site with Cloud CMS content is simple with Next JS. Below you will find tools and examples for how to get started. API Keys Every mobile app or web site that you build will need to have a set of API Keys that it will use to connect to your Cloud CMS platform on behalf of your code. These API keys consist of client and user key/secret pairs. Log in to your Cloud CMS tenant at https://
Score: 6.0748434
|
|
Gitana / 4.0 / Developers / Frameworks / SvelteKit
SvelteKit Generate static and hybrid sites with SvelteKit Building a static or hybrid site with Cloud CMS content is simple with SvelteKit. Below you will find tools and examples for how to get started. API Keys Every mobile app or web site that you build will need to have a set of API Keys that it will use to connect to your Cloud CMS platform on behalf of your code. These API keys consist of client and user key/secret pairs. Log in to your Cloud CMS tenant at https://
Score: 6.0748434
|
|
Gitana / 4.0 / Content Engine / Workflow / Workflow Handlers / Web HookWeb Hook Type: webhook This handler makes an HTTP(S) POST to a remote web service. It automatically passes along any relevant information about the workflow, task or transition so that your web service can get to work. The config for this handler looks like this: { "url": "http://myserver:port/controller" } In addition, you can supply username and password properties in support of Basic authentication to your listener endpoint: { "url": "http://myserver:port/controller", "username":
Score: 6.0748434
|
|
Proxy API calls
Whenever a resulting URL looks something like: https://api.cloudcms.com/repositories/f0fb4efd3de07c54420a/branches/9bcdbfea8f2d900f0387/nodes/
Score: 6.0748434
|
|
Gitana / 3.2 / Guide / Guide / Actions / Web HookWeb Hook ID: webhook Makes a remote call to an HTTP endpoint. Core Configuration Property Type Required Default Description url text true The fully-qualified HTTP endpoint (i.e. http://www.myserver.com/endpoint) method text false The HTTP method to invoke (default: POST) username text false The Basic authentication username. password text false The Basic authentication password. payload object false The JSON payload for PUT and POST calls. headers object false The headers to apply to the HTTP ca
Score: 6.062092
|
|
Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / HTTP Deployment HandlerHTTP Deployment Handler Handles the deployment of one or more Deployment Packages to a custom HTTP endpoint. The custom HTTP endpoint is described by: url statusUrl username password Custom HTTP endpoints are useful for a large variety of purposes, including writing data into custom databases, synchronizing content from Cloud CMS with existing Content Management products, hooking into custom logic for CDN or cache invalidation and much more. Configuration { "url": "{url}", "statusUrl": "
Score: 6.062092
|
|
Gitana / 4.0 / Content Engine / Behaviors / Actions / Web HookWeb Hook ID: webhook Makes a remote call to an HTTP endpoint. Core Configuration Property Type Required Default Description url text true The fully-qualified HTTP endpoint (i.e. http://www.myserver.com/endpoint) method text false The HTTP method to invoke (default: POST) username text false The Basic authentication username. password text false The Basic authentication password. payload object false The JSON payload for PUT and POST calls. headers object false The headers to apply to the HTTP ca
Score: 6.062092
|