I know this may seem like a sarcastic response, but it isn't...
Why not just write the HTML and CSS?
I will occasionally work on a static site for a friend or colleague, and I can't understand why - for some folks - instead of "spreading the butter onto the bread" it becomes a huge project of figuring out how to "evenly distribute all butter dependencies within the scope of a bread slice, which will often have optional properties associated with them."
I code an HTML template with <!-- CONTENT GOES HERE--> within the body. I link to a CSS file. Now, every time I create a new page, I use the _template.html for the base (adding any necessary styles to the CSS file.)
Done.
If you're looking for vanilla HTML/CSS that is a tad more capable of things, such as includes or partials, then - as a developer - Gulp is a nice way to automate various things, including the ability to use Sass, concatenate header/body/footer content, etc. This is also where Codekit or Prepros can come in handy, too - since I would say that this is going a bit beyond KISSing the project ("Keep It Short and Simple").
However, unless it's something personal - or I feel it will speed up the process - I simply "spread the butter onto the bread."