Have you, as a professional web developer, ever looked at one of
your html files and wondered why there are so many <div
class="">? All the divs and classes are just boilerplate.
The only three html elements a true web dev needs are link
type=stylesheet, script and div,
and as far as a true web developer knows, those are the only three
html elements that exist. Why use <img src=''>
when background-image exists in CSS, and why use
<a href=''> when emcascript has
window.location = ''?
This project seeks to accommodate true web developers by removing the boilerplate. Defined within is a lightweight markup syntax that can be preprocessed into html.
And just in case you think I am building a strawman: web-frameworks
expect you to do exactly this, most web-icon sets don't hand you
images and expect you to know what ::after is, they
expect you to put an empty div with classes in your html, and
probably most importantly, inexcusably and
straw-camel-back-breakingly,
seeing
someone in meatspace with no intention of framework-making convert
content-important img tags to divs-with-background-image.
A sample div-reduce file.
After rendering, the result is example.html
Scala implementations for converting div-reduce to html
Webapp demo of the scala converter