JBLOUD vs Appernetic
When comparing JBLOUD vs Appernetic, the Slant community recommends Appernetic for most people. In the question“What is the fastest CMS for web content (news website with some static pages) ?” Appernetic is ranked 12th while JBLOUD is ranked 18th. The most important reason people chose Appernetic is:
Non-developers can easily write and update content using the inline PageDown editor.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easy, fast, no server load
JBLOUD is 100% EC6 javascript, uses WebDAV to upload/delete both data and media. Doesn't require any DB or server side programming language, a single server can host hundreds of sites without any significative load.
Pro PageDown editor with image upload
Non-developers can easily write and update content using the inline PageDown editor.
Pro Integrated git flow
Git and GitHub is used for version control, cloning, publishing and syncing of your Appernetic Hugo project. No need to manually enter git commands.
Pro Fast set-up
A Hugo site is configured with git, a file structure and a theme in 2 min instead of 30 min.
Pro Integrated Cloudinary image management
You automatically get a cloudinary link when you upload an image.
Pro Developers have complete control over the source code
Cons
Con Young
Can be fully customised, on the other hand template engine (GUI driven customisation) is still under development.