I haven’t been able to figure out how to communicate how valuable I find PostHTML to be and how much I would like to see it get some additional features. As a big fan of PostCSS, I’ve been writing my own version of PostHTML that borrows a lot of the same concepts and brings them to PostHTML.
https://jonathantneal.github.io/posthtml/
The API is nearly fully documented, though I haven’t yet added the tokenizer for classList’ing any attribute (see https://briankardell.wordpress.com/2016/03/29/tokenlists-missing-web-dna/)
I’d love to see these features make their way into an existing library. I’m working on writing the most common Webpack, Express, Grunt, and Gulp bindings, as well as CLI tooling and a handful of common plugins necessary to make it worthwhile.
If you are interested; could you let me know how I could help wire up PRs, or which features you might take issue with?
Feel free to delete this if you are not interested. I’m sorry to bother you. I know my proposal is being pitched in a really weird way.
I haven’t been able to figure out how to communicate how valuable I find PostHTML to be and how much I would like to see it get some additional features. As a big fan of PostCSS, I’ve been writing my own version of PostHTML that borrows a lot of the same concepts and brings them to PostHTML.
https://jonathantneal.github.io/posthtml/
The API is nearly fully documented, though I haven’t yet added the tokenizer for classList’ing any attribute (see https://briankardell.wordpress.com/2016/03/29/tokenlists-missing-web-dna/)
I’d love to see these features make their way into an existing library. I’m working on writing the most common Webpack, Express, Grunt, and Gulp bindings, as well as CLI tooling and a handful of common plugins necessary to make it worthwhile.
If you are interested; could you let me know how I could help wire up PRs, or which features you might take issue with?
Feel free to delete this if you are not interested. I’m sorry to bother you. I know my proposal is being pitched in a really weird way.