Found 124 results for "publishing preview-servers"

The search executed in 0.001207136 seconds. That's fast.

Gitana / 4.0 / Data Engine / Publishing / Example Publishing Setup

Example Publishing Setup The following are the steps to config a typical Publishing setup (Publish and Unpublish): Step 1: Create Projects Create two projects Create an "Authoring" project Create a "Live" Project Step 2 : Create a Deployment Target Deployment Target is the endpoint where the package will be deployed or sent. Go to Manage Platform Go to Deployment Targets under Deployment Left Navigation Menu Click on Create a Deployment Target Title : "Live Web Site" Deployment Target Type : "Br

Score: 15.457925

Gitana / 3.2 / Guide / Guide / Publishing

Publishing Publishing brings together many parts of Cloud CMS to enable you to manage the lifecycle of your Content. Our Publishing is very configurable to meet your diverse needs. To help get you started we have a simple example showing a Publish and Unpublish mechanism between an Authoring Project and a Live project. When Publishing is enabled in a Project you get: Workflow With Publishing enabled there are 2 simple workflows added to your Project: simple publish and simple unpublish. The simp

Score: 14.921502

Gitana / 3.2 / Guide / Guide / Releases

Releases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab

Score: 9.184786

Gitana / 4.0 / Data Engine / Releases / Overview

Releases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab

Score: 9.184786

Gitana / 4.0 / Data Engine / Publishing / Content Types

Content Types Cloud CMS lets you customize the Publishing Behavior and the Workflow Per Content Type. You can now Enable/Disable the Preview and Publishing buttons for each Content Type. Customize Publishing Behavior Per Content Type You can disable the Publishing Behavior like Preview button or the Publishing buttons for all the Content types whose content or data you do not want to publish. To Disable the Publishing behaviors of the Content Types: Go to Project Go to Manage Project Go to Publi

Score: 9.179909

Gitana / 3.2 / Guide / Guide / Publishing / Example Publishing Setup

Example Publishing Setup The following are the steps to config a typical Publishing setup (Publish and Unpublish): Step 1: Create Projects Create two projects Create an "Authoring" project Create a "Live" Project Step 2 : Create a Deployment Target Deployment Target is the endpoint where the package will be deployed or sent. Go to Manage Platform Go to Deployment Targets under Deployment Left Navigation Menu Click on Create a Deployment Target Title : "Live Web Site" Deployment Target Type : "Br

Score: 8.9763775

Gitana / 4.0 / Data Engine / Publishing / Overview

Publishing Publishing brings together many parts of Cloud CMS to enable you to manage the lifecycle of your Content. Our Publishing is very configurable to meet your diverse needs. To help get you started we have a simple example showing a Publish and Unpublish mechanism between an Authoring Project and a Live project. When Publishing is enabled in a Project you get: Workflow With Publishing enabled there are 2 simple workflows added to your Project: simple publish and simple unpublish. The simp

Score: 8.900606

Gitana / 4.0 / Data Engine / Publishing / Workflow

Workflow Cloud CMS lets you define your own Workflows and choose them for the Publish and Unpublish activities. Each activity like Publish and Unpublish will have a Workflow Model which will have a set of instructions on how the contents should be routed during each activity. The default Workflow models we use for the Publish activity is Simple Publish and for the Unpublish activity is Simple Unpublish. You can add your own Workflows and customize your publish and unpublish activities.

Score: 8.729385

Gitana / 3.2 / Guide / Guide / Getting Started / Publishing

Publishing Cloud CMS brings together several power components to offer publishing of content to your live web sites and applications: Workspaces allow individuals and teams to work together without stepping on each other's toes Workflow provides managers with the tools to review and approve content Instant Preview allows reviewers to see how content changes would impact their live site Completed and approved content can be published to release snapshots or can be copied to target projects on eit

Score: 8.44326

Gitana / 4.0 / Data Engine / Publishing / Lifecycle States

Lifecycle States Cloud CMS contains four content Lifecycle States during the Publishing process of a content. These define the state of the Content in the Publishing Lifecycle. Each state will have an ID, Title and a Preview Endpoint The four states in the Publishing lifecycle are : - None - Draft - Live - Archived You can look at the lifecycle states as follows: Each state has a Preview Endpoint which can be defined or modified under Preview Servers. These gives a chance to instantly preview t

Score: 8.318014

Gitana / 4.0 / Data Engine / Publishing / Publications

Publications Publications tell the system whenever content on the "master" branch goes into the "live" state, it should be pushed out to the deployment target. Once you Add a Publication to the Project, the content from the Selected Branch will be published to the Selected Deployment Target and its Lifecycle State will change to Live. To Add Publication: Go to Manage Project Publication Settings Click on Publications Click on Add a Publication Select the Branch whose content you wish to deploy t

Score: 8.104233

Gitana / 4.0 / Data Engine / Deployment / Deployment Strategy

Deployment Strategy A Deployment Strategy defines the conditions by which a Deployment Package should automatically be assembled and delivered to one or more Deployment Targets. A Deployment Strategy is a recipe that tells a listener within Cloud CMS how to identify nodes whose content has changed and should be deployed. It then describes what steps to take in terms of deploying the content. If you're using Cloud CMS Publishing, you will not need to set up a Deployment Strategy by hand. The Publ

Score: 7.837488

Gitana / 4.0 / Data Engine / Publishing / Preview Servers

Preview Servers Before your changes go to Live website i.e. on the Production mode, to discover problems and fix them right away you can set up the Preview Servers and review the content changes instantly. You can look at the default Preview Servers under Manage Project : The default servers are Authoring and Production and are setup to a sample URL which can be modified with your website URL or some API or an Application. To add your Custom Server, you can click on Add Preview Server and set-up

