zine 0.15.0 → 0.16.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ec6708f393eb728e1c5683a092f37ee2008c41c292105be0587c89045f9b267a
-  data.tar.gz: c33be8fdc0d2b17ea341cd532827493491d41c665ffb21f0505dab21adfeaf27
+  metadata.gz: 1a733c0fc351f0cebc4de9bc02c2960217ec5ff32ddced28ccc8e8ea6b3104b8
+  data.tar.gz: 2d877e8987f3f575da1a128921db7510cd683f9868457d189b622facfe409054
 SHA512:
-  metadata.gz: dd3359cbf10d141396f05ab17489eb44d80ff1bd6830dac029e8469a5d0a7d503d332a4892191f1240cf42813657ad10f90afed54ca19106e679710915196f9f
-  data.tar.gz: 51769bedd049eac1a94a9e94cd4c0114303e847861f7cfb38044269d3aa1f05a538c62cdb3e0289a72f1835247d64236849e36bb33586bf963cc3d4d6f312ec5
+  metadata.gz: 161010777cf556c39c64669e1983fcb25a6114e30c82404d18c1ef5f3bbb45b20a74c3acfb5a5da48b502a7f38c52645f37c86ffbb2e3f0da717625bb2423ef0
+  data.tar.gz: addf78c26a6cd74b1127a2e0a225ca0540f3c3205e03053d2f9f0c164172368987db648651dd8b0c02c86289d84f77cdcc5f28334a7a789a8daff1a7db83e008

data/CHANGELOG.md

@@ -1,76 +1,78 @@
 # Zine Changelog
 
-## Pre 0.0.1
+# 0.16.0 - 17 June, 2022
 
-- set up the blog & repos
-- set up bundler, rspec tests
-- Thor for the menu & as a generator
-- YAML options
-- have a Site object pushing file names to Page objects
-- Kramdown
-- played with cucumber for a while but decided not to use it, it's a DSL too far.
-- Slim, then dropped Slim, back with ERB - translation was going to take too long
-- added HTML compression, even though the difference is only around 1kb a page
-- ERB partials
-- working posts & tags
-- replaced Colorize with Rainbow
-- replaced ERB::Util with a slug name generator
-- added dates to tag lists
-- copies files that aren't Markdown or templates to the build directory, preserving the folder structure
-- a simple WEBrick server for preview, with SSL, then
-- WEBrick swapped out for Thin - WEBrick's been ridiculously slow
-- DataPage class carved out of Page
-- home & all tags index pages
-- more serious site & page class refactoring
-- pages that aren't blog posts (eg about)
-- started into RSS/Atom feeds, and the standard library docs are borderline nonexistent
+- temp warning about missing atom template in zine.yaml, better handling of missing templates
+- cli missing options bug fixed - from 0.15.0
+- added Thor self.exit_on_failure? method
+- increased the required version of Ruby to 2.6
+- changed the license - from MIT, to GNU Affero GPL
+- reversed the sort order for this change log
+- changed the date format in the log - from US style, to everywhere else style
 
-## 0.1.0, February 6, 2017
+# 0.16.0 - 3 February, 2022 - not published as a gem
 
-- claimed the feed content is xhtml to get it to work, will revisit & fix this with CDATA
-- started testing the engine against old blog posts
-- first code to GitHub
-- gem published
+- BREAKING CHANGE: added an RSS 2.0 feed in addition to the Atom feed, the rss.erb file and /rss.xml feed link will now be RSS, an Atom and RSS template are both required in the local site copy, and need to be listed in a site's zine.yml file
+- year bump in starter template
 
-## 0.2.0, February 9, 2017
+# 0.15.0 - 26 May, 2020
 
-- RSS now using DataPage & ERB, with CDATA tags
-- added Ruby 2.0 as a minimum to the gemspec
-- template names from zine.yaml
-- consolidated the DataPage calls in the Site class (the home page, feed, and now added an articles/archive index to that)
-- added 'skip to main content' back into the header partial
-- some bug fixes & minor refactoring
+- dependency version bumps, year bump in template
+- replaced zine.dev with https://mikekreuzer.com/projects/zine/
+- other minor refactoring & doc rewrites
 
-## 0.3.0, February 19, 2017
+# 0.14.0 - 27 May, 2019
 
