> Lektor is file-based by default, so updating content does not require a cloud server at all but merely access to the root file itself, which can be stored on a service like Dropbox or Google Drive. A developer can use a local server to generate dynamic content and a full-featured site, but the CMS, which is currently a simple Mac app, simply updates the original file.
This. This would be something phenomenal. The problem with WordPress and services like it, is that they take your content, package them into something they can understand and hides them under their pillows.
Inverting the control, like what the OP says -- where the user owns the content, that can be plugged into layers like WordPress, looks like the path towards the future.
I made http://hexopress.com with a similar vision. It is not yet a full blown shape of what I have in mind, but it cuts the concept well.
This. This would be something phenomenal. The problem with WordPress and services like it, is that they take your content, package them into something they can understand and hides them under their pillows.
Inverting the control, like what the OP says -- where the user owns the content, that can be plugged into layers like WordPress, looks like the path towards the future.
I made http://hexopress.com with a similar vision. It is not yet a full blown shape of what I have in mind, but it cuts the concept well.