Score: 6.935455

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / publishing-manage-subcontext

publishing-manage-subcontext [ { "evaluator": "context-project", "config": { "publishing-manage-subcontext": { "items": [ { "key": "project/publishing", "title": "Publishing", "header": true, "items": [ { "key": "project/publishing/settings", "title": "Settings", "uri": "#/projects/{projectId}/manage/publishing", "iconClass": "fa fa-angle

Score: 6.634879

Gitana / 4.0 / Developers / User Interface Customization / Contexts / publishing-manage-subcontext

publishing-manage-subcontext [ { "evaluator": "context-project", "config": { "publishing-manage-subcontext": { "items": [ { "key": "project/publishing", "title": "Publishing", "header": true, "items": [ { "key": "project/publishing/settings", "title": "Settings", "uri": "#/projects/{projectId}/manage/publishing", "iconClass": "fa fa-angle

Score: 6.634879

Gitana / 4.0 / Data Engine / Deployment / Deployment Mappings

Deployment Mappings The following Deployment Handlers supports the deployment of resources from Cloud CMS to files or file system equivalents: S3 Deployment Handler File System Deployment Handler FTP Deployment Handler These Deployment Handlers all have the common function. They must work with content from Cloud CMS, consisting of Nodes, Associations, binary attachments and a potentially complex content graph of relationships. They must take that content and then map it down into a file system c

Score: 6.343508

Gitana / 4.0 / Data Engine / Deployment / Deployment Receivers

Deployment Receivers A Deployment Receiver acts as an endpoint for local and remote Deployment Handlers that seek to ship their Deployment Packages to a destination. These are frequently used to move content between data centers or across different parts of the world to solve for latency issues (or to simply move content to the correct side of a DMZ for security reasons or runtime-performance reasons). Cloud CMS lets you create Deployment Receivers from within its user interface. You can create

Score: 6.1747427

Gitana / 3.2 / Guide / Guide / Deployment

Deployment Cloud CMS Deployment lets you publish content from a source Cloud CMS project branch to one or more destination Deployment Endpoints. These Deployment Endpoints may include Amazon S3 buckets, FTP servers, file system locations and Cloud CMS branches on the same cluster or running in a cluster located in another data center somewhere else in the world. The Deployment process can be triggered manually or automatically. It may run as part of a Publishing process for your content. It may

Score: 6.088078

Gitana / 4.0 / Data Engine / Deployment / Overview

Deployment Cloud CMS Deployment lets you publish content from a source Cloud CMS project branch to one or more destination Deployment Endpoints. These Deployment Endpoints may include Amazon S3 buckets, FTP servers, file system locations and Cloud CMS branches on the same cluster or running in a cluster located in another data center somewhere else in the world. The Deployment process can be triggered manually or automatically. It may run as part of a Publishing process for your content. It may

Score: 6.088078

Gitana / 4.0 / Data Engine / Deployment / Deployment Target

Deployment Target A Deployment Target contains the configuration for a Deployment Handler. It informs the handler about how to connect or what settings should be used when executing. Deployment Targets are configured for Deployment Strategies as well as for Deployment Receivers. When content is changed within Cloud CMS, a Deployment Strategy may decide to package up that modified content and deployment it to one or more Deployment Targets. Similarly, content may be deployed to a Deployment Recei

Score: 5.862791

Real Time Publishing - Gitana

Real Time Publishing - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, distribute and utilize your data operations, all integrated seamlessly and managed via single point of access. Automate Automate your content creation and approval flows while taking advantage of AI services to enhan

Score: 5.5478525

Gitana / 3.2 / Guide / Guide / Publishing / Content Types

Content Types Cloud CMS lets you customize the Publishing Behavior and the Workflow Per Content Type. You can now Enable/Disable the Preview and Publishing buttons for each Content Type. Customize Publishing Behavior Per Content Type You can disable the Publishing Behavior like Preview button or the Publishing buttons for all the Content types whose content or data you do not want to publish. To Disable the Publishing behaviors of the Content Types: Go to Project Go to Manage Project Go to Publi

Score: 4.4619694

Gitana / 3.2 / Guide / Guide / Publishing / Lifecycle States

Lifecycle States Cloud CMS contains four content Lifecycle States during the Publishing process of a content. These define the state of the Content in the Publishing Lifecycle. Each state will have an ID, Title and a Preview Endpoint The four states in the Publishing lifecycle are : - None - Draft - Live - Archived You can look at the lifecycle states as follows: Each state has a Preview Endpoint which can be defined or modified under Preview Servers. These gives a chance to instantly preview t

Score: 4.063895

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Strategy

Deployment Strategy A Deployment Strategy defines the conditions by which a Deployment Package should automatically be assembled and delivered to one or more Deployment Targets. A Deployment Strategy is a recipe that tells a listener within Cloud CMS how to identify nodes whose content has changed and should be deployed. It then describes what steps to take in terms of deploying the content. If you're using Cloud CMS Publishing, you will not need to set up a Deployment Strategy by hand. The Publ

Score: 3.5833695

Gitana / 3.2 / Guide / Guide / Publishing / Publications

Publications Publications tell the system whenever content on the "master" branch goes into the "live" state, it should be pushed out to the deployment target. Once you Add a Publication to the Project, the content from the Selected Branch will be published to the Selected Deployment Target and its Lifecycle State will change to Live. To Add Publication: Go to Manage Project Publication Settings Click on Publications Click on Add a Publication Select the Branch whose content you wish to deploy t

Score: 3.5114496