Update partial

.gitignore

@@ -3,6 +3,9 @@
 /public/
 /resources/_gen/
 
+# Don't take into account the openring generated
+layouts/partials/openring-out.html
+
 # Executable may be added to repository
 hugo.exe
 hugo.darwin

LICENSE.md

@@ -1,20 +1,675 @@
-The MIT License (MIT)
+### GNU GENERAL PUBLIC LICENSE
 
-Copyright (c) 2018 Joe Hutchinson
+Version 3, 29 June 2007
 
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
-the Software, and to permit persons to whom the Software is furnished to do so,
-subject to the following conditions:
+Copyright (C) 2007 Free Software Foundation, Inc.
+<https://fsf.org/>
 
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
-FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
-COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
-IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
-CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+### Preamble
+
+The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+the GNU General Public License is intended to guarantee your freedom
+to share and change all versions of a program--to make sure it remains
+free software for all its users. We, the Free Software Foundation, use
+the GNU General Public License for most of our software; it applies
+also to any other work released this way by its authors. You can apply
+it to your programs, too.
+
+When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights. Therefore, you
+have certain responsibilities if you distribute copies of the
+software, or if you modify it: responsibilities to respect the freedom
+of others.
+
+For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. You must make sure that they, too, receive
+or can get the source code. And you must show them these terms so they
+know their rights.
+
+Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software. For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the
+manufacturer can do so. This is fundamentally incompatible with the
+aim of protecting users' freedom to change the software. The
+systematic pattern of such abuse occurs in the area of products for
+individuals to use, which is precisely where it is most unacceptable.
+Therefore, we have designed this version of the GPL to prohibit the
+practice for those products. If such problems arise substantially in
+other domains, we stand ready to extend this provision to those
+domains in future versions of the GPL, as needed to protect the
+freedom of users.
+
+Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish
+to avoid the special danger that patents applied to a free program
+could make it effectively proprietary. To prevent this, the GPL
+assures that patents cannot be used to render the program non-free.
+
+The precise terms and conditions for copying, distribution and
+modification follow.
+
+### TERMS AND CONDITIONS
+
+#### 0. Definitions.
+
+"This License" refers to version 3 of the GNU General Public License.
+
+"Copyright" also means copyright-like laws that apply to other kinds
+of works, such as semiconductor masks.
+
+"The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+
+To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of
+an exact copy. The resulting work is called a "modified version" of
+the earlier work or a work "based on" the earlier work.
+
+A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user
+through a computer network, with no transfer of a copy, is not
+conveying.
+
+An interactive user interface displays "Appropriate Legal Notices" to
+the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+#### 1. Source Code.
+
+The "source code" for a work means the preferred form of the work for
+making modifications to it. "Object code" means any non-source form of
+a work.
+
+A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users can
+regenerate automatically from other parts of the Corresponding Source.
+
+The Corresponding Source for a work in source code form is that same
+work.
+
+#### 2. Basic Permissions.
+
+All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not convey,
+without conditions so long as your license otherwise remains in force.
+You may convey covered works to others for the sole purpose of having
+them make modifications exclusively for you, or provide you with
+facilities for running those works, provided that you comply with the
+terms of this License in conveying all material for which you do not
+control copyright. Those thus making or running the covered works for
+you must do so exclusively on your behalf, under your direction and
+control, on terms that prohibit them from making any copies of your
+copyrighted material outside their relationship with you.
+
+Conveying under any other circumstances is permitted solely under the
+conditions stated below. Sublicensing is not allowed; section 10 makes
+it unnecessary.
+
+#### 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such
+circumvention is effected by exercising rights under this License with
+respect to the covered work, and you disclaim any intention to limit
+operation or modification of the work as a means of enforcing, against
+the work's users, your or third parties' legal rights to forbid
+circumvention of technological measures.
+
+#### 4. Conveying Verbatim Copies.
+
+You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+#### 5. Conveying Modified Source Versions.
+
+You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these
+conditions:
+
+-   a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+-   b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under
+    section 7. This requirement modifies the requirement in section 4
+    to "keep intact all notices".
+-   c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy. This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged. This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+-   d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+#### 6. Conveying Non-Source Forms.
+
+You may convey a covered work in object code form under the terms of
+sections 4 and 5, provided that you also convey the machine-readable
+Corresponding Source under the terms of this License, in one of these
+ways:
+
+-   a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+-   b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the Corresponding
+    Source from a network server at no charge.
+-   c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source. This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+-   d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge. You need not require recipients to copy the
+    Corresponding Source along with the object code. If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source. Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+-   e) Convey the object code using peer-to-peer transmission,
+    provided you inform other peers where the object code and
+    Corresponding Source of the work are being offered to the general
+    public at no charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal,
+family, or household purposes, or (2) anything designed or sold for
+incorporation into a dwelling. In determining whether a product is a
+consumer product, doubtful cases shall be resolved in favor of
+coverage. For a particular product received by a particular user,
+"normally used" refers to a typical or common use of that class of
+product, regardless of the status of the particular user or of the way
+in which the particular user actually uses, or expects or is expected
+to use, the product. A product is a consumer product regardless of
+whether the product has substantial commercial, industrial or
+non-consumer uses, unless such uses represent the only significant
+mode of use of the product.
+
+"Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to
+install and execute modified versions of a covered work in that User
+Product from a modified version of its Corresponding Source. The
+information must suffice to ensure that the continued functioning of
+the modified object code is in no case prevented or interfered with
+solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or
+updates for a work that has been modified or installed by the
+recipient, or for the User Product in which it has been modified or
+installed. Access to a network may be denied when the modification
+itself materially and adversely affects the operation of the network
+or violates the rules and protocols for communication across the
+network.
+
+Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+#### 7. Additional Terms.
+
+"Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders
+of that material) supplement the terms of this License with terms:
+
+-   a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+-   b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+-   c) Prohibiting misrepresentation of the origin of that material,
+    or requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+-   d) Limiting the use for publicity purposes of names of licensors
+    or authors of the material; or
+-   e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+-   f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions
+    of it) with contractual assumptions of liability to the recipient,
+    for any liability that these contractual assumptions directly
+    impose on those licensors and authors.
+
+All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions; the
+above requirements apply either way.
+
+#### 8. Termination.
+
+You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+However, if you cease all violation of this License, then your license
+from a particular copyright holder is reinstated (a) provisionally,
+unless and until the copyright holder explicitly and finally
+terminates your license, and (b) permanently, if the copyright holder
+fails to notify you of the violation by some reasonable means prior to
+60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+#### 9. Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or run
+a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+#### 10. Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+#### 11. Patents.
+
+A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+
+A contributor's "essential patent claims" are all patent claims owned
+or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+A patent license is "discriminatory" if it does not include within the
+scope of its coverage, prohibits the exercise of, or is conditioned on
+the non-exercise of one or more of the rights that are specifically
+granted under this License. You may not convey a covered work if you
+are a party to an arrangement with a third party that is in the
+business of distributing software, under which you make payment to the
+third party based on the extent of your activity of conveying the
+work, and under which the third party grants, to any of the parties
+who would receive the covered work from you, a discriminatory patent
+license (a) in connection with copies of the covered work conveyed by
+you (or copies made from those copies), or (b) primarily for and in
+connection with specific products or compilations that contain the
+covered work, unless you entered into that arrangement, or that patent
+license was granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+#### 12. No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under
+this License and any other pertinent obligations, then as a
+consequence you may not convey it at all. For example, if you agree to
+terms that obligate you to collect a royalty for further conveying
+from those to whom you convey the Program, the only way you could
+satisfy both those terms and this License would be to refrain entirely
+from conveying the Program.
+
+#### 13. Use with the GNU Affero General Public License.
+
+Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+#### 14. Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions
+of the GNU General Public License from time to time. Such new versions
+will be similar in spirit to the present version, but may differ in
+detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies that a certain numbered version of the GNU General Public
+License "or any later version" applies to it, you have the option of
+following the terms and conditions either of that numbered version or
+of any later version published by the Free Software Foundation. If the
+Program does not specify a version number of the GNU General Public
+License, you may choose any version ever published by the Free
+Software Foundation.
+
+If the Program specifies that a proxy can decide which future versions
+of the GNU General Public License can be used, that proxy's public
+statement of acceptance of a version permanently authorizes you to
+choose that version for the Program.
+
+Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+#### 15. Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
+WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT
+LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND
+PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
+DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
+CORRECTION.
+
+#### 16. Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR
+CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
+ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT
+NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR
+LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM
+TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER
+PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+#### 17. Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+END OF TERMS AND CONDITIONS
+
+### How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these
+terms.
+
+To do so, attach the following notices to the program. It is safest to
+attach them to the start of each source file to most effectively state
+the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+        <one line to give the program's name and a brief idea of what it does.>
+        Copyright (C) <year>  <name of author>
+
+        This program is free software: you can redistribute it and/or modify
+        it under the terms of the GNU General Public License as published by
+        the Free Software Foundation, either version 3 of the License, or
+        (at your option) any later version.
+
+        This program is distributed in the hope that it will be useful,
+        but WITHOUT ANY WARRANTY; without even the implied warranty of
+        MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+        GNU General Public License for more details.
+
+        You should have received a copy of the GNU General Public License
+        along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper
+mail.
+
+If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+        <program>  Copyright (C) <year>  <name of author>
+        This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+        This is free software, and you are welcome to redistribute it
+        under certain conditions; type `show c' for details.
+
+The hypothetical commands \`show w' and \`show c' should show the
+appropriate parts of the General Public License. Of course, your
+program's commands might be different; for a GUI interface, you would
+use an "about box".
+
+You should also get your employer (if you work as a programmer) or
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. For more information on this, and how to apply and follow
+the GNU GPL, see <https://www.gnu.org/licenses/>.
+
+The GNU General Public License does not permit incorporating your
+program into proprietary programs. If your program is a subroutine
+library, you may consider it more useful to permit linking proprietary
+applications with the library. If this is what you want to do, use the
+GNU Lesser General Public License instead of this License. But first,
+please read <https://www.gnu.org/licenses/why-not-lgpl.html>.

README.md

@@ -1,6 +1,8 @@
 # blogotheme
+
 The theme for my blog, used by the Hugo static website generator. It's based on the design of newspapers, brutalist web design, and inspired by the solar website built by low tech magazine.
 
+![](cover.png)
 
 ## Features
  - It's **Fast**! PageSpeed scores consistently between 94-100
@@ -14,10 +16,11 @@ The theme for my blog, used by the Hugo static website generator. It's based on
 
 
 ## Installation
+
 In the root directory of your Hugo Project, clone the repo into the themes directory.
 
 ```shell session
