starting a brand new varia website

6 years ago · cb1ffc27e9
79 changed files with 350 additions and 2963 deletions
--- a/.gitignore
+++ b/.gitignore
@ -3,3 +3,4 @@ output/*
 *.pid
 .DS_Store
 .swp
 plugins
--- a/674
+++ b/674
@ -1,674 +0,0 @@
                    GNU GENERAL PUBLIC LICENSE
                       Version 3, 29 June 2007
 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.
                            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.
    cet-cat
    Copyright (C) 2017  rscmbbng
    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 <http://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:
    cet-cat  Copyright (C) 2017  rscmbbng
    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
 <http://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
 <http://www.gnu.org/philosophy/why-not-lgpl.html>.
--- a/69
+++ b/69
@ -1,4 +1,4 @@
-PY?=python
+PY?=python3
 PELICAN?=pelican
 PELICANOPTS=
@ -8,24 +8,6 @@ OUTPUTDIR=$(BASEDIR)/output
 CONFFILE=$(BASEDIR)/pelicanconf.py
 PUBLISHCONF=$(BASEDIR)/publishconf.py
 FTP_HOST=localhost
 FTP_USER=anonymous
 FTP_TARGET_DIR=/
 SSH_HOST=majesticmoo.se
 SSH_PORT=22
 SSH_USER=cat
 SSH_TARGET_DIR=/home/cat/cat-cet
 S3_BUCKET=my_s3_bucket
 CLOUDFILES_USERNAME=my_rackspace_username
 CLOUDFILES_API_KEY=my_rackspace_api_key
 CLOUDFILES_CONTAINER=my_cloudfiles_container
 DROPBOX_DIR=~/Dropbox/Public/
 GITHUB_PAGES_BRANCH=gh-pages
 DEBUG ?= 0
 ifeq ($(DEBUG), 1)
@ -47,15 +29,9 @@ help:
 	@echo '   make publish                        generate using production settings '
 	@echo '   make serve [PORT=8000]              serve site at http://localhost:8000'
 	@echo '   make serve-global [SERVER=0.0.0.0]  serve (as root) to $(SERVER):80    '
-	@echo '   make devserver [PORT=8000]          start/restart develop_server.sh    '
+	@echo '   make devserver [PORT=8000]          serve and regenerate together      '
 	@echo '   make stopserver                     stop local server                  '
 	@echo '   make ssh_upload                     upload the web site via SSH        '
 	@echo '   make rsync_upload                   upload the web site via rsync+ssh  '
 	@echo '   make dropbox_upload                 upload the web site via Dropbox    '
 	@echo '   make ftp_upload                     upload the web site via FTP        '
 	@echo '   make s3_upload                      upload the web site via S3         '
 	@echo '   make cf_upload                      upload the web site via Cloud Files'
 	@echo '   make github                         upload the web site via gh-pages   '
 	@echo '                                                                          '
 	@echo 'Set the DEBUG variable to 1 to enable debugging, e.g. make DEBUG=1 html   '
 	@echo 'Set the RELATIVE variable to 1 to enable relative urls                    '
@ -72,53 +48,28 @@ regenerate:
 serve:
 ifdef PORT
-	cd $(OUTPUTDIR) && $(PY) -m pelican.server $(PORT)
+	$(PELICAN) -l $(INPUTDIR) -o $(OUTPUTDIR) -s $(CONFFILE) $(PELICANOPTS) -p $(PORT)
 else
-	cd $(OUTPUTDIR) && $(PY) -m pelican.server
+	$(PELICAN) -l $(INPUTDIR) -o $(OUTPUTDIR) -s $(CONFFILE) $(PELICANOPTS)
 endif
 serve-global:
 ifdef SERVER
-	cd $(OUTPUTDIR) && $(PY) -m pelican.server 80 $(SERVER)
+	$(PELICAN) -l $(INPUTDIR) -o $(OUTPUTDIR) -s $(CONFFILE) $(PELICANOPTS) -p $(PORT) -b $(SERVER)
 else
-	cd $(OUTPUTDIR) && $(PY) -m pelican.server 80 0.0.0.0
+	$(PELICAN) -l $(INPUTDIR) -o $(OUTPUTDIR) -s $(CONFFILE) $(PELICANOPTS) -p $(PORT) -b 0.0.0.0
 endif
 devserver:
 ifdef PORT
-	$(BASEDIR)/develop_server.sh restart $(PORT)
+	$(PELICAN) -lr $(INPUTDIR) -o $(OUTPUTDIR) -s $(CONFFILE) $(PELICANOPTS) -p $(PORT)
 else
-	$(BASEDIR)/develop_server.sh restart
+	$(PELICAN) -lr $(INPUTDIR) -o $(OUTPUTDIR) -s $(CONFFILE) $(PELICANOPTS)
 endif
 stopserver:
 	$(BASEDIR)/develop_server.sh stop
 	@echo 'Stopped Pelican and SimpleHTTPServer processes running in background.'
 publish:
-	$(PELICAN) $(INPUTDIR) -o /var/www/html/ -s $(PUBLISHCONF) $(PELICANOPTS)
+	$(PELICAN) $(INPUTDIR) -o $(OUTPUTDIR) -s $(PUBLISHCONF) $(PELICANOPTS)
 ssh_upload: publish
 	scp -P $(SSH_PORT) -r $(OUTPUTDIR)/* $(SSH_USER)@$(SSH_HOST):$(SSH_TARGET_DIR)
 rsync_upload: publish
 	rsync -e "ssh -p $(SSH_PORT)" -P -rvzc --delete $(OUTPUTDIR)/ $(SSH_USER)@$(SSH_HOST):$(SSH_TARGET_DIR) --cvs-exclude
 dropbox_upload: publish
 	cp -r $(OUTPUTDIR)/* $(DROPBOX_DIR)
 ftp_upload: publish
 	lftp ftp://$(FTP_USER)@$(FTP_HOST) -e "mirror -R $(OUTPUTDIR) $(FTP_TARGET_DIR) ; quit"
 s3_upload: publish
 	s3cmd sync $(OUTPUTDIR)/ s3://$(S3_BUCKET) --acl-public --delete-removed --guess-mime-type --no-mime-magic --no-preserve
 cf_upload: publish
 	cd $(OUTPUTDIR) && swift -v -A https://auth.api.rackspacecloud.com/v1.0 -U $(CLOUDFILES_USERNAME) -K $(CLOUDFILES_API_KEY) upload -c $(CLOUDFILES_CONTAINER) .
 github: publish
 	ghp-import -m "Generate Pelican site" -b $(GITHUB_PAGES_BRANCH) $(OUTPUTDIR)
 	git push origin $(GITHUB_PAGES_BRANCH)
-.PHONY: html help clean regenerate serve serve-global devserver stopserver publish ssh_upload rsync_upload dropbox_upload ftp_upload s3_upload cf_upload github
+.PHONY: html help clean regenerate serve serve-global devserver stopserver publish 
--- a/README.md
+++ b/README.md
@ -1,21 +1,10 @@
 # Varia website
-## Pelican
+TO BE UPDATED !
-The Varia website is made with Pelican, a static site generator written in Python. This means that the website is first generated on a computer (using Python, Jinja and Pelican) into a set of html pages, files and images. This set of documents is then uploaded to the server.
+## Cloning
-One of the things that Pelican uses is *plugins*. They are used to add extra features to the generation process of the website. 
+The folder 'plugins' is linked to the Pelican project '[pelican-plugins](https://github.com/getpelican/pelican-plugins/)' repository. To clone both the varia.website and pelican-plugins repository, add the --recurse-submodules option in your git clone command:
 In this repository there is a folder called 'plugins' and another one called 'plugins-custom'. 
 The first one, 'plugins', is linked to the offical collection of plugins from the Pelican project '[pelican-plugins](https://github.com/getpelican/pelican-plugins/)'. 
 The other one, 'plugins-custom', consists of plugins that we wrote ourself. 
 ## Clone
 To clone both the varia.website and pelican-plugins repository, add the --recurse-submodules option in your git clone command:
 `git clone https://git.vvvvvvaria.org/varia/varia.website.git --recurse-submodules`
--- a/content/borrel2019_EN.md
+++ b/content/borrel2019_EN.md
@ -1,19 +0,0 @@
 Title: Varia New Year's Reception
 Date: 2019-01-11
 Category: event
 Tags: event
 slug: borrel2019
 lang: en
 Event_start: 2019-01-11 19:30
 event_duration: 4h
 featured_image: /images/20195.jpg
 It's a new year! Dennis (de Bel) is back, the window is broken and l'intolerant #18 is out. Enough reasons to come together and have a drink.
 This Friday, the 11th of January, from 19:30, Varia opens its doors for some special new year's drinks and some fitting music.
 Woodstone Kugelblitz will also be presenting the latest issue of L'Intolerant #18: A Really Useful Cookbook.
 Almost everyone is welcome and the entrance is free. However, a voluntary donation of 5 euros will help us replace our window and is greatly appreciated!
 See you there!
--- a/content/borrel2019_NL.md
+++ b/content/borrel2019_NL.md
@ -1,21 +0,0 @@
 Title: Varia's Nieuwjaarsborrel
 Date: 2019-01-11
 Category: event
 slug: borrel2019
 Tags: event
 lang: nl
 Event_start: 2019-01-11 19:30
 event_duration: 4h
 featured_image: /images/20195.jpg
 Varia's Nieuwjaarsborrel
 Een nieuw jaar is aangebroken; Dennis (de Bel) is terug, de ruit ligt aan diggelen en l'intolerant #18 moet worden gelanceerd! Reden genoeg om bijeen te komen voor een drankje!
 Deze vrijdag, 7 januari opent Varia om 19:30 de deuren voor een nieuwjaarsborrel met bijpassende muziek van DJ Listentomerijn.
 Woodstone Kugelblitz zal dan de nieuwste editie van L'Intolerant presenteren: Nummer 18, A Really Useful Cookbook.
 Iedereen is welkom en de toegang is uiteraard vrij. Echter, vrijwillige donatie van 5 euro helpen ons bij het vervangen van de ruit en worden zeer gewaardeerd!
 Tot dan!
--- a/content/conversas-feb.en.md
+++ b/content/conversas-feb.en.md
@ -1,43 +0,0 @@
 Title: Conversas at varia
 Date: 2019-02-06
 Category: event
 Slug:conversas-february
 lang: en
 event_start: 2019-02-06 19:30
 event_duration: 2h
 featured_image: /images/ConversasEvento137-02.png
 summary: In February, Varia has the pleasure to host one of the nomadic Conversas evenings. Conversas is a series of bi-weekly informal meetings made so that we can get to know each other, share projects, stories or interests.
 tags: Conversas, informal, meetings
 On the ***6th of February from 19:30 to 21:30***, Varia has the pleasure to host one of the nomadic Conversas evenings.
 Conversas is a series of bi-weekly informal meetings made so that we can get to know each other, share projects, stories or interests. 
 During the event, three Conversadores (those who start the conversation) bring something to share with the gathered group, for thirty minutes each. As the title suggests, Conversas (Conversations in Portuguese) aim at an equal set up from which both the Conversadores and the group benefit. In this series, we are challenging our guests to not use a beamer, try to be creative and use only words and/or other objects to tell their story.
 The three Conversadores for the session at Varia are:
 - Karla de Witte (Dutch Love Letters)
 - Clara Mendes (Nude models, postcolonialism and museums)
 - Ludovic Lacreuse (Digressions around a flag)
 **Karla** is designer and educator of visual arts. <a href="www.facebook.com/pg/dutchloveletters/
 ">DLL</a> started when two mothers met at a colorful schoolyard in Rotterdam. Both born and grown up in different parts of the world, sharing similar memories of New Year's Eve with waffles. Delicate and very thin made with great patience by their grandmothers.
 www.instagram.com/dutch_love_letters/
 **Clara** has recently moved from Portugal to The Netherlands to pursue her wish to learn more about how art impacts the lives of different people. She will talk about the projects she jumped into throughout her master's program in Arts and Society whilst she was still struggling to find her way around a new city.
 After a 3 month artist residency (State of the City, in Paviljoen aan het Water, in Rotterdam), **<a href="http://ludoviclacreuse.net/">Ludovic</a>** will present a flag which will be hoisted on top of the varia zone building. His conversation will be filled by digressions about different subjects more or less related to the flag.
 The 13th series of ten <a href="www.facebook.com/conversasrotterdam">Conversas Rotterdam</a> starts on the 7th of November and runs every other Wednesday until the 20th of March. This series is happening in different locations spread through the city of Rotterdam. It is organized by Bérénice Staiger, Constança Saraiva, Marco Aperti, Zahra Said and Sebastian Helbers.
 <a href="www.conversas.net">Conversas</a> is a project initiated in Lisbon by Constança Saraiva and Mafalda Fernandes, in 2012. Nowadays, it's a project of many people and cities.
 Events are open to all and the entrance is free.
--- a/content/conversas-feb.nl.md
+++ b/content/conversas-feb.nl.md
@ -1,42 +0,0 @@
 Title: Conversas bij varia
 Date: 2019-02-06
 Category: event
 Slug:conversas-february
 lang: nl
 event_start: 2019-02-06 19:30
 event_duration: 2h
 featured_image: /images/ConversasEvento137-02.png
 summary: In februari heeft Varia het genoegen een van de nomadische Conversas-avonden te ontvangen. Conversas is een serie van tweewekelijkse informele ontmoetingen, zodat we elkaar kunnen leren kennen, projecten, verhalen of interesses kunnen delen.
 tags: Conversas, informeel, ontmoetingen
 Op de ***6 februari van 19.30 tot 21.30 uur*** heeft Varia het genoegen om een van de nomadische Conversas-avonden te ontvangen.
 Conversas is een reeks van tweewekelijkse informele ontmoetingen om elkaar te leren kennen, projecten, verhalen of interesses te delen.
 Tijdens het evenement brengen drie Conversadores (degenen die het gesprek beginnen) gedurende dertig minuten elk iets te delen met de verzamelde groep. Zoals de titel al doet vermoeden, streeft Conversas (Conversations in Portuguese) naar een gelijkwaardige opzet waar zowel de Conversadores als de groep baat bij hebben. In deze serie dagen we onze gasten uit om geen beamer te gebruiken, creatief te zijn en alleen woorden en/of andere objecten te gebruiken om hun verhaal te vertellen.
 De drie Conversadores voor de sessie bij Varia zijn dat wel:
 - Karla de Witte (Nederlandse liefdesbrieven)
 - Clara Mendes (Naakt modellen, postkolonialisme en musea)
 - Ludovic Lacreuse (Digressies rond een vlag)
 **Karla** is ontwerper en docent beeldende kunst. <a href="www.facebook.com/pg/dutchloveletters/">DLL</a> begon toen twee moeders elkaar ontmoetten op een kleurrijk schoolplein in Rotterdam. Zowel geboren als opgegroeid in verschillende delen van de wereld, met wafels die soortgelijke herinneringen aan oud en nieuw delen. Delicaat en zeer dun gemaakt met veel geduld door hun grootmoeders.
 www.instagram.com/dutch_love_letters/liefdebrieven/
 **Clara** is onlangs verhuisd van Portugal naar Nederland om haar wens na te streven om meer te weten te komen over de impact van kunst op het leven van verschillende mensen. Ze zal vertellen over de projecten waar ze tijdens haar masteropleiding Kunst en Maatschappij in is gesprongen terwijl ze nog worstelde om haar weg te vinden in een nieuwe stad.
 Na een residentie van 3 maanden (Staat van de Stad, in Paviljoen aan het Water, in Rotterdam), presenteert **<a href="http://ludoviclacreuse.net/">Ludovic</a>** een vlag die bovenop het varia-zonegebouw wordt gehesen. Zijn gesprek wordt gevuld met uitweidingen over verschillende onderwerpen die min of meer met de vlag te maken hebben.
 De 13e serie van tien <a href="www.facebook.com/conversasrotterdam">Conversas Rotterdam</a> begint op 7 november en loopt elke andere woensdag tot 20 maart. Deze serie vindt plaats op verschillende locaties verspreid door de stad Rotterdam. Het wordt georganiseerd door Bérénice Staiger, Constança Saraiva, Marco Aperti, Zahra Said en Sebastian Helbers.
 <a href="www.conversas.net">Conversas</a> is een project geïnitieerd in Lissabon door Constança Saraiva en Mafalda Fernandes, in 2012. Tegenwoordig is het een project van veel mensen en steden.
 Evenementen zijn voor iedereen toegankelijk en de toegang is gratis.
--- a/content/images/20195.jpg
+++ b/content/images/20195.jpg
--- a/content/images/ConversasEvento137-02.png
+++ b/content/images/ConversasEvento137-02.png
--- a/content/images/beachbombart.jpg
+++ b/content/images/beachbombart.jpg
--- a/content/images/kettle4-web-xs.jpg
+++ b/content/images/kettle4-web-xs.jpg
--- a/content/kettle.md
+++ b/content/kettle.md
@ -1,39 +0,0 @@
 Title: The Call Of The Kettle
 Date: 2019-03-15
 Category: event
 slug: kettle
 Tags: event
 lang: nl
 Event_start: 2019-03-15 20:00
 event_duration: 4h
 featured_image: /images/kettle4-web-xs.jpg
 Er is meer tussen hemel en aarde dan de mens! Op 15 maart besteden we daarom aandacht aan “levenloze” object in ons midden. Op de stenen vloer van Varia zullen een vijftal artiesten te zien zijn die een intieme relatie met hun naaimachines, broodroosters, ventilatoren, waterkokers en opgeviste werkhandschoenen durven aan te gaan. Dit alles onder het mom van ‘The Call Of The Kettle’; de eerste object georienteerde muziekavond bij Varia! Tijdens dit evenement zullen er optredens te zien zijn van de volgende artiesten:
 ** Agente Costura en Stephen Doyle ** is een duo dat geïmproviseerde geluiden speelt met behulp van versterkte naaimachine en drums. Constura speelt al sinds 2003 op de Singer. Overdag werkt ze met ongewenste kleding  en transformeert die in nieuwe draagbare vormen. 's Nachts sluit de Singer zich aan bij haar medemuzikanten en naait zij op het ritme van de muziek. Zo improviseert zij kleding op basis van ritme en geluid. Costura heeft onder meer opgetreden in The Vancouver Art Gallery, de Month of Performance Art Berlin, het Bimhuis Amsterdam en de Curitiba Fashion Week. Stephen Doyle is een drummer die woont en werkt in Amsterdam. Costura en Doyle creëren samen een percussieve upcycled stortvloed van uniek gebeeldhouwd geluid.
 [Agente Costura Online](www.agentecostura.blogspot.de/)<br>
 [Stephen Doyle op Soundcloud](https://soundcloud.com/stephen-doyle-drummer)
 <iframe width="560" height="315" src="https://www.youtube.com/embed/oey80a-7CQ0" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 ** Watt's Cookin '** bestaat uit Zeynep Aslan, Tamara van Suylekom en Inge Hoonte, die elkaar hebben leren kennen via re#sister en repeteren buh Worm. Voor deze voorstelling hebben de drie samengewerkt om te knallen, te kletsen en te sleutelen met  huishoudelijke artikelen. Ze repeteren momenteel in de keuken van Inge met hun orkestleden, waaronder waterkokers en koffiepercolators, een mes en een snijplank, een paar potten met noten, rijst en maïs, een mini-oven, twee pannen, twee theelepels en een eierklopper. Alleen een broodrooster en een blik kokosmelk aarzelen nog of ze lid willen worden van deze vrolijke groep!
 ** De Brut ** is een nieuw project van Marijn Verbiesen, die volgens bronnen "een van de krachten is die de Rotterdamse underground bij elkaar houdt!" Ze heeft deelgenomen aan tal van projecten (Sweat Tongue, Red Brut) en is actief als een van de organisatoren van de beruchte Herman concertreeks. Daarnaast staat Verbiesen bekend om haar tapecollages die zeer persoonlijk zijn en hoog aangeschreven staan door bladen als The Wire.
 [De Website van Red Brut](https://redbrut.com/)
 <iframe width="560" height="315" src="https://www.youtube.com/embed/pa066-UzitY" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 ** Beachcombartband ** is een "one-man-sea-trash-band" uit Rotterdam met kunstenaar Bart Koppe aan het roer. Het mechanisch en met de hand bespeelde afval van het schoongeveegde strand zal door hem op uw hoofd worden geloosd, in een netwerk van audio-galactische bevrediging!
 ** The Singing Toaster ** is niet zoals andere broodroosters, omdat niet elke broodrooster kan zingen. Daarom is deze bijdrage aan "The Call Of The Kettle" nu al een beetje bijzonder. Zullen de verbrande kruimels tussen zijn verwarmingselementen ook uw hart kunnen verwarmen?
 **Datum:** Vrijdag, 15 Maart 2019<br>
 **Entree:** 5 euro<br>
 **Deur:** 20:00<br>
 **Start:** 20:30	
--- a/content/kettle_EN.md
+++ b/content/kettle_EN.md
@ -1,36 +0,0 @@
 Title: The Call Of The Kettle
 Date: 2019-03-15
 Category: event
 slug: kettle_MD
 Tags: event
 lang: en
 Event_start: 2019-03-15 20:00
 event_duration: 4h
 featured_image: /images/kettle4-web-xs.jpg
 There is more between heaven and earth than humankind! Therefore, we would like to direct your attention to your fellow "inanimate" object on the 15th of March. On this day five special acts will showcase their intimate relationship with their sewing machines, toasters, fans and working gloves. All this under the guise of 'The Call Of The Kettle'; the first object oriented music evening at Varia! During this event there will be performances by the following artists:
 ** Agente Costura and Stephen Doyle ** are a duo playing improvised sounds, on amplified sewing machine and drums. Constura has been playing the Singer since 2003. In the daytime she tackles unwanted clothing, transforming them into new wearable shapes. At night, the Singer joins her fellow musicians and Lisa sews to the beat of the music, improvising on clothing based on rhythm and sound. Lisa has performed extensively, for instance at The Vancouver Art Gallery, the Month of Performance Art Berlin, the Bimhuis Amsterdam, and Curitiba Fashion Week. Stephen Doyle is a drummer, living and working in Amsterdam. His sounds have previously graced the creations of Dagora, 78rpm, and many more. Together, Costura and Doyle create a percussive upcycled torrent of uniquely sculpted sound.
 [Agente Costura Online](www.agentecostura.blogspot.de/)<br>
 [Stephen Doyle on Soundcloud](https://soundcloud.com/stephen-doyle-drummer)
 <iframe width="560" height="315" src="https://www.youtube.com/embed/oey80a-7CQ0" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 ** Watt’s Cookin’ ** is composed of Zeynep Aslan, Tamara van Suylekom and Inge Hoonte who met through re#sister and rehearse at Worm. For this performance, the three have teamed up to bang, clang and tinker with everyday household items. They are currently rehearsing in Inge's kitchen with the orchestra members they’ve interested to participate, such as water cookers and coffee percolators, a knife and a cutting board, a few jars with nuts, rice, and corn, and a couple of empty jars, a mini oven, two pans, two tea spoons and an egg beater. A bread toaster and a coconut milk can are hesitant if they want to join this upbeat troupe, but they will probably fit right in!
 ** De Brut ** is a new project by Marijn Verbiesen who, according to sources, is "one of the forces that keeps the Rotterdam underground together!" She has participated in numerous projects (Sweat Tongue, Red Brut) and is active as one of the organizers of the infamous Herman concert series. Besides that Verbiesen is renowned for her tape collages that are highly personal and highly regarded by magazines like The Wire.
 [Red Brut Online](https://redbrut.com/)
 <iframe width="560" height="315" src="https://www.youtube.com/embed/pa066-UzitY" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 ** Beachcombartband ** is a one-man-sea-trash-band from Rotterdam, helmed by none other than Bart Koppe. He performs with a collection of marine debris, played by mechanics and by hand. He will sweep the beach and throw its garbage on your head, in a maze of audio galactic joyfulness.
 ** The Singing Toaster ** is not like other toasters, because not every toaster is able to sing. Therefore the inclusion of this one during ‘the call of the kettle’ is somewhat of an occasion. Will the burned crumbs between its heating elements be enough to warm your heart? 
 **Date:** Friday, 15 March 2019<br>
 **Entrance:** 5 euro<br>
 **Door:** 20:00<br>
 **Start:** 20:30	
--- a/content/pages/about.nl.md
+++ b/content/pages/about.nl.md
@ -9,14 +9,13 @@ lang: nl
 # <a id="offline">ruimte</a>
 Gouwstraat 3<br>
-3082 BA<br>
+3082 BA, Rotterdam
 Rotterdam
 ![de ruimte](/images/varia.jpg)
 # <a id="contact">contact</contact>
-mail: [info@varia.zone](mailto:info@varia.zone)
+mail: info@varia.zone
 abboneer je op de mailinglijst: [varia@we.lurk.org](https://we.lurk.org/hyperkitty/list/varia@we.lurk.org/)
--- a/content/pages/colophon.en.md
+++ b/content/pages/colophon.en.md
@ -0,0 +1,16 @@
 Title: colophon
 Date: 2018-12-18
 Category: about
 Slug: colophon
 lang: en
 Varia<br>
 Gouwstraat 3<br>
 3082 BA<br> 
 Rotterdam<br>
 [info@varia.zone](mailto:info@varia.zone)
 [mailinglist](https://we.lurk.org/postorius/lists/varia.we.lurk.org/)<br>
 [RSS feed](feeds/all-en.rss.xml)
 [NL](/) / [EN](/en/){.active} <br>
--- a/content/pages/colophon.nl.md
+++ b/content/pages/colophon.nl.md
@ -0,0 +1,16 @@
 Title: colophon
 Date: 2018-12-18
 Category: about
 Slug: colophon
 lang: nl
 Varia<br>
 Gouwstraat 3<br>
 3082 BA<br> 
 Rotterdam<br>
 [info@varia.zone](mailto:info@varia.zone)
 [mailinglijst](https://we.lurk.org/postorius/lists/varia.we.lurk.org/)<br>
 [RSS feed](feeds/all-nl.rss.xml)
 [NL](/){.active} / [EN](/en/)<br>
--- a/content/pages/header.en.md
+++ b/content/pages/header.en.md
@ -4,4 +4,6 @@ Category: about
 Slug: header
 lang: en
-<a class="h-card" rel="me" href="https://varia.zone/en/">*varia*</a> (Gouwstraat 3, Rotterdam) is a space for developing collective approaches to everyday technology. *varia* is an [association](/en/pages/about.html#contact) whose members organize [events](/en/category/event.html) and collaborate in [work groups](/en/category/work-group.html). *varia* is [around 90m<sup>2</sup>](/en/pages/about.html#offline) and has a [100/35<sup>mbps</sup> connection](/en/pages/about.html#online). *varia* works with [free software](https://git.vvvvvvaria.org), provides [a set of tools](/en/pages/about.html). *varia* figures things out as she goes, tries to keep [notes](https://vvvvvvaria.org/archive), is [bilingual](/) and uses [info[@]varia.zone](mailto:info@varia.zone) to send and receive emails. 
+<a class="h-card" rel="me" href="https://varia.zone/en/">*varia*</a> (Gouwstraat 3, Rotterdam) is a space for collective approaches to everyday technology. Through events and work groups, varia members facilitate [a social infrastructure](/en/pages/infrastructure.html) for questions, opinions, modifications, help and action. *varia* works with free software, is around 90m2 and has a 100/35mbps connection. *varia* figures things out as she goes, tries to keep notes, is [bilingual](/) and can be contacted via [info[@]varia.zone](mailto:info@varia.zone).
--- a/content/pages/infrastructure.en.md
+++ b/content/pages/infrastructure.en.md
@ -0,0 +1,32 @@
 Title: infrastructure
 Date: 2018-12-18
 Category: about
 Slug: infrastructure
 lang: en
 #Channels
 varia experiments with tools for building physical and digital infrastructures of affinity. 
 A conscious decision has been taken to be considerate about the channels that we use to communicate through: what kind of new interactions are made possible through the protocolary other? Its members use federated networks like XMPP group chats, Mastodon instances, RSS feeds or the unflinching mailing list. Fragmented spaces of sociality that self-determine how they connect to one another.
 We look for ways to stay connected by offering a locally-accessible [library](https://books.vvvvvvaria.org/)(accessible without login in Varia itself), etherpads, calendar and [git repositories](https://git.vvvvvvaria.org/). Similarly, we are working on developing a depot for electronic parts and workbenches, as well as printing facilities.
 + archive mentioned somewhere
 ## <a id="online">online resources</a>
 *varia* hosts , , [etherpad](https://pad.vvvvvvaria.org/) and a [calender](https://cal.vvvvvvaria.org/).
 ###XMPP
 In addition to the above web services *varia* hosts a server for the federated chat protocol XMPP, supporting all the latest features.
 <a href='https://check.messaging.one/result.php?domain=vvvvvvaria.org&amp;type=client'>
  <img src='https://check.messaging.one/badge.php?domain=vvvvvvaria.org' alt='IM observatory score' />
 </a>
 <a href='https://compliance.conversations.im/server/vvvvvvaria.org'><img src='https://compliance.conversations.im/badge/vvvvvvaria.org'></a> 
 ###RSS
 Subscribe to our RSS feeds, available in [Dutch](http://varia.zone/feeds/all-nl.rss.xml) and [English](http://varia.zone/en/feeds/all-en.rss.xml). 
 <a href="https://validator.w3.org/feed/check.cgi?url=http%3A//varia.zone/feeds/all-nl.rss.xml"><img src="/images/valid-rss-rogers.png" alt="[Valid RSS]" title="Validate my RSS feed" /></a>
--- a/content/pages/stream.en.md
+++ b/content/pages/stream.en.md
@ -1,4 +0,0 @@
 Title: stream
 Category: meta
 Slug: stream
 lang: en
--- a/content/pages/stream.md
+++ b/content/pages/stream.md
@ -0,0 +1,16 @@
 Title: stream
 Category: meta
 Slug: stream
 # 18 Dec 2018
 [![](https://vvvvvvaria.org/stream/fXQltIw8Ti2w4C0eYlQE5g.jpg)](https://vvvvvvaria.org/stream/fXQltIw8Ti2w4C0eYlQE5g.jpg){.container}
 ---
 # 12 Dec 2018 
 XPPL is running! 
 ---
--- a/content/pages/stream.nl.md
+++ b/content/pages/stream.nl.md
@ -1,4 +0,0 @@
 Title: stream.nl
 Category: meta
 Slug: stream
 lang: nl
--- a/develop_server.sh
+++ b/develop_server.sh
@ -1,103 +0,0 @@
 #!/usr/bin/env bash
 ##
 # This section should match your Makefile
 ##
 PY=${PY:-python}
 PELICAN=${PELICAN:-pelican}
 PELICANOPTS=
 BASEDIR=$(pwd)
 INPUTDIR=$BASEDIR/content
 OUTPUTDIR=$BASEDIR/output
 CONFFILE=$BASEDIR/pelicanconf.py
 ###
 # Don't change stuff below here unless you are sure
 ###
 SRV_PID=$BASEDIR/srv.pid
 PELICAN_PID=$BASEDIR/pelican.pid
 function usage(){
  echo "usage: $0 (stop) (start) (restart) [port]"
  echo "This starts Pelican in debug and reload mode and then launches"
  echo "an HTTP server to help site development. It doesn't read"
  echo "your Pelican settings, so if you edit any paths in your Makefile"
  echo "you will need to edit your settings as well."
  exit 3
 }
 function alive() {
  kill -0 $1 >/dev/null 2>&1
 }
 function shut_down(){
  PID=$(cat $SRV_PID)
  if [[ $? -eq 0 ]]; then
    if alive $PID; then
      echo "Stopping HTTP server"
      kill $PID
    else
      echo "Stale PID, deleting"
    fi
    rm $SRV_PID
  else
    echo "HTTP server PIDFile not found"
  fi
  PID=$(cat $PELICAN_PID)
  if [[ $? -eq 0 ]]; then
    if alive $PID; then
      echo "Killing Pelican"
      kill $PID
    else
      echo "Stale PID, deleting"
    fi
    rm $PELICAN_PID
  else
    echo "Pelican PIDFile not found"
  fi
 }
 function start_up(){
  local port=$1
  echo "Starting up Pelican and HTTP server"
  shift
  $PELICAN --debug --autoreload -r $INPUTDIR -o $OUTPUTDIR -s $CONFFILE $PELICANOPTS &
  pelican_pid=$!
  echo $pelican_pid > $PELICAN_PID
  mkdir -p $OUTPUTDIR && cd $OUTPUTDIR
  $PY -m pelican.server $port &
  srv_pid=$!
  echo $srv_pid > $SRV_PID
  cd $BASEDIR
  sleep 1
  if ! alive $pelican_pid ; then
    echo "Pelican didn't start. Is the Pelican package installed?"
    return 1
  elif ! alive $srv_pid ; then
    echo "The HTTP server didn't start. Is there another service using port" $port "?"
    return 1
  fi
  echo 'Pelican and HTTP server processes now running in background.'
 }
 ###
 #  MAIN
 ###
 [[ ($# -eq 0) || ($# -gt 2) ]] && usage
 port=''
 [[ $# -eq 2 ]] && port=$2
 if [[ $1 == "stop" ]]; then
  shut_down
 elif [[ $1 == "restart" ]]; then
  shut_down
  start_up $port
 elif [[ $1 == "start" ]]; then
  if ! start_up $port; then
    shut_down
  fi
 else
  usage
 fi
--- a/1
+++ b/1
@ -1 +0,0 @@
 Subproject commit 8de8e847ce78e53b62dfdcd7e0e1923614adead5
--- a/pelicanconf.py
+++ b/pelicanconf.py
@ -2,37 +2,30 @@
 # -*- coding: utf-8 -*- #
 from __future__ import unicode_literals
-AUTHOR = u'Varia'
+AUTHOR = 'Varia'
-SITENAME = u'Varia'
+SITENAME = 'Varia'
 SITEURL = 'https://varia.zone'
 PATH = 'content'
 TIMEZONE = 'Europe/Amsterdam'
-DEFAULT_LANG = u'nl'
+DEFAULT_LANG = 'nl'
 DEFAULT_DATE = 'fs'
 USE_FOLDER_AS_CATEGORY = True
 # Feed generation is usually not desired when developing
 FEED_DOMAIN = SITEURL
 FEED_ALL_RSS = 'feeds/all.rss.xml'
-TRANSLATION_FEED_RSS = 'feeds/all-%s.rss.xml'
+# CATEGORY_FEED_ATOM = None
-RSS_FEED_SUMMARY_ONLY = False
+TRANSLATION_FEED_RSS = 'feeds/all-{lang}.rss.xml'
 FEED_ALL_ATOM = None
 CATEGORY_FEED_ATOM = None
 CATEGORY_FEED_RSS = None
 TRANSLATION_FEED_ATOM = None
 AUTHOR_FEED_ATOM = None
 AUTHOR_FEED_RSS = None
-DEFAULT_PAGINATION = 50
+DEFAULT_PAGINATION = False
-# Uncomment following line if you want document-relative URLs when developing
+THEME = 'themes/varia'
-PLUGIN_PATHS = ['./pelican-plugins', './plugins-custom']
+THEME_STATIC_DIR = 'theme'
 PLUGINS = ['dateish', 'extract_toc', 'i18n_subsites', 'summary', 'events-ics','complex_footnotes', 'stream', 'thumbnailer'] 
 MD_EXTENSIONS = ['codehilite','extra','toc']
 PLUGIN_PATHS = ['plugins/pelican-plugins', 'plugins/plugins-custom']
 PLUGINS = ['dateish', 'extract_toc', 'i18n_subsites', 'summary', 'events-ics','complex_footnotes', 'stream', 'thumbnailer'] 
 STATIC_PATHS = ['extra/favicon.ico', 'images', 'pdfs', 'stream']
 EXTRA_PATH_METADATA = {
 	'extra/robots.txt': {'path': 'robots.txt'},
@ -40,9 +33,29 @@ EXTRA_PATH_METADATA = {
 	'extra/htaccess': {'path': '.htaccess'}
 }
-THEME = 'themes/varia'
+MARKDOWN = {
-THEME_STATIC_DIR = 'theme/'
+	'extensions':[
 		'markdown.extensions.codehilite',
 		'markdown.extensions.extra',
 		'markdown.extensions.smarty',
 		'markdown.extensions.toc' # We're probably not using this one?
 	]
 }
 #Our custom events plugin
 PLUGIN_EVENTS = {
 	'ics_calendars': ['events.ics', 'curriculum.ics'],
 	'default_location' : '',
 	'calendar_per_category': False
 }
 #Our custom Thumbnailer plugin settings
 IMAGE_PATH ="images"
 THUMBNAIL_KEEP_NAME = True
 THUMBNAIL_DIR ="images"
 THUMBNAIL_SIZES = {'thumb':'200x?', 'thumb2x':'400x?'}
 # Translations plugin settings
 I18N_SUBSITES = {
 	'en': {
 		'SITESUBTITLE':u'Centre for Everyday Technology',
@ -56,23 +69,11 @@ I18N_SUBSITES = {
 	}
 }
 #Options for plugins
 #Our custom events plugin
 PLUGIN_EVENTS = {
 	'ics_calendars': ['events.ics', 'curriculum.ics'],
 	'default_location' : '',
 	'calendar_per_category': False
 }
 #Dateish plugin settings
 DATEISH_PROPERTIES = ['event_start', 'event_end']
 #Thumbnailer plugin settings
 IMAGE_PATH ="images"
 THUMBNAIL_KEEP_NAME = True
 THUMBNAIL_DIR ="images"
 THUMBNAIL_SIZES = {'thumb':'200x?', 'thumb2x':'400x?'}
 # category url
 CATEGORY_URL = '/{slug}.html'
 # Uncomment following line if you want document-relative URLs when developing
 #RELATIVE_URLS = True
--- a/1
+++ b/1
@ -1 +0,0 @@
 Subproject commit 06abd8f6b37abcd6ec58c6d134edd5cd8332a3d2
--- a/publishconf.py
+++ b/publishconf.py
@ -10,9 +10,16 @@ import sys
 sys.path.append(os.curdir)
 from pelicanconf import *
 # If your site is available via HTTPS, make sure SITEURL begins with https://
 SITEURL = 'https://varia.zone'
 RELATIVE_URLS = False
 FEED_ALL_ATOM = 'feeds/all.atom.xml'
 CATEGORY_FEED_ATOM = 'feeds/{slug}.atom.xml'
 DELETE_OUTPUT_DIRECTORY = True
 # Following items are often useful when publishing
 #DISQUS_SITENAME = ""
 #GOOGLE_ANALYTICS = ""
--- a/requirements.txt
+++ b/requirements.txt
@ -1,5 +1,5 @@
 icalendar==4.0.2
 Markdown==2.6.11
-pelican==3.7.1
+pelican==4.0.1
 beautifulsoup4==4.6.3
 html5lib==1.0.1
--- a/themes/varia/static/css/main.css
+++ b/themes/varia/static/css/main.css
@ -1,403 +0,0 @@
@font-face{
 	font-family: "header";
 	src:url('../fonts/cmuntt.ttf');
 	font-weight: normal;
 	font-style: normal;
 }
@font-face{
 	font-family: "kop";
 	src:url('../fonts/cmunssdc.ttf');
 	font-weight: normal;
 	font-style: normal;
 }
@font-face{
 	font-family: "main";
 	src:url('../fonts/cooper-hewitt/CooperHewitt-Medium.otf');
 	font-weight: normal;
 	font-style: normal;
 }
@font-face{
 	font-family: "main";
 	src:url('../fonts/cooper-hewitt/CooperHewitt-Bold.otf');
 	font-weight: bold;
 	font-style: normal;
 }
@font-face{
 	font-family: "main";
 	src:url('../fonts/cooper-hewitt/CooperHewitt-MediumItalic.otf');
 	font-weight: normal;
 	font-style: italic;
 }
@font-face{
 	font-family: "main";
 	src:url('../fonts/cooper-hewitt/CooperHewitt-BoldItalic.otf');
 	font-weight: bold;
 	font-style: italic;
 }
 body{
 	position: relative;
 	width: calc(100% - 50px);
 	min-width: 500px;
 	top:0px;
 	left:0px;
 	margin:0 auto 5em auto;
 	padding: 14px 15px;
 	font-family: "main", monospace;
 	font-size: 22px;
 	line-height:1.65;
 	background-color: rgba(238, 238, 238, 0.5);
 	color:#164515;
 }
 #content{
 	margin-top:1em;
 }
 /****************************/
 /* general elements */
 a {
 	color:#7e5211;
 }
 a:hover{
 	border:0;
 	text-decoration: none;
 }
 h1, h2, h3, h4, h5, h6, #header{
 	margin:0;
 	padding:0;
 }
 	h1{
 		font-family: "kop";
 		font-size: 100%;
 	}
 	h2{
 		font-size: 100%;
 		text-decoration: underline;
 	}
 	h3{
 		font-size: 100%;
 		font-weight: normal;
 	}
 p{
 	margin:0 0 1em 0;
 }
 em{
 }
 small{
 	display: block;
 	font-size: 15px;
 	line-height: 1.2;
 	margin-top:0.5em;
 }
 sup{
 	font-size: 12px;
 }
 pre{
 	line-height: 1.0;
 	font-family: monospace;
 }
 hr, .separator hr {
 	border:0;
 	border-top:1px dotted #7e5211;
 	color: black;
 	margin:1em 0 .5em;
 }
 blockquote {
 	font-style:italic;
 }
 ul {
 	padding-left:0px;
 }
 .paginator{
 	float:right;
 	margin:0px;
 }
 #post-list {
 	padding-left:0px;
 	margin-top:0px;
 }
 ul li{
 	list-style: none;
 	margin: 0 0 0 20px;
 }
 	ul li:before{
 		content: '* ';
 		margin: 0 4px 0 -20px;
 	}
 /* article info */
 .article-info{
 	font-size: 12px;
 	margin:0;
 }
 	/* date */
 	.article-info .event-details{
 		color:#7e5211;
 	}
 	/* featured image */
 	.article-info .featured-image img{
 		width:100%;
 		margin:0.5em 0;
 	}
 	.event-details .article-event-start{
 		margin-bottom:1em;
 	}
 	/* category & translation link */
 	.post-info{
 		font-size: 12px;
 		font-style: italic;
 	}
 		.post-info time{
 			display: block;
 		}
 		.post-info sup{
 			font-size: 80%;
 		}
 		.post-info .article-authors{
 			display: block;
 		}
 		.post-info .article-translation{
 			margin-top:1em;
 		}
 		.post-info .categories:before, .post-info .article-translation:before{
 			content:'↓';
 			color:#7e5211;
 			font-family: sans-serif;
 			padding-right: 5px;
 		}
 		.post-info .article-translation:before{
 			content:'→';
 		}
 /****************************/
 /* header & #translation */
 header {
 	width:calc(100% - 50px);
 	margin-top:26px;
 	margin-bottom:5em;
 	padding-bottom:1em;
 	font-family: "header";
 	font-size: 17px;
 	line-height: 1.6;
 	letter-spacing: -0.03em;
 }
 	header img{
 		width: 50px;
 		display: inline;
 		margin: 0;
 		vertical-align: calc(-2px);
 	}
 	/* custom font size for index */
 	#content.index header{
 		font-size: 24px;
 		line-height: 1.5;
 		margin-top:0;
 	}
 	header p{
 		display: inline;
 	}
 	#stream{
 		position: absolute;
 		width: 100%;
 	}
 		#stream a .container{
 		    background-clip: padding-box;
 		    background-position: center center;
 		    background-size: cover;
 		    height: 600px;
 		    width: 100%;
 		}
 			/* reset header img styles */
 			#stream a .container img{
 				min-width: none;
 				min-height: none;
 				width: none;
 				height: none;
 			}
 			#stream a{
 				display: block;
 			}
 	#stream.overview{
 		width: 100%;
 	}
 	div#stream a:nth-child(odd) {
   		transform: skew(-2deg);
 	}
 	div#stream a:nth-child(even) {
    	transform: skew(2deg);
 	}
 .buttons{
 	position: absolute;
 	font-size: 14px;
 	margin:0;
 	padding:0;
 }
 	.buttons.top, .buttons.side{
 		top:10px;
 		right:15px;
 		text-align: right;
 	}
 	.buttons.side{
 		top:40px;
 	}
 		.buttons.side li{
 			display: block;
 		}
 	.buttons li{
 		list-style: none;
 		display: inline-block;
 		padding-left: 3px;
 	}
 	.buttons li.active a{
 		text-decoration: none;
 	}
 /****************************/
 /* main/index overview page */
 #content #post-list{
 	width: 100%;
 }
 .summary p{
 	display: inline;
 }
 .summary .read_more:before{
 	content:'→';
 	padding: 0 5px;
 	font-family: sans-serif;
 	font-size:12px;
 	color:#7e5211;
 }
 .article.hentry, /*.documentation.hentry*/{
 	width:calc(400px + 2em);
 }
 .hentry{
 	display: inline-block;
 	width: 200px;
 	font-size: 14px;
 	line-height: 1.65;
 	margin:0 2em 5em 0;
 	padding:0;
 	vertical-align: top;
 }
 	.hentry .article-info{
 		width: 100%;
 	}
 		.hentry .article-info .event-details{
 			margin:5px 0 2px;
 			min-height: 1.65em;
 			font-family: monospace;
 		}
 		/* title */
 		.hentry .article-info .entry-title{
 			display: block;
 			width: 100%;
 			font-family: "kop";
 			font-size: 185%;
 			font-weight: bold;
 			line-height: 1.15;
 			margin:0;
 		}
 			.hentry .article-info .entry-title a{
 				text-decoration: none;
 			}
 	/* ascii art styling */
 	.hentry pre{
 		font-size: 14.4px;
 		font-weight: normal;
 		clear:both; /*to prevent the ascii to break up*/
 	}
 	/* double-blocks for super important categories */
 	.hentry.current, .hentry.article, .hentry.artikel, .hentry.current .article-info, .hentry.current .featured-image img{
 		width: calc(400px + 1em);
 	}
 	/* color background for articles */
 	.hentry.article, .hentry.artikel{
 		padding:1.5em 1em 1em 1em;
 		border:1px dashed #7e5211;
 		border-radius:15px;
 	}
 /****************************/
 /* article */
 #content.body .entry-title{
 	display:inline-block;
 	font-family: "kop";
 	font-size: 250%;
 	line-height: 1.25;
 	font-weight: bold;
 	margin:30px 0 30px 250px;
 	color:#7e5211;
 	width: calc(100% - 250px);
 }
 #content.body .article-info{
 	width:200px;
 	float: left;
 }
 .entry-content-container, #page-content-container{
 	width: calc(100% - 260px);
 	float: right;
 	padding:0 30px;
 	margin-bottom:25px;
 }
 	.entry-content, #page-content{
 		position: relative;
 		max-width: 750px;
 		margin:-3px auto 0 20px;
 	}
 		.entry-content img, #page-content img{
 			max-height:400px;
 		}
 		.entry-content .seperator hr, #page-content hr{
 			width:100%;
 		}
 /****************************/
 /* other */
 .highlight{
 	margin: auto;
 	max-width:800px;
 }
 .divider {
 	font-size:14.8px;
 	width:100%;
 	line-height:1em;
 	background-color:white;
 }
 #categories {
 	font-size: 40px;
 	margin-top: 2em;
 	text-align: center;
 }
 .author{
 	/*display: none;*/
 }
 iframe{
 	width: 100%;
 	height: auto;
 	min-height: 500px;
 	margin:0.5em 0 1em 0;
 }
 /*footnotes*/
 sup span{
 	float: right;
 	width: 200px;
 	margin:0.25em -150px 1em 3em;
 	clear:both;
 	font-size: 11px;
 	line-height: 1.5;
 	display: inline;
 }
 	sup span p{
 		display: inline;
 	}