-- moved the local post directory creation to the write method
-- added a minimalist version of building additional posts while build is running
-- PostsAndHeadlines class extracted from Site
-- CSS preprocessing with Sass added (LibSass and SassC)
-- messing about with styles
-- some minor refactoring & doc work
-- watching the Markdown files for changes with Listener
-- started on incremental builds
-- added SFTP uploads of the files that changed, which includes (and it warrants a line)...
-- my own homegrown (& no doubt pretty rough) SFTP version of mkdir_p
-- incremental builds handle Markdown file deletions now
-- rearranged the zine.yaml preferences file to accommodate file transfers
-- added footer links via zine.yaml, tweaking the style & templates a little
-- consolidate upload paths instead of sending duplicate mkdir requests via SFTP
-- file watcher extended to cover non Markdown files
-- testing real world data with my blog
-- start the file watcher earlier to catch the initial build in a full build,
-  meant everything was a change so everything's uploaded...
-- added an incremental build that skipped the initial writes to fix that
-- linked homepage post titles to posts
+- added an AWS S3 uploader
+- added AWS CloudFront invalidation
+- added zine.dev to the footer template
+- bug fix - catch carriage returns as default yes answers to the upload? question
 
-## 0.4.0, February 20, 2017
+# 0.13.0 - lucky 13 - 26 May, 2019
 
