DOM-ERB is a prototype for an ERB based HTML template system that has the following benefits over regular ERB HTML templates:
- The template file is a standalone renderable HTML file and can be viewed directly in a browser.
- The template file can contain seed data so that directly viewing it in a browser gives a realistic result.
- Because of these benefits, users can work on it without the need to install any sort of processor dependencies, lowering the barrier to contribution. (E.g. setting up a full web-app stack.)
- Without the optional
description
and 1platform
entry: https://gist.github.com/alloy/ee073e642e981b7326e3 - With the optional
description
and 2platform
entries: https://gist.github.com/alloy/9ce3e8c48ab0d1af94c4
And as I said before, I think anything beyond replacing element content is a Bad Idea® and People Who Edit This Will Get Confused And Fuck That Up™.
For example, one thing those pesky web designers always seem to want to be able to do is this:
How are you planning to support that (without adding a ton of additional markup that’s not needed)?