beez_20 and beez5
A template usually contains more than you can see at first glance. Apart from the design, it distinguishes itself by how it is implemented in technical terms.
You may be familiar with the Beez template version 1.5. When I created it, I wanted to build a standards-conforming, easily accessible and adaptable template. I chose to use the color purple to make it obvious that you were meant to customize the template to fix your style rather than use it as it was. I hoped that many designers would use the code, modify it creatively, and make it available for free use. I was counting on a multitude of new templates. Sadly, this has not happened. Many users did not understand how to modify the template, and many others did use the code but did not publish their templates.
I made another mistake in not communicating clearly what I had in mind. The output was structured in such a way that almost any design could be achieved with it, simply and without complications. Easy modifications could also be made in the CCS code. I have kept to this principle with each new version of Beez, while making some important changes. There is now more accessible JavaScript. beez5 has a small portion of HTML5, and beez_20 manages without template overrides because the default output has been adapted to the output of the old Beez templates, so overrides are not required.
In beez5 you will find HTML5 code in the overrides.