--- a/themes/varia/static/css/pygment.css
+++ b/themes/varia/static/css/pygment.css
@ -1,438 +0,0 @@
 /*
 pre .hll {
    background-color: #ffffcc;
 }
 pre .c {
    color: #60a0b0;
    font-style: italic;
 }
 pre .err {
    border: 1px solid #ff0000;
 }
 pre .k {
    color: #007020;
    font-weight: bold;
 }
 pre .o {
    color: #666666;
 }
 pre .ch {
    color: #60a0b0;
    font-style: italic;
 }
 pre .cm {
    color: #60a0b0;
    font-style: italic;
 }
 pre .cp {
    color: #007020;
 }
 pre .cpf {
    color: #60a0b0;
    font-style: italic;
 }
 pre .c1 {
    color: #60a0b0;
    font-style: italic;
 }
 pre .cs {
    background-color: #fff0f0;
    color: #60a0b0;
 }
 pre .gd {
    color: #a00000;
 }
 pre .ge {
    font-style: italic;
 }
 pre .gr {
    color: #ff0000;
 }
 pre .gh {
    color: #000080;
    font-weight: bold;
 }
 pre .gi {
    color: #00a000;
 }
 pre .go {
    color: #888888;
 }
 pre .gp {
    color: #c65d09;
    font-weight: bold;
 }
 pre .gs {
    font-weight: bold;
 }
 pre .gu {
    color: #800080;
    font-weight: bold;
 }
 pre .gt {
    color: #0044dd;
 }
 pre .kc {
    color: #007020;
    font-weight: bold;
 }
 pre .kd {
    color: #007020;
    font-weight: bold;
 }
 pre .kn {
    color: #007020;
    font-weight: bold;
 }
 pre .kp {
    color: #007020;
 }
 pre .kr {
    color: #007020;
    font-weight: bold;
 }
 pre .kt {
    color: #902000;
 }
 pre .m {
    color: #40a070;
 }
 pre .s {
    color: #4070a0;
 }
 pre .na {
    color: #4070a0;
 }
 pre .nb {
    color: #007020;
 }
 pre .nc {
    color: #0e84b5;
    font-weight: bold;
 }
 pre .no {
    color: #60add5;
 }
 pre .nd {
    color: #555555;
    font-weight: bold;
 }
 pre .ni {
    color: #d55537;
    font-weight: bold;
 }
 pre .ne {
    color: #007020;
 }
 pre .nf {
    color: #06287e;
 }
 pre .nl {
    color: #002070;
    font-weight: bold;
 }
 pre .nn {
    color: #0e84b5;
    font-weight: bold;
 }
 pre .nt {
    color: #062873;
    font-weight: bold;
 }
 pre .nv {
    color: #bb60d5;
 }
 pre .ow {
    color: #007020;
    font-weight: bold;
 }
 pre .w {
    color: #bbbbbb;
 }
 pre .mb {
    color: #40a070;
 }
 pre .mf {
    color: #40a070;
 }
 pre .mh {
    color: #40a070;
 }
 pre .mi {
    color: #40a070;
 }
 pre .mo {
    color: #40a070;
 }
 pre .sb {
    color: #4070a0;
 }
 pre .sc {
    color: #4070a0;
 }
 pre .sd {
    color: #4070a0;
    font-style: italic;
 }
 pre .s2 {
    color: #4070a0;
 }
 pre .se {
    color: #4070a0;
    font-weight: bold;
 }
 pre .sh {
    color: #4070a0;
 }
 pre .si {
    color: #70a0d0;
    font-style: italic;
 }
 pre .sx {
    color: #c65d09;
 }
 pre .sr {
    color: #235388;
 }
 pre .s1 {
    color: #4070a0;
 }
 pre .ss {
    color: #517918;
 }
 pre .bp {
    color: #007020;
 }
 pre .vc {
    color: #bb60d5;
 }
 pre .vg {
    color: #bb60d5;
 }
 pre .vi {
    color: #bb60d5;
 }
 pre .il {
    color: #40a070;
 }
 .syntax pre .hll {
    background-color: #ffffcc;
 }
 .syntax pre {
    background: #f0f0f0 none repeat scroll 0 0;
 }
 .syntax pre .c {
    color: #60a0b0;
    font-style: italic;
 }
 .syntax pre .err {
    border: 1px solid #ff0000;
 }
 .syntax pre .k {
    color: #007020;
    font-weight: bold;
 }
 .syntax pre .o {
    color: #666666;
 }
 .syntax pre .ch {
    color: #60a0b0;
    font-style: italic;
 }
 .syntax pre .cm {
    color: #60a0b0;
    font-style: italic;
 }
 .syntax pre .cp {
    color: #007020;
 }
 .syntax pre .cpf {
    color: #60a0b0;
    font-style: italic;
 }
 .syntax pre .c1 {
    color: #60a0b0;
    font-style: italic;
 }
 .syntax pre .cs {
    background-color: #fff0f0;
    color: #60a0b0;
 }
 .syntax pre .gd {
    color: #a00000;
 }
 .syntax pre .ge {
    font-style: italic;
 }
 .syntax pre .gr {
    color: #ff0000;
 }
 .syntax pre .gh {
    color: #000080;
    font-weight: bold;
 }
 .syntax pre .gi {
    color: #00a000;
 }
 .syntax pre .go {
    color: #888888;
 }
 .syntax pre .gp {
    color: #c65d09;
    font-weight: bold;
 }
 .syntax pre .gs {
    font-weight: bold;
 }
 .syntax pre .gu {
    color: #800080;
    font-weight: bold;
 }
 .syntax pre .gt {
    color: #0044dd;
 }
 .syntax pre .kc {
    color: #007020;
    font-weight: bold;
 }
 .syntax pre .kd {
    color: #007020;
    font-weight: bold;
 }
 .syntax pre .kn {
    color: #007020;
    font-weight: bold;
 }
 .syntax pre .kp {
    color: #007020;
 }
 .syntax pre .kr {
    color: #007020;
    font-weight: bold;
 }
 .syntax pre .kt {
    color: #902000;
 }
 .syntax pre .m {
    color: #40a070;
 }
 .syntax pre .s {
    color: #4070a0;
 }
 .syntax pre .na {
    color: #4070a0;
 }
 .syntax pre .nb {
    color: #007020;
 }
 .syntax pre .nc {
    color: #0e84b5;
    font-weight: bold;
 }
 .syntax pre .no {
    color: #60add5;
 }
 .syntax pre .nd {
    color: #555555;
    font-weight: bold;
 }
 .syntax pre .ni {
    color: #d55537;
    font-weight: bold;
 }
 .syntax pre .ne {
    color: #007020;
 }
 .syntax pre .nf {
    color: #06287e;
 }
 .syntax pre .nl {
    color: #002070;
    font-weight: bold;
 }
 .syntax pre .nn {
    color: #0e84b5;
    font-weight: bold;
 }
 .syntax pre .nt {
    color: #062873;
    font-weight: bold;
 }
 .syntax pre .nv {
    color: #bb60d5;
 }
 .syntax pre .ow {
    color: #007020;
    font-weight: bold;
 }
 .syntax pre .w {
    color: #bbbbbb;
 }
 .syntax pre .mb {
    color: #40a070;
 }
 .syntax pre .mf {
    color: #40a070;
 }
 .syntax pre .mh {
    color: #40a070;
 }
 .syntax pre .mi {
    color: #40a070;
 }
 .syntax pre .mo {
    color: #40a070;
 }
 .syntax pre .sb {
    color: #4070a0;
 }
 .syntax pre .sc {
    color: #4070a0;
 }
 .syntax pre .sd {
    color: #4070a0;
    font-style: italic;
 }
 .syntax pre .s2 {
    color: #4070a0;
 }
 .syntax pre .se {
    color: #4070a0;
    font-weight: bold;
 }
 .syntax pre .sh {
    color: #4070a0;
 }
 .syntax pre .si {
    color: #70a0d0;
    font-style: italic;
 }
 .syntax pre .sx {
    color: #c65d09;
 }
 .syntax pre .sr {
    color: #235388;
 }
 .syntax pre .s1 {
    color: #4070a0;
 }
 .syntax pre .ss {
    color: #517918;
 }
 .syntax pre .bp {
    color: #007020;
 }
 .syntax pre .vc {
    color: #bb60d5;
 }
 .syntax pre .vg {
    color: #bb60d5;
 }
 .syntax pre .vi {
    color: #bb60d5;
 }
 .syntax pre .il {
    color: #40a070;
 }
 */
