I'm curious about the intended audience for this product: people working professionally in this area are likely to have a predefined workflow that's going to be difficult to fit this into be that: it's 'just not VIM'; it being outside of version control and/or build systems; or any number of other reasons (both with objective and subjective merit).
Is the audience not these professional people? Is it aimed more at the shallower end of the learning curve?
That's something we're still trying to work out ourselves. As for professionals, the aim is to replicate a certain existing workflow, but move it to the web. That workflow is design file > HTML template > ??? (cms template, etc.)
A lot of people just use a text editor, their browser and firebug, so we want to serve those people but with a much faster and streamlined experience.
Comments
I'm curious about the intended audience for this product: people working professionally in this area are likely to have a predefined workflow that's going to be difficult to fit this into be that: it's 'just not VIM'; it being outside of version control and/or build systems; or any number of other reasons (both with objective and subjective merit).
Is the audience not these professional people? Is it aimed more at the shallower end of the learning curve?
That's something we're still trying to work out ourselves. As for professionals, the aim is to replicate a certain existing workflow, but move it to the web. That workflow is design file > HTML template > ??? (cms template, etc.)
A lot of people just use a text editor, their browser and firebug, so we want to serve those people but with a much faster and streamlined experience.