Found 306 results for "ui projects project-import"
The search executed in 0.001440344 seconds. That's fast.
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / project-mypreferences-contextproject-mypreferences-context [ { "evaluator": "context-project", "config": { "project-mypreferences-context": { "items": [ { "key": "project/mypreferences", "title": "My Preferences", "order": 10000, "header": true, "items": [ { "key": "project/mypreferences/properties", "title": "Properties", "uri": "#/projects/{projectId}/mypreferences",
Score: 4.1929026
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / project-mypreferences-contextproject-mypreferences-context [ { "evaluator": "context-project", "config": { "project-mypreferences-context": { "items": [ { "key": "project/mypreferences", "title": "My Preferences", "order": 10000, "header": true, "items": [ { "key": "project/mypreferences/properties", "title": "Properties", "uri": "#/projects/{projectId}/mypreferences",
Score: 4.1929026
|
|
Gitana / 3.2 / Guide / Guide / Docker / Kits / OEMOEM The OEM kit provides a way for developers, integrators, partners and those who are embedded Cloud CMS in custom solutions to build and test extensions. These extensions include UI extensions as well as API extensions in the form of Java / Spring beans. The kit consists of the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To acc
Score: 4.1858635
|
|
Gitana / 4.0 / Self Managed / Kits / OEMOEM The OEM kit provides a way for developers, integrators, partners and those who are embedded Cloud CMS in custom solutions to build and test extensions. These extensions include UI extensions as well as API extensions in the form of Java / Spring beans. The kit consists of the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To acc
Score: 4.1858635
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / uitemplates-subcontextuitemplates-subcontext [ { "config": { "uitemplates-subcontext": { "items": [ { "key": "project-uitemplates", "title": "Project UI Templates", "header": true, "order": 1000, "items": [ { "key": "project/uitemplates/settings", "title": "Settings", "uri": "#/projects/{projectId}/uitemplates/settings", "iconClass": "fa fa-sliders"
Score: 3.5702195
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / uitemplates-subcontextuitemplates-subcontext [ { "config": { "uitemplates-subcontext": { "items": [ { "key": "project-uitemplates", "title": "Project UI Templates", "header": true, "order": 1000, "items": [ { "key": "project/uitemplates/settings", "title": "Settings", "uri": "#/projects/{projectId}/uitemplates/settings", "iconClass": "fa fa-sliders"
Score: 3.5702195
|
|
Gitana / 3.2 / Guide / Guide / Overview_page Access Policies Actions Antivirus Scanning API API Keys Applications Application Server Attachments Auditing Authentication Binary Files Branches Bulk Import Command Line Conditions Content Modeling Cookbooks Deployment Docker Features Find Forms General GraphQL Integrations Multifactor Authentication Modules Narration Optical Character Recognition Platform Policies Projects Publishing Query Recognition Releases Reports Rules Scripting Search Security Single Sign On (SSO) Supported Stacks
Score: 3.1846135
|
|
How does multi-tenancy work?How does multi-tenancy work? ie I want to have multiple companies with sub-groups of users in each company - to follow, how would we customize the interface for each company? There are two good ways to achieve multi-tenancy with Cloud CMS. - One is to use multiple "projects" - i.e. one per customer. Each project has it's own domain of users and groups, as well as it's own content definitions, instances and ACLs. As such, you can use each project to store the content on a per-client basis. You ca
Score: 3.0580378
|
|
Gitana / 3.2 / Guide / Guide / Getting StartedGetting Started Welcome to the Cloud CMS Documentation center. Cloud CMS is an API-first content management system that provides everything you need on the back end to power web sites and mobile applications. Cloud CMS makes it easy for your business users to create, manage and publish amazing content to your users! You are reading the Getting Started guide. To learn more about Cloud CMS and what it does, select from the links provided below or use the tree on the left-hand side. We offer severa
Score: 2.8153448
|
|
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: 2.5809612
|
|
Pricing: Hosted Options - GitanaPricing: Hosted Options - 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, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI services to enhanc
Score: 2.4985077
|
|
Gitana / 4.0 / Forms / API / Custom FieldsCustom Fields Alpaca has a pretty inclusive field library that you can use straight away. Fields are simply referenced by their type within your Alpaca forms configuration. If you don't provide specific field types to use, Alpaca guesses at sensible defaults for you. You can also create your own fields. Alpaca fields are object-oriented (essentially) so that you can extend existing fields, override methods and modify behaviors. The result is less work and a complete extensibility layer so that y
Score: 2.3907382
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / platform-mypreferences-contextplatform-mypreferences-context [ { "evaluator": "context-platform", "config": { "platform-mypreferences-context": { "items": [ { "key": "platform/mypreferences", "title": "My Preferences", "order": 10000, "header": true, "items": [ { "key": "platform/mypreferences/properties", "title": "Properties", "uri": "#/mypreferences", "
Score: 2.2848818
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / platform-mypreferences-contextplatform-mypreferences-context [ { "evaluator": "context-platform", "config": { "platform-mypreferences-context": { "items": [ { "key": "platform/mypreferences", "title": "My Preferences", "order": 10000, "header": true, "items": [ { "key": "platform/mypreferences/properties", "title": "Properties", "uri": "#/mypreferences", "
Score: 2.2848818
|
|
My UI modules aren't deploying. What should I check?If you're running an on-premise installation of Cloud CMS and are unable to deploy UI modules via the main user interface, here are a few tips and pointers. Things to consider: 1. When you click on the "Deploy Module" option, your a URL connection is made from the UI server back to the API server. Specifically, it invokes a POST to the route: /oneteam/modules/deploy Check your API side logs or any firewalls or proxies along the way to make sure that an API server receives this call. For example,
Score: 2.2356706
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / platform-manage-contextplatform-manage-context [ { "evaluator": "context-platform", "config": { "platform-manage-context": { "items": [ { "key": "platform/manage/header", "title": "Manage Platform", "header": true, "order": 10000, "allowAuthority": [ "owner", "manager", "admin" ], "items": [ { "key": "platform/settings",
Score: 2.1814852
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / platform-manage-contextplatform-manage-context [ { "evaluator": "context-platform", "config": { "platform-manage-context": { "items": [ { "key": "platform/manage/header", "title": "Manage Platform", "header": true, "order": 10000, "allowAuthority": [ "owner", "manager", "admin" ], "items": [ { "key": "platform/settings",
Score: 2.1814852
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / SamplesSamples In this section, we've collected sample configurations that customers and our support team refer to frequently when guiding developers down the path of building out UI extensions. To understand what is provided here, we recommend first reading up on the following: Configuration Service UI Views UI Modules The samples provided here can be included in custom modules and can also be plugged into UI Views. The following samples are provided: Developer Menu Items Releases Menu Item
Score: 2.1722505
|
|
Gitana / 4.0 / Developers / User Interface Customization / SamplesSamples In this section, we've collected sample configurations that customers and our support team refer to frequently when guiding developers down the path of building out UI extensions. To understand what is provided here, we recommend first reading up on the following: Configuration Service UI Views UI Modules The samples provided here can be included in custom modules and can also be plugged into UI Views. The following samples are provided: Developer Menu Items Releases Menu Item
Score: 2.1722505
|
|
Gitana / 3.2 / Guide / Guide / Docker / Kits / QuickstartQuickstart The Quickstart kit defines the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To access the API directly: https://localhost:8080 docker-compose.yml version: "2" services: ui: build: ./ui networks: - cloudcms depends_on: - api env_file: - ./ui/ui.env ports: - "80:80" api:
Score: 2.1446466
|
|
Gitana / 4.0 / Self Managed / Kits / QuickstartQuickstart The Quickstart kit defines the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To access the API directly: https://localhost:8080 docker-compose.yml version: "2" services: ui: build: ./ui networks: - cloudcms depends_on: - api env_file: - ./ui/ui.env ports: - "80:80" api:
Score: 2.1446466
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / project-contextproject-context [ { "evaluator": "context-project", "config": { "project-context": { "items": [ { "key": "project/developers/heading", "title": "Developers", "order": 10000, "header": true, "allowAuthority": [ "manager" ], "items": [ { "key": "project/developers/query", "title": "Query", "uri": "#/project
Score: 2.067652
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / project-contextproject-context [ { "evaluator": "context-project", "config": { "project-context": { "items": [ { "key": "project/developers/heading", "title": "Developers", "order": 10000, "header": true, "allowAuthority": [ "manager" ], "items": [ { "key": "project/developers/query", "title": "Query", "uri": "#/project
Score: 2.067652
|
|
Gitana / 3.2 / Guide / Guide / Docker / Kits / API ClusterAPI Cluster The api-cluster kit defines the following services: ui api1 api2 apilb mongodb elasticsearch This kit differs from the quickstart in how it handles API requests. Requests are sent to the apilb container which runs a load balancer, distributing work between api1 and api2. It is worth reviewing the cluster settings for both of your api servers in order for them to correctly communicate. Running Use the following commands: docker-compose build --force-rm docker-compose up And then open
Score: 2.0409074
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / team-subcontextteam-subcontext [ { "evaluator": "context-team", "config": { "team-subcontext": { "items": [ { "key": "team", "title": "Team", "order": 1000, "header": true, "items": [ { "key": "team/view", "title": "Overview", "uri": "#/projects/{projectId}/teams/{teamId}", "order": 1000 }, { "key"
Score: 2.0309331
|