CushyCMS – you'll have to host it on their servers.
PageLime – you'll have to provide PageLime with your FTP login credentials.
With Liberate, all you need is to get your webmaster to add in the DIVs and Javascript that Liberate gives you to the HTML page you're trying to update.
This is handy if there's an existing website that's already hosted somewhere that you'll need to update now and then, much faster than porting the whole site to CushyCMS.
Some webmasters aren't too comfortable saving FTP login credentials onto a 3rd party service either.
But technically with this solution your content will be hosted on the Liberate server too. So when that server goes down or gets slow, so does your entire website. PageLime would be the best option in that case. Allowing remote javascript on your site can be just as bad as giving FTP credentials. Besides, you can just create an FTP account for the CMS.
rvschuilenburg, that's true, it's a convenience tradeoff.
On my end, I intend to grow this service at a slower, manageable pace, which which makes it easier to focus on availability for a smaller, more valued user base.
Comments
Hey mtogo,
Here are some differences I'm aware of:
CushyCMS – you'll have to host it on their servers.
PageLime – you'll have to provide PageLime with your FTP login credentials.
With Liberate, all you need is to get your webmaster to add in the DIVs and Javascript that Liberate gives you to the HTML page you're trying to update.
This is handy if there's an existing website that's already hosted somewhere that you'll need to update now and then, much faster than porting the whole site to CushyCMS.
Some webmasters aren't too comfortable saving FTP login credentials onto a 3rd party service either.
But technically with this solution your content will be hosted on the Liberate server too. So when that server goes down or gets slow, so does your entire website. PageLime would be the best option in that case. Allowing remote javascript on your site can be just as bad as giving FTP credentials. Besides, you can just create an FTP account for the CMS.
rvschuilenburg, that's true, it's a convenience tradeoff.
On my end, I intend to grow this service at a slower, manageable pace, which which makes it easier to focus on availability for a smaller, more valued user base.