3 ms·
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
by Joe8Bit 14y ago
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?
- jmitcheson 14y agoThat'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.
- deleted 14y ago[deleted]
- Joe8Bit 14y agoFair enough, but I suspect people building more complex applications fall outside of that simple "CMS" based workflow, in my context the tool feels more suitable to designers producing prototypes than front-end developers producing complex production quality applications. I also suspect your assumption that people's workflow involves a intermediate step of creating an HTML template between a flat design and a "final" implementation (in whatever form) isn't necessarily a completely sound one.