Thanks Paul. That's a work-flow I'm all too familiar with. Most of our more complex sites are built with .net mvc, which comes down to building static pages and then handing them over to the back-end developers who divide them up into relevant 'chunks'.
This would definitely be an option, but it does mean using a separate IDE, build the whole page, and only then go into MODX. I was mostly wondering how MODX serves as an IDE, i.e. how easy it would be to do front-end development in MODX.
All that would really be needed for that is a code editor and a live screen, which I guess would be a nice plug-in to request since I haven't found anything like it yet.
But even editing CSS, saving, and then refreshing a separate browser window with the relevant page open would be a good option.
Given what is available to MODX now, my question becomes: "How easy is it to use
only the MODX interface to edit CSS?" and "What would the work-flow be when using
only MODX?"
May be it's not easy at all and you're better off building static at first, in which case your answer is the correct one