Found 227 results for "features indexable"
The search executed in 0.001606179 seconds. That's fast.
|
Gitana / 3.2 / Guide / Guide / FeaturesFeatures Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu
Score: 17.916964
|
|
|
Gitana / 4.0 / Data Engine / Aspects / OverviewFeatures Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu
Score: 11.904159
|
|
|
Gitana / 3.2 / Guide / Guide / Features / IndexableIndexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc
Score: 11.629019
|
|
|
Gitana / 4.0 / Data Engine / Aspects / IndexableIndexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc
Score: 11.629019
|
|
|
Gitana / 3.2 / Guide / Guide / Content ModelingContent Modeling A content model consists of definitions which describe your project's content types, properties, graph associations, and the aspect-oriented features that Cloud CMS uses to ensure data consistency, integrity and validity when content is created, updated or deleted. In Cloud CMS, all content modeling is done using JSON and more specifically, JSON Schema. JSON Schema provides an elegant and well-adopted model for describing the types for content objects, properties and other neste
Score: 9.17575
|
|
|
Gitana / 4.0 / Data Engine / Content Models / OverviewContent Modeling A content model consists of definitions which describe your project's content types, properties, graph associations, and the aspect-oriented features that Cloud CMS uses to ensure data consistency, integrity and validity when content is created, updated or deleted. In Cloud CMS, all content modeling is done using JSON and more specifically, JSON Schema. JSON Schema provides an elegant and well-adopted model for describing the types for content objects, properties and other neste
Score: 9.17575
|
|
|
Gitana / 4.0 / Data Engine / Content Models / Default PathsDefault Paths Your content types define schemas that Cloud CMS uses to render intuitive forms for content entry. In addition, content types let you configure persistence paths so that JSON documents created using these forms are automatically saved in a directory structure that you intend. Paths support templated variables so that the path can be dynamic. It can depend on the values having been entered. For example, let's suppose I have the content type for an article, like this: { "title":
Score: 7.9725256
|
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Remove Features
Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Score: 6.637067
|
|
|
Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Remove Features
Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Score: 6.637067
|
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Add Features
Add Features Type: addFeatures This handler adds features to a node that is part of the workflow's payload. This can be used to apply one or more features to your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Score: 6.626053
|
|
|
Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Add Features
Add Features Type: addFeatures This handler adds features to a node that is part of the workflow's payload. This can be used to apply one or more features to your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Score: 6.626053
|
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / content-model-features-list-item-actionscontent-model-features-list-item-actions [ { "config": { "content-model-features-list-item-actions": [ { "key": "edit-document", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/properties", "iconClass": "fa fa-pencil" }, { "key": "view-json", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/json", "iconClass": "fa fa-code" }, { "key": "content-i
Score: 4.4123044
|
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / content-model-features-list-item-actionscontent-model-features-list-item-actions [ { "config": { "content-model-features-list-item-actions": [ { "key": "edit-document", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/properties", "iconClass": "fa fa-pencil" }, { "key": "view-json", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/json", "iconClass": "fa fa-code" }, { "key": "content-i
Score: 4.4123044
|
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / Default PathsDefault Paths Your content types define schemas that Cloud CMS uses to render intuitive forms for content entry. In addition, content types let you configure persistence paths so that JSON documents created using these forms are automatically saved in a directory structure that you intend. Paths support templated variables so that the path can be dynamic. It can depend on the values having been entered. For example, let's suppose I have the content type for an article, like this: { "title":
Score: 3.523994
|
|
Getting Started Videos for Cloud CMSWe are very proud of Cloud CMS and encourage you to see for yourself the potential of Cloud CMS (Free Trial). To help you get the most out of the trial and knowledge of some of the features, we have recorded a number of ‘Getting Started’ videos showing some basic features, administration, and a ‘taster’ of some of the more interesting advanced features. (More videos to come for the advanced features). The Getting Started videos: Create a Project Add Users to Projects Upload Content Add Comments
Score: 1.7828033
|
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / Definitions / Feature DefinitionFeature Definition A Feature Definition is a cross-cutting concern or Aspect that you can apply arbitrarily to content instances or content types (to apply to all instances of a type). A Feature Definition is used to optionally describe additional schema that should be applied to a content or association type. Feature Definitions also endow content instances with special behaviors. Feature Definitions are defined in much the same way as Types or Associations. Each Feature has a QName and the JSO
Score: 1.723007
|
|
|
Gitana / 4.0 / Data Engine / Content Models / Definitions / Feature DefinitionFeature Definition A Feature Definition is a cross-cutting concern or Aspect that you can apply arbitrarily to content instances or content types (to apply to all instances of a type). A Feature Definition is used to optionally describe additional schema that should be applied to a content or association type. Feature Definitions also endow content instances with special behaviors. Feature Definitions are defined in much the same way as Types or Associations. Each Feature has a QName and the JSO
Score: 1.723007
|
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Workflow HandlersWorkflow Handlers Add Features Copy Node Email Lock Node Logger Move Node Remove Features Remove Properties Script Set Properties Slack Message Sync Node Unlock Node Web Hook
Score: 1.7158738
|
|
|
Gitana / 4.0 / Data Engine / Workflow / Workflow HandlersWorkflow Handlers Add Features Copy Node Email Lock Node Logger Move Node Remove Features Remove Properties Script Set Properties Slack Message Sync Node Unlock Node Web Hook
Score: 1.7158738
|
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / model-subcontextmodel-subcontext [ { "evaluator": "context-project", "config": { "model-subcontext": { "items": [ { "key": "model/heading", "title": "Content Model", "header": true, "order": 1000, "items": [ { "key": "model/types", "title": "Types", "uri": "#/projects/{projectId}/model/types", "order": 100 }, {
Score: 1.6765472
|
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / model-subcontextmodel-subcontext [ { "evaluator": "context-project", "config": { "model-subcontext": { "items": [ { "key": "model/heading", "title": "Content Model", "header": true, "order": 1000, "items": [ { "key": "model/types", "title": "Types", "uri": "#/projects/{projectId}/model/types", "order": 100 }, {
Score: 1.6765472
|
|
Pricing: Free Options - GitanaPricing: Free 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 enhance
Score: 1.6762131
|
|
|
Alpaca 1.0.3 Released!We’re pleased to announce the release of Alpaca Web Forms 1.0.3 for jQuery, jQuery UI and jQuery Mobile. Alpaca is an open-source project that provides an easy way to render web forms using JSON schema. It consists of a jQuery plugin and provides a nice abstraction so that you can change form layouts, validation logic and presentation with simple changes to JSON. Alpaca provides the web forms capabilities for Cloud CMS - The Cloud Content Management Platform for the Enterprise. This release incl
Score: 1.6672237
|
|
|
The top 3 features that differentiate Cloud CMS from the competitionYou have determined you need a Content Management System (CMS) and have begun the daunting task of reducing the number of CMS products to a manageable number to evaluate in depth. Having reached this article you are aware of, or interested in, CMSs that can be described as: Headless CMS, API First, Platform as a Service (PaaS), Decoupled CMS, Cloud-First. I am sure there are more beautiful categorizations and terminology provided by the latest analyst buzz. As much as I may not like the catagori
Score: 1.6611905
|
|
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.636879
|