3 ms·
I prefer that the content rendering system should be completely seperate from the content editing system - very few systems do that though. In my experience th
by timclark 16y ago
I prefer that the content rendering system should be completely seperate from the content editing system - very few systems do that though.
In my experience the rendering system and editing system probably have very different performance and scalability requirements.
I agree that having the edited content looking visually different from the rendered content is usually a bad thing.
- bergie 16y agoThis allows you to still communicate with a separate backend, just implement Backbone.sync in the way you need. There is even a guy implementing this system for Jekyll (a static HTML blog generation tool)
- balupton 16y agoThat guy has a name Bergie! Hehehe. It's me btw :)
- modernerd 16y agoPerhaps that's why WordPress doesn't do it yet. To offload CMS functionality onto theme designers (and to make it a requirement to be able to use WP) might prove disastrous; the editing experience could become inconsistent between themes.