--- a/themes/varia/static/css/stylesheet.css
+++ b/themes/varia/static/css/stylesheet.css
--- a/themes/varia/static/fonts/CourierCode-Bold.ttf
+++ b/themes/varia/static/fonts/CourierCode-Bold.ttf
--- a/themes/varia/static/fonts/CourierCode-BoldItalic.ttf
+++ b/themes/varia/static/fonts/CourierCode-BoldItalic.ttf
--- a/themes/varia/static/fonts/CourierCode-Italic.ttf
+++ b/themes/varia/static/fonts/CourierCode-Italic.ttf
--- a/themes/varia/static/fonts/CourierCode-Roman.ttf
+++ b/themes/varia/static/fonts/CourierCode-Roman.ttf
--- a/themes/varia/static/fonts/cmunit.ttf
+++ b/themes/varia/static/fonts/cmunit.ttf
--- a/themes/varia/static/fonts/cmunobx.ttf
+++ b/themes/varia/static/fonts/cmunobx.ttf
--- a/themes/varia/static/fonts/cmunorm.ttf
+++ b/themes/varia/static/fonts/cmunorm.ttf
--- a/themes/varia/static/fonts/cmunssdc.ttf
+++ b/themes/varia/static/fonts/cmunssdc.ttf
--- a/themes/varia/static/fonts/cmuntb.ttf
+++ b/themes/varia/static/fonts/cmuntb.ttf
--- a/themes/varia/static/fonts/cmuntt.ttf
+++ b/themes/varia/static/fonts/cmuntt.ttf
--- a/themes/varia/static/fonts/cmuntx.ttf
+++ b/themes/varia/static/fonts/cmuntx.ttf
--- a/themes/varia/static/fonts/cmunvi.ttf
+++ b/themes/varia/static/fonts/cmunvi.ttf
--- a/themes/varia/static/fonts/cmunvt.ttf
+++ b/themes/varia/static/fonts/cmunvt.ttf
--- a/themes/varia/static/fonts/cooper-hewitt/-CooperHewitt-FontLog.txt
+++ b/themes/varia/static/fonts/cooper-hewitt/-CooperHewitt-FontLog.txt
@ -1,100 +0,0 @@
 Font Log
 Cooper Hewitt Typeface
 / / / / / / / / / /
 This file provides information on the Cooper Hewitt typeface. This information should be distributed along with the Cooper Hewitt fonts and any derivative works.
 Basic Font Information
 / / / / / / / / / /
 Cooper Hewitt is a Unicode sans serif typeface family, created for the Cooper Hewitt Smithsonian Design Museum - cooperhewitt.org - in 2014 as part of the museum's new visual identity.
 The typeface was designed by Chester Jenkins at Village Type and Design LLC, working with Eddie Opara and his group at Pentagram, and Cooper Hewitt Smithsonian Design Museum director Caroline Baumann and her team. 
 The typeface at June 2014 has 7 weights in roman and italic, in the Latin script only.
 Supported Codepages and Languages
 / / / / / / / / / /
 ISO 8859-1 / LATIN1
 Afrikaans, Albanian, Basque, Breton, Catalan, Catalan, Corsican, Czech, Danish, Dutch, English (UK and US), Estonian, Faroese, Finnish, French, Galician, German, Hungarian, Icelandic, Indonesian, Irish, Irish (new orthography), Italian, Latin (basic classical orthography), Leonese, Luxembourgish (basic classical orthography), Malay, Manx, Māori, Norwegian (Bokmål and Nynorsk), Occitan, Portuguese, Rhaeto-Romanic, Scottish Gaelic, Spanish, Swahili, Swedish, Turkish, Walloon, Welsh
 ISO 8859-2 / LATIN2
 Bosnian, Croatian, Czech, German, Hungarian, Polish, Romanian, Serbian (when in the Latin script), Slovak, Slovene, Upper Sorbian, and Lower Sorbian
 ISO 8859-3 / LATIN3
 South European: Esperanto, Maltese, Turkish
 ISO 8859-4 / LATIN4
 North European: Estonian, Greenlandic, Latvian, Lithuanian, Sami
 ISO 8859-9 / LATIN5
 Turkish
 ISO 8859-10 / LATIN6
 Nordic
 ISO 8859-13 / LATIN7
 Baltic Rim
 ISO 8859-14 / LATIN8
 Celtic: Breton, Cornish, Irish, Manx, Scottish Gaelic, Welsh
 ISO 8859-15 / LATIN9
 Afrikaans, Albanian, Breton, Catalan, Danish, Dutch, English (US and modern British), Estonian, Faroese, Finnish, French, Galician, German, Icelandic, Irish (New orthography), Italian, Kurdish (Unified Alphabet), Latin (basic classical orthography), Luxembourgish (basic classical orthography), Malay (Rumi script), Norwegian (Bokmål and Nynorsk), Occitan, Portuguese (European and Brazilian), Rhaeto-Romanic, Scottish Gaelic, Scots, Spanish, Swahili, Swedish, Tagalog, Walloon
 ISO 8859-16 / LATIN10
 Albanian, Croatian, French, German, Hungarian, Irish Gaelic (new orthography), Italian, Polish, Romanian, Serbian, Slovenian
 Change Log
 / / / / / / / / / /
 (This should list both major and minor changes, most recent first.)
 2014/06/16
 Initial release.
 Information for Developers/Contributors
 / / / / / / / / / /
 The release of Cooper Hewitt v1.000 (and any subsequent versions) under the OFL license provides a means for people to modify the fonts to meet their needs and contribute to the project. For information on what you're allowed to
 change or modify, consult the OFL and OFL-FAQ.
 Anyone can make their own modified version of Cooper Hewitt (using a different name), but Cooper Hewitt Smithsonian Design Museum and Village Type and Design LLC will continue to maintain and develop the canonical version of the Cooper Hewitt typeface. As the package maintainer, we welcome contributions. Here are some things to keep in mind:
 Format: We are happy to accept contributions, but to maximise the chances of us including your work, please make it available to us (via email or a URL) as a UFO file.
 Source files: The primary source files for the fonts are the UFO files.
 Copyright attribution: If you submit something for inclusion in the main Cooper Hewitt fonts, we will ask you to affirm that it is your original work, and ask you to assign the copyright of your work to Cooper Hewitt Smithsonian Design Museum. This is to ensure that future releases can be made under improved versions of the OFL without requiring further permission. This follows
 the same principle used by the FSF. The Cooper Hewitt typeface is property of a not-for-profit organization committed to the dissemination of knowledge and information, and that any contributions incorporated in the fonts will always be available under the OFL or a similar license.
 Quality: Because we want to be able to guarantee a high level of quality for the primary Cooper Hewitt typeface, we will review submissions carefully. Please don't be discouraged if we do not include a submission for this reason, or ask you to make specific revisions, or make revisions we deem necessary or desirable.
 Types of contributions: If you wish to make a contribution - a set of additional glyphs, scripts, code, etc. - please contact us before you do any work to see if it is a contribution we currently need. Every addition adds to the complexity of the project and needs to be carefully planned. This also avoids two people working on the same type of addition at the same time.
 When submissions will be included: We will revise the fonts when major updates are needed - new versions of Unicode, for example - and/or when we have material for a useful addition to the typeface. If you wish to make submissions, please contact us. 
 Acknowledgements
 / / / / / / / / / /
 (Here is where contributors can be acknowledged. If you make modifications be sure to add your name (N), email (E), web-address (W) and description (D). This list is sorted by last name in alphabetical order.)
 N: Chester Jenkins
 E: chester@vllg.com
 W: http://vllg.com/
 D: Original Designer
 N: Tal Leming
 E: tal@typesupply.com
 W: http://typesupply.com/
 D: UFO file preparation
 The Cooper Hewitt typeface is maintained by Village Type and Design LLC: CooperHewitt@vllg.com
 (We acknowledge SIL, the company behind the Open Font License (OFL); this Font Log is based on the Fontlog created for the Gentium typeface project.)
