September 18, 2018

One API for all CMSs

I'm building a set of APIs that can help you to distribute content through all mainstream CMS systems. Anyone out there is interested in this idea as well? Want to validate it before putting too much time into it.


  1. 1

    What do you mean by "through all mainstream CMS systems"? (sorry it that's a simple question, I don't know too much about this area)

  2. 1

    Two thoughts:

    • There are two 'unified API' providers that I'm aware of -- cloud elements is the big one; a newer player is cloudrail. To my knowledge, neither deals in CMS, but maybe worth investigating to see how that market, who they market to, etc.

    • Main question is the demand for a unified CMS API and if you're playing a chicken and egg game. Is this primary for simple migration from wix to squarespace or wordpress or forestry (which means you're targeting people that are thinking about long term implications of lock in)? Or are you imagining agnostic content creation tools that could then post to these CMSs (which have probably not yet been created) or something else? In my experience, we've only changed CMS when we've done a major overhaul and the hardest part for us (old blog entries) was taken care of by importers in the new CMS. Maybe I'm missing a core value prop here though...

    fwiw.