-- fixed a bug in file uploads, which warrants a gem version bump
-- fixed some typos in the blog
-- updated some styles (footer links, bold text)
+- added some of the style changes that survived from v12, eg moved social media to the footer
+- added a (permissive as they come) robots.txt file
+- dependency updates, kramdown split into kramdown & kramdown-parser-gfm which seems to be slower :-(
+- bumped the required version of Ruby to 2.3 (for bundler, kramdown, etc)
+- dropped the highline gem (it was only used to get the one input, originally there was going to be more)
+- minor readme updates
+- placeholder site, mostly in case there's ever an app: https://zine.dev
+
+# 0.12.0 - never pushed, used up until 25 April, 2019
+
+- added (then removed) Mastodon from the list of contacts, changed the styling a few times, neglected to publish
+
+# 0.11.0, 7 November, 2018
+
+- fixed a bug where String#split would break apart markdown files on tables as well as at the metadata/markdown boundary
+
+# 0.9.0, 1 January, 2018
+
+- a bug in 'zine notice' involving full & partial paths that duplicated the post to notice on the history page, fixed
+- minor code clean-up in cli.rb and server.rb
+
+# 0.10.0, 7 November, 2018
+
+- dependency version bumps
+
+## 0.8.0, 2 October, 2017
+
+- SFTP upload error wasn't caught in 0.7.0... TODO
+- added a notice command, zine notice [FILE], which adds that file to the build queue without having to force a general build, so zine can be called in scripts to upload particular files (a rake script in Ripley, specifically)
+
+## 0.7.0, 30 September, 2017
+
+- caught an SFTP upload error where SFTP credentials aren't in the keychain
+- updated bundler
+
+## 0.6.0, 17 September, 2017
+
+- tests: for Upload & UploaderGitHub - found a bug, which is gratifying... would've been caught by a compiler, oh well
+- fixed a mismatched div tag in the footer
+- changed to a non 100 days of code change log
+- updated some development dependencies (curb, rake, rspec, simplecov)
 
-## 0.5.0, March 9, 2017
+## 0.5.0, 9 March, 2017
 
 - updated dependencies: Rake & Simplecov
 - refactored Zine::Site#housekeeping_copy
@@ -96,76 +98,72 @@
 - Upload class split up, into Upload and UploadSFTP
 - UploadGitHub class added - GitHub uploads
 
-## 0.6.0, September 17, 2017
+## 0.4.0, 20 February, 2017
 
-- tests: for Upload & UploaderGitHub - found a bug, which is gratifying... would've been caught by a compiler, oh well
-- fixed a mismatched div tag in the footer
-- changed to a non 100 days of code change log
-- updated some development dependencies (curb, rake, rspec, simplecov)
-
-## 0.7.0, September 30, 2017
-
-- caught an SFTP upload error where SFTP credentials aren't in the keychain
-- updated bundler
-
-## 0.8.0, October 2, 2017
-
-- SFTP upload error wasn't caught in 0.7.0... TODO
-- added a notice command, zine notice [FILE], which adds that file to the build queue without having to force a general build, so zine can be called in scripts to upload particular files (a rake script in Ripley, specifically)
-
-# 0.9.0, January 1, 2018
-
-- a bug in 'zine notice' involving full & partial paths that duplicated the post to notice on the history page, fixed
-- minor code clean-up in cli.rb and server.rb
-
-# 0.10.0, November 7, 2018
-
-- dependency version bumps
-
-# 0.11.0, November 7, 2018
-
-- fixed a bug where String#split would break apart markdown files on tables as well as at the metadata/markdown boundary
-
-# 0.12.0 - never pushed, used up until April 25, 2019
-
-- added (then removed) Mastodon from the list of contacts, changed the styling a few times, neglected to publish
-
-# 0.13.0 - lucky 13 - May 26, 2019
-
-- added some of the style changes that survived from v12, eg moved social media to the footer
-- added a (permissive as they come) robots.txt file
-- dependency updates, kramdown split into kramdown & kramdown-parser-gfm which seems to be slower :-(
-- bumped the required version of Ruby to 2.3 (for bundler, kramdown, etc)
-- dropped the highline gem (it was only used to get the one input, originally there was going to be more)
-- minor readme updates
-- placeholder site, mostly in case there's ever an app: https://zine.dev
+- fixed a bug in file uploads, which warrants a gem version bump
+- fixed some typos in the blog
+- updated some styles (footer links, bold text)
 
-# 0.14.0 - May 27, 2019
+## 0.3.0, 19 February, 2017
 
-- added an AWS S3 uploader
-- added AWS CloudFront invalidation
-- added zine.dev to the footer template
-- bug fix - catch carriage returns as default yes answers to the upload? question
+- moved the local post directory creation to the write method
+- added a minimalist version of building additional posts while build is running
+- PostsAndHeadlines class extracted from Site
+- CSS preprocessing with Sass added (LibSass and SassC)
+- messing about with styles
+- some minor refactoring & doc work
+- watching the Markdown files for changes with Listener
+- started on incremental builds
+- added SFTP uploads of the files that changed, which includes (and it warrants a line)...
+- my own homegrown (& no doubt pretty rough) SFTP version of mkdir_p
+- incremental builds handle Markdown file deletions now
+- rearranged the zine.yaml preferences file to accommodate file transfers
+- added footer links via zine.yaml, tweaking the style & templates a little
+- consolidate upload paths instead of sending duplicate mkdir requests via SFTP
+- file watcher extended to cover non Markdown files
+- testing real world data with my blog
+- start the file watcher earlier to catch the initial build in a full build,
+  meant everything was a change so everything's uploaded...
+- added an incremental build that skipped the initial writes to fix that
+- linked homepage post titles to posts
 
-# 0.15.0 - May 26, 2020
+## 0.2.0, 9 February, 2017
 
-- dependency version bumps, year bump in template
-- replaced zine.dev with https://mikekreuzer.com/projects/zine/
-- other minor refactoring & doc rewrites
+- RSS now using DataPage & ERB, with CDATA tags
+- added Ruby 2.0 as a minimum to the gemspec
+- template names from zine.yaml
+- consolidated the DataPage calls in the Site class (the home page, feed, and now added an articles/archive index to that)
+- added 'skip to main content' back into the header partial
+- some bug fixes & minor refactoring
 
-TO DO
+## 0.1.0, 6 February, 2017
 
-- add canonical links to page headers, means the build order needs to change...
-- generate sitemap.xml
-- fix the SFTP error from 0.7/0.8, also likely applies to S3
-- make sure the server's killed on errors (eg if no credentials) so can run it again later without a port conflict
-- tests, lots of tests
+- claimed the feed content is xhtml to get it to work, will revisit & fix this with CDATA
+- started testing the engine against old blog posts
+- first code to GitHub
+- gem published
 
-MAY DO
+## Pre 0.0.1
 
-- concurrent-ruby gem
-- migration scripts from eg Jekyll?
-- Apple News
-- much refactoring, frozen_string_literal, split monster classes, etc
-- replace thor with optparse
-- an app... maybe
+- set up the blog & repos
+- set up bundler, rspec tests
+- Thor for the menu & as a generator
+- YAML options
+- have a Site object pushing file names to Page objects
+- Kramdown
+- played with cucumber for a while but decided not to use it, it's a DSL too far.
+- Slim, then dropped Slim, back with ERB - translation was going to take too long
+- added HTML compression, even though the difference is only around 1kb a page
+- ERB partials
+- working posts & tags
+- replaced Colorize with Rainbow
+- replaced ERB::Util with a slug name generator
+- added dates to tag lists
+- copies files that aren't Markdown or templates to the build directory, preserving the folder structure
+- a simple WEBrick server for preview, with SSL, then
+- WEBrick swapped out for Thin - WEBrick's been ridiculously slow
+- DataPage class carved out of Page
+- home & all tags index pages
+- more serious site & page class refactoring
+- pages that aren't blog posts (eg about)
+- started into RSS/Atom feeds, and the standard library docs are borderline nonexistent

data/LICENSE

@@ -1,21 +1,661 @@
-MIT License
-
-Copyright (c) 2017 Mike Kreuzer
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+                    GNU AFFERO GENERAL PUBLIC LICENSE
+                       Version 3, 19 November 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU Affero General Public License is a free, copyleft license for
+software and other kinds of works, specifically designed to ensure
+cooperation with the community in the case of network server software.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+our General Public Licenses are 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.
+
+  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.
+
+  Developers that use our General Public Licenses protect your rights
+with two steps: (1) assert copyright on the software, and (2) offer
+you this License which gives you legal permission to copy, distribute
+and/or modify the software.
+
+  A secondary benefit of defending all users' freedom is that
+improvements made in alternate versions of the program, if they
+receive widespread use, become available for other developers to
+incorporate.  Many developers of free software are heartened and
+encouraged by the resulting cooperation.  However, in the case of
+software used on network servers, this result may fail to come about.
+The GNU General Public License permits making a modified version and
+letting the public access it on a server without ever releasing its
+source code to the public.
+
+  The GNU Affero General Public License is designed specifically to
+ensure that, in such cases, the modified source code becomes available
+to the community.  It requires the operator of a network server to
+provide the source code of the modified version running there to the
+users of that server.  Therefore, public use of a modified version, on
+a publicly accessible server, gives the public access to the source
+code of the modified version.
+
+  An older license, called the Affero General Public License and
+published by Affero, was designed to accomplish similar goals.  This is
+a different license, not a version of the Affero GPL, but Affero has
+released a new version of the Affero GPL which permits relicensing under
+this license.
+
+  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 Affero 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. Remote Network Interaction; Use with the GNU General Public License.
+
+  Notwithstanding any other provision of this License, if you modify the
+Program, your modified version must prominently offer all users
+interacting with it remotely through a computer network (if your version
+supports such interaction) an opportunity to receive the Corresponding
+Source of your version by providing access to the Corresponding Source
+from a network server at no charge, through some standard or customary
+means of facilitating copying of software.  This Corresponding Source
+shall include the Corresponding Source for any work covered by version 3
+of the GNU General Public License that is incorporated pursuant to the
+following paragraph.
+
+  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 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 work with which it is combined will remain governed by version
+3 of the GNU General Public License.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU Affero 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 Affero 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 Affero 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 Affero General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU Affero 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 Affero General Public License for more details.
+
+    You should have received a copy of the GNU Affero General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If your software can interact with users remotely through a computer
+network, you should also make sure that it provides a way for users to
+get its source.  For example, if your program is a web application, its
+interface could display a "Source" link that leads users to an archive
+of the code.  There are many ways you could offer source, and different
+solutions will be better for different programs; see section 13 for the
+specific requirements.
+
+  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 AGPL, see
+<https://www.gnu.org/licenses/>.

data/lib/zine/cli.rb

@@ -15,11 +15,22 @@ module Zine
     attr_accessor :the_site # only used in testing
 
     no_commands do
+      def self.exit_on_failure?
+        true
+      end
+
       def init_site
         @the_site ||= Zine::Site.new
       end
 
       def options
+        init_site
+
+        # for v0.16.0 only
+        unless @the_site.options['templates']['atom']
+          puts "v0.16.0 changes how rss & atom works, see CHANGELOG.md if you haven't already\n\n"
+        end
+
         @the_site.options
       end
     end

data/lib/zine/data_page.rb

@@ -5,6 +5,7 @@ module Zine
   # links to other pages, eg an index page like the home page
   class DataPage < Zine::Page
     def initialize(data, templates, site_options, suffix = '.html')
+      # super(front_matter, site_opt)
       init_templates(templates)
       @formatted_data = FormattedData.new({}, site_options)
       @formatted_data.page[:title] = data[:title]

data/lib/zine/page.rb

@@ -30,6 +30,7 @@ module Zine
       def initialize(front_matter, site_opt)
         site = site_opt['options']
         @page = { date_rfc3339: front_matter['date'],
+                  date_rfc822: parse_822_date(front_matter['date']),
                   date_us: parse_date(front_matter['date']),
                   github_name: site['github_name'],
                   links_array: site_opt['links'],
@@ -56,6 +57,12 @@ module Zine
         ''
       end
 
+      def parse_822_date(front_matter_date)
+        DateTime.rfc3339(front_matter_date).rfc2822
+      rescue ArgumentError
+        ''
+      end
+
       def slugify_tags(tags)
         return unless tags && tags.any?
         tags.map { |tag| { name: tag, tag_slug: Page.slug(tag) } }

data/lib/zine/posts_and_headlines.rb

@@ -32,15 +32,54 @@ module Zine
       dir = @options['directories']['build']
       options = @options['options']
       templates = @options['templates']
-      [{ build_dir: dir, name: templates['articles'], number: @post_array.size,
-         suffix: '.html', template_name: templates['articles'],
-         title: 'Articles' },
-       { build_dir: dir, name: 'index',
-         number: options['num_items_on_home'], suffix: '.html',
-         template_name: templates['home'], title: 'Home' },
-       { build_dir: dir, name: 'rss',
-         number: options['number_items_in_RSS'], suffix: '.xml',
-         template_name: templates['rss'], title: '' }]
+      
+      headlines = []
+      if templates['home']
+        headlines <<
+          {
+            build_dir: dir,
+            name: 'index',
+            number: options['num_items_on_home'],
+            suffix: '.html',
+            template_name: templates['home'],
+            title: 'Home'
+          }
+      end
+      if templates['articles']
+        headlines <<
+          {
+            build_dir: dir,
+            name: templates['articles'],
+            number: @post_array.size,
+            suffix: '.html',
+            template_name: templates['articles'],
+            title: 'Articles'
+          }
+      end
+      if templates['rss']
+        headlines <<
+          {
+            build_dir: dir,
+            name: 'rss',
+            number: options['number_items_in_RSS'],
+            suffix: '.xml',
+            template_name: templates['rss'],
+            title: ''
+          }
+      end
+      if templates['atom']
+        headlines <<
+          {
+            build_dir: dir,
+            name: 'atom',
+            number: options['number_items_in_RSS'],
+            suffix: '.xml',
+            template_name: templates['atom'],
+            title: ''
+          }
+      end
+
+      headlines
     end
 
     def once_only(source_file)
@@ -114,7 +153,7 @@ module Zine
     def preview_straight_delete(file)
       FileUtils.rm(File.join(
                      preview_relative_equivalent(file), File.basename(file)
-      ))
+                  ))
     end
 
     # rebuild a page that's not a post - doesn't create the file structure for a
@@ -192,7 +231,7 @@ module Zine
       @post_array.first(page[:number]).each do |post|
         post_data = post.formatted_data
         data[:post_array] << { page: post_data.page, html: post_data.html,
-                               uri:  post_data.uri }
+                               uri: post_data.uri }
       end
       data_page = DataPage.new(data,
                                @site.make_template_bundle(data[:template_name]),

data/lib/zine/skeleton/source/templates/atom.erb

@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<feed xmlns="http://www.w3.org/2005/Atom"
+  xmlns:dc="http://purl.org/dc/elements/1.1/">
+  <author>
+    <name><%= page[:site_author] %></name>
+  </author>
+  <id><%= page[:site_URL] %>/atom.xml</id>
+  <title><%= page[:site_name] %></title>
+  <dc:date><%= data[0][:page][:date_rfc3339] %></dc:date>
+  <updated><%= data[0][:page][:date_rfc3339] %></updated>
+  <link href="<%= page[:site_URL] %>/atom.xml" rel="self" type="application/atom+xml"/>
+  <% for @post in data %>
+    <entry>
+      <content type="html"><![CDATA[<%= @post[:html] %>]]></content>
+      <id><%= @post[:uri] %></id>
+      <link href="<%= @post[:uri] %>"/>
+      <title><%= @post[:page][:title] %></title>
+      <updated><%= @post[:page][:date_rfc3339] %></updated>
+      <dc:date><%= @post[:page][:date_rfc3339] %></dc:date>
+    </entry>
+  <% end %>
+</feed>

data/lib/zine/skeleton/source/templates/footer_partial.erb

@@ -18,7 +18,7 @@
     <h3>The fine print</h3>
     <ul>
       <li>Built with <a href="https://mikekreuzer.com/projects/zine/">Zine</a></li>
-      <li>&copy; 2020<span> <%= page[:site_author] %></span></li>
+      <li>&copy;2017-2022<span> <%= page[:site_author] %></span></li>
     </ul>
   </div>
   </footer>

data/lib/zine/skeleton/source/templates/header_partial.erb

@@ -5,7 +5,8 @@
     <meta name="viewport" content="width=device-width,user-scalable=yes">
     <meta name="description" content="<%= page[:site_description] %>">
     <title><%= page[:site_name] %> | <%= page[:title] %></title>
-    <link rel="home" href="<%= page[:site_URL] %>/rss.xml" type="application/rss+xml" title="<%= page[:site_name] %>">
+    <link rel="home alternate" href="<%= page[:site_URL] %>/atom.xml" type="application/atom+xml" title="<%= page[:site_name] %>">
+    <link rel="home alternate" href="<%= page[:site_URL] %>/rss.xml" type="application/rss+xml" title="<%= page[:site_name] %>">
     <link rel="stylesheet" href="/screen.css">
     <link rel="apple-touch-icon" href="/apple-touch-icon.png">
     <!--<link rel="canonical" href="<%= page[:uri] %>" />-->

data/lib/zine/skeleton/source/templates/rss.erb

@@ -1,21 +1,19 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<feed xmlns="http://www.w3.org/2005/Atom"
-  xmlns:dc="http://purl.org/dc/elements/1.1/">
-  <author>
-    <name><%= page[:site_author] %></name>
-  </author>
-  <id><%= page[:site_URL] %>/rss.xml</id>
-  <title><%= page[:site_name] %></title>
-  <dc:date><%= data[0][:page][:date_rfc3339] %></dc:date>
-  <updated><%= data[0][:page][:date_rfc3339] %></updated>
-  <% for @post in data %>
-    <entry>
-      <content type="html"><![CDATA[<%= @post[:html] %>]]></content>
-      <id><%= @post[:uri] %></id>
-      <link href="<%= @post[:uri] %>"/>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+<channel>
+	<title><%= page[:site_name] %></title>
+	<link><%= page[:site_URL] %>/rss.xml</link>
+	<description><%= page[:site_description] %></description>
+	<pubDate><%= data[0][:page][:date_rfc822] %></pubDate>
+  <lastBuildDate><%= data[0][:page][:date_rfc822] %></lastBuildDate>
+  <atom:link href="<%= page[:site_URL] %>/rss.xml" rel="self" type="application/rss+xml" />
+	<% for @post in data %>
+    <item>
       <title><%= @post[:page][:title] %></title>
-      <updated><%= @post[:page][:date_rfc3339] %></updated>
-      <dc:date><%= @post[:page][:date_rfc3339] %></dc:date>
-    </entry>
-  <% end %>
-</feed>
+      <link><%= @post[:uri] %></link>
+      <description><![CDATA[<%= @post[:html] %>]]></description>
+      <pubDate><%= @post[:page][:date_rfc822] %></pubDate>
+      <guid><%= @post[:uri] %></guid>
+    </item>
+	<% end %>
+</channel>
+</rss>

data/lib/zine/skeleton/zine.yaml

@@ -25,6 +25,7 @@ options:
   twitter_name: mikekreuzer
 templates:
   articles: articles
+  atom: atom
   default: default
   home: home
   new_post: new_post.erb

data/lib/zine/version.rb

@@ -2,5 +2,5 @@
 
 module Zine
   # The version
-  VERSION = '0.15.0'
+  VERSION = '0.16.0'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: zine
 version: !ruby/object:Gem::Version
-  version: 0.15.0
+  version: 0.16.0
 platform: ruby
 authors:
 - Mike Kreuzer
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-05-26 00:00:00.000000000 Z
+date: 2022-06-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -324,6 +324,7 @@ files:
 - lib/zine/skeleton/source/screen.css
 - lib/zine/skeleton/source/styles/screen.scss
 - lib/zine/skeleton/source/templates/articles.erb
+- lib/zine/skeleton/source/templates/atom.erb
 - lib/zine/skeleton/source/templates/default.erb
 - lib/zine/skeleton/source/templates/footer_partial.erb
 - lib/zine/skeleton/source/templates/header_partial.erb
@@ -345,7 +346,7 @@ files:
 - lib/zine/watcher.rb
 homepage: https://mikekreuzer.com/projects/zine/
 licenses:
-- MIT
+- AGPL-3.0-or-later
 metadata: {}
 post_install_message: 
 rdoc_options: []
@@ -355,14 +356,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '2.3'
+      version: '2.6'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.0.6
+rubygems_version: 3.1.4
 signing_key: 
 specification_version: 4
 summary: Yet another blog aware static site generator.