more explicite...  It'd be nice to put everything in a div or something
that would scroll all the pre > code elements, but don't know how now..

make the font a bit smaller, but larger on the sidebar...

move styling for sidebar into css from style attribute..

make sure my custom css can override the tufte css (to allow setting
the font size)..

convert the slug into a macro so it can be used else where

make the title link to a slug, but use -title since the bare
slug is the body which doesn't make it go to the title of the
blog post...

make a few of the side bar elements bold (the year and the month)..

This is used for sidebar navigation..  the committed w3.css file has
a few fixes applied to it, see the NOTES.md for more info..

these are based upon slight modifications from the basic template...

they still need to be proofed to make sure they got fully converted.

putting the content in a section tag meaning the css wasn't being
applied like it should..

page working...  This is more documented in NOTES.md, which will
be committed shortly..

Slight modifications to Tufte to have some space on the right, and
add a custom.css to style the tags a bit better...

We can drop article.j2 as it was a test and isn't needed anymore,
and macros.j2 is empty now, and may be used for other things in
the future...

duplicated..  This is to freeze a working version before I try
to make macros work via call blocks...