Skip to content

Update feature list #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kmelve wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Update feature list #11

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
362a582
Update feature list
kmelve Feb 7, 2019
1a4623e
Updated plans
kmelve Mar 11, 2019
7f41d56
Update sanity.json
kmelve Mar 12, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
70 changes: 35 additions & 35 deletions sanity.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,84 +1,84 @@
{
"Timestamp": "2018-07-28T17:10:29.733Z",
"Timestamp": "2019-03-11T17:10:29.733Z",
"Name": "Sanity",
"Version": "08-2018",
"License": "Commercial",
"Version": "03-2019",
"License": "MIT/Commercial",
"Inception": "05-2016",
"Category": "Essential - Professional",
"Open Source": "No",
"Category": "Standard - Advanced - Enterprise",
"Open Source": "Yes",
"Cloud Service": "Yes",
"On Premises Installation": "No",
"Cloud Service Hosted in Europe": "?",
"Cloud Service Hosted in Europe": "Yes",
"Commercial Support Available?": "Yes",
"GraphQL API": "No",
"GraphQL API": "Yes",
"GraphQL [Mutations]": "No",
"GraphQL [Subscriptions]": "No",
"REST API": "Yes",
"REST API": "Yes, GROQ",
"REST [Create]": "Yes",
"REST [Read]": "Yes",
"REST [Update]": "Yes",
"REST [Delete]": "Yes",
"REST [Upload]": "No",
"REST [Upload]": "Yes",
"Search API": "Yes",
"Search Features [Full Text Search]": "No",
"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]": "No",
"Search Features [Result Highlighting]": "No",
"Search Features [Autocompletion]": "NA",
"Search Features [Autosuggestion]": "NA",
"Search Features [Result Highlighting]": "NA",
"Search Features [Geospatial Search]": "No",
"Search Features [Search within uploads (pdf,doc)]": "No",
"Image Manipulation": "Yes",
"Image Focalpoint support": "",
"Image Facedetection": "",
"Image Focalpoint support": "Yes",
"Image Facedetection": "No",
"Optimized Image Encoding": "Yes",
"Asset fingerprinting": "",
"Asset fingerprinting": "No",
"CDN Support": "Yes",
"Antivirus Scanning": "No",
"Custom Binary Handler": "No",
"System Requirements": "NA",
"Supported Databases": "NA",
"Clustering": "No",
"Clustering": "NA",
"Docker Support": "NA",
"Backup Feature": "No",
"Backup Feature": "Yes",
Copy link
Author

@kmelve kmelve Mar 11, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All changes/patches to content are backed up, also API endpoints for full exports of datasets.

Copy link
Contributor

@Jotschi Jotschi Mar 12, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where is the backup feature documented? I could not find it in the docs.

"Import/Export": "Yes",
"CLI": "Yes",
"SDK [Java]": "No",
"SDK [C#]": "No",
"SDK [C#]": "Yes",
"SDK [PHP]": "Yes",
"SDK [JavaScript]": "Yes",
"SDK [React]": "No",
"SDK [React]": "Yes",
"SDK [AngularJS]": "No",
"SDK [TypeScript]": "No",
"SDK [TypeScript]": "Yes",
"Web Hooks": "Yes",
"Eventbus": "Yes",
"Bulk Import": "Yes",
"Client Side Forms": "No",
"Client Side Forms": "Yes",
"Plugin System": "Yes",
"Customizable UI": "Yes",
"Custom Field Types": "No",
"User Management": "",
"Custom Field Types": "Yes",
"User Management": "Yes",
"Role Based Permissions": "Yes",
"Document Level Permissions": "Yes",
"OAuth 2.0 Support": "No",
"Auditing": "",
"OAuth 2.0 Support": "Yes",
"Auditing": "No",
"API Keys": "Yes",
"Project Support": "Yes",
"I18N Localized Content": "Yes",
"Content Trees": "",
"Tagging": "",
"Content Relations": "",
"Nesting of Fields": "",
"GDPR Statement": "",
"Content Trees": "Yes",
Copy link
Author

@kmelve kmelve Mar 11, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fully customizeable with Structure Builder. https://www.sanity.io/docs/content-studio/structure-builder

Copy link
Contributor

@Jotschi Jotschi Mar 12, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this also limited to 20 levels?

Copy link
Author

@kmelve kmelve Mar 12, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's theoretically unlimited

"Tagging": "Yes",
"Content Relations": "Yes",
"Nesting of Fields": "Yes",
"GDPR Statement": "Yes",
"GDPR API": "No",
"Editing Conflict Detection": "",
"Editing Conflict Detection": "Yes",
Copy link
Author

@kmelve kmelve Mar 11, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Backend is real-time, every patch get a revision ID

Copy link
Contributor

@Jotschi Jotschi Mar 12, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens when a content is updated with two different requests? Will the second request override the updated data of the first request?

Copy link
Author

@kmelve kmelve Mar 12, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything is transactional, so if the transaction includes the revision id of the document, it will fail if the document has been changed meanwhile (and tell the client). If not, it will update the document.

Copy link
Contributor

@Jotschi Jotschi Mar 12, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kmelve Very nice. Is this documented somewhere? What is the error code in those cases? 409? 400?

"Versioning": "Yes",
"Content Scheduling": "No",
"Content Scheduling": "Yes",
Copy link
Author

@kmelve kmelve Mar 11, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can use custom access control https://www.sanity.io/docs/data-store/access-control#group-documents and predefined parameters in GROQ (https://www.sanity.io/docs/groq/groq-parameters#predefined-parameters)

Copy link
Contributor

@Jotschi Jotschi Mar 12, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this applies. Is it possible to schedule the publication of a specific content? Is it possible to define a timeframe in which the content is online?

Copy link
Author

@kmelve kmelve Mar 12, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, on any document type you can add a date field (or more). You can then set the access rules to "make this available for a said group (everyone, and/or certain roles) when the date on the document is less than what time is now", and vice-versa if you want to unpublish it.

"Content Branches": "",
"Content Models / Schemas": "Yes",
"Content Model / Schema Versioning": "",
"Content Model / Schema Versioning": "Yes",
"Content Migration": "Yes",
"Workflows": "No",
"Special Features": ""
"Special Features": "Real-time hosted backend, fully customizeable editor, powerful asset pipeline"
}