3 files changed, 69 insertions, 2 deletions
diff --git a/project/complexity.yml b/project/complexity.yml
index 3060354..883d253 100644
--- a/project/complexity.yml
+++ b/project/complexity.yml
@@ -1,13 +1,14 @@
 
 
-# default directory names are fine too
+# Default directory names are fine too.
 templates_dir: "templates"
 assets_dir: "assets"
 context_dir: "context"
 output_dir: "../www"
 
 
-# I don't know why the hell anyone thought hiding the .html was a good idea
+# I don't know why the hell anyone thought hiding the .html was a good idea.
+# Was this the same person who thought hiding file extensions on Windows was a good plan?
 unexpanded_templates:
  - "about.html"
  - "grasp.html"
@@ -15,4 +16,5 @@ unexpanded_templates:
  - "adapad.html"
  - "stvcount.html"
  - "fltkada.html"
+ - "sunset.html"
 
diff --git a/project/templates/index.html b/project/templates/index.html
index fd97587..fa0abab 100644
--- a/project/templates/index.html
+++ b/project/templates/index.html
@@ -16,6 +16,9 @@
 {% block content %}
 
 <ul class="index">
+    <li><a href="/sunset.html">Sunset License</a><br>
+        <span class="post">(Posted 29/6/2017)</span></li>
+
     <li><a href="/fltkada.html">FLTK Ada Binding</a><br>
         <span class="post">(Posted 25/6/2017)</span></li>
 
diff --git a/project/templates/sunset.html b/project/templates/sunset.html
new file mode 100644
index 0000000..042e936
--- /dev/null
+++ b/project/templates/sunset.html
@@ -0,0 +1,62 @@
+
+{% extends "base.html" %}
+
+
+
+{% block title %}Sunset License{% endblock %}
+
+
+
+{% block content %}
+
+<h4>Sunset License</h4>
+<h5>29/6/2017</h5>
+
+<p>Software licenses bother me. As a general rule I prefer to make my projects open source,
+and for that purpose something like the <a href="https://unlicense.org/" target="_blank">Unlicense</a>
+is often sufficient. But if I don't want to put my work in the public domain immediately, then
+I have to make use of a <a href="https://www.copyleft.org/">copyleft</a> license. And all
+of the ones currently available are both incredibly, unnecessarily verbose, and fail to
+address the primary failing of modern copyright law, which is the unreasonably long term
+lengths.</p>
+
+<p>So after a considerable amount of thought, I've written my own. (I can hear those with
+legal knowledge wailing and gnashing their teeth already.) Care has been taken to mimic the
+phrasing used in popular existing licenses where possible. I've also kept it as simple and as
+straightforward as I can make it. So hopefully there are no loopholes and it's exactly as it
+appears: a simple weak copyleft license which places older parts of a work under a public
+domain disclaimer in a reasonable timeframe.</p>
+
+<p>The full text is as follows:</p>
+<pre>
+SUNSET LICENSE
+Version 1.0, June 2017
+
+1. You may copy, modify, use, sell, or distribute this work, verbatim or
+modified, for any purpose.
+
+2. If you sell or distribute this work, whether verbatim or modified, you must
+include a copy of this license, and you must make the source code available for
+no extra charge.
+
+3. A modified version of this work must be clearly labeled as such.
+
+4. Derivative works must also be licensed under this license or a license of
+equivalent terms. As an exception, linking this work with another, whether
+statically or dynamically, does not impose any license requirements on the
+other work.
+
+5. If a minimum of 15 years have passed since the date of first publishing for
+a part of this work, then that part is placed into the public domain and you
+may do whatever you want with it, regardless of all other clauses.
+</pre>
+
+<p>The license file, accompanying detailed rationale, and a simple logo I threw together can
+all be found in <a href="/cgit/cgit.cgi/sunset.git/" target="_blank">this</a> repo.</p>
+
+<p>In the future, all my projects will either use this license or the Unlicense. Works I've
+already created will be relicensed as appropriate.</p>
+
+{% endblock %}
+
+