Found 465 results for "docs fields time"
The search executed in 0.002039308 seconds. That's fast.
![]() |
Gitana 3.2 / Guide / Guide / UI Developers GuideOptimize your Cloud CMS user interface with customizable JavaScript and JSON-driven modules for powerful, tailored content management solutions.
Score: 0.9812385
|
![]() |
Gitana 4.0 / Developers / User Interface CustomizationOptimize your Cloud CMS experience with our guide to enhancing the user interface through customizable JavaScript and JSON configurations.
Score: 0.9812385
|
![]() |
Gitana 4.0 / Reference / Types / Deployment TargetExplore our comprehensive guide on Deployment Target objects, including methods, properties, and schema details to accelerate development.
Score: 0.9812385
|
![]() |
Gitana 4.0 / Reference / Types / Deployment StrategyExplore comprehensive API methods and properties for managing deployment strategies on Giganta's platform, enhancing development with language driver support.
Score: 0.9812385
|
![]() |
Gitana 4.0 / Reference / Types / Deployment ReceiverComprehensive guide on Gitana Deployment Receiver: properties, methods, examples, and more to streamline your development.
Score: 0.9812385
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Maintenance / Health Check / Load BalancersOptimize your Cloud CMS production environment with efficient load balancers for API and UI, ensuring high availability and reliability.
Score: 0.9803893
|
![]() |
Gitana 4.0 / Self Managed / Maintenance / Health Check / Load BalancersOptimize your Cloud CMS production environment with efficient load balancers for API and UI, ensuring high availability and reliability.
Score: 0.9803893
|
![]() |
Gitana 4.0 / Reference / Types / VaultVault stores backups, replications, and exports of data. Manage archives, access control, and development with our API.
Score: 0.97708464
|
![]() |
Gitana 4.0 / Reference / Types / IdentityExplore detailed documentation on Identity objects, properties, methods, and schema within your Gitana directory.
Score: 0.9712275
|
![]() |
Gitana 3.2 / Guide / Guide / DeploymentEffortlessly deploy your content across diverse endpoints like Amazon S3, FTP, and Cloud CMS branches with automated, transactional Cloud CMS Deployment.
Score: 0.96749955
|
![]() |
Gitana 4.0 / Content Engine / DeploymentCloud CMS Deployment lets you efficiently publish and transfer content across various endpoints, including Amazon S3, FTP, and remote servers.
Score: 0.96749955
|
![]() |
Gitana 3.2 / Guide / Guide / User Interface / Projects / Deleted ItemsEfficiently manage and restore deleted content with Cloud CMS's intuitive tools, ensuring data is never lost entirely. Explore our unique features today!
Score: 0.96269435
|
![]() |
Gitana 4.0 / User Interface / Projects / Deleted ItemsManage content recovery effortlessly with Cloud CMS's 'copy on write' system, offering a simple way to view, restore, or purge deleted items.
Score: 0.96269435
|
![]() |
Gitana 3.2 / Guide / Guide / Application Server / Tags / @queryOptimize queries for nodes with customizable parameters to enhance template flexibility, including sorting, caching, and locale for targeted results.
Score: 0.9572164
|
![]() |
Gitana 4.0 / Developers / Application Server / Tags / @queryOptimize queries for nodes with customizable parameters to enhance template flexibility, including sorting, caching, and locale for targeted results.
Score: 0.9572164
|
![]() |
How does Cloud CMS compare to DIY (do-it-yourself)?Not sure whether to build or buy? Review these points to help guide your selection. Why DIY: exact fit with your technology stack use existing in-house skills and resources build only the features you need able to add new features as required use existing developers for support cost / budget - internal no need for external services to deliver and support product can be a ‘skunk works’ project Why not DIY: Risk (more complex than it looks) time/effort/cost are all easy to under-estimate CMS requi
Score: 0.9491274
|
![]() |
Recommended Cloud CMS architectureIn general, we recommend a three-tier architecture (browser -> app server -> API) for any applications you build. This would be our recommendation whether you're using Cloud CMS or anyone else. There are a few good reasons: The browser is an insecure runtime. Exposing any API keys within the browser is a very big security hole. Even exposing credentials within the browser (such as within a cookie) for the sake of working around this is also not recommended since hackers can siphon off the creden
Score: 0.9491274
|
![]() |
The Gitana Blog - Page 1The Gitana Blog - Page 1 Status Releases Registry Blog Cloud CMS Platform Platform Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Automation Automate your content creation and approval flows while taking advantage of AI services to enhance and curate content
Score: 0.941405
|
![]() |
Security Policy - GitanaSecurity Policy - Gitana Status Releases Registry Blog Cloud CMS Platform Platform Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Automation Automate your content creation and approval flows while taking advantage of AI services to enhance and curate content
Score: 0.9402124
|
![]() |
Gitana 4.0 / Reference / Types / Access PolicyExplore our Access Policy guide to learn about creating, updating, and managing policies within the Gitana platform, complete with examples and schema details.
Score: 0.9366063
|
![]() |
Gitana 4.0 / Reference / Types / Workflow TaskExplore our comprehensive guide on Workflow Tasks within the Platform, featuring detailed methods, properties, and use cases for seamless integration.
Score: 0.9366063
|
![]() |
Sync from one environment to anotherWithin Cloud CMS sync capabiities are generally referred to as the "transfer system". They allow you to export individual objects, data stores or even collections of these as an archive (ZIP) within a vault. You can then move those archives to storage for backup or move them to new Cloud CMS server instances for restoration or replication. We have support for transfer within our API, our drivers and also within the user interface. The latter is useful in that you can script it pretty effectively
Score: 0.93253344
|
![]() |
Gitana 3.2 / Guide / Guide / ModulesBuild custom add-on modules for Cloud CMS using GitHub and JavaScript. Easily register and deploy your module to enhance the Cloud CMS interface.
Score: 0.93175757
|
![]() |
Gitana 4.0 / User Interface / ModulesLearn to build and deploy add-on modules for Cloud CMS using GitHub, enhancing the user interface with customizable module extensions.
Score: 0.93175757
|
![]() |
What is the reason for "Failed to index node"?If you scan your log entries and see "Failed to index node", this indicates that Elastic Search failed to update its index for a node. Cloud CMS tells Elastic Search to updates its index whenever a node is created or updated. When a node is deleted, Cloud CMS tells Elastic Search to remove the node from its index. This error message means that Elastic Search failed to update the index and therefore the index wasn't updated. If you open up the error, you may see further information that indicates
Score: 0.93175757
|