and are structured
grant (permissions)
conditioned on (conditions)
with limitations
Permissions coming first combats mistaken but apparently widespread
impression that licenses impose conditions, even such that without
a license, there would be no conditions/work would be in the public
domain.
Requirements->Conditions emphasizes that they are pertinent if one
wants to take advantage of permissions.
Forbiddens->Limitations is more accurate: in most cases licenses
don't give permission to hold licensors liable, in some cases to
use licensors' trademarks or patents, but a licensee does not lose
the permissions granted by the license if the licensee holds licensor
liable, etc. Also emphasizes that there are limitatations on the
license grant, not that the license imposes prohibitions.
The most concise place to see both the rename and reorder is in
_includes/license-overview.html
I did not reorder the appearance of the groups of properties in
license source files (.txt files in _licenses) as those orderings
are not used to render anything on the webiste. Might do so later.
We already do this in the license bodies, and we need to
match here (currently we just print junk like `replace <>
with ...` because we end up with garbled HTML.
This replacement should arguably be factored out, as it
would want to be the same everywhere (and we might want to
make it bold everywhere or something).
* Move licenses to license template
* Move home / about to page template
* Move annotations to config file, included via annotations.js
* Move license metadata to YML Front matter
* Automate the presentation of license metadata
* Move sidebar to include
* Add _site to gitignore
