Create Bold CMS from Quintype #20
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,84 @@ | ||
| { | ||
| "Timestamp": "2019-09-10'T'12:10:10", | ||
| "Name": "BoldCMS from Quintype", | ||
| "Version": "2", | ||
| "License": "Proprietary", | ||
| "Inception": "09-2015", | ||
| "Category": "Essential - Professional", | ||
| "Open Source": "No", | ||
| "Cloud Service": "Yes", | ||
| "On Premises Installation": "No", | ||
| "Cloud Service Hosted in Europe": "No", | ||
| "Commercial Support Available?": "Yes", | ||
| "GraphQL API": "No", | ||
| "GraphQL [Mutations]": "No", | ||
| "GraphQL [Subscriptions]": "No", | ||
| "REST API": "Yes", | ||
| "REST [Create]": "Yes", | ||
| "REST [Read]": "Yes", | ||
| "REST [Update]": "Yes", | ||
| "REST [Delete]": "Yes", | ||
| "REST [Upload]": "Yes", | ||
| "Search API": "Yes", | ||
| "Search Features [Full Text Search]": "Yes", | ||
| "Search Features [Stemming]": "No", | ||
| "Search Features [Stop Words]": "No", | ||
| "Search Features [Boosting]": "No", | ||
| "Search Features [Autocompletion]": "No", | ||
| "Search Features [Autosuggestion]": "Yes", | ||
| "Search Features [Result Highlighting]": "No", | ||
| "Search Features [Geospatial Search]": "No", | ||
| "Search Features [Search within uploads (pdf,doc)]": "No", | ||
| "Image Manipulation": "Yes", | ||
| "Image Focalpoint support": "Yes", | ||
| "Image Facedetection": "No", | ||
| "Optimized Image Encoding": "Yes", | ||
| "Asset fingerprinting": "Yes", | ||
|
Contributor
There was a problem hiding this comment. Can you provide a link to the docs for this feature as well please? |
||
| "CDN Support": "Yes", | ||
| "Antivirus Scanning": "No", | ||
| "Custom Binary Handler": "No", | ||
| "System Requirements": "NA", | ||
| "Supported Databases": "NA", | ||
| "Clustering": "NA", | ||
| "Docker Support": "NA", | ||
| "Backup Feature": "Yes", | ||
|
Contributor
There was a problem hiding this comment. I did not find information about a backup feature. Only the import export was mentioned in the release notes.
Author
There was a problem hiding this comment. We do have this feature enabled to only customers upon request. That's why it's not mentioned in our help doc. However, we do support this feature. |
||
| "Import/Export": "Yes", | ||
| "CLI": "No", | ||
| "SDK [Java]": "Yes", | ||
|
Contributor
There was a problem hiding this comment. Not found in the docs: |
||
| "SDK [C#]": "No", | ||
| "SDK [PHP]": "Yes", | ||
|
Contributor
There was a problem hiding this comment. Not found in the docs: |
||
| "SDK [JavaScript]": "Yes", | ||
| "SDK [React]": "Yes", | ||
|
Contributor
There was a problem hiding this comment. Not found in the docs: |
||
| "SDK [AngularJS]": "Yes", | ||
| "SDK [TypeScript]": "Yes", | ||
| "Web Hooks": "Yes", | ||
|
Contributor
There was a problem hiding this comment. Not found in API and docs:
Author
There was a problem hiding this comment. |
||
| "Eventbus": "No", | ||
| "Bulk Import": "Yes", | ||
| "Client Side Forms": "No", | ||
| "Plugin System": "No", | ||
| "Customizable UI": "Yes", | ||
|
Contributor
There was a problem hiding this comment. How can the UI be customized?
Author
There was a problem hiding this comment. We have a dark and white theme. That's the only customization for the platform UI |
||
| "Custom Field Types": "Yes", | ||
|
Contributor
There was a problem hiding this comment. Can you point me to the documentation for custom field types? I did not find this in the help.
Author
There was a problem hiding this comment. We call it attributes in our platform. https://help.quintype.com/topic/administrative-tasks#adding-story-attributes
Author
There was a problem hiding this comment. |
||
| "User Management": "Yes", | ||
| "Role Based Permissions": "Yes", | ||
| "Document Level Permissions": "Yes", | ||
|
Contributor
There was a problem hiding this comment. Permissions seem to be role/action based and not be configurable on a document level.
Author
There was a problem hiding this comment. We have granular permissions for users and roles. This can be enhances with our Teams permission roles. |
||
| "OAuth 2.0 Support": "Yes", | ||
| "Auditing": "Yes", | ||
| "API Keys": "Yes", | ||
| "Project Support": "Yes", | ||
| "I18N Localized Content": "Yes", | ||
|
Contributor
There was a problem hiding this comment. I did not find information on how to load language specific contents via REST. I checked: https://developers.quintype.com/swagger/ |
||
| "Content Trees": "Yes", | ||
|
Contributor
There was a problem hiding this comment. I did not find information on how tree structures can be build. A story does not seem to be nestable.
Author
There was a problem hiding this comment. We have collections and that allows you to branch out. Refer https://help.quintype.com/topic/collections#understanding-collections |
||
| "Tagging": "Yes", | ||
| "Content Relations": "1:1, 1:n, n:n, n:1", | ||
| "Nesting of Fields": "Yes", | ||
| "GDPR Statement": "No", | ||
| "GDPR API": "No", | ||
| "Editing Conflict Detection": "Yes", | ||
|
Contributor
There was a problem hiding this comment. How are conflicts being detected and handled?
Author
There was a problem hiding this comment. We have a versioning model and edit and lock - https://help.quintype.com/topic/platform#release-notes |
||
| "Versioning": "Yes", | ||
| "Content Scheduling": "Yes", | ||
| "Content Branches": "Yes", | ||
| "Content Models / Schemas": "Yes", | ||
| "Content Model / Schema Versioning": "Yes", | ||
| "Content Migration": "Yes", | ||
|
Contributor
There was a problem hiding this comment. How is content migration being handled? Where is this documented?
Author
There was a problem hiding this comment. |
||
| "Workflows": "Yes", | ||
|
Contributor
There was a problem hiding this comment. Where can I find the documentation on workflows?
Author
There was a problem hiding this comment. |
||
| "Special Features": "Live Preview, Geo location tagging, advanced permission and validation, Integrations with ASANA, Multi-domain manager" | ||
| } | ||
Uh oh!
There was an error while loading. Please reload this page.