-git clone TODO themes/blogotheme
+git clone http://git.n07070.xyz/n07070/blogotheme.git themes/blogotheme
 ```
 
 ## Usage
@@ -98,7 +101,7 @@ The `dropCap` parameter is used to determine if the first letter of a post shoul
 
 Add an interesting description and a good image to each post to get the most value from this theme.
 
-Aether takes advantage of [page bundles](https://gohugo.io/content-management/page-bundles/) to optimize your images for your site.  This may require you to update the way your content is structured, also see [content organization](https://gohugo.io/content-management/organization/).  Use the `image` and `smallimg` shortcodes to take full advantage of image optimization.  Also, the `featuredImage` resource must exist in the post's page bundle.
+Blogotheme takes advantage of [page bundles](https://gohugo.io/content-management/page-bundles/) to optimize your images for your site.  This may require you to update the way your content is structured, also see [content organization](https://gohugo.io/content-management/organization/).  Use the `image` and `smallimg` shortcodes to take full advantage of image optimization.  Also, the `featuredImage` resource must exist in the post's page bundle.
 
 Posts are written in markdown. You can find how to write in markdown from this [markdown cheatsheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet).
 
@@ -146,7 +149,7 @@ You can add optional Open Graph, Twitter, or other meta tags by adding `project_
 Refer to [/exampleSite/layouts/partials](/exampleSite/layouts/partials) for sample meta configs.
 
 ## Helpful Links