--- a/themes/varia/static/fonts/cooper-hewitt/-CooperHewitt-OFL-201406.txt
+++ b/themes/varia/static/fonts/cooper-hewitt/-CooperHewitt-OFL-201406.txt
@ -1,45 +0,0 @@
 Copyright (c) 2014, Cooper Hewitt Smithsonian Design Museum (cooperhewitt.org), with Reserved Font Name Cooper Hewitt.
 This Font Software is licensed under the SIL Open Font License, Version 1.1.
 This license is copied below, and is also available with a FAQ at: http://scripts.sil.org/OFL
 -----------------------------------------------------------
 SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
 -----------------------------------------------------------
 PREAMBLE
 The goals of the Open Font License (OFL) are to stimulate worldwide development of collaborative font projects, to support the font creation efforts of academic and linguistic communities, and to provide a free and open framework in which fonts may be shared and improved in partnership with others.
 The OFL allows the licensed fonts to be used, studied, modified and redistributed freely as long as they are not sold by themselves. The fonts, including any derivative works, can be bundled, embedded, redistributed and/or sold with any software provided that any reserved names are not used by derivative works. The fonts and derivatives, however, cannot be released under any other type of license. The requirement for fonts to remain under this license does not apply to any document created using the fonts or their derivatives.
 DEFINITIONS
 "Font Software" refers to the set of files released by the Copyright Holder(s) under this license and clearly marked as such. This may include source files, build scripts and documentation.
 "Reserved Font Name" refers to any names specified as such after the copyright statement(s).
 "Original Version" refers to the collection of Font Software components as distributed by the Copyright Holder(s).
 "Modified Version" refers to any derivative made by adding to, deleting, or substituting -- in part or in whole -- any of the components of the Original Version, by changing formats or by porting the Font Software to a new environment.
 "Author" refers to any designer, engineer, programmer, technical writer or other person who contributed to the Font Software.
 PERMISSION & CONDITIONS
 Permission is hereby granted, free of charge, to any person obtaining a copy of the Font Software, to use, study, copy, merge, embed, modify, redistribute, and sell modified and unmodified copies of the Font Software, subject to the following conditions:
 1) Neither the Font Software nor any of its individual components, in Original or Modified Versions, may be sold by itself.
 2) Original or Modified Versions of the Font Software may be bundled, redistributed and/or sold with any software, provided that each copy contains the above copyright notice and this license. These can be included either as stand-alone text files, human-readable headers or in the appropriate machine-readable metadata fields within text or binary files as long as those fields can be easily viewed by the user.
 3) No Modified Version of the Font Software may use the Reserved Font Name(s) unless explicit written permission is granted by the corresponding Copyright Holder. This restriction only applies to the primary font name as presented to the users.
 4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font Software shall not be used to promote, endorse or advertise any Modified Version, except to acknowledge the contribution(s) of the Copyright Holder(s) and the Author(s) or with their explicit written permission.
 5) The Font Software, modified or unmodified, in part or in whole, must be distributed entirely under this license, and must not be distributed under any other license. The requirement for fonts to remain under this license does not apply to any document created using the Font Software.
 TERMINATION
 This license becomes null and void if any of the above conditions are not met.
 DISCLAIMER
 THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE.
