Create Bold CMS from Quintype #20
Conversation
|
Thanks for your PR. Could you please provide links to the features so that I can quickly crosscheck the fields? See #19 for example. Thanks |
You can refer to these documentations |
|
@Susannavargs90 If you could provide to each individual mentioned feature via a link this would help a lot to find the correct information. Otherwise I have to search the whole documentation and this takes a lot of time. |
| "Custom Field Types": "Yes", | ||
| "User Management": "Yes", | ||
| "Role Based Permissions": "Yes", | ||
| "Document Level Permissions": "Yes", |
There was a problem hiding this comment.
Permissions seem to be role/action based and not be configurable on a document level.
There was a problem hiding this comment.
We have granular permissions for users and roles. This can be enhances with our Teams permission roles.
| "Supported Databases": "NA", | ||
| "Clustering": "NA", | ||
| "Docker Support": "NA", | ||
| "Backup Feature": "Yes", |
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.
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.
| "Client Side Forms": "No", | ||
| "Plugin System": "No", | ||
| "Customizable UI": "Yes", | ||
| "Custom Field Types": "Yes", |
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.
There was a problem hiding this comment.
We call it attributes in our platform. https://help.quintype.com/topic/administrative-tasks#adding-story-attributes
There was a problem hiding this comment.
| "Bulk Import": "Yes", | ||
| "Client Side Forms": "No", | ||
| "Plugin System": "No", | ||
| "Customizable UI": "Yes", |
There was a problem hiding this comment.
How can the UI be customized?
There was a problem hiding this comment.
We have a dark and white theme. That's the only customization for the platform UI
| "API Keys": "Yes", | ||
| "Project Support": "Yes", | ||
| "I18N Localized Content": "Yes", | ||
| "Content Trees": "Yes", |
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.
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
| "Auditing": "Yes", | ||
| "API Keys": "Yes", | ||
| "Project Support": "Yes", | ||
| "I18N Localized Content": "Yes", |
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/
| "Nesting of Fields": "Yes", | ||
| "GDPR Statement": "No", | ||
| "GDPR API": "No", | ||
| "Editing Conflict Detection": "Yes", |
There was a problem hiding this comment.
How are conflicts being detected and handled?
There was a problem hiding this comment.
We have a versioning model and edit and lock - https://help.quintype.com/topic/platform#release-notes
| "Content Models / Schemas": "Yes", | ||
| "Content Model / Schema Versioning": "Yes", | ||
| "Content Migration": "Yes", | ||
| "Workflows": "Yes", |
There was a problem hiding this comment.
Where can I find the documentation on workflows?
There was a problem hiding this comment.
| "Content Branches": "Yes", | ||
| "Content Models / Schemas": "Yes", | ||
| "Content Model / Schema Versioning": "Yes", | ||
| "Content Migration": "Yes", |
There was a problem hiding this comment.
How is content migration being handled? Where is this documented?
There was a problem hiding this comment.
We also have asset fingerprinting.
| "Image Focalpoint support": "Yes", | ||
| "Image Facedetection": "No", | ||
| "Optimized Image Encoding": "Yes", | ||
| "Asset fingerprinting": "Yes", |
There was a problem hiding this comment.
Can you provide a link to the docs for this feature as well please?
No description provided.