I know it seems nice and it has a lot of nice features (features that have been in other CMSes before) .. but this is just an old school way of thinking.
Any enterprise, before anything else, should be looking at headless CMSes, primarily in my opinion. This is what I advise all of our enterprise clients. (we have no horse in the race)
The benefits of headless CMSes are multiplied by enterprises with very large and rich content needs, and generally, what these businesses need, is less coupling of things.
I'd rather look at something like strapi, which is open source, has a MVC architecture built on express, is headless by default, more than a single db option, has a graphql api etc.
Or if you want to go SAAS, use Prismic.io or Contentful
It brought my gpu's (Radeon VII) video decode to 90%, and brought my whole pc to a standstill.
Interestingly if I use OBS to record it happening, and use AMD AMF as the encoder, then the decode load only hits 73%. After swapping over to cpu x264 encoding, back to 90%+ (Peaked at 96%). Might have a power limit for encode/decode. Weeeeird.
Comparing it to something like Adobe Experience Manager/CQ, I wonder if it has mobile editing modes and if any large enterprises outside of their customer logos section are using it.
Also I like the pitch but I think you need to focus more on what separates this from the status quo.
Has anyone used this before? It has a bunch of nice features but I don't understand what separated it into a "Enterprise" category.
They also seem to have migrated to a completely different platform from 1.5 to 2 (PHP -> NodeJS). So that doesn't really scream stable Enterprise to me.
Choose boring technology - especially for a relatively simple use case such as a CMS.
Anyone who, after reading that list of issues and seeing the repeated sketchy behaviour of MongoDB (the company), still doesn't recognize the deep-seated issues behind how MongoDB is being developed and marketed, isn't going to be convinced by an updated list of grievances either. It'd be a waste of my time and energy.
But if you insist on evidence that they haven't actually meaningfully improved, this is their latest problem, from a few months ago: https://www.ongres.com/blog/benchmarking-do-it-with-transpar...
Seriously. My original article wasn't just a to-do list for the MongoDB developers. It was meant to illustrate the deeper problems with MongoDB, and how it's a database that was developed just to have a product to sell, not to actually build a better database.
If that message still hasn't gotten through to people, well, I've tried.
What's the point of continuing to pour engineering resources into something that doesn't actually improve upon what's already available?
Who knows why, but the gov dept wanted Apostrophe.
It was mostly good to use. Admin UI on mobile pretty terrible, but they weren’t worried about that.
Most of the work involved configuring the CMS, customizing templates and hacking on CSS to implement the site design. Wrote a couple Mongo queries, that’s it.
Not the best dev experience, but I wouldn’t run from another Apostrophe project.
Here's what happened: when we first came to Node back in 2012, Node itself was being very, very cautious about releasing a 1.0 version, something that didn't happen for quite some time after. So the culture was to be conservative with module version numbers, and we felt our first Node release shouldn't be 1.0 or 2.0... and we wound up releasing it as 0.4. Then the second major release on Node, which should if anything have been 3.0, as 0.5.
Then node version numbering got rational, we got serious about semantic versioning, and for our next major rewrite we went to 2.0. Still confusingly close to the old PHP 1.5 version number, but at least it's not a smaller number!
2.x is an LTS (Long Term Support) release, supported through 2023, so we've been iterating on it while maintaining bc. 3.x, which will finally break bc but also be an LTS for quite a while, will be released sometime in 2020.
Connectors to SAP, Dynamics, Commerce solutions.
Connectors to multi-channel campaigns and built-in analytics.
Ability to define workflows, either through rules, or via specific actions.
Plugin based interface to customize the CMS behaviour at all levels, handling the HTTP request, exposing WebAPIs, authentication into various kind of security systems, extending the menu options available on the UI designer.
Ah, and a enterprise CMS also has their own set of certifications, developer conferences and partnerships with different kinds of support levels.