a dynamically structured <form> is much faster for content people to work with than contenteditable crap. our flow is like: * does content have more than X nu

a dynamically structured <form> is much faster for content people to work with than contenteditable crap. our flow is like: * does content have more than X number of words? * yes: prompt if the content has to be promoted as special "tweet" like feature * is the content tagged as Y and Z , or A, or B and C? * yes: prompt for other ways to promote the content. * does the content include video? * yes: prompt if the content needs to be featured in video playlists in a section page. * is it also tagged as D? should it be promoted in another section's hot-play list? * ... our content people start with simple form asking for title, author, tags, and content (html). the content is parsed to see if any of our media (image, video, audio) is embedded. if our games are included... etc. And depending on the title, tags, author, content new input fields are injected dynamically. order of dynamic fields are carefully chosen so that workflow is optimal. we initially went with contenteditable blocks (or components). that failed miserably: database became complicated. We ended up building something similar to DOM tree in database. start with a simple form. analyze user input. dynamically add/remove more fields.