Found 619 results for "gitana 4.0 developers api definitions settings"
The search executed in 0.007349605 seconds. That's fast.
![]() |
Gitana 4.0 / Content Engine / IntegrationsConnect your Cloud CMS projects to leading cloud services securely, with reusable service descriptors for seamless integrations.
Score: 1.168546
|
![]() |
Content Entry Forms ExampleCloud CMS lets you easily design and deploy forms for your web applications and content contributors. In this blog entry, we’ll walk through how you can do this within the Cloud CMS user interface. In this example, we’ll create a form that allows editors to create City Guide information. Note: in the Cloud CMS Trial there is a City Guide Content definition which can be used as a starting point or as a reference for this example. Add a Definition The Content Definitions can be found in the Cloud
Score: 1.1664109
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Security Notices / CVE-2021-44228Secure your Cloud CMS with Log4j2 updates against CVE-2021-44228. Upgrade to version 3.2.71 and follow mitigation steps for enhanced protection.
Score: 1.1541961
|
![]() |
Gitana 3.2 / Guide / Guide / Single Sign On (SSO) / KeycloakLearn how to configure Cloud CMS Single Sign-On (SSO) with JBoss Keycloak, an open-source identity provider supporting SAML 2.0 and JWT.
Score: 1.1541636
|
![]() |
Gitana 4.0 / Content Engine / Single Sign On (SSO) / KeycloakOptimize your Cloud CMS SSO with Keycloak using this detailed setup guide, offering seamless identity management for secure access.
Score: 1.1541636
|
![]() |
Experimenting with blogsToday we’re switching over to Tumblr for our blogging capabilities. You might ask a couple of questions - one of which is “why tumblr?” and the other is “why would you use an external CMS for your blog?” These are both excellent questions. They’re both pretty easy to answer as well. With respect to blog software, our feeling is that it’s very much a commodity at this point. When this stuff came out early last decade, it was novel and a wide diversity of features were to be found from one product
Score: 1.1411117
|
![]() |
Gitana 4.0 / Self Managed / ContainersExplore configuration guides for Antivirus, API, and UI servers in Gitana's self-managed containers documentation.
Score: 1.1327596
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / ConfigurationExplore configuration guides for Docker components including antivirus, API, encryption, support, and UI server.
Score: 1.1280513
|
![]() |
Gitana 4.0 / Content Engine / Branch Overview / Pull RequestsSimplify pull requests with Cloud CMS: merge, validate conflicts, and manage approvals for seamless content updates.
Score: 1.1248773
|
![]() |
CEM - shuffling deck chairs on the titanicGoing back 15 years, we’ve seen the core of providing websites shift across various types of “platforms” - from Web Content Management (WCM) to Enterprise Content Management (ECM) to Customer Experience Management (CEM). Every iteration involved another set of technologies, and associated migration headaches. Each expansion also consumed more and more of the resulting presentation tier. At first, this was mostly a good thing as no standard mechanisms existed to facilitate efforts. However, in th
Score: 1.117235
|
![]() |
Gitana 3.2 / Guide / Guide / Application Server / Services / FlowEffortlessly integrate UI wizards with our API, using JSON configurations for seamless browser-side applications.
Score: 1.1141585
|
![]() |
Gitana 4.0 / Developers / Application Server / Services / FlowEffortlessly integrate UI wizards with our API, using JSON configurations for seamless browser-side applications.
Score: 1.1141585
|
![]() |
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: 1.1051036
|
![]() |
How do I retrieve the folder path for my content?In Cloud CMS, you may choose to associate nodes with folders. This allows the content to be worked with by editorial teams such that they can navigate to content within folders, move content between folders and generally organize their content as they wish. It also allows for content to be retrieved by path via the API, if you wish. Technically speaking, Cloud CMS does not require folders or paths. In fact, plenty of customers use Cloud CMS in such a way that they don't require folders at all. C
Score: 1.1041106
|
![]() |
Create Once, Publish Everywhere!One of the things that our customers love about Cloud CMS is that it lets them create content once and easily publish it to all of their mobile and web applications. It reduces the amount of work required to create fresh and interesting content and saves them time and money in the process. Our goal is straightforward. We want to provide all of the things that small business owners need on the backend to give their users a seamless experience in creating, editing and publishing content. With Clou
Score: 1.1041106
|
![]() |
Gitana 3.2 / Guide / Guide / Application Server / Services / Virtual DriverOptimize virtual driver settings for seamless API key retrieval for incoming tenants.
Score: 1.1006037
|
![]() |
Gitana 4.0 / Developers / Application Server / Services / Virtual DriverOptimize virtual driver settings for seamless API key retrieval for incoming tenants.
Score: 1.1006037
|
![]() |
Gitana 4.0 / Forms / APIExplore comprehensive API documentation including callbacks, functions, validation, and more for Gitana 4.0 forms. Ideal for developers and tech enthusiasts.
Score: 1.0976362
|
![]() |
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: 1.0952454
|
![]() |
Gitana 3.2 / Guide / Guide / Application Server / Authentication / Authenticators / CustomCreate a custom authenticator for your application server by extending the AbstractAuthenticator class. Follow step-by-step implementation guidance.
Score: 1.0952454
|
![]() |
Gitana 4.0 / Developers / Application Server / Authentication / Authenticators / CustomCreate a custom authenticator for your application server by extending the AbstractAuthenticator class. Follow step-by-step implementation guidance.
Score: 1.0952454
|
![]() |
Gitana 4.0 / Content Engine / Branch Overview / Editorial FlowsOptimize content workflow with Editorial Flows. Create, schedule, and manage tasks and releases, ensuring seamless collaboration for your team.
Score: 1.0952454
|
![]() |
Gitana 4.0 / Content Engine / Publishing / Example Publishing SetupLearn how to set up a publishing workflow to seamlessly manage projects from authoring to live, including deployment targets and publication rules.
Score: 1.0952454
|
![]() |
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: 1.0952454
|
![]() |
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: 1.0952454
|