--- a/themes/varia/static/fonts/cooper-hewitt/-OFL-FAQ.txt
+++ b/themes/varia/static/fonts/cooper-hewitt/-OFL-FAQ.txt
@ -1,425 +0,0 @@
 OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL)
 Version 1.1-update3 - Sept 2013
 (See http://scripts.sil.org/OFL for updates)
 CONTENTS OF THIS FAQ
 1  USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
 2  USING OFL FONTS FOR WEB PAGES AND ONLINE WEB FONT SERVICES
 3  MODIFYING OFL-LICENSED FONTS
 4  LICENSING YOUR ORIGINAL FONTS UNDER THE OFL
 5  CHOOSING RESERVED FONT NAMES
 6  ABOUT THE FONTLOG
 7  MAKING CONTRIBUTIONS TO OFL PROJECTS
 8  ABOUT THE LICENSE ITSELF
 9  ABOUT SIL INTERNATIONAL
 APPENDIX A - FONTLOG EXAMPLE
 1  USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
 1.1  Can I use the fonts for a book or other print publication, to create logos or other graphics or even to manufacture objects based on their outlines?
 Yes. You are very welcome to do so. Authors of fonts released under the OFL allow you to use their font software as such for any kind of design work. No additional license or permission is required, unlike with some other licenses. Some examples of these uses are: logos, posters, business cards, stationery, video titling, signage, t-shirts, personalised fabric, 3D-printed/laser-cut shapes, sculptures, rubber stamps, cookie cutters and lead type.
 1.1.1  Does that restrict the license or distribution of that artwork?
 No. You remain the author and copyright holder of that newly derived graphic or object. You are simply using an open font in the design process. It is only when you redistribute, bundle or modify the font itself that other conditions of the license have to be respected (see below for more details).
 1.1.2  Is any kind of acknowledgement required?
 No. Font authors may appreciate being mentioned in your artwork's acknowledgements alongside the name of the font, possibly with a link to their website, but that is not required.
 1.2  Can the fonts be included with Free/Libre and Open Source Software collections such as GNU/Linux and BSD distributions and repositories?
 Yes! Fonts licensed under the OFL can be freely included alongside other software under FLOSS (Free/Libre and Open Source Software) licenses. Since fonts are typically aggregated with, not merged into, existing software, there is little need to be concerned about incompatibility with existing software licenses. You may also repackage the fonts and the accompanying components in a .rpm or .deb package (or other similar package formats or installers) and include them in distribution CD/DVDs and online repositories. (Also see section 5.9 about rebuilding from source.)
 1.3  I want to distribute the fonts with my program. Does this mean my program also has to be Free/Libre and Open Source Software?
 No. Only the portions based on the Font Software are required to be released under the OFL. The intent of the license is to allow aggregation or bundling with software under restricted licensing as well.
 1.4  Can I sell a software package that includes these fonts?
 Yes, you can do this with both the Original Version and a Modified Version of the fonts. Examples of bundling made possible by the OFL would include: word processors, design and publishing applications, training and educational software, games and entertainment software, mobile device applications, etc.
 1.5  Can I include the fonts on a CD of freeware or commercial fonts?
 Yes, as long some other font or software is also on the disk, so the OFL font is not sold by itself.
 1.6  Why won't the OFL let me sell the fonts alone?
 The intent is to keep people from making money by simply redistributing the fonts. The only people who ought to profit directly from the fonts should be the original authors, and those authors have kindly given up potential direct income to distribute their fonts under the OFL. Please honour and respect their contribution!
 1.7  What about sharing OFL fonts with friends on a CD, DVD or USB stick?
 You are very welcome to share open fonts with friends, family and colleagues through removable media. Just remember to include the full font package, including any copyright notices and licensing information as available in OFL.txt. In the case where you sell the font, it has to come bundled with software.
 1.8  Can I host the fonts on a web site for others to use?
 Yes, as long as you make the full font package available. In most cases it may be best to point users to the main site that distributes the Original Version so they always get the most recent stable and complete version. See also discussion of web fonts in Section 2.
 1.9  Can I host the fonts on a server for use over our internal network?
 Yes. If the fonts are transferred from the server to the client computer by means that allow them to be used even if the computer is no longer attached to the network, the full package (copyright notices, licensing information, etc.) should be included.
 1.10  Does the full OFL license text always need to accompany the font?
 The only situation in which an OFL font can be distributed without the text of the OFL (either in a separate file or in font metadata), is when a font is embedded in a document or bundled within a program. In the case of metadata included within a font, it is legally sufficient to include only a link to the text of the OFL on http://scripts.sil.org/OFL, but we strongly recommend against this. Most modern font formats include metadata fields that will accept the full OFL text, and full inclusion increases the likelihood that users will understand and properly apply the license.
 1.11  What do you mean by 'embedding'? How does that differ from other means of distribution?
 By 'embedding' we mean inclusion of the font in a document or file in a way that makes extraction (and redistribution) difficult or clearly discouraged. In many cases the names of embedded fonts might also not be obvious to those reading the document, the font data format might be altered, and only a subset of the font - only the glyphs required for the text - might be included. Any other means of delivering a font to another person is considered 'distribution', and needs to be accompanied by any copyright notices and licensing information available in OFL.txt.
 1.12  So can I embed OFL fonts in my document?
 Yes, either in full or a subset. The restrictions regarding font modification and redistribution do not apply, as the font is not intended for use outside the document.
 1.13  Does embedding alter the license of the document itself?
 No. Referencing or embedding an OFL font in any document does not change the license of the document itself. The requirement for fonts to remain under the OFL does not apply to any document created using the fonts and their derivatives. Similarly, creating any kind of graphic using a font under OFL does not make the resulting artwork subject to the OFL.
 1.14  If OFL fonts are extracted from a document in which they are embedded (such as a PDF file), what can be done with them? Is this a risk to author(s)?
 The few utilities that can extract fonts embedded in a PDF will typically output limited amounts of outlines - not a complete font. To create a working font from this method is much more difficult and time consuming than finding the source of the original OFL font. So there is little chance that an OFL font would be extracted and redistributed inappropriately through this method. Even so, copyright laws address any misrepresentation of authorship. All Font Software released under the OFL and marked as such by the author(s) is intended to remain under this license regardless of the distribution method, and cannot be redistributed under any other license. We strongly discourage any font extraction - we recommend directly using the font sources instead - but if you extract font outlines from a document, please be considerate: respect the work of the author(s) and the licensing model.
 1.15  What about distributing fonts with a document? Within a compressed folder structure? Is it distribution, bundling or embedding?
 Certain document formats may allow the inclusion of an unmodified font within their file structure which may consist of a compressed folder containing the various resources forming the document (such as pictures and thumbnails). Including fonts within such a structure is understood as being different from embedding but rather similar to bundling (or mere aggregation) which the license explicitly allows. In this case the font is conveyed unchanged whereas embedding a font usually transforms it from the original format. The OFL does not allow anyone to extract the font from such a structure to then redistribute it under another license. The explicit permission to redistribute and embed does not cancel the requirement for the Font Software to remain under the license chosen by its author(s). Even if the font travels inside the document as one of its assets, it should not lose its authorship information and licensing.
 1.16  What about ebooks shipping with open fonts?
 The requirements differ depending on whether the fonts are linked, embedded or distributed (bundled or aggregated). Some ebook formats use web technologies to do font linking via @font-face, others are designed for font embedding, some use fonts distributed with the document or reading software, and a few rely solely on the fonts already present on the target system. The license requirements depend on the type of inclusion as discussed in 1.15.
 1.17  Can Font Software released under the OFL be subject to URL-based access restrictions methods or DRM (Digital Rights Management) mechanisms?
 Yes, but these issues are out-of-scope for the OFL. The license itself neither encourages their use nor prohibits them since such mechanisms are not implemented in the components of the Font Software but through external software. Such restrictions are put in place for many different purposes corresponding to various usage scenarios. One common example is to limit potentially dangerous cross-site scripting attacks. However, in the spirit of libre/open fonts and unrestricted writing systems, we strongly encourage open sharing and reuse of OFL fonts, and the establishment of an environment where such restrictions are unnecessary. Note that whether you wish to use such mechanisms or you prefer not to, you must still abide by the rules set forth by the OFL when using fonts released by their authors under this license. Derivative fonts must be licensed under the OFL, even if they are part of a service for which you charge fees and/or for which access to source code is restricted. You may not sell the fonts on their own - they must be part of a larger software package, bundle or subscription plan. For example, even if the OFL font is distributed in a software package or via an online service using a DRM mechanism, the user would still have the right to extract that font, use, study, modify and redistribute it under the OFL.
 1.18  I've come across a font released under the OFL. How can I easily get more information about the Original Version? How can I know where it stands compared to the Original Version or other Modified Versions?
 Consult the copyright statement(s) in the license for ways to contact the original authors. Consult the FONTLOG (see section 6 for more details and examples) for information on how the font differs from the Original Version, and get in touch with the various contributors via the information in the acknowledgement section. Please consider using the Original Versions of the fonts whenever possible.
 1.19  What do you mean in condition 4 of the OFL's permissions and conditions? Can you provide examples of abusive promotion / endorsement / advertisement vs. normal acknowledgement?
 The intent is that the goodwill and reputation of the author(s) should not be used in a way that makes it sound like the original author(s) endorse or approve of a specific Modified Version or software bundle. For example, it would not be right to advertise a word processor by naming the author(s) in a listing of software features, or to promote a Modified Version on a web site by saying "designed by ...". However, it would be appropriate to acknowledge the author(s) if your software package has a list of people who deserve thanks. We realize that this can seem to be a grey area, but the standard used to judge an acknowledgement is that if the acknowledgement benefits the author(s) it is allowed, but if it primarily benefits other parties, or could reflect poorly on the author(s), then it is not.
 1.20 I'm writing a small app for mobile platforms, do I need to include the whole package? 
 If you bundle a font under the OFL with your mobile app you must comply with the terms of the license. At a minimum you must include the copyright statement, the license notice and the license text. A mention of this information in your About box or Changelog, with a link to where the font package is from, is good practice, and the extra space needed to carry these items is very small. You do not, however, need to include the full contents of the font package - only the fonts you use and the copyright and license that apply to them. For example, if you only use the regular weight in your app, you do not need to include the italic and bold versions.
 1.21 What about including OFL fonts by default in my firmware or dedicated operating system? 
 Many such systems are restricted and turned into appliances so that users cannot study or modify them. Using open fonts to increase quality and language coverage is a great idea, but you need to be aware that if there is a way for users to extract fonts you cannot legally prevent them from doing that. The fonts themselves, including any changes you make to them, must be distributed under the OFL even if your firmware has a more restrictive license. If you do transform the fonts and change their formats when you include them in your firmware you must respect any names reserved by the font authors via the RFN mechanism and pick your own font name. Alternatively if you directly add a font under the OFL to the font folder of your firmware without modifying or optimizing it you are simply bundling the font like with any other software collection, and do not need to make any further changes.
 1.22  Can I make and publish CMS themes or templates that use OFL fonts?  Can I include the fonts themselves in the themes or templates? Can I sell the whole package?
 Yes, you are very welcome to integrate open fonts into themes and templates for your preferred CMS and make them more widely available. Remember that you can only sell the fonts and your CMS add-on as part of a software bundle. (See 1.4 for details and examples about selling bundles).
 1.23  Can OFL fonts be included in services that deliver fonts to the desktop from remote repositories? Even if they contain both OFL and non-OFL fonts?
 Yes. Some foundries have set up services to deliver fonts to subscribers directly to desktops from their online repositories; similarly, plugins are available to preview and use fonts directly in your design tool or publishing suite. These services may mix open and restricted fonts in the same channel, however they should make a clear distinction between them to users. These services should also not hinder users (such as through DRM or obfuscation mechanisms) from extracting and using the OFL fonts in other environments, or continuing to use OFL fonts after subscription terms have ended, as those uses are specifically allowed by the OFL.
 1.24  Can services that provide or distribute OFL fonts restrict my use of them?
 No. The terms of use of such services cannot replace or restrict the terms of the OFL, as that would be the same as distributing the fonts under a different license, which is not allowed. You are still entitled to use, modify and redistribute them as the original authors have intended outside of the sole control of that particular distribution channel. Note, however, that the fonts provided by these services may differ from the Original Versions.
 2  USING OFL FONTS FOR WEBPAGES AND ONLINE WEB FONT SERVICES
 NOTE: This section often refers to a separate paper on 'Web Fonts & RFNs'. This is available at http://scripts.sil.org/OFL_web_fonts_and_RFNs
 2.1  Can I make webpages using these fonts?
 Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended. Your three best options are: 
 - referring directly in your stylesheet to open fonts which may be available on the user's system
 - providing links to download the full package of the font - either from your own website or from elsewhere - so users can install it themselves
 - using @font-face to distribute the font directly to browsers. This is recommended and explicitly allowed by the licensing model because it is distribution. The font file itself is distributed with other components of the webpage. It is not embedded in the webpage but referenced through a web address which will cause the browser to retrieve and use the corresponding font to render the webpage (see 1.11 and 1.15 for details related to embedding fonts into documents). As you take advantage of the @font-face cross-platform standard, be aware that web fonts are often tuned for a web environment and not intended for installation and use outside a browser. The reasons in favour of using web fonts are to allow design of dynamic text elements instead of static graphics, to make it easier for content to be localized and translated, indexed and searched, and all this with cross-platform open standards without depending on restricted extensions or plugins. You should check the CSS cascade (the order in which fonts are being called or delivered to your users) when testing.
 2.2  Can I make and use WOFF (Web Open Font Format) versions of OFL fonts?
 Yes, but you need to be careful. A change in font format normally is considered modification, and Reserved Font Names (RFNs) cannot be used. Because of the design of the WOFF format, however, it is possible to create a WOFF version that is not considered modification, and so would not require a name change. You are allowed to create, use and distribute a WOFF version of an OFL font without changing the font name, but only if:
 - the original font data remains unchanged except for WOFF compression, and
 - WOFF-specific metadata is either omitted altogether or present and includes, unaltered, the contents of all equivalent metadata in the original font.
 If the original font data or metadata is changed, or the WOFF-specific metadata is incomplete, the font must be considered a Modified Version, the OFL restrictions would apply and the name of the font must be changed: any RFNs cannot be used and copyright notices and licensing information must be included and cannot be deleted or modified. You must come up with a unique name - we recommend one corresponding to your domain or your particular web application. Be aware that only the original author(s) can use RFNs. This is to prevent collisions between a derivative tuned to your audience and the original upstream version and so to reduce confusion.
 Please note that most WOFF conversion tools and online services do not meet the two requirements listed above, and so their output must be considered a Modified Version. So be very careful and check to be sure that the tool or service you're using is compressing unchanged data and completely and accurately reflecting the original font metadata.
 2.3  What about other web font formats such as EOT/EOTLite/CWT/etc.?
 In most cases these formats alter the original font data more than WOFF, and do not completely support appropriate metadata, so their use must be considered modification and RFNs may not be used. However, there may be certain formats or usage scenarios that may allow the use of RFNs. See http://scripts.sil.org/OFL_web_fonts_and_RFNs 
 2.4  Can I make OFL fonts available through web font online services?
 Yes, you are welcome to include OFL fonts in online web font services as long as you properly meet all the conditions of the license. The origin and open status of the font should be clear among the other fonts you are hosting. Authorship, copyright notices and license information must be sufficiently visible to your users or subscribers so they know where the font comes from and the rights granted by the author(s). Make sure the font file contains the needed copyright notice(s) and licensing information in its metadata. Please double-check the accuracy of every field to prevent contradictory information. Other font formats, including EOT/EOTLite/CWT and superior alternatives like WOFF, already provide fields for this information. Remember that if you modify the font within your library or convert it to another format for any reason the OFL restrictions apply and you need to change the names accordingly. Please respect the author's wishes as expressed in the OFL and do not misrepresent original designers and their work. Don't lump quality open fonts together with dubious freeware or public domain fonts. Consider how you can best work with the original designers and foundries, support their efforts and generate goodwill that will benefit your service. (See 1.17 for details related to URL-based access restrictions methods or DRM mechanisms).
 2.5  Some web font formats and services provide ways of "optimizing" the font for a particular website or web application; is that allowed? 
 Yes, it is permitted, but remember that these optimized versions are Modified Versions and so must follow OFL requirements like appropriate renaming. Also you need to bear in mind the other important parameters beyond compression, speed and responsiveness: you need to consider the audience of your particular website or web application, as choosing some optimization parameters may turn out to be less than ideal for them. Subsetting by removing certain glyphs or features may seriously limit functionality of the font in various languages that your users expect. It may also introduce degradation of quality in the rendering or specific bugs on the various target platforms compared to the original font from upstream. In other words, remember that one person's optimized font may be another person's missing feature. Various advanced typographic features (OpenType, Graphite or AAT) are also available through CSS and may provide the desired effects without the need to modify the font.
 2.6  Is subsetting a web font considered modification?
 Yes. Removing any parts of the font when delivering a web font to a browser, including unused glyphs and smart font code, is considered modification. This is permitted by the OFL but would not normally allow the use of RFNs. Some newer subsetting technologies may be able to subset in a way that allows users to effectively have access to the complete font, including smart font behaviour. See 2.8 and http://scripts.sil.org/OFL_web_fonts_and_RFNs
 2.7  Are there any situations in which a modified web font could use RFNs?
 Yes. If a web font is optimized only in ways that preserve Functional Equivalence (see 2.8), then it may use RFNs, as it reasonably represents the Original Version and respects the intentions of the author(s) and the main purposes of the RFN mechanism (avoids collisions, protects authors, minimizes support, encourages derivatives). However this is technically very difficult and often impractical, so a much better scenario is for the web font service or provider to sign a separate agreement with the author(s) that allows the use of RFNs for Modified Versions.
 2.8  How do you know if an optimization to a web font preserves Functional Equivalence?
 Functional Equivalence is described in full in the 'Web fonts and RFNs' paper at http://scripts.sil.org/OFL_web_fonts_and_RFNs, in general, an optimized font is deemed to be Functionally Equivalent (FE) to the Original Version if it:
 - Supports the same full character inventory. If a character can be properly displayed using the Original Version, then that same character, encoded correctly on a web page, will display properly. 
 - Provides the same smart font behavior. Any dynamic shaping behavior that works with the Original Version should work when optimized, unless the browser or environment does not support it. There does not need to be guaranteed support in the client, but there should be no forced degradation of smart font or shaping behavior, such as the removal or obfuscation of OpenType, Graphite or AAT tables.
 - Presents text with no obvious degradation in visual quality. The lettershapes should be equally (or more) readable, within limits of the rendering platform.
 - Preserves original author, project and license metadata. At a minimum, this should include: Copyright and authorship; The license as stated in the Original Version, whether that is the full text of the OFL or a link to the web version; Any RFN declarations; Information already present in the font or documentation that points back to the Original Version, such as a link to the project or the author's website.
 If an optimized font meets these requirements, and so is considered to be FE, then it's very likely that the original author would feel that the optimized font is a good and reasonable equivalent. If it falls short of any of these requirements, the optimized font does not reasonably represent the Original Version, and so should be considered to be a Modified Version. Like other Modified Versions, it would not be allowed to use any RFNs and you simply need to pick your own font name.
 2.9  Isn't use of web fonts another form of embedding?
 No. Unlike embedded fonts in a PDF, web fonts are not an integrated part of the document itself. They are not specific to a single document and are often applied to thousands of documents around the world. The font data is not stored alongside the document data and often originates from a different location. The ease by which the web fonts used by a document may be identified and downloaded for desktop use demonstrates that they are philosophically and technically separate from the web pages that specify them. See http://scripts.sil.org/OFL_web_fonts_and_RFNs
 2.10  So would it be better to not use RFNs at all if you want your font to be distributed by a web fonts service?
 No. Although the OFL does not require authors to use RFNs, the RFN mechanism is an important part of the OFL model and completely compatible with web font services. If that web font service modifies the fonts, then the best solution is to sign a separate agreement for the use of any RFNs. It is perfectly valid for an author to not declare any RFNs, but before they do so they need to fully understand the benefits they are giving up, and the overall negative effect of allowing many different versions bearing the same name to be widely distributed. As a result, we don't generally recommend it.
 2.11  What should an agreement for the use of RFNs say? Are there any examples?
 There is no prescribed format for this agreement, as legal systems vary, and no recommended examples. Authors may wish to add specific clauses to further restrict use, require author review of Modified Versions, establish user support mechanisms or provide terms for ending the agreement. Such agreements are usually not public, and apply only to the main parties. However, it would be very beneficial for web font services to clearly state when they have established such agreements, so that the public understands clearly that their service is operating appropriately.
 See the separate paper on 'Web Fonts & RFNs' for in-depth discussion of issues related to the use of RFNs for web fonts. This is available at http://scripts.sil.org/OFL_web_fonts_and_RFNs
 3  MODIFYING OFL-LICENSED FONTS
 3.1  Can I change the fonts? Are there any limitations to what things I can and cannot change?
 You are allowed to change anything, as long as such changes do not violate the terms of the license. In other words, you are not allowed to remove the copyright statement(s) from the font, but you could put additional information into it that covers your contribution. See the placeholders in the OFL header template for recommendations on where to add your own statements. (Remember that, when authors have reserved names via the RFN mechanism, you need to change the internal names of the font to your own font name when making your modified version even if it is just a small change.)
 3.2  I have a font that needs a few extra glyphs - can I take them from an OFL licensed font and copy them into mine?
 Yes, but if you distribute that font to others it must be under the OFL, and include the information mentioned in condition 2 of the license.
 3.3  Can I charge people for my additional work? In other words, if I add a bunch of special glyphs or OpenType/Graphite/AAT code, can I sell the enhanced font?
 Not by itself. Derivative fonts must be released under the OFL and cannot be sold by themselves. It is permitted, however, to include them in a larger software package (such as text editors, office suites or operating systems), even if the larger package is sold. In that case, you are strongly encouraged, but not required, to also make that derived font easily and freely available outside of the larger package.
 3.4  Can I pay someone to enhance the fonts for my use and distribution?
 Yes. This is a good way to fund the further development of the fonts. Keep in mind, however, that if the font is distributed to others it must be under the OFL. You won't be able to recover your investment by exclusively selling the font, but you will be making a valuable contribution to the community. Please remember how you have benefited from the contributions of others.
 3.5  I need to make substantial revisions to the font to make it work with my program. It will be a lot of work, and a big investment, and I want to be sure that it can only be distributed with my program. Can I restrict its use?
 No. If you redistribute a Modified Version of the font it must be under the OFL. You may not restrict it in any way beyond what the OFL permits and requires. This is intended to ensure that all released improvements to the fonts become available to everyone. But you will likely get an edge over competitors by being the first to distribute a bundle with the enhancements. Again, please remember how you have benefited from the contributions of others.
 3.6  Do I have to make any derivative fonts (including extended source files, build scripts, documentation, etc.) publicly available?
 No, but please consider sharing your improvements with others. You may find that you receive in return more than what you gave.
 3.7  If a trademark is claimed in the OFL font, does that trademark need to remain in modified fonts?
 Yes. Any trademark notices must remain in any derivative fonts to respect trademark laws, but you may add any additional trademarks you claim, officially registered or not. For example if an OFL font called "Foo" contains a notice that "Foo is a trademark of Acme", then if you rename the font to "Bar" when creating a Modified Version, the new trademark notice could say "Foo is a trademark of Acme Inc. - Bar is a trademark of Roadrunner Technologies Ltd.". Trademarks work alongside the OFL and are not subject to the terms of the licensing agreement. The OFL does not grant any rights under trademark law. Bear in mind that trademark law varies from country to country and that there are no international trademark conventions as there are for copyright. You may need to significantly invest in registering and defending a trademark for it to remain valid in the countries you are interested in. This may be costly for an individual independent designer.
 3.8 If I commit changes to a font (or publish a branch in a DVCS) as part of a public open source software project, do I have to change the internal font names? 
 Only if there are declared RFNs. Making a public commit or publishing a public branch is effectively redistributing your modifications, so any change to the font will require that you do not use the RFNs. Even if there are no RFNs, it may be useful to change the name or add a suffix indicating that a particular version of the font is still in development and not released yet. This will clearly indicate to users and fellow designers that this particular font is not ready for release yet. See section 5 for more details.
 4  LICENSING YOUR ORIGINAL FONTS UNDER THE OFL
 4.1  Can I use the SIL OFL for my own fonts?
 Yes! We heartily encourage everyone to use the OFL to distribute their own original fonts. It is a carefully constructed license that allows great freedom along with enough artistic integrity protection for the work of the authors as well as clear rules for other contributors and those who redistribute the fonts. The licensing model is used successfully by various organisations, both for-profit and not-for-profit, to release fonts of varying levels of scope and complexity.
 4.2  What do I have to do to apply the OFL to my font?
 If you want to release your fonts under the OFL, we recommend you do the following:
 4.2.1  Put your copyright and Reserved Font Names information at the beginning of the main OFL.txt file in place of the dedicated placeholders (marked with the <> characters). Include this file in your release package.
 4.2.2  Put your copyright and the OFL text with your chosen Reserved Font Name(s) into your font files (the copyright and license fields). A link to the OFL text on the OFL web site is an acceptable (but not recommended) alternative. Also add this information to any other components (build scripts, glyph databases, documentation, test files, etc). Accurate metadata in your font files is beneficial to you as an increasing number of applications are exposing this information to the user. For example, clickable links can bring users back to your website and let them know about other work you have done or services you provide. Depending on the format of your fonts and sources, you can use template human-readable headers or machine-readable metadata. You should also double-check that there is no conflicting metadata in the font itself contradicting the license, such as the fstype bits in the os2 table or fields in the name table.
 4.2.3  Write an initial FONTLOG.txt for your font and include it in the release package (see Section 6 and Appendix A for details including a template).
 4.2.4  Include the relevant practical documentation on the license by adding the current OFL-FAQ.txt file in your package.
 4.2.5  If you wish you can use the OFL graphics (http://scripts.sil.org/OFL_logo) on your website. 
 4.3  Will you make my font OFL for me?
 We won't do the work for you. We can, however, try to answer your questions, unfortunately we do not have the resources to review and check your font packages for correct use of the OFL. We recommend you turn to designers, foundries or consulting companies with experience in doing open font design to provide this service to you. 
 4.4  Will you distribute my OFL font for me?
 No, although if the font is of sufficient quality and general interest we may include a link to it on our partial list of OFL fonts on the OFL web site. You may wish to consider other open font catalogs or hosting services, such as the Unifont Font Guide (http://unifont.org/fontguide), The League of Movable Type (http://theleagueofmovabletype.com) or the Open Font Library (http://openfontlibrary.org/), which despite the name has no direct relationship to the OFL or SIL. We do not endorse any particular catalog or hosting service - it is your responsibility to determine if the service is right for you and if it treats authors with fairness. 
 4.5  Why should I use the OFL for my fonts?
 - to meet needs for fonts that can be modified to support lesser-known languages
 - to provide a legal and clear way for people to respect your work but still use it (and reduce piracy)
 - to involve others in your font project
 - to enable your fonts to be expanded with new weights and improved writing system/language support
 - to allow more technical font developers to add features to your design (such as OpenType, Graphite or AAT support)
 - to renew the life of an old font lying on your hard drive with no business model
 - to allow your font to be included in Libre Software operating systems like Ubuntu
 - to give your font world status and wide, unrestricted distribution
 - to educate students about quality typeface and font design
 - to expand your test base and get more useful feedback 
 - to extend your reach to new markets when users see your metadata and go to your website
 - to get your font more easily into one of the web font online services
 - to attract attention for your commercial fonts
 - to make money through web font services
 - to make money by bundling fonts with applications
 - to make money adjusting and extending existing open fonts
 - to get a better chance that foundations/NGOs/charities/companies who commission fonts will pick you 
 - to be part of a sharing design and development community 
 - to give back and contribute to a growing body of font sources
 5  CHOOSING RESERVED FONT NAMES
 5.1  What are Reserved Font Names?
 These are font names, or portions of font names, that the author has chosen to reserve for use only with the Original Version of the font, or for Modified Version(s) created by the original author.
 5.2  Why can't I use the Reserved Font Names in my derivative font names? I'd like people to know where the design came from.
 The best way to acknowledge the source of the design is to thank the original authors and any other contributors in the files that are distributed with your revised font (although no acknowledgement is required). The FONTLOG is a natural place to do this. Reserved Font Names ensure that the only fonts that have the original names are the unmodified Original Versions. This allows designers to maintain artistic integrity while allowing collaboration to happen. It eliminates potential confusion and name conflicts. When choosing a name, be creative and avoid names that reuse almost all the same letters in the same order or sound like the original. It will help everyone if Original Versions and Modified Versions can easily be distinguished from one another and from other derivatives. Any substitution and matching mechanism is outside the scope of the license.
 5.3  What do you mean by "primary name as presented to the user"? Are you referring to the font menu name?
 Yes, this applies to the font menu name and other mechanisms that specify a font in a document. It would be fine, however, to keep a text reference to the original fonts in the description field, in your modified source file or in documentation provided alongside your derivative as long as no one could be confused that your modified source is the original. But you cannot use the Reserved Font Names in any way to identify the font to the user (unless the Copyright Holder(s) allow(s) it through a separate agreement). Users who install derivatives (Modified Versions) on their systems should not see any of the original Reserved Font Names in their font menus, for example. Again, this is to ensure that users are not confused and do not mistake one font for another and so expect features only another derivative or the Original Version can actually offer. 
 5.4  Am I not allowed to use any part of the Reserved Font Names?
 You may not use individual words from the Reserved Font Names, but you would be allowed to use parts of words, as long as you do not use any word from the Reserved Font Names entirely. We do not recommend using parts of words because of potential confusion, but it is allowed. For example, if "Foobar" was a Reserved Font Name, you would be allowed to use "Foo" or "bar", although we would not recommend it. Such an unfortunate choice would confuse the users of your fonts as well as make it harder for other designers to contribute.
 5.5  So what should I, as an author, identify as Reserved Font Names?
 Original authors are encouraged to name their fonts using clear, distinct names, and only declare the unique parts of the name as Reserved Font Names. For example, the author of a font called "Foobar Sans" would declare "Foobar" as a Reserved Font Name, but not "Sans", as that is a common typographical term, and may be a useful word to use in a derivative font name. Reserved Font Names should also be single words for simplicity and legibility. A font called "Flowing River" should have Reserved Font Names "Flowing" and "River", not "Flowing River". You also need to be very careful about reserving font names which are already linked to trademarks (whether registered or not) which you do not own.
 5.6  Do I, as an author, have to identify any Reserved Font Names?
 No. RFNs are optional and not required, but we encourage you to use them. This is primarily to avoid confusion between your work and Modified Versions. As an author you can release a font under the OFL and not declare any Reserved Font Names. There may be situations where you find that using no RFNs and letting your font be changed and modified - including any kind of modification - without having to change the original name is desirable. However you need to be fully aware of the consequences. There will be no direct way for end-users and other designers to distinguish your Original Version from many Modified Versions that may be created. You have to trust whoever is making the changes and the optimizations to not introduce problematic changes. The RFNs you choose for your own creation have value to you as an author because they allow you to maintain artistic integrity and keep some control over the distribution channel to your end-users. For discussion of RFNs and web fonts see section 2.
 5.7  Are any names (such as the main font name) reserved by default?
 No. That is a change to the license as of version 1.1. If you want any names to be Reserved Font Names, they must be specified after the copyright statement(s).
 5.8  Is there any situation in which I can use Reserved Font Names for a Modified Version?
 The Copyright Holder(s) can give certain trusted parties the right to use any of the Reserved Font Names through separate written agreements. For example, even if "Foobar" is a RFN, you could write up an agreement to give company "XYZ" the right to distribute a modified version with a name that includes "Foobar". This allows for freedom without confusion. The existence of such an agreement should be made as clear as possible to downstream users and designers in the distribution package and the relevant documentation. They need to know if they are a party to the agreement or not and what they are practically allowed to do or not even if all the details of the agreement are not public.
 5.9  Do font rebuilds require a name change? Do I have to change the name of the font when my packaging workflow includes a full rebuild from source?
 Yes, all rebuilds which change the font data and the smart code are Modified Versions and the requirements of the OFL apply: you need to respect what the Author(s) have chosen in terms of Reserved Font Names. However if a package (or installer) is simply a wrapper or a compressed structure around the final font - leaving them intact on the inside - then no name change is required. Please get in touch with the author(s) and copyright holder(s) to inquire about the presence of font sources beyond the final font file(s) and the recommended build path. That build path may very well be non-trivial and hard to reproduce accurately by the maintainer. If a full font build path is made available by the upstream author(s) please be aware that any regressions and changes you may introduce when doing a rebuild for packaging purposes is your own responsibility as a package maintainer since you are effectively creating a separate branch. You should make it very clear to your users that your rebuilt version is not the canonical one from upstream.
 5.10  Can I add other Reserved Font Names when making a derivative font?
 Yes. List your additional Reserved Font Names after your additional copyright statement, as indicated with example placeholders at the top of the OFL.txt file. Be sure you do not remove any existing RFNs but only add your own. RFN statements should be placed next to the copyright statement of the relevant author as indicated in the OFL.txt template to make them visible to designers wishing to make their separate version.
 6  ABOUT THE FONTLOG
 6.1  What is this FONTLOG thing exactly?
 It has three purposes: 1) to provide basic information on the font to users and other designers and developers, 2) to document changes that have been made to the font or accompanying files, either by the original authors or others, and 3) to provide a place to acknowledge authors and other contributors. Please use it!
 6.2  Is the FONTLOG required?
 It is not a requirement of the license, but we strongly recommend you have one.
 6.3  Am I required to update the FONTLOG when making Modified Versions?
 No, but users, designers and other developers might get very frustrated with you if you don't. People need to know how derivative fonts differ from the original, and how to take advantage of the changes, or build on them. There are utilities that can help create and maintain a FONTLOG, such as the FONTLOG support in FontForge.
 6.4  What should the FONTLOG look like?
 It is typically a separate text file (FONTLOG.txt), but can take other formats. It commonly includes these four sections:
 - brief header describing the FONTLOG itself and name of the font family
 - Basic Font Information - description of the font family, purpose and breadth
 - ChangeLog - chronological listing of changes
 - Acknowledgements - list of authors and contributors with contact information
 It could also include other sections, such as: where to find documentation, how to make contributions, information on contributing organizations, source code details, and a short design guide. See Appendix A for an example FONTLOG.
 7  MAKING CONTRIBUTIONS TO OFL PROJECTS
 7.1  Can I contribute work to OFL projects?
 In many cases, yes. It is common for OFL fonts to be developed by a team of people who welcome contributions from the wider community. Contact the original authors for specific information on how to participate in their projects.
 7.2  Why should I contribute my changes back to the original authors?
 It would benefit many people if you contributed back in response to what you've received. Your contributions and improvements to the fonts and other components could be a tremendous help and would encourage others to contribute as well and 'give back'. You will then benefit from other people's contributions as well. Sometimes maintaining your own separate version takes more effort than merging back with the original. Be aware that any contributions, however, must be either your own original creation or work that you own, and you may be asked to affirm that clearly when you contribute.
 7.3  I've made some very nice improvements to the font. Will you consider adopting them and putting them into future Original Versions?
 Most authors would be very happy to receive such contributions. Keep in mind that it is unlikely that they would want to incorporate major changes that would require additional work on their end. Any contributions would likely need to be made for all the fonts in a family and match the overall design and style. Authors are encouraged to include a guide to the design with the fonts. It would also help to have contributions submitted as patches or clearly marked changes - the use of smart source revision control systems like subversion, mercurial, git or bzr is a good idea. Please follow the recommendations given by the author(s) in terms of preferred source formats and configuration parameters for sending contributions. If this is not indicated in a FONTLOG or other documentation of the font, consider asking them directly. Examples of useful contributions are bug fixes, additional glyphs, stylistic alternates (and the smart font code to access them) or improved hinting. Keep in mind that some kinds of changes (esp. hinting) may be technically difficult to integrate.
 7.4  How can I financially support the development of OFL fonts?
 It is likely that most authors of OFL fonts would accept financial contributions - contact them for instructions on how to do this. Such contributions would support future development. You can also pay for others to enhance the fonts and contribute the results back to the original authors for inclusion in the Original Version.
 8  ABOUT THE LICENSE ITSELF
 8.1  I see that this is version 1.1 of the license. Will there be later changes?
 Version 1.1 is the first minor revision of the OFL. We are confident that version 1.1 will meet most needs, but are open to future improvements. Any revisions would be for future font releases, and previously existing licenses would remain in effect. No retroactive changes are possible, although the Copyright Holder(s) can re-release the font under a revised OFL. All versions will be available on our web site: http://scripts.sil.org/OFL.
 8.2  Does this license restrict the rights of the Copyright Holder(s)?
 No. The Copyright Holder(s) still retain(s) all the rights to their creation; they are only releasing a portion of it for use in a specific way. For example, the Copyright Holder(s) may choose to release a 'basic' version of their font under the OFL, but sell a restricted 'enhanced' version. Only the Copyright Holder(s) can do this.
 8.3  Is the OFL a contract or a license?
 The OFL is a license and not a contract and so does not require you to sign it to have legal validity. By using, modifying and redistributing components under the OFL you indicate that you accept the license.
 8.4  I really like the terms of the OFL, but want to change it a little. Am I allowed to take ideas and actual wording from the OFL and put them into my own custom license for distributing my fonts?
 We strongly recommend against creating your very own unique open licensing model. Using a modified or derivative license will likely cut you off - along with the font(s) under that license - from the community of designers using the OFL, potentially expose you and your users to legal liabilities, and possibly put your work and rights at risk. The OFL went though a community and legal review process that took years of effort, and that review is only applicable to an unmodified OFL. The text of the OFL has been written by SIL (with review and consultation from the community) and is copyright (c) 2005-2013 SIL International. You may re-use the ideas and wording (in part, not in whole) in another non-proprietary license provided that you call your license by another unambiguous name, that you do not use the preamble, that you do not mention SIL and that you clearly present your license as different from the OFL so as not to cause confusion by being too similar to the original. If you feel the OFL does not meet your needs for an open license, please contact us.
 8.5  Can I translate the license and the FAQ into other languages?
 SIL certainly recognises the need for people who are not familiar with English to be able to understand the OFL and its use. Making the license very clear and readable has been a key goal for the OFL, but we know that people understand their own language best.
 If you are an experienced translator, you are very welcome to translate the OFL and OFL-FAQ so that designers and users in your language community can understand the license better. But only the original English version of the license has legal value and has been approved by the community. Translations do not count as legal substitutes and should only serve as a way to explain the original license. SIL - as the author and steward of the license for the community at large - does not approve any translation of the OFL as legally valid because even small translation ambiguities could be abused and create problems.
 SIL gives permission to publish unofficial translations into other languages provided that they comply with the following guidelines:
 - Put the following disclaimer in both English and the target language stating clearly that the translation is unofficial:
 "This is an unofficial translation of the SIL Open Font License into <language_name>. It was not published by SIL International, and does not legally state the distribution terms for fonts that use the OFL. A release under the OFL is only valid when using the original English text. However, we recognize that this unofficial translation will help users and designers not familiar with English to better understand and use the OFL. We encourage designers who consider releasing their creation under the OFL to read the OFL-FAQ in their own language if it is available. Please go to http://scripts.sil.org/OFL for the official version of the license and the accompanying OFL-FAQ."
 - Keep your unofficial translation current and update it at our request if needed, for example if there is any ambiguity which could lead to confusion.  
 If you start such a unofficial translation effort of the OFL and OFL-FAQ please let us know.
 9  ABOUT SIL INTERNATIONAL
 9.1  Who is SIL International and what do they do?
 SIL serves language communities worldwide, building their capacity for sustainable language development, by means of research, translation, training and materials development. SIL makes its services available to all without regard to religious belief, political ideology, gender, race, or ethnic background. SIL's members and volunteers share a Christian commitment.
 9.2  What does this have to do with font licensing?
 The ability to read, write, type and publish in one's own language is one of the most critical needs for millions of people around the world. This requires fonts that are widely available and support lesser-known languages. SIL develops - and encourages others to develop - a complete stack of writing systems implementation components available under open licenses. This open stack includes input methods, smart fonts, smart rendering libraries and smart applications. There has been a need for a common open license that is specifically applicable to fonts and related software (a crucial component of this stack), so SIL developed the SIL Open Font License with the help of the Free/Libre and Open Source Software community.
 9.3  How can I contact SIL?
 Our main web site is: http://www.sil.org/
 Our site about complex scripts is: http://scripts.sil.org/
 Information about this license (and contact information) is at: http://scripts.sil.org/OFL
 APPENDIX A - FONTLOG EXAMPLE
 Here is an example of the recommended format for a FONTLOG, although other formats are allowed.
 -----
 FONTLOG for the GlobalFontFamily fonts
 This file provides detailed information on the GlobalFontFamily Font Software. This information should be distributed along with the GlobalFontFamily fonts and any derivative works.
 Basic Font Information
 GlobalFontFamily is a Unicode typeface family that supports all languages that use the Latin script and its variants, and could be expanded to support other scripts.
 NewWorldFontFamily is based on the GlobalFontFamily and also supports Greek, Hebrew, Cyrillic and Armenian.
 More specifically, this release supports the following Unicode ranges...
 This release contains...
 Documentation can be found at...
 To contribute to the project...
 ChangeLog
 10 December 2010 (Fred Foobar) GlobalFontFamily-devel version 1.4
 - fix new build and testing system (bug #123456)
 1 August 2008 (Tom Parker) GlobalFontFamily version 1.2.1
 - Tweaked the smart font code (Branch merged with trunk version)
 - Provided improved build and debugging environment for smart behaviours
 7 February 2007 (Pat Johnson) NewWorldFontFamily Version 1.3
 - Added Greek and Cyrillic glyphs
 7 March 2006 (Fred Foobar) NewWorldFontFamily Version 1.2
 - Tweaked contextual behaviours
 1 Feb 2005 (Jane Doe) NewWorldFontFamily Version 1.1
 - Improved build script performance and verbosity
 - Extended the smart code documentation
 - Corrected minor typos in the documentation
 - Fixed position of combining inverted breve below (U+032F)
 - Added OpenType/Graphite smart code for Armenian
 - Added Armenian glyphs (U+0531 -> U+0587) 
 - Released as "NewWorldFontFamily"
 1 Jan 2005 (Joe Smith) GlobalFontFamily Version 1.0
 - Initial release
 Acknowledgements
 If you make modifications be sure to add your name (N), email (E), web-address (if you have one) (W) and description (D). This list is in alphabetical order.
 N: Jane Doe
 E: jane@university.edu
 W: http://art.university.edu/projects/fonts
 D: Contributor - Armenian glyphs and code
 N: Fred Foobar
 E: fred@foobar.org
 W: http://foobar.org
 D: Contributor - misc Graphite fixes
 N: Pat Johnson
 E: pat@fontstudio.org
 W: http://pat.fontstudio.org
 D: Designer - Greek & Cyrillic glyphs based on Roman design
 N: Tom Parker
 E: tom@company.com
 W: http://www.company.com/tom/projects/fonts
 D: Engineer - original smart font code
 N: Joe Smith
 E: joe@fontstudio.org
 W: http://joe.fontstudio.org
 D: Designer - original Roman glyphs
 Fontstudio.org is an not-for-profit design group whose purpose is...
 Foobar.org is a distributed community of developers...
 Company.com is a small business who likes to support community designers...
 University.edu is a renowned educational institution with a strong design department...
 -----
--- a/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-Bold.otf
+++ b/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-Bold.otf
--- a/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-BoldItalic.otf
+++ b/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-BoldItalic.otf
--- a/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-Book.otf
+++ b/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-Book.otf
--- a/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-BookItalic.otf
+++ b/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-BookItalic.otf
--- a/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-Heavy.otf
+++ b/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-Heavy.otf
--- a/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-HeavyItalic.otf
+++ b/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-HeavyItalic.otf
--- a/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-Light.otf
+++ b/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-Light.otf
--- a/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-LightItalic.otf
+++ b/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-LightItalic.otf
--- a/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-Medium.otf
+++ b/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-Medium.otf
--- a/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-MediumItalic.otf
+++ b/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-MediumItalic.otf
--- a/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-Semibold.otf
+++ b/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-Semibold.otf
--- a/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-SemiboldItalic.otf
+++ b/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-SemiboldItalic.otf
--- a/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-Thin.otf
+++ b/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-Thin.otf
--- a/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-ThinItalic.otf
+++ b/themes/varia/static/fonts/cooper-hewitt/CooperHewitt-ThinItalic.otf
--- a/themes/varia/static/js/stars.js
+++ b/themes/varia/static/js/stars.js
@ -1,27 +0,0 @@
 // stars.js
 // Random Stars
 var generateStars = function(){
    var $galaxy = $(".galaxy");
    var iterator = 0;
    while (iterator <= 100){
        var xposition = Math.random();
        var yposition = Math.random();
        var star_type = Math.floor((Math.random() * 3) + 1);
        var position = {
            "x" : $galaxy.width() * xposition,
            "y" : $galaxy.height() * yposition,
        };
        $('<div class="star star-type' + star_type + '"></div>').appendTo($galaxy).css({
            "top" : position.y,
            "left" : position.x
        });
        iterator++;
    }
 };
 generateStars();
--- a/themes/varia/templates/archives.html
+++ b/themes/varia/templates/archives.html
@ -1,4 +1,7 @@
 {% extends "base.html" %}
 {% block title %}{{ SITENAME }} - Archives{% endblock %}
 {% block content %}
 <h1>Archives for {{ SITENAME }}</h1>
--- a/themes/varia/templates/article.html
+++ b/themes/varia/templates/article.html
@ -1,116 +1,67 @@
 {% extends "base.html" %}
 {% block html_lang %}{{ article.lang }}{% endblock %}
-{% block head %}
+{% block title %}{{ SITENAME }} - {{ article.title }}{% endblock %}
 {{ super() }}
 {% if article.description %}
 <meta name="description" content="{{article.description}}" />
 {% endif %}
-{% if article.tags or article.category or article.keywords %}
+{% block head %}
-<meta name="keywords" content="{{ [article.tags|join(', '), article.category, article.keywords]|join(', ') }}" />
+  {{ super() }}
 {% endif %}
 {% endblock %}
-{% block content %}
+  {% import 'translations.html' as translations with context %}
-<header id="banner">
+  {% if translations.entry_hreflang(article) %}
-    {% for p in pages %}
+    {{ translations.entry_hreflang(article) }}
        {% if p.title == 'header' %}
            <div id="title">{{ p.content }}</div>
  {% endif %}
    {% endfor %}
 </header>
-{% set glob={} %}
+  {% if article.description %}
-{% if article.translations %}
+    <meta name="description" content="{{article.description}}" />
 	{% for translation in article.translations %}
 		{% if translation.lang == 'nl' %}
 			{% set _ = glob.update({'published_at': 'Published at '}) %}
 			{% set _ = glob.update({'translate_article': 'Lees dit artikel in het Nederlands'}) %}
 			{% set _ = glob.update({'related_to': ' relating to '}) %}
 			{% set _ = glob.update({'translation_url': translation.url}) %}
 			{% set _ = glob.update({'written_by': 'Written by '}) %}
 		{% endif %}
 		{% if translation.lang == 'en' %}
 			{% set _ = glob.update({'published_at': 'Gepubliceerd op '}) %}
 			{% set _ = glob.update({'translate_article': 'Read this article in English'}) %}
 			{% set _ = glob.update({'related_to': ' gerelateerd aan '}) %}
 			{% set _ = glob.update({'translation_url': translation.url}) %}
 			{% set _ = glob.update({'written_by': 'Geschreven door '}) %}
  {% endif %}
  {% for tag in article.tags %}
    <meta name="tags" content="{{tag}}" />
  {% endfor %}
 {% endif %}
 {% endblock %}
-<section id="content" class="body h-entry">
+{% block content %}
-	<div class="entry-title p-name">
+<section id="content" class="body">
-		{{ article.title }}
+  <header>
-	</div>
+    <h2 class="entry-title">
-	<div class="article-info">
+      <a href="{{ SITEURL }}/{{ article.url }}" rel="bookmark"
-		<div class="featured-image u-photo">
+         title="Permalink to {{ article.title|striptags }}">{{ article.title }}</a></h2>
-            {% if article.featured_image %}
+ {% import 'translations.html' as translations with context %}
-	            {% set thumb_size ='/thumb'%}
+ {{ translations.translations_for(article) }}
-	            <a href="{{ article.featured_image }}">
+  </header>
-	            {% if article.featured_image.endswith('.gif') %}
+  <footer class="post-info">
-	                {% set thumb_size =''%}
+    <time class="published" datetime="{{ article.date.isoformat() }}">
-	            {% endif %}
+      {{ article.locale_date }}
-	            <img src="{{ article.featured_image | replace('images','images'+thumb_size) }}">
+    </time>
-	            </a>
+    {% if article.modified %}
-            {% endif %}
+    <time class="modified" datetime="{{ article.modified.isoformat() }}">
-		</div>
+      {{ article.locale_modified }}
-		<div class="event-details">
+    </time>
 			{% if article.event_start %}
 				<div class="article-event-start">{{ article.event_start }}</div>
    {% endif %}
-			<div>{{ glob.published_at }} {{ article.date | strftime('%d %B %Y') }}</div>	
+    {% if article.authors %}
-		</div>
+    <address class="vcard author">
-		<div class="post-info">
+      By {% for author in article.authors %}
-			<div class="article-authors">
+          <a class="url fn" href="{{ SITEURL }}/{{ author.url }}">{{ author }}</a>
-				{% if article.author %}
+        {% endfor %}
-					{{ glob.written_by }} 
+    </address>
 					{{ article.author }}
    {% endif %}
 			</div>
 			<a style="visibility:hidden;" rel="author" class="p-author h-card">{{ article.author }}</a>
 			<time class="dt-published" datetime="{{ article.date }}"></time>
 			<a class="u-url" href="{{ article.url }}"></a>
    {% if article.category %}
-			<span class="categories">
+    <div class="category">
-				<span itemprop="articleSection">
+        Category: <a href="{{ SITEURL }}/{{ article.category.url }}">{{ article.category }}</a>
-					<a href="/category{{ article.category.url }}" rel="category">{{ article.category }}</a>
+    </div>
 				</span>
 			</span>
    {% endif %}
    {% if article.tags %}
-	            <span class="tags">
+    <div class="tags">
-	                {{ glob.related_to }} 
+        Tags:
        {% for tag in article.tags %}
-		                <span itemprop="keywords">
+            <a href="{{ SITEURL }}/{{ tag.url }}">{{ tag }}</a>
 		                    <a href="/{{ tag.url }}" rel="tag">{{ tag }}</a>
 		                </span> 
        {% endfor %}
 	            </span>
            {% endif %}
 			<div class="article-translation">
 				<a href="{{ glob.translation_url }}">{{ glob.translate_article }}</a>
 			</div>
    </div>
-	</div>
+    {% endif %}
-<div class="entry-content-container">
+  </footer><!-- /.post-info -->
-	<div class="entry-content e-content">
+  <div class="entry-content">
    {{ article.content }}
 	<div class="separator"><hr></div>
  </div><!-- /.entry-content -->
 </div><!-- /.entry-content-container -->
 </section>
 <script type="text/javascript">
 	var footnotes = document.querySelectorAll('[id^="fnref-"]');
 	for(var i in footnotes){
 		if(i < footnotes.length){
 			console.log(footnotes[i]);
 			var id = footnotes[i].id.replace('fnref-','fn-');
 		footnotes[i].innerHTML = footnotes[i].innerHTML + '<span>['+ parseInt(Number(i)+1) + '] '+ document.getElementById(id).innerHTML +'</span>';
 		}
 	}
 	document.getElementsByClassName('footnote')[0].remove();
 </script>
 {% endblock %}
--- a/themes/varia/templates/author.html
+++ b/themes/varia/templates/author.html
@ -1,6 +1,7 @@
 {% extends "index.html" %}
 {% block title %}{{ SITENAME }} - Articles by {{ author }}{% endblock %}
 {% block content_title %}
 <h2>Articles by {{ author }}</h2>
 {% endblock %}
--- a/themes/varia/templates/authors.html
+++ b/themes/varia/templates/authors.html
@ -4,9 +4,8 @@
 {% block content %}
    <h1>Authors on {{ SITENAME }}</h1>
    <ul>
-    {%- for author, articles in authors|sort %}
+    {% for author, articles in authors|sort %}
        <li><a href="{{ SITEURL }}/{{ author.url }}">{{ author }}</a> ({{ articles|count }})</li>
    {% endfor %}
    </ul>
--- a/themes/varia/templates/base.html
+++ b/themes/varia/templates/base.html
@ -1,50 +1,62 @@
 <!DOCTYPE html>
-<html lang="{{ DEFAULT_LANG }}">
+<html lang="{% block html_lang %}{{ DEFAULT_LANG }}{% endblock html_lang %}">
 <head>
-{% block head %}
+        {% block head %}
-<title>{% block title %}{{ SITENAME }} {{SITESUBTITLE}}{% endblock title %}</title>
+        <title>{% block title %}{{ SITENAME }}{% endblock title %}</title>
-<meta charset="utf-8" />
+        <meta charset="utf-8" />
-<link rel="icon" href="{{ SITEURL}}/favicon.ico" type="image/x-icon">
+        {% if FEED_ALL_ATOM %}
-<link rel="shortcut icon" href="{{ SITEURL }}/favicon.ico" type="image/x-icon"> 
+        <link href="{{ FEED_DOMAIN }}/{% if FEED_ALL_ATOM_URL %}{{ FEED_ALL_ATOM_URL }}{% else %}{{ FEED_ALL_ATOM }}{% endif %}" type="application/atom+xml" rel="alternate" title="{{ SITENAME }} Full Atom Feed" />
-{% from 'syndication.html' import syndication with context %}
+        {% endif %}
-{{ syndication(article) }}
+        {% if FEED_ALL_RSS %}
-<link rel="stylesheet" type="text/css" href="/{{ THEME_STATIC_DIR }}css/pygment.css" />
+        <link href="{{ FEED_DOMAIN }}/{% if FEED_ALL_RSS_URL %}{{ FEED_ALL_RSS_URL }}{% else %}{{ FEED_ALL_RSS }}{% endif %}" type="application/rss+xml" rel="alternate" title="{{ SITENAME }} Full RSS Feed" />
-<link rel="stylesheet" type="text/css" href="/{{ THEME_STATIC_DIR }}css/{{ CSS_FILE }}" />
+        {% endif %}
-{% endblock head %}
+        {% if FEED_ATOM %}
        <link href="{{ FEED_DOMAIN }}/{%if FEED_ATOM_URL %}{{ FEED_ATOM_URL }}{% else %}{{ FEED_ATOM }}{% endif %}" type="application/atom+xml" rel="alternate" title="{{ SITENAME }} Atom Feed" />
        {% endif %}
        {% if FEED_RSS %}
        <link href="{{ FEED_DOMAIN }}/{% if FEED_RSS_URL %}{{ FEED_RSS_URL }}{% else %}{{ FEED_RSS }}{% endif %}" type="application/rss+xml" rel="alternate" title="{{ SITENAME }} RSS Feed" />
        {% endif %}
        {% if CATEGORY_FEED_ATOM and category %}
        <link href="{{ FEED_DOMAIN }}/{% if CATEGORY_FEED_ATOM_URL %}{{ CATEGORY_FEED_ATOM_URL|format(category.slug) }}{% else %}{{ CATEGORY_FEED_ATOM|format(category.slug) }}{% endif %}" type="application/atom+xml" rel="alternate" title="{{ SITENAME }} Categories Atom Feed" />
        {% endif %}
        {% if CATEGORY_FEED_RSS and category %}
        <link href="{{ FEED_DOMAIN }}/{% if CATEGORY_FEED_RSS_URL %}{{ CATEGORY_FEED_RSS_URL|format(category.slug) }}{% else %}{{ CATEGORY_FEED_RSS|format(category.slug) }}{% endif %}" type="application/rss+xml" rel="alternate" title="{{ SITENAME }} Categories RSS Feed" />
        {% endif %}
        {% if TAG_FEED_ATOM and tag %}
        <link href="{{ FEED_DOMAIN }}/{% if TAG_FEED_ATOM_URL %}{{ TAG_FEED_ATOM_URL|format(tag.slug) }}{% else %}{{ TAG_FEED_ATOM|format(tag.slug) }}{% endif %}" type="application/atom+xml" rel="alternate" title="{{ SITENAME }} Tags Atom Feed" />
        {% endif %}
        {% if TAG_FEED_RSS and tag %}
        <link href="{{ FEED_DOMAIN }}/{% if TAG_FEED_RSS_URL %}{{ TAG_FEED_RSS_URL|format(tag.slug) }}{% else %}{{ TAG_FEED_RSS|format(tag.slug) }}{% endif %}" type="application/rss+xml" rel="alternate" title="{{ SITENAME }} Tags RSS Feed" />
        {% endif %}
        {% endblock head %}
 </head>
 <body id="index" class="home">
-    <div class="buttons top">
+        <header id="banner" class="body">
-    {% if I18N_SUBSITES %}
+                <h1><a href="{{ SITEURL }}/">{{ SITENAME }} <strong>{{ SITESUBTITLE }}</strong></a></h1>
-        {% for lang, url in I18N_SUBSITES.items() %}
+        </header><!-- /#banner -->
-            {% if DEFAULT_LANG == 'nl' %}
+        <nav id="menu"><ul>
-                {% if lang == 'nl' %}
+        {% for title, link in MENUITEMS %}
-                    <li><em>varia</em> kent de volgende gedaantes: </li>
+            <li><a href="{{ link }}">{{ title }}</a></li>
-                    <li><a href="https://we.lurk.org/postorius/lists/varia.we.lurk.org/" target="_blank"><i class="fa fa-rss "></i>mailinglijst </a></li>
+        {% endfor %}
-                    <li><a href="feeds/all-{{ DEFAULT_LANG }}.rss.xml" type="application/rss+xml"><i class="fa fa-rss "></i>RSS feed </a></li>
+        {% if DISPLAY_PAGES_ON_MENU %}
-                    <!-- <li><a href="#"><i class="fa fa-rss "></i>.ics kalendar</a></li> -->
+          {% for p in pages %}
-                <li {% if DEFAULT_LANG == 'nl' %} class="active"><a href="/">Nederlands</a>{% else %}><a href="/">Nederlands</a>{% endif %}</li>
+            <li{% if p == page %} class="active"{% endif %}><a href="{{ SITEURL }}/{{ p.url }}">{{ p.title }}</a></li>
-                <li{% if DEFAULT_LANG == 'en' %} class="active"><a href="/en/">English</a>{% else %}><a href="/en/">English</a>{% endif %}</li>
+          {% endfor %}
             {% endif %}
            {% endif %}
            {% if DEFAULT_LANG == 'en' %}
                {% if lang == 'en' %}
                    <li><em>varia</em> comes in many forms: </li>
                    <li><a href="https://we.lurk.org/postorius/lists/varia.we.lurk.org/" target="_blank"><i class="fa fa-rss "></i>mailinglist </a></li>
                    <li><a href="feeds/all-{{ DEFAULT_LANG }}.rss.xml" type="application/rss+xml"><i class="fa fa-rss "></i>RSS feed </a></li>
                    <!-- <li><a href="#"><i class="fa fa-rss "></i>.ics calendar</a></li> -->
                <li {% if DEFAULT_LANG == 'nl' %} class="active"><a href="/">Nederlands</a>{% else %}><a href="/">Nederlands</a>{% endif %}</li>
                <li{% if DEFAULT_LANG == 'en' %} class="active"><a href="/{{lang}}">English</a>{% else %}><a href="/{{lang}}">English</a>{% endif %}</li>
                {% endif %}
        {% endif %}
        {% if DISPLAY_CATEGORIES_ON_MENU %}
          {% for cat, null in categories %}
            <li{% if cat == category %} class="active"{% endif %}><a href="{{ SITEURL }}/{{ cat.url }}">{{ cat }}</a></li>
          {% endfor %}
        {% endif %}
-        <br>
+        </ul></nav><!-- /#menu -->
    </div>
    <div class="buttons top">
    </div>
        {% block content %}
        {% endblock %}
        <footer id="contentinfo" class="body">
                <address id="about" class="vcard body">
                Proudly powered by <a href="http://getpelican.com/">Pelican</a>,
                which takes great advantage of <a href="http://python.org">Python</a>.
                </address><!-- /#about -->
        </footer><!-- /#contentinfo -->
 </body>
 </html>
--- a/themes/varia/templates/base.varia.html
+++ b/themes/varia/templates/base.varia.html
@ -0,0 +1,16 @@
 <!DOCTYPE html>
 <html lang="{{ DEFAULT_LANG }}">
 <head>
 {% block head %}
 <title>{% block title %}{{ SITENAME }} {{SITESUBTITLE}}{% endblock title %}</title>
 <meta charset="utf-8" />
 <link rel="icon" href="{{ SITEURL }}/favicon.ico" type="image/x-icon">
 <link rel="stylesheet" type="text/css" href="{{ THEME_STATIC_DIR }}/css/stylesheet.css">
 {% endblock %}
 </head>
 <body id="index" class="home">
 	{% block content %}
 	{% endblock %}
 </body>
 </html>
--- a/themes/varia/templates/categories.html
+++ b/themes/varia/templates/categories.html
@ -1,8 +1,12 @@
 {% extends "base.html" %}
 {% block title %}{{ SITENAME }} - Categories{% endblock %}
 {% block content %}
-<div id="categories">
+    <h1>Categories on {{ SITENAME }}</h1>
-{% for category, articles in categories %}
+    <ul>
-    <a href="{{ SITEURL }}/{{ category.url }}">{{ category }}</a>
+    {% for category, articles in categories|sort %}
-{% endfor %}
+        <li><a href="{{ SITEURL }}/{{ category.url }}">{{ category }}</a> ({{ articles|count }})</li>
-</div>
+    {% endfor %}
    </ul>
 {% endblock %}
--- a/themes/varia/templates/category.html
+++ b/themes/varia/templates/category.html
@ -1,6 +1,8 @@
 {% extends "index.html" %}
 {% block title %}{{ SITENAME }} - {{ category }} category{% endblock %}
 {% block content_title %}
-<h1>Category: {{ category }}</h1>
+<h2>Articles in the {{ category }} category</h2>
 <hr>
 {% endblock %}
--- a/themes/varia/templates/events_list.html
+++ b/themes/varia/templates/events_list.html
@ -1,36 +0,0 @@
 {% extends "base.html" %}
 {% block title %} Events list - {{ SITENAME }}{% endblock %}
 {% block content %}
    {% if events_list %}
    <ul class="post-list">
    {% for evstart, evend, event in events_list %}
      <li>
        <p>
          <a href="../{{event.slug}}.html">
            <b>{{event['title']}}</b>
          </a>
        </p>
        <p>
        {% if evstart.date() == evend.date() %}
        From {{evstart}} to {{evend.time()}}
        {% else %}
        From {{evstart}} to {{evend}}
        {% endif %}
        </p>
        {% if event.location %}
        <p>Location: {{event.location}}</p>
        {% endif %}
        <p>{{event['summary']}}</p>
      </li>
    {% endfor %}
    </ul>
    {% endif %}
 {% endblock %}
--- a/themes/varia/templates/index.html
+++ b/themes/varia/templates/index.html
@ -1,111 +1,28 @@
 {% extends "base.html" %}
 {% block content %}
-<section id="content" class="index">
+<section id="content">
 <header id="banner">
    {% for p in pages %}
        {% if p.title == 'header' %}
            <div id="title">
                {{ p.content }}
            </div>      
        {% endif %}
    {% endfor %}
 </header>
 {% set glob={} %}
 {% if DEFAULT_LANG == 'nl' %}
    {% set _ = glob.update({'published_at': 'Gepubliceerd op '}) %}
    {% set _ = glob.update({'related_to': ' gerelateerd aan '}) %}
    {% set _ = glob.update({'written_by': 'Geschreven door '}) %}
    {% set _ = glob.update({'read_more': 'lees meer '}) %}
 {% endif %}
 {% if DEFAULT_LANG == 'en' %}
    {% set _ = glob.update({'published_at': 'Published at '}) %}
    {% set _ = glob.update({'related_to': ' relating to '}) %}
    {% set _ = glob.update({'written_by': 'Written by '}) %}
    {% set _ = glob.update({'read_more': 'read more'}) %}
 {% endif %}
 {% block content_title %}
 <h2>All articles</h2>
 {% endblock %}
 <ol id="post-list">
 {% for article in articles_page.object_list %}
        <li><article class="hentry">
                <header> <h2 class="entry-title"><a href="{{ SITEURL }}/{{ article.url }}" rel="bookmark" title="Permalink to {{ article.title|striptags }}">{{ article.title }}</a></h2> </header>
                <footer class="post-info">
                    <time class="published" datetime="{{ article.date.isoformat() }}"> {{ article.locale_date }} </time>
                    <address class="vcard author">By
                    {% for author in article.authors %}
                        <a class="url fn" href="{{ SITEURL }}/{{ author.url }}">{{ author }}</a>
                    {% endfor %}
                    </address>
                </footer><!-- /.post-info -->
                <div class="entry-content"> {{ article.summary }} </div><!-- /.entry-content -->
        </article></li>
 {% endfor %}
 </ol><!-- /#posts-list -->
 {% if articles_page.has_other_pages() %}
    {% include 'pagination.html' %}
 {% endif %}
 <div id="post-list">
 {% for article in articles_page.object_list %}
    {% set thumb_size = '/thumb' %}
    {% if article.category %}       
        {% if article.event_start %}
            {% set event_status = '' %}
            {% if article.event_start < article.date.now() %}
                {% set event_status = ' past' %}
            {% endif %}
            {% if article.event_start >= article.date.now() %}
                {% set event_status = ' current' %}
                {% set thumb_size = '/thumb2x' %}
            {% endif %}    
            {% if article.category == 'article' %}
                {% set thumb_size = '/thumb2x' %}
            {% endif %}
        {% endif %}
    <article class="hentry {{article.category}}{{event_status}}">
    {% endif %}
        <div class="article-info">
            <span class="entry-title"><a href="/{% if article.lang == 'en' %}en/{% endif %}{{ article.url }}" rel="bookmark" title="Permalink to {{ article.title|striptags }}">{{ article.title }}</a></span>
            {% if article.event_start %}
                <div class="event-details">
                    {{ article.event_start  | strftime('%d %B %Y') }}
                </div>
            {% else %}
                <div class="event-details"></div>
            {% endif %}
            <div class="featured-image {{event_status}}">
                {% if article.featured_image %}
                    <a href="/{% if article.lang == 'en' %}en/{% endif %}{{ article.url }}" rel="bookmark" title="Permalink to {{ article.title|striptags }}">
                        {% if article.featured_image.endswith('.gif') %}
                            {% set thumb_size =''%}
                        {% endif %}
                        <img src="{{ article.featured_image | replace('images','images'+thumb_size) }}">
                    </a>
                {% endif %}
            </div>
        </div>
        <div class="summary {{ article.category }}">{{ article.summary }}
            <span class="read_more">
                {% if DEFAULT_LANG == 'en' %}
                    <a href="/en/{{ article.url }}">{{ glob.read_more }}</a>
                {% elif DEFAULT_LANG == 'nl' %}
                    <a href="/{{ article.url }}">{{ glob.read_more }}</a>
                {% endif %}
            </span>
        </div>
        <div class="separator"><hr></div>
        <div class="post-info">
            {% if article.category %}
                <span class="categories">
                    <span itemprop="articleSection">
                        <a href="/category{{ article.category.url }}" rel="category">{{ article.category }}</a>
                    </span>
                </span>
            {% endif %} 
            {% if article.tags %}
                <span class="tags">
                    {{ glob.related_to }}
                    {% for tag in article.tags %}
                    <span itemprop="keywords">
                        <a href="/{{ tag.url }}" rel="tag">{{ tag }}</a>
                    </span> {% endfor %}
                </span>
            {% endif %}
        </div>
    </article>
 {% endfor %}
 </div><!-- /#posts-list -->
 </section><!-- /#content -->
 {% endblock content %}
--- a/themes/varia/templates/page.html
+++ b/themes/varia/templates/page.html
@ -1,20 +1,22 @@
 {% extends "base.html" %}
-{% block title %}{{ page.title }}{%endblock%}
+{% block html_lang %}{{ page.lang }}{% endblock %}
-{% block content %}
+{% block title %}{{ SITENAME }} - {{ page.title }}{%endblock%}
-<section id="content" class="index">
+
-	<header id="banner">
+{% block head %}
-	{% for p in pages %}
+  {{ super() }}
-		<!-- header -->
+  {% import 'translations.html' as translations with context %}
-	    {% if p.title == 'header' %}
+  {% if translations.entry_hreflang(page) %}
-	        <div id="title">{{ p.content }}</div>
+    {{ translations.entry_hreflang(page) }}
  {% endif %}
 {% endblock %}
 {% block content %}
    <h1>{{ page.title }}</h1>
    {% import 'translations.html' as translations with context %}
    {{ translations.translations_for(page) }}
 	{% endfor %}
 	</header>
 </section>
    <div id="page-content">
    {{ page.content }}
    {% if page.modified %}
@ -22,19 +24,4 @@
        Last updated: {{ page.locale_modified }}
        </p>
    {% endif %}
 		<!-- {% import 'translations.html' as translations with context %} -->
 	    <!-- {{ translations.translations_for(page) }} -->
 		{% for page in pages %}
 			{% if page.slug == 'stream' %}
 				<div id="stream" class="overview">
 			   	{% for img in page.stream %}
 					<a href="https://vvvvvvaria.org/stream/{{ img }}"><div class="container" style="background-image: url(https://vvvvvvaria.org/stream/{{ img }})"></div></a>
 				{% endfor %}
 				</div>
 			{% endif %}
 		{% endfor %}
   </div>
 {% endblock %}
--- a/themes/varia/templates/period_archives.html
+++ b/themes/varia/templates/period_archives.html
@ -1,4 +1,7 @@
 {% extends "base.html" %}
 {% block title %}{{ SITENAME }} - {{ period | reverse | join(' ') }} archives{% endblock %}
 {% block content %}
 <h1>Archives for {{ period | reverse | join(' ') }}</h1>
--- a/themes/varia/templates/stream.html
+++ b/themes/varia/templates/stream.html
@ -1,27 +0,0 @@
 <!-- {% extends "page.html" %}
 {% if page.slug == 'stream' %}
 {% block content %}
 <section id="content" class="index">
 	{{ pages }}
 	<div>streaming...</div>
 	{% for page in pages %}
 		{% if page.slug == 'stream' %}
 			<div id="stream" class="overview">
 		   	{% for img in page.stream %}
 				<div class="container" style="background-image: url(/stream/{{ img }})"></div>
 			{% endfor %}
 			</div>
 		{% endif %}
 	{% endfor %}
 </section>
 {% endblock %}
 {% endif %}
 -->
--- a/themes/varia/templates/syndication.html
+++ b/themes/varia/templates/syndication.html
@ -1,63 +0,0 @@
 {#This template is for syndicating across the fucked up part of the  web. It implements Open Graph and Twitter Card metadata to display links to HBSC well on social media
 # This code is mostly taken from Talha Mansoor's Elegant pelican theme https://github.com/talha131/pelican-elegant
 #}
 {# Thumbnail image to show when homepage is shared on social media. It also
 serves as the default image for posts whose featured_image is not set. #}
 {% if not FEATURED_IMAGE %}
 {% set FEATURED_IMAGE = 'https://varia.zone/images/de_varia.png' %}
 {% else %}
 {% set FEATURED_IMAGE = FEATURED_IMAGE %}
 {% endif %}
 {% macro syndication(article) %}
 {% if article %}
 <meta property="og:title" content="{{ article.title|striptags|e }} {%if article.subtitle %} - {{ article.subtitle|striptags|e }} {% endif %}"/>
 <meta property="og:url" content="{{ SITEURL }}/{{ article.url }}" />
 <meta property="og:description" content="{% if article.summary %}{{article.summary|striptags}}{% endif %}" />
 <meta property="og:site_name" content="{{ SITENAME|striptags|e }}" />
 <meta property="og:article:author" content="{{ article.author }}" />
 {% if article.date %}
 <meta property="og:article:published_time" content="{{ article.date.isoformat() }}" />
 {% endif %}
 {% if article.locale_modified and article.modified %}
 <meta property="" content="{{ article.modified.isoformat() }}" />
 {% endif %}
 <meta name="twitter:card" content="summary_large_image">
 <meta name="twitter:title" content="{{ article.title|striptags|e }} {%if article.subtitle %} - {{ article.subtitle|striptags|e }} {% endif %}">
 <meta name="twitter:description" content="{% if article.summary %}{{article.summary|striptags}}{% endif %}">
 {% if article.featured_image %}
    {% if I18N_SUBSITES %}
    {% for lang, url in I18N_SUBSITES.items() %}
        {% if lang == 'en' %} 
 <meta property="og:image" content="http://varia.zone{{article.featured_image}}" />
 <meta property="og:image:secure_url" content="https://varia.zone{{article.featured_image}}" />
 <meta name="twitter:image" content="https://varia.zone{{article.featured_image}}" >           
        {% endif %}
    {% endfor %}
 {% endif %}
 {% else %}
 {% if FEATURED_IMAGE %}
 <meta property="og:image" content="{{FEATURED_IMAGE}}" />
    <meta name="twitter:image" content="{{FEATURED_IMAGE}}" >
    {% endif %}
 {% endif %}
 {% endif %}
 {% if not article %}
 <meta property="og:title" content="{{ SITENAME|striptags|e }}"/>
 <meta name="twitter:title" content="{{ SITENAME|striptags|e }}">
 <meta name="twitter:card" content="summary" />
 <meta property="og:url" content="{{ SITEURL }}" />
 <meta property="og:description" content="The Center of Everyday Technology is a Rotterdam based initiative that collects, conducts and instigates research into everyday technology.">
 <meta property="twitter:description" content="The Center of Everyday Technology is a Rotterdam based initiative that collects, conducts and instigates research into everyday technology.">
 <meta property="og:site_name" content="{{ SITENAME|striptags|e }}" />
 <meta property="og:article:author" content="{{ AUTHOR }}" />
 {% if FEATURED_IMAGE %}
 <meta property="og:image" content="{{FEATURED_IMAGE}}" />
 <meta name="twitter:image" content="{{FEATURED_IMAGE}}" >
 {% endif %}
 {% endif %}
 {% endmacro %}
--- a/themes/varia/templates/tag.html
+++ b/themes/varia/templates/tag.html
@ -1,2 +1,7 @@
 {% extends "index.html" %}
-{% block title %}{{ SITENAME }} - {{ tag }}{% endblock %}
+
 {% block title %}{{ SITENAME }} - {{ tag }} tag{% endblock %}
 {% block content_title %}
 <h2>Articles tagged with {{ tag }}</h2>
 {% endblock %}
--- a/themes/varia/templates/tags.html
+++ b/themes/varia/templates/tags.html
@ -4,7 +4,9 @@
 {% block content %}
    <h1>Tags for {{ SITENAME }}</h1>
-    {%- for tag, articles in tags|sort %}
+    <ul>
    {% for tag, articles in tags|sort %}
        <li><a href="{{ SITEURL }}/{{ tag.url }}">{{ tag }}</a> ({{ articles|count }})</li>
    {% endfor %}
    </ul>
 {% endblock %}
--- a/themes/varia/templates/translations.html
+++ b/themes/varia/templates/translations.html
@ -1,10 +1,16 @@
 {% macro translations_for(article) %}
 {% if article.translations %}
-	<div id="translation">
+Translations:
-		{% for translation in article.translations %}
+{% for translation in article.translations %}
-			→ <a href="{{ SITEURL }}/{{ translation.url }}">{{ translation.lang }}</a>
+<a href="{{ SITEURL }}/{{ translation.url }}" hreflang="{{ translation.lang }}">{{ translation.lang }}</a>
-		{% endfor %}
+{% endfor %}
 	</div>
 {% endif %}
 {% endmacro %}
 {% macro entry_hreflang(entry) %}
 {% if entry.translations %}
  {% for translation in entry.translations %}
    <link rel="alternate" hreflang="{{ translation.lang }}" href="{{ SITEURL }}/{{ translation.url }}">
  {% endfor %}
 {% endif %}
 {% endmacro %}
	`@ -1 +0,0 @@`
		`Subproject commit 8de8e847ce78e53b62dfdcd7e0e1923614adead5`
	`@ -1 +0,0 @@`
		`Subproject commit 06abd8f6b37abcd6ec58c6d134edd5cd8332a3d2`