Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Superdesk vs Squidex, the Slant community recommends Superdesk for most people. In the question“What are the best open source headless CMS's?” Superdesk is ranked 10th while Squidex is ranked 17th. The most important reason people chose Superdesk is:
The interface is clean and well designed. You can tell someone with a UX background worked on it and not just software engineers.
Specs
Question Ranking
Pros
Pro Visual
The interface is clean and well designed. You can tell someone with a UX background worked on it and not just software engineers.
Pro Easy to use
Putting together an article is straightforward: you type the text into the main fields and then use drag and drop to add photos.
Pro Publish to more than one website
You have the option of setting up publishing routes to choose where something gets published in case you have multiple websites.
Pro Customizable
I like that you can set up a personal workspace and also add different widgets to your dashboard depending on what you’re interested in.
Pro Newsroom automation
Superdesk can aggregate and automate multiple mundane newsroom jobs.
Pro Open source
Pro Versioning
Pro Powerful rule engine for integrations
Pro REST and GraphQL
Pro Slick UI
Pro Generous free package
2 locales, 2 collaborators, many API calls
Cons
Con Sometimes buggy
Sometimes, when trying to publish a post I was getting errors which was a bit annoying. However, after we updated to the latest version the instance was running smoothly.
Con Not one-click publishing
At least in our company’s system you need to do a couple of extra steps to publish an article.
Con Limited to SImple Content
Limited to simple displaying of contents but will struggle with complex business rules ie ones that require cascading drop-downs, complex nested documents, etc..
Con Un-debuggable Script Editors
You can't debug any of its in-built script editors
Con References
It will allow you to delete references which are used by documents and when you come to open those documents, it will then perform its 'shake' logic to remove it (make it balnk') and will also disappear from history / versioning
Con UI can be messy to navigate for an editor
Con Small team
