Easy is hard. That is, to make something easy for users, you have to work hard to build great tools for them. Helix appears to be punting on that. Examples: >

Easy is hard. That is, to make something easy for users, you have to work hard to build great tools for them. Helix appears to be punting on that. Examples: > Helix dynamically renders HTML via Markdown that is generated from the content source documents. Markdown is a lossy format. Sometimes that's good (it'll strip unwanted Word formatting), but there are vital things that get lost too. (The easiest to grasp are the internationalisation issues, like mixing right-to-left and left-to-right scripts in the same paragraph, or multiple language spans.) > To add metadata to your page, create a table like this at the end of the document And how is this better than an actual tool, with actual field validation, helpful UX, etc? It's not: it's undiscoverable magic boxes with inexplicable (to the user) side-effects that oblige users to remember secret incantations (or sticky them to their screens) and hope everything works out all right. This is the opposite of "intuitive and fast". Which anybody familiar with AEM won't be surprised by.