-[Aether Blog Post](https://www.joehutch.com/posts/blogotheme-theme/) - See blogotheme in action and learn more about the theme
+[Blogotheme in action](https://n07070.xyz) - See blogotheme in action and learn more about the theme
 
 [Hugo Documentation](https://gohugo.io/documentation/) - Learn how to use Hugo
 
@@ -158,4 +161,6 @@ Refer to [/exampleSite/layouts/partials](/exampleSite/layouts/partials) for samp
 I welcome you to help make it better! Contributions in the way of new features, documentation improvements, bug fixes, and feature requests are appreciated. Please make an individual pull-request/issue for each suggestion.
 
 ## License
-AGPLV - N07070
+AGPLV3 - N07070
+
+Based on the Aether Theme 

assets/css/override.css

@@ -5,6 +5,21 @@
   * You should not modify this file.
   */
 
+/* Enable smooth scrolling for footnotes. */
+
+html {
+    scroll-behavior: smooth;
+}
+
+
+ol > li > ::first-line {
+line-height: 3.1em;
+
+}
+/*
+  * Dark theme  
+  */
+
 @media (prefers-color-scheme: dark) {
   body {
     color: #eee;
@@ -17,7 +32,9 @@
 
   .content {
       background: #121212;
-      box-shadow: 0 0.7rem 2.3rem 0 rgba(255,255,255,0.3);
+      border: solid;
+      border-width: 3px;
+      border-color: white;
   }
 
   .card-container {
@@ -42,6 +59,10 @@
   .blog-card {
       background:  #121212;
       color: white;
+      border: solid;
+      border-color: white;
+      border-width: 3px;
+
   }
 
   .blog-card h2{

assets/css/print.css

@@ -42,6 +42,7 @@
        text-align: justify;
        margin: 0;
        max-width: none;
+       box-shadow: none;
 
    }
 
@@ -60,11 +61,23 @@
    }
 
    footer {
-       color: black;
        font-size: 1em;
+       padding: 1em;
    }
 
    footer::after {
-       content: "Printed from https://n07070.xyz"
+       content: "Printed from https://n07070.xyz";
+       font-size: 1em;
+       font-weight: bolder;
+       display: flex;
+        justify-content: center;
+   }
+
+   footer small {
+       display: none;
+   }
+
+   footer sup {
+       display: none;
    }
 }

assets/css/style.css

@@ -18,23 +18,20 @@ body {
                  "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif;
     color: #454545;
     font-size: 1.1em;
-    /* background: linear-gradient(90deg, #000 21px, transparent 1%) center, linear-gradient(#000 21px, transparent 1%) center, white; */
     background-size: 22px 22px;
     margin: 0;
     display: flex;
     flex-direction: column;
     align-items: center;
     width: 100%;
-    box-sizing: border-box;
+    /* box-sizing: border-box; */
     word-break: break-word;
-
-
 }
 
-}
 p {
     margin: 1.5em 0;
 }
+
 .home-header {
     min-height: 26rem;
     max-width: 50rem;
@@ -55,7 +52,7 @@ p {
     width: 100%;
     background-color: white;
     border-radius: 1.2rem;
-    box-shadow: 0 0.7rem 2.3rem 0 rgba(0,0,0,0.3);
+    /* box-shadow: 0 0.7rem 2.3rem 0 rgba(0,0,0,0.3); */
 }
 .home-faceshot {
     margin: 0;
@@ -82,11 +79,12 @@ p {
     /* display: flex; */
     justify-content: space-between;
     align-items: center;
+    border-color: black;
 }
 .nav-header {
     margin: 0;
     padding: 0.4em;
-    font-size: 1.4em;
+    font-size: 1.5em;
 }
 .nav-text {
     font-weight: normal;
@@ -94,7 +92,7 @@ p {
     z-index: 105;
     color: black;
     font-weight: bolder;
-    font-size: 3rem;
+    font-size: 5rem;
 }
 
 
@@ -102,6 +100,7 @@ p {
 
 .menu-container {
     align-content: space-between;
+    display: flex;
 }
 
 #menu {
@@ -129,14 +128,14 @@ p {
 
 
 .post {
-    margin: 0 0 1em 0;
+    margin: 3vw 1.8vw 3vw 1.8vw;
     line-height: 1.9;
 }
 .post-header {
     margin: 0 0 1.5em 0;
 }
 .post-title {
-    font-size: 1.8em;
+    font-size: 2em;
     font-weight: 500;
     line-height: 1.2;
     margin: 0 0 0.4em 0;
@@ -152,24 +151,28 @@ p {
     margin: 1.5em 0;
 }
 .dropcase > p:first-of-type::first-letter {
-    float: left;
+    /* float: left; */
     font-size: 3em;
     line-height: 1;
-    margin: 0.08em 0.15em -0.4em 0;
-    /* initial-letter: 2; Maybe someday*/
+    /* margin: 0.08em 0.15em -0.4em 0; */
+    font-family: serif;
 }
 .content {
     background-color: white;
     /* padding: 2em 0; */
     margin-bottom: 3rem;
     margin-top: 1em;
-    width: 100%;
+    /* width: 100%; */
     max-width: 50rem;
     /* border-radius: 1.2rem; */
     z-index: 2;
-    transition: transform 0.2s cubic-bezier(0.25,0.8,0.25,1), box-shadow 0.2s cubic-bezier(0.25,0.8,0.25,1);
-    box-shadow: 0 0.7rem 2.3rem 0 rgba(0,0,0,0.3);
+    /* transition: transform 0.2s cubic-bezier(0.25,0.8,0.25,1), box-shadow 0.2s cubic-bezier(0.25,0.8,0.25,1); */
+
+    border: solid;
+    border-width: 3px;
+    border-color: black;
 }
+
 .list-header {
     margin: 1em;
     text-align: center;
@@ -189,22 +192,22 @@ p {
     margin: 5em 0;
     line-height: 1.6em;
 }
-.card-container {
-    max-width: 48rem;
-}
+
 /* .card-container > a:first-of-type {
     margin-top: 5em;
 } */
+
 .card {
     display: block;
-    margin: 3rem 0;
-    box-sizing: border-box;
+    /* margin: 3rem 0; */
+    width: 100%;
+    max-width: 50rem;
+    /* /* box-sizing: border-box; */ */
     background-color: white;
     text-decoration: none;
     /* border-radius: 1.2rem; */
     -webkit-tap-highlight-color: rgba(0, 0, 0, 0);
-    transition: transform 0.2s cubic-bezier(0.25,0.8,0.25,1), box-shadow 0.2s cubic-bezier(0.25,0.8,0.25,1);
-    box-shadow: 0 0.7rem 2.3rem 0 rgba(0,0,0,0.3);
+    /* transition: transform 0.2s cubic-bezier(0.25,0.8,0.25,1), box-shadow 0.2s cubic-bezier(0.25,0.8,0.25,1); */
 }
 .home-card {
     padding: 0.8em;
@@ -217,12 +220,24 @@ p {
 }
 .blog-card {
     display: flex;
+
+    border: solid;
+    border-color: black;
+    border-width: 3px;
+
     flex-direction: column;
     align-items: stretch;
-    border-style: solid;
+    border-style: none;
+    margin-bottom: 1em;
 }
+
+/* .blog-card-feed {
+  margin: 1em;
+} */
+
 .bc-next {
     margin-top: 0;
+
 }
 .card-img-container {
     position: relative;
@@ -236,14 +251,13 @@ p {
     object-fit: cover;
 }
 .card-img-overlay {
-    /* border-radius: 0.8rem 0.8rem 0 0; */
     position: absolute;
     top: 0;
     font-size: 1.27em;
     text-align: center;
     padding: 0.77em 0;
     width: 100%;
-    box-sizing: border-box;
+    /* /* box-sizing: border-box; */ */
     margin: 0;
     color: white;
     background-color: rgba(0, 0, 0, 0.4);
@@ -280,33 +294,37 @@ p {
 }
 .end-nav {
     width: 100%;
-    max-width: 48rem;
     z-index: 2;
 }
 .pagination-nav {
     margin: 2em 0;
-    width: 100%;
     max-width: 47rem;
 }
-/* .pagination-text {
-    font-family: 'LatoLatinWebMedium';
-} */
+
+.pagination-text {
+    font-weight: bold;
+    color: inherit;
+    padding: 1rem;
+    text-align: center;
+    align-content: center;
+}
+
 .pagination-newer {
-    float:left;
+    float:right;
 }
 .pagination-older {
-    float: right;
+    float: left;
 }
 .button {
     padding: 0.5em 0.6em;
     background-color: #FFF;
     text-decoration: none;
     border-radius: 0.3rem;
-    transition: transform 0.1s cubic-bezier(0.25,0.8,0.25,1), box-shadow 0.1s cubic-bezier(0.25,0.8,0.25,1);
-    box-shadow: 0 0.7rem 2.3rem 0 rgba(0,0,0,0.3);
+    /* transition: transform 0.1s cubic-bezier(0.25,0.8,0.25,1), box-shadow 0.1s cubic-bezier(0.25,0.8,0.25,1); */
+    /* box-shadow: 0 0.7rem 2.3rem 0 rgba(0,0,0,0.3); */
 }
 .button:hover {
-    box-shadow: 0 0.05rem 0.15rem rgba(0,0,0,0.12), 0 0.05rem 0.1rem rgba(0,0,0,0.24);
+    /* box-shadow: 0 0.05rem 0.15rem rgba(0,0,0,0.12), 0 0.05rem 0.1rem rgba(0,0,0,0.24); */
     transform: scale(0.97);
 }
 .button:active {
@@ -319,12 +337,12 @@ p {
 .side-padding {
     padding-left: 1.2rem !important;
     padding-right: 1.2rem !important;
-    box-sizing: border-box !important;
+    /* /* box-sizing: border-box !important; */ */
 }
 .side-text-padding {
     padding-left: 1.2rem !important;
     padding-right: 1.2rem !important;
-    box-sizing: border-box !important;
+    /* /* box-sizing: border-box !important; */ */
 }
 .small-pic {
     display: block;
@@ -389,6 +407,7 @@ code {
     line-height: 1.5;
     border-radius: 0.3rem;
     background-color: #f5f6f7;
+    color: orangered;
 }
 pre > code {
     margin: 1.5em 0;
@@ -482,7 +501,6 @@ footer h3 {
 
     .nav-header {
         margin: 0;
-        font-size: 1.4em;
         background-color: white;
     }
 
@@ -510,6 +528,10 @@ footer h3 {
     .blog-card {
         flex-direction: row;
         align-items: stretch;
+        border: solid;
+        border-color: black;
+        border-width: 3px;
+        border-style: solid;
     }
     .card-img {
         margin: 0;
@@ -517,9 +539,8 @@ footer h3 {
         height: 100%;
         width: 16em;
     }
-    .card-img-overlay {
-        border-radius: 0.8rem 0.8rem 0 0;
-    }
+
+
     .card-body {
         margin: 1.3em 1.7em;
     }
@@ -534,12 +555,7 @@ footer h3 {
         font-size: 0.7em;
         margin-bottom: 0.7em;
     }
-    .content {
-        /* border-radius: 1.2rem; */
-    }
-    .post {
-        margin: 1em 1.8em 2em 1.8em;
-    }
+
     .post-title {
         font-size: 2em;
     }

exampleSite/config.toml

@@ -1,16 +0,0 @@
-baseurl = "https://example.com"
-title = "Hugo Themes - aether"
-author = "Joe Hutchinson"
-canonifyurls = true
-paginate = 3
-theme = "aether"
-themesDir = "../../" 
-
-[params]
-    brand = "aether"
-    description = "aether Hugo theme for blogs"
-    headshotimg = "img/faceshot.jpg"
-
-[markup]
-  [markup.highlight]
-    style = "igor"

exampleSite/content/_index.md

@@ -1,5 +0,0 @@
----
-title: "aether"
-date: 2018-04-27T09:46:15-04:00
-description: "A clean Hugo theme for blogs emphasizing motion, material, and depth."
----

exampleSite/content/about/index.md

@@ -1,20 +0,0 @@
-+++
-title = "About Hugo"
-date = "2014-04-09"
-displayInMenu = true
-displayInList = false
-dropCap = false
-+++
-
-Hugo is the **world’s fastest framework for building websites**. It is written in Go.
-
-It makes use of a variety of open source projects including:
-
-* https://github.com/russross/blackfriday
-* https://github.com/alecthomas/chroma
-* https://github.com/muesli/smartcrop
-* https://github.com/spf13/cobra
-* https://github.com/spf13/viper
-
-Learn more and contribute on [GitHub](https://github.com/gohugoio).
-

exampleSite/content/posts/aether-features/index.md

@@ -1,135 +0,0 @@
----
-title: "Aether Features"
-date: 2018-12-19T10:35:35-05:00
-description: "Hugo combined with the Aether theme turns easy to write markdown into powerful web pages.  KaTeX, Highlight.js, and Hugo provides the ability to create mathmatical symobols, equations, highlighted code, tables, lists, and much more."
-categories: ["Features"]
-dropCap: true
-displayInMenu: false
-displayInList: true
-draft: false
-resources:
-- name: featuredImage
-  src: "mdd-iphone.jpg"
----
-
-Hugo combined with the Aether theme turns easy to write markdown into powerful web pages.  KaTeX, Highlight.js, and Hugo provides the ability to create mathmatical symobols, equations, highlighted code, tables, lists, and much more.
-
-For each feature below, the first line is the markdown and the second line is the result after Hugo, KaTeX, and Highlight.js process the markdown.  You can find many more features in the Hugo documentation.
-
-## LaTeX style math typsetting with KaTeX
-
-```md
-{{</* raw */>}}
-\[u(t) = K_p e(t) + K_i \int_{0}^{t} e(\tau) d\tau + K_d \frac{de(t)}{dt} \]
-{{</* /raw */>}}
-```
-
-{{< raw >}}
-\[u(t) = K_p e(t) + K_i \int_{0}^{t} e(\tau) d\tau + K_d \frac{de(t)}{dt} \]
-{{< /raw >}}
-
-## Code (Supports many programming languages and formats)
-
-````md
-```javascript
-var s = "JavaScript syntax highlighting";
-alert(s);
-```
-````
-
-```javascript
-var s = "JavaScript syntax highlighting";
-alert(s);
-```
-
-## Inline code
-
-```md
-Here is `var s = "Hello World"` inline code
-```
-
-Here is `var s = "Hello World"` inline code
-
-## Tables 
-
-```md
-| Tables        | Are           | Cool  |
-| ------------- |:-------------:| -----:|
-| col 3 is      | right-aligned | $1600 |
-| col 2 is      | centered      |   $12 |
-| zebra stripes | are neat      |    $1 |
-```
-
-| Tables        | Are           | Cool  |
-| ------------- |:-------------:| -----:|
-| col 3 is      | right-aligned | $1600 |
-| col 2 is      | centered      |   $12 |
-| zebra stripes | are neat      |    $1 |
-
-## Ordered List
-
-```md
-1. Number one
-2. Number Two
-    1. Indented Number 1
-    2. Indented Number 2
-```
-
-1. Number one
-2. Number Two
-    1. Indented Number 1
-    2. Indented Number 2
-
-## Unordered List
-
-```md
-* Get groceries at Harris Teeter before the party
-* Get a Spider Man cake
-    * Chocolate or marble
-    * Whipped cream frosting
-* Don't forget to walk the dog before you leave
-* Bring lots of plates and silverware so that we don't run out
-    * Plastic Dixie brand is fine
-```
-
-* Get groceries at Harris Teeter before the party
-* Get a Spider Man cake
-    * Chocolate or marble
-    * Whipped cream frosting
-* Don't forget to walk the dog before you leave
-* Bring lots of plates and silverware so that we don't run out
-    * Plastic Dixie brand is fine
-
-## Comments
-
-```md
-> This is some text that should show up as a comment. Someone may have made this comment but i'm not sure.
-```
-
-> This is some text that should show up as a comment. Someone may have made this comment but i'm not sure.
-
-## Images
-
-```md
-![NYC Skyline](/post/aether-features/mdd-iphone.jpg)
-```
-
-![NYC Skyline](/post/aether-features/mdd-iphone.jpg)
-
-## Small Images
-
-```md
-{{</* smallimg src="featuredImage" alt="NYC Skyline" smartfloat="left" width="250px" */>}}
-```
-
-{{<smallimg src="featuredImage" alt="aether theme displayed on an iPhone" smartfloat="left" width="250px">}}
-
-This image floats to the left of this paragraph and is 250px wide. Its aspect ratio is maintained so it will not stretch. The picture shows the New York skyline. You can see how the design is responsive and how the cards intelligently fit to the display. With flexbox and css grid, heavy frameworks such as bootstrap aren't necessary to create beautiful responsive designs. The cards in aether use flexbox to change the image from the right side on desktops to the top on mobile.
-
-## Links
-
-```md
-[Aether's Github page](https://github.com/josephhutch/aether)
-```
-
-[Aether's Github page](https://github.com/josephhutch/aether)

exampleSite/content/posts/aether-theme/index.md

@@ -1,97 +0,0 @@
----
-title: "Aether: A Clean Theme for Hugo"
-date: 2018-05-02T14:33:42-04:00
-description: " Aether is new theme for Hugo that emphasizes motion, material, and depth as design elements. Distracting styling and page elements are forgone to focus on the content."
-categories: ["Web"]
-dropCap: true
-displayInMenu: false
-displayInList: true
-draft: false
-resources:
-- name: featuredImage
-  src: "mdd-macbook.jpg"
-  params:
-    description: "A MacBook showing a website using the aether theme"
----
-
-Today's web is a frustrating mess of pop-ups, intrusive banners, and ads obstructing the content. I designed aether to be free of all these distractions and simply highlight the content. The result feels more like a native application than a website. Interactions are intuitive, content is the focus, and distractions are omitted.
-
-Aether is a Hugo theme for blogs that elevates good writing and photography. If you use Hugo for your blog, give aether a try.
-
-## Installation
-In the root directory of your Hugo Project, clone the aether repo into the themes directory.
-
-```shell session
-git clone https://github.com/josephhutch/aether.git themes/aether
-```
-
-## Usage
-
-### Website Configuration
-
-Add the following parameters to your config file if they are not present already.
-
-```toml
-baseURL = "https://yourwebsitenamegoeshere.com"
-languageCode = "your language code"
-title = "your website title"
-theme = "aether"
-googleAnalytics = "Your google analytics tracking ID"
-
-[params]
-brand = "the title displayed in the nav bar - optional"
-description = "your website's description"
-homeimg = "url to the image used for the home button - optional"
-bgimg = "url to the image used for the background - optional"
-```
-
-The `title` parameter is used for each page title, the title that search engines display in search results. If you would like the title shown in the top left of the page to be different from the page title, use the `brand` parameter. For instance, the title parameter for my site is `Joe Hutchinson` but the brand parameter is set to `joehutch`.
-
-The `homeimg` and `bgimg` parameters give you the ability to customize the look of your site further. The homeimg parameter is the image used for the home button at the bottom of every page. Since the text used on the home button is white, a darker background image is preferred. If the homeimg parameter is not specified, a fallback image is used. Similarly, the bgimg parameter is used for the background of each webpage. Aether is designed to look best with a subtle tiling image for the background. If no background image is specified, the background will be a solid gray color.
-
-That is the only configuration required at the site level! You can now begin writing content for your site.
-
-### Creating content
-Make a new blog post by executing `hugo new posts/postnamehere/index.md` in your shell. At the top of the new markdown file, is what's called the front matter. The front matter is the page's metadata that determines how Hugo and aether generate the HTML for your post. Below you can find what the front matter should contain for a new post and what each of the parameters mean.
-
-```properties
----
-title: "The title of your post"
-date: date the post was generated
-description: "Description of the post (displayed in the post's card)"
-categories: ["add comma separated categories here", "another category"]
-featuredImage: "url to the page's featured image"
-featuredImageDescription: "Description for the featured image, used as the alt text"
-dropCap: if the first letter should be a large decorative capital letter (true, false)
-displayInMenu: if post is listed in the navigation menu (true, false)
-displayInList: if post is listed on the home page and category pages (true, false)
-draft: if the page is a draft (true, false)
----
-```
-
-The `displayInMenu` and `displayInList` parameters are used to determine where your content is displayed. Posts typically have displayInMenu set to false so that the post is not a menu option, and displayInList set to true so it shows up on the homepage's list of posts and in category page lists. An About Me page, on the other hand, would have displayInMenu set to true and displayInList set to false.  That will allow the About Me page to be accessible from the menu but not displayed in the homepage's list of posts.
-
-The `categories` parameter is used to group similar posts in category pages. Category pages are accessible from the menu and list all posts with the same category.
-
-The `dropCap` parameter is used to determine if the first letter of a post should be a dropped capital. A dropped capital letter is the large decorative letter at the beginning of a book or section.
-
-Add an interesting description and a good image to each post to get the most value from this theme.
-
-Aether takes advantage of [page bundles](https://gohugo.io/content-management/page-bundles/) to optimize your images for your site.  This may require you to update the way your content is structured, also see [content organization](https://gohugo.io/content-management/organization/).  Use the `image` and `smallimg` shortcodes to take full advantage of image optimization.
-
-Posts are written in markdown and LaTeX (for math symbols and equations). You can find tons of information on how to format your posts with markdown and LaTeX on the web.
-
-### Further Customization
-To change the heading and subtext at the top of list pages just add a \_index.md file in the folder that the list page is generated from. For example to change the heading at the top of the homepage, add an \_index.md file to the content folder with the following parameters.
-
-```properties
----
-title: "This is the main heading text in big letters"
-date: the date
-description: "This is the subtext above the main heading in small letters"
----
-```
-
-### Learn  More
-
-To learn more about aether, visit [aether's Github page](https://github.com/josephhutch/aether). To learn more about Hugo, visit [Hugo's website](https://gohugo.io/).

exampleSite/content/posts/goisforlovers/index.md

@@ -1,350 +0,0 @@
-+++
-title = "(Hu)go Template Primer"
-displayInMenu = false
-displayInList = true
-draft = false
-tags = [
-    "go",
-    "golang",
-    "templates",
-    "themes",
-    "development",
-]
-date = "2014-04-02"
-categories = [
-    "Development",
-    "golang",
-]
-[[resources]]
-  name = "featuredImage"
-  src = "lucas-benjamin-565254-unsplash.jpg"
-  [resources.params]
-    description = "Alt description for the featured image"
-+++
-
-Hugo uses the excellent [Go][] [html/template][gohtmltemplate] library for
-its template engine. It is an extremely lightweight engine that provides a very
-small amount of logic. In our experience that it is just the right amount of
-logic to be able to create a good static website. If you have used other
-template systems from different languages or frameworks you will find a lot of
-similarities in Go templates.
-
-This document is a brief primer on using Go templates. The [Go docs][gohtmltemplate]
-provide more details.
-
-## Introduction to Go Templates
-
-Go templates provide an extremely simple template language. It adheres to the
-belief that only the most basic of logic belongs in the template or view layer.
-One consequence of this simplicity is that Go templates parse very quickly.
-
-A unique characteristic of Go templates is they are content aware. Variables and
-content will be sanitized depending on the context of where they are used. More
-details can be found in the [Go docs][gohtmltemplate].
-
-## Basic Syntax
-
-Golang templates are HTML files with the addition of variables and
-functions.
-
-**Go variables and functions are accessible within {{ }}**
-
-Accessing a predefined variable "foo":
-
-    {{ foo }}
-
-**Parameters are separated using spaces**
-
-Calling the add function with input of 1, 2:
-
-    {{ add 1 2 }}
-
-**Methods and fields are accessed via dot notation**
-
-Accessing the Page Parameter "bar"
-
-    {{ .Params.bar }}
-
-**Parentheses can be used to group items together**
-
-    {{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}
-
-
-## Variables
-
-Each Go template has a struct (object) made available to it. In hugo each
-template is passed either a page or a node struct depending on which type of
-page you are rendering. More details are available on the
-[variables](/layout/variables) page.
-
-A variable is accessed by referencing the variable name.
-
-    <title>{{ .Title }}</title>
-
-Variables can also be defined and referenced.
-
-    {{ $address := "123 Main St."}}
-    {{ $address }}
-
-
-## Functions
-
-Go template ship with a few functions which provide basic functionality. The Go
-template system also provides a mechanism for applications to extend the
-available functions with their own. [Hugo template
-functions](/layout/functions) provide some additional functionality we believe
-are useful for building websites. Functions are called by using their name
-followed by the required parameters separated by spaces. Template
-functions cannot be added without recompiling hugo.
-
-**Example:**
-
-    {{ add 1 2 }}
-
-## Includes
-
-When including another template you will pass to it the data it will be
-able to access. To pass along the current context please remember to
-include a trailing dot. The templates location will always be starting at
-the /layout/ directory within Hugo.
-
-**Example:**
-
-    {{ template "chrome/header.html" . }}
-
-
-## Logic
-
-Go templates provide the most basic iteration and conditional logic.
-
-### Iteration
-
-Just like in Go, the Go templates make heavy use of range to iterate over
-a map, array or slice. The following are different examples of how to use
-range.
-
-**Example 1: Using Context**
-
-    {{ range array }}
-        {{ . }}
-    {{ end }}
-
-**Example 2: Declaring value variable name**
-
-    {{range $element := array}}
-        {{ $element }}
-    {{ end }}
-
-**Example 2: Declaring key and value variable name**
-
-    {{range $index, $element := array}}
-        {{ $index }}
-        {{ $element }}
-    {{ end }}
-
-### Conditionals
-
-If, else, with, or, & and provide the framework for handling conditional
-logic in Go Templates. Like range, each statement is closed with `end`.
-
-
-Go Templates treat the following values as false:
-
-* false
-* 0
-* any array, slice, map, or string of length zero
-
-**Example 1: If**
-
-    {{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}
-
-**Example 2: If -> Else**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{else}}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-**Example 3: And & Or**
-
-    {{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-
-**Example 4: With**
-
-An alternative way of writing "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent.
-
-The first example above could be simplified as:
-
-    {{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}
-
-**Example 5: If -> Else If**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{ else if isset .Params "caption" }}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-## Pipes
-
-One of the most powerful components of Go templates is the ability to
-stack actions one after another. This is done by using pipes. Borrowed
-from unix pipes, the concept is simple, each pipeline's output becomes the
-input of the following pipe.
-
-Because of the very simple syntax of Go templates, the pipe is essential
-to being able to chain together function calls. One limitation of the
-pipes is that they only can work with a single value and that value
-becomes the last parameter of the next pipeline.
-
-A few simple examples should help convey how to use the pipe.
-
-**Example 1 :**
-
-    {{ if eq 1 1 }} Same {{ end }}
-
-is the same as
-
-    {{ eq 1 1 | if }} Same {{ end }}
-
-It does look odd to place the if at the end, but it does provide a good
-illustration of how to use the pipes.
-
-**Example 2 :**
-
-    {{ index .Params "disqus_url" | html }}
-
-Access the page parameter called "disqus_url" and escape the HTML.
-
-**Example 3 :**
-
-    {{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-    Stuff Here
-    {{ end }}
-
-Could be rewritten as
-
-    {{  isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" | if }}
-    Stuff Here
-    {{ end }}
-
-
-## Context (aka. the dot)
-
-The most easily overlooked concept to understand about Go templates is that {{ . }}
-always refers to the current context. In the top level of your template this
-will be the data set made available to it. Inside of a iteration it will have
-the value of the current item. When inside of a loop the context has changed. .
-will no longer refer to the data available to the entire page. If you need to
-access this from within the loop you will likely want to set it to a variable
-instead of depending on the context.
-
-**Example:**
-
-      {{ $title := .Site.Title }}
-      {{ range .Params.tags }}
-        <li> <a href="{{ $baseurl }}/tags/{{ . | urlize }}">{{ . }}</a> - {{ $title }} </li>
-      {{ end }}
-
-Notice how once we have entered the loop the value of {{ . }} has changed. We
-have defined a variable outside of the loop so we have access to it from within
-the loop.
-
-# Hugo Parameters
-
-Hugo provides the option of passing values to the template language
-through the site configuration (for sitewide values), or through the meta
-data of each specific piece of content. You can define any values of any
-type (supported by your front matter/config format) and use them however
-you want to inside of your templates.
-
-
-## Using Content (page) Parameters
-
-In each piece of content you can provide variables to be used by the
-templates. This happens in the [front matter](/content/front-matter).
-
-An example of this is used in this documentation site. Most of the pages
-benefit from having the table of contents provided. Sometimes the TOC just
-doesn't make a lot of sense. We've defined a variable in our front matter
-of some pages to turn off the TOC from being displayed.
-
-Here is the example front matter:
-
-```
----
-title: "Permalinks"
-date: "2013-11-18"
-aliases:
-  - "/doc/permalinks/"
-groups: ["extras"]
-groups_weight: 30
-notoc: true
----
-```
-
-Here is the corresponding code inside of the template:
-
-      {{ if not .Params.notoc }}
-        <div id="toc" class="well col-md-4 col-sm-6">
-        {{ .TableOfContents }}
-        </div>
-      {{ end }}
-
-
-
-## Using Site (config) Parameters
-In your top-level configuration file (eg, `config.yaml`) you can define site
-parameters, which are values which will be available to you in chrome.
-
-For instance, you might declare:
-
-```yaml
-params:
-  CopyrightHTML: "Copyright &#xA9; 2013 John Doe. All Rights Reserved."
-  TwitterUser: "spf13"
-  SidebarRecentLimit: 5
-```
-
-Within a footer layout, you might then declare a `<footer>` which is only
-provided if the `CopyrightHTML` parameter is provided, and if it is given,
-you would declare it to be HTML-safe, so that the HTML entity is not escaped
-again.  This would let you easily update just your top-level config file each
-January 1st, instead of hunting through your templates.
-
-```
-{{if .Site.Params.CopyrightHTML}}<footer>
-<div class="text-center">{{.Site.Params.CopyrightHTML | safeHtml}}</div>
-</footer>{{end}}
-```
-
-An alternative way of writing the "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent:
-
-```
-{{with .Site.Params.TwitterUser}}<span class="twitter">
-<a href="https://twitter.com/{{.}}" rel="author">
-<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
- alt="Twitter"></a>
-</span>{{end}}
-```
-
-Finally, if you want to pull "magic constants" out of your layouts, you can do
-so, such as in this example:
-
-```
-<nav class="recent">
-  <h1>Recent Posts</h1>
-  <ul>{{range first .Site.Params.SidebarRecentLimit .Site.Recent}}
-    <li><a href="{{.RelPermalink}}">{{.Title}}</a></li>
-  {{end}}</ul>
-</nav>
-```
-
-
-[go]: https://golang.org/
-[gohtmltemplate]: https://golang.org/pkg/html/template/

exampleSite/content/posts/hugoisforlovers/index.md

@@ -1,94 +0,0 @@
-+++
-title = "Getting Started with Hugo"
-featuredImage = "img/andrew-neel-609846-unsplash.jpg"
-displayInMenu = false
-displayInList = true
-draft = false
-tags = [
-    "go",
-    "golang",
-    "hugo",
-    "development",
-]
-date = "2014-04-02"
-categories = [
-    "Development",
-    "golang",
-]
-[[resources]]
-  name = "featuredImage"
-  src = "andrew-neel-609846-unsplash.jpg"
-+++
-
-## Step 1. Install Hugo
-
-Go to [Hugo releases](https://github.com/spf13/hugo/releases) and download the
-appropriate version for your OS and architecture.
-
-Save it somewhere specific as we will be using it in the next step.
-
-More complete instructions are available at [Install Hugo](https://gohugo.io/getting-started/installing/)
-
-## Step 2. Build the Docs
-
-Hugo has its own example site which happens to also be the documentation site
-you are reading right now.
-
-Follow the following steps:
-
- 1. Clone the [Hugo repository](http://github.com/spf13/hugo)
- 2. Go into the repo
- 3. Run hugo in server mode and build the docs
- 4. Open your browser to http://localhost:1313
-
-Corresponding pseudo commands:
-
-    git clone https://github.com/spf13/hugo
-    cd hugo
-    /path/to/where/you/installed/hugo server --source=./docs
-    > 29 pages created
-    > 0 tags index created
-    > in 27 ms
-    > Web Server is available at http://localhost:1313
-    > Press ctrl+c to stop
-
-Once you've gotten here, follow along the rest of this page on your local build.
-
-## Step 3. Change the docs site
-
-Stop the Hugo process by hitting Ctrl+C.
-
-Now we are going to run hugo again, but this time with hugo in watch mode.
-
-    /path/to/hugo/from/step/1/hugo server --source=./docs --watch
-    > 29 pages created
-    > 0 tags index created
-    > in 27 ms
-    > Web Server is available at http://localhost:1313
-    > Watching for changes in /Users/spf13/Code/hugo/docs/content
-    > Press ctrl+c to stop
-
-
-Open your [favorite editor](http://vim.spf13.com) and change one of the source
-content pages. How about changing this very file to *fix the typo*. How about changing this very file to *fix the typo*.
-
-Content files are found in `docs/content/`. Unless otherwise specified, files
-are located at the same relative location as the url, in our case
-`docs/content/overview/quickstart.md`.
-
-Change and save this file.. Notice what happened in your terminal.
-
-    > Change detected, rebuilding site
-
-    > 29 pages created
-    > 0 tags index created
-    > in 26 ms
-
-Refresh the browser and observe that the typo is now fixed.
-
-Notice how quick that was. Try to refresh the site before it's finished building. I double dare you.
-Having nearly instant feedback enables you to have your creativity flow without waiting for long builds.
-
-## Step 4. Have fun
-
-The best way to learn something is to play with it.

exampleSite/content/posts/migrate-from-jekyll/index.md

@@ -1,156 +0,0 @@
----
-date: 2014-03-10
-displayInMenu: false
-displayInList: true
-draft: false
-title: Migrate to Hugo from Jekyll
-resources:
-- name: featuredImage
-  src: "yan-ots-257617-unsplash.jpg"
----
-
-## Move static content to `static`
-Jekyll has a rule that any directory not starting with `_` will be copied as-is to the `_site` output. Hugo keeps all static content under `static`. You should therefore move it all there.
-With Jekyll, something that looked like
-
-    ▾ <root>/
-        ▾ images/
-            logo.png
-
-should become
-
-    ▾ <root>/
-        ▾ static/
-            ▾ images/
-                logo.png
-
-Additionally, you'll want any files that should reside at the root (such as `CNAME`) to be moved to `static`.
-
-## Create your Hugo configuration file
-Hugo can read your configuration as JSON, YAML or TOML. Hugo supports parameters custom configuration too. Refer to the [Hugo configuration documentation](/overview/configuration/) for details.
-
-## Set your configuration publish folder to `_site`
-The default is for Jekyll to publish to `_site` and for Hugo to publish to `public`. If, like me, you have [`_site` mapped to a git submodule on the `gh-pages` branch](http://blog.blindgaenger.net/generate_github_pages_in_a_submodule.html), you'll want to do one of two alternatives:
-
-1. Change your submodule to point to map `gh-pages` to public instead of `_site` (recommended).
-
-        git submodule deinit _site
-        git rm _site
-        git submodule add -b gh-pages git@github.com:your-username/your-repo.git public
-
-2. Or, change the Hugo configuration to use `_site` instead of `public`.
-
-        {
-            ..
-            "publishdir": "_site",
-            ..
-        }
-
-## Convert Jekyll templates to Hugo templates
-That's the bulk of the work right here. The documentation is your friend. You should refer to [Jekyll's template documentation](http://jekyllrb.com/docs/templates/) if you need to refresh your memory on how you built your blog and [Hugo's template](/layout/templates/) to learn Hugo's way.
-
-As a single reference data point, converting my templates for [heyitsalex.net](http://heyitsalex.net/) took me no more than a few hours.
-
-## Convert Jekyll plugins to Hugo shortcodes
-Jekyll has [plugins](http://jekyllrb.com/docs/plugins/); Hugo has [shortcodes](/doc/shortcodes/). It's fairly trivial to do a port.
-
-### Implementation
-As an example, I was using a custom [`image_tag`](https://github.com/alexandre-normand/alexandre-normand/blob/74bb12036a71334fdb7dba84e073382fc06908ec/_plugins/image_tag.rb) plugin to generate figures with caption when running Jekyll. As I read about shortcodes, I found Hugo had a nice built-in shortcode that does exactly the same thing.
-
-Jekyll's plugin:
-
-    module Jekyll
-      class ImageTag < Liquid::Tag
-        @url = nil
-        @caption = nil
-        @class = nil
-        @link = nil
-        // Patterns
-        IMAGE_URL_WITH_CLASS_AND_CAPTION =
-        IMAGE_URL_WITH_CLASS_AND_CAPTION_AND_LINK = /(\w+)(\s+)((https?:\/\/|\/)(\S+))(\s+)"(.*?)"(\s+)->((https?:\/\/|\/)(\S+))(\s*)/i
-        IMAGE_URL_WITH_CAPTION = /((https?:\/\/|\/)(\S+))(\s+)"(.*?)"/i
-        IMAGE_URL_WITH_CLASS = /(\w+)(\s+)((https?:\/\/|\/)(\S+))/i
-        IMAGE_URL = /((https?:\/\/|\/)(\S+))/i
-        def initialize(tag_name, markup, tokens)
-          super
-          if markup =~ IMAGE_URL_WITH_CLASS_AND_CAPTION_AND_LINK
-            @class   = $1
-            @url     = $3
-            @caption = $7
-            @link = $9
-          elsif markup =~ IMAGE_URL_WITH_CLASS_AND_CAPTION
-            @class   = $1
-            @url     = $3
-            @caption = $7
-          elsif markup =~ IMAGE_URL_WITH_CAPTION
-            @url     = $1
-            @caption = $5
-          elsif markup =~ IMAGE_URL_WITH_CLASS
-            @class = $1
-            @url   = $3
-          elsif markup =~ IMAGE_URL
-            @url = $1
-          end
-        end
-        def render(context)
-          if @class
-            source = "<figure class='#{@class}'>"
-          else
-            source = "<figure>"
-          end
-          if @link
-            source += "<a href=\"#{@link}\">"
-          end
-          source += "<img src=\"#{@url}\">"
-          if @link
-            source += "</a>"
-          end
-          source += "<figcaption>#{@caption}</figcaption>" if @caption
-          source += "</figure>"
-          source
-        end
-      end
-    end
-    Liquid::Template.register_tag('image', Jekyll::ImageTag)
-
-is written as this Hugo shortcode:
-
-    <!-- image -->
-    <figure {{ with .Get "class" }}class="{{.}}"{{ end }}>
-        {{ with .Get "link"}}<a href="{{.}}">{{ end }}
-            <img src="{{ .Get "src" }}" {{ if or (.Get "alt") (.Get "caption") }}alt="{{ with .Get "alt"}}{{.}}{{else}}{{ .Get "caption" }}{{ end }}"{{ end }} />
-        {{ if .Get "link"}}</a>{{ end }}
-        {{ if or (or (.Get "title") (.Get "caption")) (.Get "attr")}}
-        <figcaption>{{ if isset .Params "title" }}
-            {{ .Get "title" }}{{ end }}
-            {{ if or (.Get "caption") (.Get "attr")}}<p>
-            {{ .Get "caption" }}
-            {{ with .Get "attrlink"}}<a href="{{.}}"> {{ end }}
-                {{ .Get "attr" }}
-            {{ if .Get "attrlink"}}</a> {{ end }}
-            </p> {{ end }}
-        </figcaption>
-        {{ end }}
-    </figure>
-    <!-- image -->
-
-### Usage
-I simply changed:
-
-    {% image full http://farm5.staticflickr.com/4136/4829260124_57712e570a_o_d.jpg "One of my favorite touristy-type photos. I secretly waited for the good light while we were "having fun" and took this. Only regret: a stupid pole in the top-left corner of the frame I had to clumsily get rid of at post-processing." ->http://www.flickr.com/photos/alexnormand/4829260124/in/set-72157624547713078/ %}
-
-to this (this example uses a slightly extended version named `fig`, different than the built-in `figure`):
-
-    {{%/* fig class="full" src="http://farm5.staticflickr.com/4136/4829260124_57712e570a_o_d.jpg" title="One of my favorite touristy-type photos. I secretly waited for the good light while we were having fun and took this. Only regret: a stupid pole in the top-left corner of the frame I had to clumsily get rid of at post-processing." link="http://www.flickr.com/photos/alexnormand/4829260124/in/set-72157624547713078/" */%}}
-
-As a bonus, the shortcode named parameters are, arguably, more readable.
-
-## Finishing touches
-### Fix content
-Depending on the amount of customization that was done with each post with Jekyll, this step will require more or less effort. There are no hard and fast rules here except that `hugo server --watch` is your friend. Test your changes and fix errors as needed.
-
-### Clean up
-You'll want to remove the Jekyll configuration at this point. If you have anything else that isn't used, delete it.
-
-## A practical example in a diff
-[Hey, it's Alex](http://heyitsalex.net/) was migrated in less than a _father-with-kids day_ from Jekyll to Hugo. You can see all the changes (and screw-ups) by looking at this [diff](https://github.com/alexandre-normand/alexandre-normand/compare/869d69435bd2665c3fbf5b5c78d4c22759d7613a...b7f6605b1265e83b4b81495423294208cc74d610).

exampleSite/layouts/partials/meta-tags.html

@@ -1,13 +0,0 @@
-<meta property="og:locale" content="{{ .Site.Language.Lang }}">
-<meta property="og:type" content="{{ if .IsHome }}website{{ else }}article{{ end }}">
-<meta property="og:title" content="{{ .Site.Params.Brand }}">
-<meta property="og:description" content="{{ .Site.Params.description }}">
-<meta property="og:url" content="{{ .Permalink }}">
-<meta property="og:site_name" content="{{ .Site.Params.Brand }}">
-<meta property="og:image" content="{{ .Site.Params.metaImage | absURL }}">
-<meta name="twitter:card" content="summary">
-<meta name="twitter:title" content="{{ .Site.Params.Brand }}">
-<meta name="twitter:description" content="{{ .Site.Params.description }}">
-<meta name="twitter:site" content="{{ .Site.BaseURL }}">
-<meta name="twitter:creator" content="{{ .Site.Params.metaCreator }}">
-<meta name="twitter:image" content="{{ .Site.Params.metaImage | absURL }}">

layouts/_default/home.html

@@ -1,10 +1,13 @@
 <!DOCTYPE html>
 <html lang="{{ .Site.LanguageCode }}" dir="ltr">
+
   {{ partial "head.html" . }}
+  
   <body class="list-body">
 
+    {{ partial "nav-bar.html" . }}
+
     <main class="card-container side-gutter">
-      {{ partial "nav-bar.html" . }}
 
       {{ if or (not (eq .Description "")) (not (eq .Title "")) -}}
       {{- end }}
@@ -21,13 +24,15 @@
       {{- range $paginator.Pages -}}
         {{ .Render "li" }}
       {{- end }}
-    </main>
+    
     {{ if or ($paginator.HasPrev) ($paginator.HasNext) -}}
-    <nav class="pagination-nav side-padding">
+    <nav class="blog-card blog-card-feed">
       {{ if $paginator.HasPrev }}<a href="{{ $paginator.Prev.URL }}" class="pagination-newer pagination-text">&lt; Newer Posts</a>{{ end }}
       {{ if $paginator.HasNext }}<a href="{{ $paginator.Next.URL }}" class="pagination-older pagination-text">Older Posts &gt;</a>{{ end }}
     </nav>
     {{- end }}
+    </main>
+   
     {{ partial "scripts.html" . }}
   </body>
 </html>

layouts/_default/li-next.html

@@ -1,4 +1,4 @@
-<a  href="{{ .Permalink }}" class="card blog-card bc-next bg-color-4" rel="bookmark" >
+<a  href="{{ .Permalink }}" class="card blog-card bc-next" rel="bookmark" >
   <div class="card-img-container">
       {{ with .Resources.GetMatch "featuredImage" }}
     <p class="card-img-overlay">Next Article</p>

layouts/_default/li.html

@@ -1,5 +1,4 @@
-<a
-  href="{{ .Permalink }}" class="card blog-card" rel="bookmark" >
+<a href="{{ .Permalink }}" class="card blog-card blog-card-feed" rel="bookmark" >
   <div class="card-img-container">
       {{ with .Resources.GetMatch "featuredImage" }}
     <picture>

layouts/_default/rss.xml

@@ -1,4 +1,5 @@
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+  
   <channel>
     <title>{{ if eq  .Title  .Site.Title }}{{ .Site.Title }}{{ else }}{{ with .Title }}{{.}} - {{ end }}{{ .Site.Title }}{{ end }}</title>
     <link>{{ .Permalink }}</link>
@@ -30,18 +31,21 @@
         {{ printf "<atom:link href=%q rel=\"self\" type=%q />" .Permalink .MediaType | safeHTML }}
     {{ end }}
 
-    {{ $paginator := .Paginate (where .Pages "Params.displayinlist" "!=" false) -}}
+    {{ $pages := .Site.RegularPages }}
+    {{ $paginator := .Paginate (where $pages "Params.displayinlist" "!=" false) -}}
     {{- range $paginator.Pages -}}
     <item>
       <title>{{ .Title }}</title>
+
       <link>{{ .Permalink }}</link>
       <pubDate>{{ .Date.Format "Mon, 02 Jan 2006 15:04:05 -0700" | safeHTML }}</pubDate>
       {{ with .Site.Author.email }}<author>{{.}}{{ with $.Site.Author.name }} ({{.}}){{end}}</author>{{end}}
       <guid>{{ .Permalink }}</guid>
       <description>
-          {{ $.Content | html }}
+          {{ .Content | html }}
+          Last modification : {{ .Lastmod }}
       </description>
     </item>
     {{- end }}
   </channel>
-</rss>
+</rss> 

layouts/_default/single.html

@@ -7,7 +7,7 @@
 
     {{ partial "nav-bar.html" . }}
 
-    <main class="content side-text-padding">
+    <main class="content side-text-padding side-gutter">
       <article class="post {{ if ne .Params.dropcap false }}dropcase{{ end }}">
         <header class="post-header">
           <h1 class="post-title">{{ .Title }}</h1>
@@ -29,13 +29,16 @@
         {{- end }}
         {{ .Content }}
       </article>
+      <nav class="end-nav card-container card">
+        {{ with .PrevInSection }}
+        {{ .Render "li-next" }}
+        {{ end }}
+      </nav>
+
+      {{ partial "footer.html" . }}
+
     </main>
-    <nav class="end-nav side-padding">
-      {{ with .PrevInSection }}
-      {{ .Render "li-next" }}
-      {{ end }}
-    </nav>
-    {{ partial "footer.html" . }}
+    
     {{ partial "scripts.html" . }}
   </body>
 </html>

layouts/partials/footer.html

@@ -1,10 +1,14 @@
 
-<nav class="end-nav side-padding card-container card content">
+<nav class="end-nav card-container card content">
       {{ partial "openring-out.html" . }}
 
 </nav>
 
 
-<footer class="content card card-container side-padding" >
-    <h3>The Octet Press is N07070's blog. It's self-hosted, low-tech, without javascript and static, as it should be.</h3><sup><a href="https://www.wired.com/2015/11/i-turned-off-javascript-for-a-whole-week-and-it-was-glorious/" rel="nofollow">Why ?</a></sup>
+<footer class="content card card-container" >
+    <h3>The Octet Press is <a href="{{ .Site.BaseURL }}about-me/">N07070's</a> blog.</h3>
+    <small>It's self-hosted, low-tech, without javascript and static, as it should be.</small>
+    <sup><a href="{{ .Site.BaseURL}}/notes/why-no-js/" rel="nofollow">Why ?</a></sup>
+    <br>
+    <p> Page last modified on {{ .Lastmod  }}</p>
 </footer>

layouts/partials/head.html

@@ -5,34 +5,37 @@
   <title>{{ if not .IsHome }}{{with .Title }}{{ . }} &middot; {{ end }}{{ end }}{{ .Site.Title }}</title>
   <meta name="description" content="{{if .IsHome}}{{ $.Site.Params.description }}{{else}}{{.Description}}{{end}}" />
   {{ if (fileExists "static/apple-touch-icon.png") -}}
-    <link rel="apple-touch-icon" sizes="180x180" href="{{ "/apple-touch-icon.png" | absURL }}">
+  <link rel="apple-touch-icon" sizes="180x180" href="{{ "/apple-touch-icon.png" | absURL }}">
   {{ end -}}
   {{ if (fileExists "static/favicon-32x32.png") -}}
-    <link rel="icon" type="image/png" sizes="32x32" href="{{ "/favicon-32x32.png" | absURL }}">
+  <link rel="icon" type="image/png" sizes="32x32" href="{{ "/favicon-32x32.png" | absURL }}">
   {{ end -}}
   {{ if (fileExists "static/favicon-16x16.png") -}}
-    <link rel="icon" type="image/png" sizes="16x16" href="{{ "/favicon-16x16.png" | absURL }}">
+  <link rel="icon" type="image/png" sizes="16x16" href="{{ "/favicon-16x16.png" | absURL }}">
   {{ end -}}
   {{ if (fileExists "static/site.webmanifest") -}}
   <link rel="manifest" href="{{ "/site.webmanifest" | absURL }}">
   {{ end -}}
   {{ if (fileExists "static/safari-pinned-tab.svg") -}}
-    <link rel="mask-icon" href="{{ "/safari-pinned-tab.svg" | absURL }}" color="#5bbad5">
+  <link rel="mask-icon" href="{{ "/safari-pinned-tab.svg" | absURL }}" color="#5bbad5">
+  {{ end -}}
+  {{ if isset $.Site.Params "mastodon_profile_link" -}}
+  <link rel="me" href="{{- $.Site.Params.mastodon_profile_link -}}">
   {{ end -}}
   {{ if (fileExists "layouts/partials/meta-tags.html") -}}
-    {{ partial "meta-tags.html" . }}
+  {{ partial "meta-tags.html" . }}
   {{ end -}}
   {{ with resources.Get "css/katex.css" -}}
-  <link href="{{ .Permalink }}" rel="stylesheet">
+  <link href="{{ .Permalink -}}" rel="stylesheet">
   {{ end -}}
-  {{ $normalizeStyle := resources.Get "css/normalize.css" }}
-  {{ $mainStyle := resources.Get "css/style.css" }}
-  {{ $overrideStyle := resources.Get "css/override.css" }}
-  {{ $printStyle := resources.Get "css/print.css" }}
-  {{ $style := slice $normalizeStyle $mainStyle $overrideStyle $printStyle | resources.Concat "css/concated.css" | minify }}
+  {{ $normalizeStyle := resources.Get "css/normalize.css" -}}
+  {{ $mainStyle := resources.Get "css/style.css" -}}
+  {{ $overrideStyle := resources.Get "css/override.css" -}}
+  {{ $printStyle := resources.Get "css/print.css" -}}
+  {{ $style := slice $normalizeStyle $mainStyle $overrideStyle $printStyle | resources.Concat "css/concated.css" | minify -}}
   <link href="{{ $style.Permalink }}" rel="stylesheet">
   {{ range .AlternativeOutputFormats -}}
-    {{ printf `<link rel="%s" type="%s" href="%s" title="%s" />` .Rel .MediaType.Type .Permalink $.Site.Title | safeHTML }}
+  {{ printf `<link rel="%s" type="%s" href="%s" title="%s" />` .Rel .MediaType.Type .Permalink $.Site.Title | safeHTML }}
   {{ end -}}
   {{ with resources.GetMatch .Site.Params.bgimg -}}
   <style>

layouts/partials/nav-bar.html

@@ -1,6 +1,6 @@
 <nav class="nav-bar card-container">
 
- <div class="card blog-card menu-container">
+ <div class="menu-container">
      <h1 class="nav-header">
          <a href="{{ .Site.BaseURL }}" class="nav-text">
            {{- if isset $.Site.Params "brand"}}

layouts/partials/openring-in.html

@@ -0,0 +1,49 @@
+<!-- License-Id: CC0-1.0 -->
+<section class="webring side-padding">
+  <h3>Articles from blogs I follow around the net</h3>
+  <section class="articles">
+    {{range .Articles}}
+    <div class="article">
+      <h4 class="title">
+        <a href="{{.Link}}" target="_blank" rel="noopener">{{.Title}}</a>
+      </h4>
+      <p class="summary">{{.Summary}}</p>
+      <small class="source">
+        via <a href="{{.SourceLink}}">{{.SourceTitle}}</a>
+      </small>
+      <small class="date">{{ .Date.Format "January 2, 2006" }}</small>
+    </div>
+    {{end}}
+  </section>
+  <p class="attribution">
+    Generated by
+    <a rel="nofollow" href="https://git.sr.ht/~sircmpwn/openring">openring</a>
+  </p>
+</section>
+<style>
+.webring .articles {
+  display: flex;
+  flex-wrap: wrap;
+  margin: -0.5rem;
+}
+.webring .title {
+  margin: 0;
+}
+.webring .article {
+  flex: 1 1 0;
+  display: flex;
+  flex-direction: column;
+  margin: 0.5rem;
+  padding: 0.5rem;
+  min-width: 10rem;
+}
+.webring .summary {
+  font-size: 0.8rem;
+  flex: 1 1 0;
+}
+.webring .attribution {
+  text-align: right;
+  font-size: 0.8rem;
+  color: #555;
+}
+</style>

layouts/partials/openring-out.html

@@ -1,44 +1,53 @@
-<section class="webring">
+
+<section class="webring side-padding">
   <h3>Articles from blogs I follow around the net</h3>
   <section class="articles">
     
     <div class="article">
       <h4 class="title">
-        <a href="https://solar.lowtechmagazine.com/2021/03/urban-fish-ponds-low-tech-sewage-treatment-for-towns-and-cities.html" target="_blank" rel="noopener">Urban Fish Ponds: Low-tech Sewage Treatment for Towns and Cities</a>
+        <a href="https://www.archdaily.com/1034557/kivikhusen-stadstudio" target="_blank" rel="noopener">
+        Kivikhusen / STADSTUDIO
+      </a>
       </h4>
-      <p class="summary">In the mid 20th century, whole cities’ sewage systems safely and successfully used fish to treat and purify their water. Waste-fed fish ponds are a low-tech, cheap, and sustainable alternative to deal with our own shit — and to obtain high protein food in…</p>
+      <p class="summary">
+        Nestled in the picturesque heart of Österlen, where the cultural landscape converges with the sea, lies &#34;Kivikhusen&#34;. This development features a thoughtfully designed, small-scale community comprising 33 wooden houses, garden rooms, and i…</p>
       <small class="source">
-        via <a href="https://solar.lowtechmagazine.com/">LOW←TECH MAGAZINE</a>
+        via <a href="https://www.archdaily.com/">ArchDaily Global</a>
       </small>
-      <small class="date">March 28, 2021</small>
+      <small class="date">October 4, 2025</small>
     </div>
     
     <div class="article">
       <h4 class="title">
-        <a href="https://www.laquadrature.net/2021/03/26/gendnotes-entre-flicage-inavoue-et-mauvaise-foi/" target="_blank" rel="noopener">GendNotes : entre flicage inavoué et mauvaise foi</a>
+        <a href="https://reporterre.net/Rachel-six-mois-ferme-et-la-lutte-climat-comme-une-necessite" target="_blank" rel="noopener">Rachel, six mois ferme et la lutte climat comme une « nécessité »</a>
       </h4>
-      <p class="summary">Il y a plus d&#39;un an, le gouvernement autorisait par décret la gendarmerie à utiliser une application de prise de notes sur téléphone mobile intitulée GendNotes. Nous avions déposé un recours contre ce décret devant…</p>
+      <p class="summary">
+                    
+                    
+« Je n&#39;ai jamais vu ça », dit son avocate. Rachel, 23 ans, a été condamnée à 6 mois de prison ferme pour avoir aspergé l&#39;hôtel Matignon de peinture à l&#39;eau. La militante du collectif Dernière rénovation …</p>
+      <small class="source">
+        via <a href="https://reporterre.net/">Reporterre, le média de l&#39;écologie - Indépendant et en accès libre</a>
+      </small>
+      <small class="date">October 4, 2025</small>
+    </div>
+    
+    <div class="article">
+      <h4 class="title">
+        <a href="https://www.laquadrature.net/2025/10/03/chat-control-on-fait-le-point/" target="_blank" rel="noopener">Chat Control : on fait le point</a>
+      </h4>
+      <p class="summary">Ceci est une traduction de l’article « Chat Control: What is actually going on? » publié le 24 septembre 2025 par EDRi, réseau d’associations européennes dont La Quadrature du Net fait partie.
+Chat Control : de quoi s’agit-il ?
+Au cours…</p>
       <small class="source">
         via <a href="https://www.laquadrature.net">La Quadrature du Net</a>
       </small>
-      <small class="date">March 26, 2021</small>
-    </div>
-    
-    <div class="article">
-      <h4 class="title">
-        <a href="https://mamot.fr/@n07070/105955483490021614" target="_blank" rel="noopener">n07070: “N&#39;empêche, …”</a>
-      </h4>
-      <p class="summary">N&#39;empêche, vu la situation actuelle, heureusement que la réforme de la sécu c&#39;était pas le premier truc à l&#39;ordre du jour des destructions prévues par Macron...</p>
-      <small class="source">
-        via <a href="https://mamot.fr/@n07070">N07070 (@n07070@mamot.fr)</a>
-      </small>
-      <small class="date">March 26, 2021</small>
+      <small class="date">October 3, 2025</small>
     </div>
     
   </section>
   <p class="attribution">
     Generated by
-    <a href="https://git.sr.ht/~sircmpwn/openring">openring</a>
+    <a rel="nofollow" href="https://git.sr.ht/~sircmpwn/openring">openring</a>
   </p>
 </section>
 <style>
@@ -65,5 +74,6 @@
 .webring .attribution {
   text-align: right;
   font-size: 0.8rem;
+  color: #555;
 }
 </style>

theme.toml

@@ -1,8 +1,8 @@
 name = "blogotheme"
 license = "AGPL"
-licenselink = "https://git.n07070.xyz/n07070/blog-theme/src/branch/main/LICENSE"
+licenselink = "https://git.n07070.xyz/n07070/blogotheme/src/branch/main/LICENSE"
 description = "The theme for my blog, used by the Hugo static website generator. It's based on the design of newspapers, brutalist web design, and inspired by the solar website built by low tech magazine."
-homepage = "https://git.n07070.xyz/n07070/blog-theme/"
+homepage = "https://git.n07070.xyz/n07070/blogotheme/"
 tags = ["Blog", "Personal", "Responsive", "Minimal", "Simple", "Clean", "Modern", "Technical", "Brutalist"]
 features = ["Responsive"]
 min_version = "0.41"