3 ms·
This is great – however, there's space for improvement, namely, flattening the JSON. Readability may also benefit from the addition of a few backslashes added b
by masswerk 7y ago
This is great – however, there's space for improvement, namely, flattening the JSON. Readability may also benefit from the addition of a few backslashes added by this procedure. A further step of x-www-form-url encoding or base64 encoding (maybe even as a data-URL?) may also add another as pleasing as satisfying step to you tool chain!
- masswerk 7y agoPersonally, I'd prefer a more explicit declaration, which is also legitimate CSS, as in: html > body > h1 { content: "Example"; } html > body > h1 + p { content: "First Paragraph"; } html > body > h1 + p + p ( content: "Second Paragraph"; } html > body > h1 + p + p + ul > li:first-child { content: "A List Item"; } (etc) Mind how missing content or copy text, like the second paragraph being omitted, may be easily detected!