Found 298 results for "gitana 4.0 developers ui-dev contexts messages"
The search executed in 0.001898784 seconds. That's fast.
![]() |
Gitana 3.2 / Guide / Guide / Docker / Security Notices / CVE-2022-22965Secure your Cloud CMS instance against CVE-2022-22965 by upgrading to 3.2.76 or applying our recommended workaround.
Score: 1.6094201
|
![]() |
Gitana 4.0 / Developers / Cookbooks / Ruby CookbookLearn how to connect to Gitana, manage Git-like branches, and create custom content types with the Ruby Cloud CMS driver.
Score: 1.6094201
|
![]() |
Gitana 3.2 / Guide / Guide / Integrations / Amazon Web Services / Amazon TranscribeIntegrate Amazon Transcribe into your app for seamless speech-to-text conversions with Cloud CMS. Enhance content creation with automatic transcriptions.
Score: 1.6057154
|
![]() |
Gitana 4.0 / Content Engine / Integrations / Amazon Web Services / Amazon TranscribeEffortlessly convert audio to text with Amazon Transcribe and Cloud CMS integration for seamless content management.
Score: 1.6057154
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / manage-all-content-of-a-typeManage access policies with Gitana: Grant project members management rights for all content of a specific type.
Score: 1.6037478
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / read-all-content-with-a-featureExplore Gitana's Access Policy Template to grant consumers access to multi-feature content efficiently. Discover JSON syntax and customization.
Score: 1.6037478
|
![]() |
Gitana 4.0 / Getting StartedExplore the Gitana Platform with our Getting Started Guide, featuring key concepts and links to detailed documentation. Dive in now!
Score: 1.6037478
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / read-all-content-from-all-projectsExplore the Gitana Access Policy Template, enabling management of all content across projects using the identifier read-all-content-from-all-projects.
Score: 1.5955994
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / edit-all-content-with-a-propertyLearn about Gitana's Access Policy Template for editing all content with a specific property value.
Score: 1.5955994
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / read-all-content-in-a-folderExplore Gitana's Access Policy Template for reading all content in a folder, supporting consumer roles with path-specific permissions.
Score: 1.5955994
|
![]() |
Gitana 3.2 / Guide / Guide / Cookbooks / PHP CookbookLearn to use Gitana's PHP driver for database connections, code samples, and advanced querying with this comprehensive guide.
Score: 1.5832016
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / read-all-content-from-a-single-projectDiscover how to implement a Gitana Access Policy Template for managing project content efficiently.
Score: 1.5795488
|
![]() |
Gitana 4.0 / Developers / Cookbooks / JavaScript (Legacy) CookbookExplore the JavaScript (Legacy) Cookbook for mastering Gitana's JavaScript driver. Learn about connecting to Gitana, asynchronous chaining, node creation, and more.
Score: 1.5789149
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / System Policies / project-collaboratorExplore the project-collaborator Gitana System Access Policy, detailing roles and conditions for granting Collaborator and Contributor permissions.
Score: 1.5716438
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / System Policies / project-userExplore the Gitana System Access Policy for project-user with detailed role permissions and JSON configurations.
Score: 1.5716438
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / read-all-content-from-multiple-projectsOptimize access to multiple projects with Gitana's Access Policy Template. Manage and consume content easily from various sources.
Score: 1.5716438
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / manage-content-of-a-type-in-a-folderExplore Gitana's Access Policy Template to manage content by type in specified folders efficiently.
Score: 1.5560691
|
![]() |
Gitana 3.2 / Guide / Guide / Application Server / Services / AwarenessOptimize user interaction with real-time updates via the Awareness Service, using Web Sockets and Redis for seamless channel management.
Score: 1.5502876
|
![]() |
Gitana 4.0 / Developers / Application Server / Services / AwarenessOptimize user location tracking with the Awareness Service; real-time updates via Socket.IO and flexible configurations, including Redis support.
Score: 1.5502876
|
![]() |
Gitana 3.2 / Guide / Guide / Integrations / Amazon Web Services / Amazon Elastic TranscoderOptimize your media with Amazon Elastic Transcoder; scalable, cost-effective cloud transcoding integrated with Cloud CMS for seamless conversion.
Score: 1.548322
|
![]() |
Gitana 4.0 / Content Engine / Integrations / Amazon Web Services / Amazon Elastic TranscoderOptimize media with Amazon Elastic Transcoder, the scalable, cost-effective solution for seamless cloud-based file conversion compatible with various devices.
Score: 1.548322
|
![]() |
Gitana 3.2 / Guide / Guide / RecognitionAutomatically process and recognize faces, text, and more in images with Cloud CMS for enhanced search and analysis.
Score: 1.525556
|
![]() |
Gitana 4.0 / Forms / API / TemplatesDiscover Alpaca's advanced templating with custom views, layouts, and wizard options for dynamic form rendering and field overrides.
Score: 1.5242416
|
![]() |
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: 1.521137
|
![]() |
Comparison: Cloud CMS vs DIYNot 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: 1.521137
|