Info about Vortex CMS (in Norwegian): http://www.uio.no/tjenester/it/web/vortex/
http://bergie.iki.fi/blog/introducing_the_midgard_create_use...
The REST API alternative, CMIS, is unfortunately a bunch of committee-designed mess.
[1] http://www.decalcms.com/page/Decal_API_Quick_Start_Guide
The fact that he specifies the size unit actually suggests that the system would accept others. It's basically CSS after all.
1. An elaborate system of decoupling styling information from content via metadata. (i.e. in situation X, this document's headline should be 20px) Their approach would be pretty interesting here. How could this be preserved as their design/layout evolves with time?
2. He was just indicating that headline in position X be 20px, communicating with the layout.
3. He was hard-setting it to 20px.
It's probably #1. So if, as he says they switch layouts and output to tumblr, how would that work? Their answer might be a lot of manual work, or it could potentially be something really clever.
BTW the in-place edit features remind me a lot of this[1] use of Deface[2] in Spree[3]
[1] http://www.youtube.com/watch?v=qjgQHzYcxIQ
http://www.gethifi.com/blog/first-we-built-an-api-then-we-bu...
That said, I didn't buy everything he said. We've built a farily agnostic API, very much like he described. That said, it's not Mongo, it's not MySQL and it's not CouchDB. It's impossible to build something that is 100% free from constraint and trade-offs.
Blog Engine CMSs are restrictive because they are Blog Engines! You can see that his system has its restrictions too as he enters a pixel based headline size in the demo video.