jekyll-paginate-v2 1.3.3 → 1.4.0

data/examples/01-typicalblog/_posts/2016-11-21-sailing-summer-olympics-1988.md

@@ -0,0 +1,15 @@
+---
+layout: post
+title:  Sailing at the 1988 Summer Olympics
+date:   2016-11-21 19:16:49 +0100
+categories: wikipedia
+---
+
+_From Wikipedia, the free encyclopedia_
+
+Sailing/Yachting is an Olympic sport starting from the 1896 Olympics in Athens, Greece). With the exception of 1904 and possible 1916 sailing was always a part of the Olympic program. The Sailing program of 1988 consisted of a total of eight sailing classes (disciplines). For each class seven races were scheduled from September 20, 1988 to September 27, 1988 of the coast of Busan and was the first time that a separate event was allocated exclusively for women (sailed in the 470 class). The sailing was done on the triangular type Olympic courses.
+
+## Venue
+According to the IOC statutes the contests in all sport disciplines must be held either in, or as close as possible to the city which the IOC has chosen. Since the sailing conditions of the coast near Seoul are not very suitable for Olympic sailing Busan was chosen for the 1988 Sailing event. A total of two race areas were created of the coast of Busan.
+
+Busan in Korea was reportedly a light wind venue but no one realised until too late that this information came from the airport which was located in a sheltered valley. It turned out to be that the 1988 Olympic Games were one of the windiest ever with one day of racing postponed due to too much wind. One day of racing saw around 30 knots of wind with 5 knots of current going against the wind. There was a lot of equipment damage and rescues for many classes resulting in many sailors did not finish and requests for redress.

data/examples/01-typicalblog/_posts/2016-11-22-rotary-engine.md

@@ -0,0 +1,27 @@
+---
+layout: post
+title:  Rotary engine
+date:   2016-11-22 19:16:49 +0100
+categories: wikipedia
+---
+
+_From Wikipedia, the free encyclopedia_
+
+The rotary engine was an early type of internal-combustion engine, usually designed with an odd number of cylinders per row in a radial configuration, in which the crankshaft remained stationary in operation, with the entire crankcase and its attached cylinders rotating around it as a unit. Its main application was in aviation, although it also saw use before its primary aviation role, in a few early motorcycles and automobiles.
+
+This type of engine was widely used as an alternative to conventional inline engines (straight or V) during World War I and the years immediately preceding that conflict. It has been described as "a very efficient solution to the problems of power output, weight, and reliability".[1]
+
+By the early 1920s, however, the inherent limitations of this type of engine had rendered it obsolete, with the power output increasingly going into overcoming the air-resistance of the spinning engine itself. The rotating mass of the engine also caused significant gyroscopic precession: depending on the type of aircraft, this produced stability and control problems, especially for inexperienced pilots. Another factor in the demise of the rotary was the fundamentally inefficient total-loss oiling system, caused by the need to aspirate the fuel/air mixture through the hollow crankshaft and crankcase along with the lubricating medium, as in a two-stroke engine.
+
+## Description
+A rotary engine is essentially a standard Otto cycle engine, but instead of having a fixed cylinder block with rotating crankshaft as with a conventional radial engine, the crankshaft remains stationary and the entire cylinder block rotates around it. In the most common form, the crankshaft was fixed solidly to the airframe, and the propeller was simply bolted to the front of the crankcase.
+
+Three key factors contributed to the rotary engine's success at the time:[2]
+
+* Smooth running: Rotaries delivered power very smoothly because (relative to the engine mounting point) there are no reciprocating parts, and the relatively large rotating mass of the crankcase/cylinders (as a unit) acted as a flywheel.
+* Improved cooling: when the engine was running the rotating crankcase/cylinder assembly created its own fast-moving cooling airflow, even with the aircraft at rest.
+* Weight advantage: many conventional engines had to have heavy flywheels added to smooth out power impulses and reduce vibration. Rotary engines gained a substantial power-to-weight ratio advantage by having no need for an added flywheel. They shared with other radial configuration engines the advantage of a small, flat crankcase, and because of their efficient air-cooling system cylinders could be made with thinner walls and shallower cooling fins, which further reduced their weight.
+
+Most rotary engines were arranged with the cylinders pointing outwards from a single crankshaft, in the same general form as a radial, but there were also rotary boxer engines[3] and even one-cylinder rotaries.
+
+Like radial engines, rotaries were generally built with an odd number of cylinders (usually either 7 or 9), so that a consistent every-other-piston firing order could be maintained, to provide smooth running. Rotary engines with an even number of cylinders were mostly of the "two row" type.

data/examples/01-typicalblog/_posts/2016-11-23-luft-fahrzeug-gesellschaft.md

@@ -0,0 +1,27 @@
+---
+layout: post
+title:  Luft-Fahrzeug-Gesellschaft
+date:   2016-11-23 19:16:49 +0100
+categories: wikipedia
+---
+
+Luft-Fahrzeug-Gesellschaft, also referred to as LFG, was a German aircraft manufacturer during World War I. They are best known for their various "Roland" designs, notably the Roland C.II Walfisch (whale), Roland D.II haifisch (Shark) and Roland D.VI, although they also produced a number of airships and many experimental designs.
+
+## Airships
+Luft-Fahrzeug-Gesellschaft formed on April 30, 1908, from the assets of an experimental airship engine company located in Bitterfeld, Motorluftschiff Studiengesellscaft (MStG). Additional funding for the new enterprise was provided primarily by Krupp, AEG, and a local chemical company. The company's offices were located in Berlin along with the factory at Adlershof. Manufacture was transferred to Charlottenburg following a fire on 6 September 1916, allegedly caused by the British Secret Service.[1]
+
+Their first project was an airship design by August von Parseval, a German airship designer. This entered service as the PL.II in 1910. During World War I, four were delivered to the German Army and Navy. In total some 25 "PL" airships were built, flown and delivered to various customers. The PL-26, one of the last, crashed on landing and burnt inside hangar Luftschiffhalle 2 with no fatalities. For the rest of the war the hangars were used mostly for repairs of observation balloons.
+
+## Aeroplanes
+
+In 1913 LFG started producing new designs under the trade name Roland to avoid confusion with the Luftverkehrsgesellschaft (L.V.G.) firm. In 1916 the company developed a floatplane version of the Albatros C.Ia as the LFG W. Some parts were built in Bitterfeld, but final assembly and checkout was carried out in new factories in Stralsund.
+
+Their first successful design was the Roland C.II Walfisch (whale), a two-seat reconnaissance biplane. It had a semi-monocoque fuselage, skinned with two layers of long plywood strips glued at opposing diagonal angles around a mold and skinned with fabric both inside and outside. The fuselage filled the full gap between the wings, leaving the pilot and observer/gunner over the top wings with an excellent view upward. The fuselage "half-shells" were each fitted onto a supporting framework of wooden formers and longerons. The "wrapping" technique of the long plywood strips for the outer fuselage surface led to this particular technique of manufacture being described in German as the Wickelrumpf (wrapped body) style of construction, and was subsequently patented by the firm,[2] licensing the construction method to Pfalz in 1917 for construction of their own single-seat fighter designs. Although it was said to have tricky handling, the Roland C.II had excellent performance, and was also used on long-range missions as a bomber escort. A version with the 200 hp Benz Bz.IV engine and new wing struts was built as the D.III, but only one prototype was ever built, as was the case for the 160 hp Mercedes D.III-powered C.V.
+
+The C.II was adapted to the pure fighter role as the Roland D.I, but in this role the poor forward view proved to be a problem. A fire at the factory severely constrained production, and only 20 were built. A newer version with a more conventional layout, the Roland D.II, followed, whose fuselage was reduced in height to leave a gap with the upper wing but was otherwise similar overall. The competing Albatros D.I was preferred, and only about 230 examples were built, which where then mostly used on the eastern front and in Macedonia. The fuselage to wing gap was further increased in the D.III, but the temperamental 180 hp Argus As.III limited production to only a handful. Six D.IIs were delivered in July 1917 to the Bulgarian Air Force, and six D.IIIs were delivered in May 1918.[3]
+
+Although the Wickelrumpf style of wood-structure monocoque fuselage was extremely strong, it was also very difficult and time-consuming to build. A new method of construction was introduced that used spruce planking running the length of the aircraft in place of the formed plywood, and the D.III was adapted using this technique to produce D.IV triplane and D.V biplane, both powered by the D.III's 160 hp Mercedes. The fuselage shell's construction technique for these aircraft resembled a clinker-planked boat hull in appearance when finished, and was named Klinkerrumpf (clinker body) construction, and was also patented by the firm.[4] A further adaptation of the D.IV with the 185 hp Benz Bz. III resulted in the Roland D.VI, which was entered in the First Fighter Competition trials at Adlershof in early 1918. Although the Fokker D.VII won that contest, the D.VI was also ordered into production as it used a different engine, and by the end of the war about 350 had been delivered. A large number of different versions using various engines were built as prototypes without entering production, as well as a triplane adaptation as the D.VI (also known as the Dr.I).
+
+The next major design from Roland were parasol monoplane designs, the D.XVI with the Siemens-Halske Sh.III or 170 hp Goebel Goe.IIIa rotary piston engines, and the otherwise similar D.XVII with the inline 185 hp BMW IIIa. Both were entered into the Second Fighter Competition at Adlershof, but lost to the Fokker D.VIII.
+
+After the war all aircraft production in Germany was banned, and the company was forced to close the Bitterfeld plant and reopen in Seddin, producing airplanes, balloons and life boats. In 1933, aircraft production shut down. Three additional Parseval pattern airships were also built during this period.

data/examples/01-typicalblog/_posts/2016-11-24-narcisse-snake-pits.md

@@ -0,0 +1,18 @@
+---
+layout: post
+title:  Narcisse Snake Pits
+date:   2016-11-24 19:16:49 +0100
+categories: wikipedia
+---
+
+_From Wikipedia, the free encyclopedia_
+
+The Narcisse Snake Pits are located in the Rural Municipality of Armstrong about 6 kilometres (3.7 mi) north of Narcisse, Manitoba, Canada. The dens are the winter home of tens of thousands of red-sided garter snakes (Thamnophis sirtalis parietalis). These pits are the largest concentration in the world of this particular type of snake. Their winter dens are subterranean caverns formed by the area's water-worn limestone bedrock. In the spring, they come up from their dens to the snake pits, where they engage in mating rituals. Then they disperse into the nearby marshes for the summer.
+
+## Conservation
+The population of red-sided garter snakes around Narcisse was roughly 70,000 until terrible weather in 1999 killed tens of thousands of them before they could reach their winter dens. [1] This tragedy triggered concern about the snakes' biannual migratory path, which cuts right across Highway 17. Every year, ten thousand snakes trying to get to or from their winter dens had been crushed under the wheels of vehicles. This had not been a problem before, because the vast population compensated for the losses. After the winter of 1999, however, the population of garter snakes was dangerously low, causing Manitoba Hydro and volunteers to intervene.
+
+Foot-high snow fences were built to force snakes into six-inch (15-cm) tunnels that went under Highway 17. Since some snakes still managed to squeeze under the fence and onto the road, signs were put up during the migratory season urging motorists to slow down to avoid accidentally driving over snakes. These measures worked, and now less than a thousand snakes per season are killed on the highway.
+
+## Visiting
+The conservation area is open to the public. The snakes are most active during the spring and fall - in late April to early May, which is the mating season, and also in early September, when the snakes slither back down to their winter dens.[1]

data/examples/01-typicalblog/_posts/2016-11-25-tele7jours.md

@@ -0,0 +1,43 @@
+---
+layout: post
+title:  Télé 7 Jours
+date:   2016-11-25 19:16:49 +0100
+categories: wikipedia
+---
+
+_From Wikipedia, the free encyclopedia_
+
+***Télé 7 Jours*** is a [French] weekly magazine published by [Hachette Filipacchi Médias] in [France]. It publishes news and materials relating to French radio and television programming.
+
+## History and profile
+
+Originally, the magazine was named “Radio 44” as it started publishing on 29 October 1944. The name would change (“Radio 45”, “Radio 46”, etc.) as the year of publication changed, until the year 1957, when it was renamed “Radio Télévision 57” and in 1959 was changed to “Télé 59”. Its contents are basically coverage of television news and listings, cultural and lifestyle news and entertainment.
+
+In 1960, Sofirad, the original owner, sold the magazine to [Jean Prouvost], who named it “7 jours Télé 60” for a short period and then renamed it to the present “Télé 7 Jours” from 7 March 1960.
+
+The magazine is published on a weekly basis.<sup>[\[1\]]</sup> Its circulation jumped to more than a million copies weekly in 1962 and 2 million by 1965 becoming the biggest circulation weekly in France.
+
+In 1976, [Hachette][Hachette Filipacchi Médias] purchased the magazine.<sup>[\[2\]]</sup> The magazine remained the most read French magazine in the 1980s and 1990s reaching a circulation of 3.2 million weekly.
+
+From 1985 to 2003, *Télé 7 Jours* organized a <a href="/wiki/French_television" class="mw-redirect" title="French television">French television</a> production award (similar in nature to the [Emmy Awards]) called the *[7 d’Or]*.<sup>[\[2\]]</sup> From 1996 to 1999, [Benjamin Cuq] worked as reporter for *Télé 7 Jours*.
+
+## Circulation
+
+Télé 7 Jours had a circulation of 2,800,000 copies in 1974.[3] The circulation of the weekly was 2,606,000 copies in 1999.[4]
+
+It was the sixth best-selling television magazine worldwide with a circulation of 2,371,000 copies during in 2001.[1] In 2005 its circulation dropped to 1,892,000 copies, but it was the best-selling magazine in France.[5]
+
+The circulation of the magazine was 1,588,000 copies during the 2007-2008 period.[6] In 2010 the magazine had a circulation of 1,471,593 copies.[7] Its circulation was 1,225,642 copies in 2014.
+
+
+  [French]: /wiki/French_language "French language"
+  [Hachette Filipacchi Médias]: /wiki/Hachette_Filipacchi_M%C3%A9dias "Hachette Filipacchi Médias"
+  [France]: /wiki/France "France"
+  [edit]: /w/index.php?title=T%C3%A9l%C3%A9_7_Jours&action=edit&section=1 "Edit section: History and profile"
+  [Jean Prouvost]: /wiki/Jean_Prouvost "Jean Prouvost"
+  [\[1\]]: #cite_note-mags-1
+  [\[2\]]: #cite_note-rich-2
+  [Emmy Awards]: /wiki/Emmy_Award "Emmy Award"
+  [7 d’Or]: /wiki/7_d%27Or "7 d'Or"
+  [Benjamin Cuq]: /wiki/Benjamin_Cuq "Benjamin Cuq"
+  [1]: /w/index.php?title=T%C3%A9l%C3%A9_7_Jours&action=edit&section=2 "Edit section: Circulation"

data/examples/01-typicalblog/_posts/2016-11-26-columbia-river.md

@@ -0,0 +1,41 @@
+---
+layout: post
+title:  Columbia River
+date:   2016-11-26 19:16:49 +0100
+categories: wikipedia
+---
+
+_From Wikipedia, the free encyclopedia_
+
+The **Columbia River** is the largest river in the [Pacific Northwest] region of North America.<sup>[\[9\]]</sup> The river <a href="/wiki/Headwater" class="mw-redirect" title="Headwater">rises</a> in the [Rocky Mountains] of [British Columbia], Canada. It flows northwest and then south into the US state of [Washington], then turns west to form most of the border between Washington and the state of [Oregon] before emptying into the Pacific Ocean. The river is 1,243 miles (2,000 km) long, and its largest [tributary] is the [Snake River]. Its [drainage basin] is roughly the size of France and extends into seven US states and a Canadian province.
+
+By volume, the Columbia is the fourth-largest river in the United States; it has the greatest flow of any North American river draining into the Pacific. The river’s heavy flow and relatively steep [gradient] gives it tremendous potential for the generation of electricity. The [14 hydroelectric dams] on the Columbia’s [main stem] and many more on its tributaries produce more than 44% of total U.S. [hydroelectric generation]<sup>[\[10\]]</sup> – much more hydroelectric power than those of any other North American river.
+
+The Columbia and its tributaries have been central to the region’s culture and economy for thousands of years. They have been used for transportation since ancient times, linking the many cultural groups of the region. The river system hosts many species of <a href="/wiki/Anadromous" class="mw-redirect" title="Anadromous">anadromous</a> fish, which migrate between <a href="/wiki/Freshwater" class="mw-redirect" title="Freshwater">freshwater</a> habitats and the [saline] waters of the Pacific Ocean. These fish—especially the [salmon] species—provided the core subsistence for native peoples; in past centuries, Indigenous peoples traveled across western North America to the Columbia to trade for fish.
+
+In the late 18th century, a private American ship became the first non-indigenous vessel to enter the river; it was followed by a British explorer, who navigated past the [Oregon Coast Range] into the [Willamette Valley]. In the following decades, [fur trading] companies used the Columbia as a key transportation route. Overland explorers entered the Willamette Valley through the scenic but treacherous [Columbia River Gorge], and pioneers began to settle the valley in increasing numbers, following both routes to enter it. [Steamships] along the river linked communities and facilitated trade; the arrival of railroads in the late 19th century, many running along the river, supplemented these links.
+
+  [Oregon Coast Range]: /wiki/Oregon_Coast_Range "Oregon Coast Range"
+  [Willamette Valley]: /wiki/Willamette_Valley "Willamette Valley"
+  [fur trading]: /wiki/Fur_trade "Fur trade"
+  [Columbia River Gorge]: /wiki/Columbia_River_Gorge "Columbia River Gorge"
+  [Steamships]: /wiki/Steamship "Steamship"
+
+  [saline]: /wiki/Saline_water "Saline water"
+  [salmon]: /wiki/Salmon "Salmon"
+
+  [gradient]: /wiki/Grade_(slope) "Grade (slope)"
+  [14 hydroelectric dams]: /wiki/List_of_dams_in_the_Columbia_River_watershed "List of dams in the Columbia River watershed"
+  [main stem]: /wiki/Main_stem "Main stem"
+  [hydroelectric generation]: /wiki/Hydroelectricity "Hydroelectricity"
+  [\[10\]]: #cite_note-IEA2014-10
+
+  [Pacific Northwest]: /wiki/Pacific_Northwest "Pacific Northwest"
+  [\[9\]]: #cite_note-9
+  [Rocky Mountains]: /wiki/Rocky_Mountains "Rocky Mountains"
+  [British Columbia]: /wiki/British_Columbia "British Columbia"
+  [Washington]: /wiki/Washington_(state) "Washington (state)"
+  [Oregon]: /wiki/Oregon "Oregon"
+  [tributary]: /wiki/Tributary "Tributary"
+  [Snake River]: /wiki/Snake_River "Snake River"
+  [drainage basin]: /wiki/Drainage_basin "Drainage basin"

data/examples/01-typicalblog/_posts/2016-11-27-welcome-to-jekyll-paginate-v2.md

@@ -0,0 +1,33 @@
+---
+layout: post
+title:  "Welcome to Jekyll Paginate V2!"
+date:   2016-11-27 19:16:49 +0100
+categories: jekyll paginate
+---
+You’ll find this post in your `_posts` directory. This post along with all of the other example posts is paginated by the new [jekyll-paginate-v2 gem](https://github.com/sverrirs/jekyll-paginate-v2).
+
+This pagination gem is built specially for Jekyll 3 and newer and is intended to replace the now discontinuted jekyll-paginate gem. 
+
+This v2 of the gem offers full backwards compatibility with the old gem and its site configuration. You can simply replace the old jekyll-paginate gem with this one and your sites will still work without any changes.
+
+However to access the new enhanced features of this gem, like pagination on categories, tags and locales, then you need to remove the old jekyll-paginate configuration and activate the new `pagination:` [site configuration](https://github.com/sverrirs/jekyll-paginate-v2#site-configuration). 
+
+The [source code](https://github.com/sverrirs/jekyll-paginate-v2/tree/master/examples) for this example project will show you all the necessary steps.
+
+## Installing
+
+Go ahead and install the latest version of the gem from [rubygems.org](https://rubygems.org/gems/jekyll-paginate-v2)
+
+```
+gem install jekyll-paginate-v2
+```
+
+Replace the `jekyll-paginate` gem with `jekyll-paginate-v2` in both your `_config.yml` and your `Gemfile`.
+
+Now go ahead and re-build your site to start running the new pagination logic. You can rebuild the site in many different ways, but the most common way is to run `jekyll serve`, which launches a web server and auto-regenerates your site when a file is updated.
+
+Please see the [GitHub repo](https://github.com/sverrirs/jekyll-paginate-v2) to learn how to get the most out of this new pagination gem. There we also discuss the gems more advanced features. 
+
+Please file all bugs/feature requests in the issues section of the [GitHub repo](https://github.com/sverrirs/jekyll-paginate-v2/issues).
+
+Have a great day :)

data/examples/01-typicalblog/about.md

@@ -0,0 +1,15 @@
+---
+layout: page
+title: About
+permalink: /about/
+---
+
+This is the base Jekyll theme. You can find out more info about customizing your Jekyll theme, as well as basic Jekyll usage documentation at [jekyllrb.com](http://jekyllrb.com/)
+
+You can find the source code for the Jekyll new theme at:
+{% include icon-github.html username="jekyll" %} /
+[minima](https://github.com/jekyll/minima)
+
+You can find the source code for Jekyll at
+{% include icon-github.html username="jekyll" %} /
+[jekyll](https://github.com/jekyll/jekyll)

data/examples/01-typicalblog/index.html

@@ -0,0 +1,8 @@
+---
+# You don't need to edit this file, it's empty on purpose.
+# Edit theme's home layout instead if you wanna make some changes
+# See: https://jekyllrb.com/docs/themes/#overriding-theme-defaults
+layout: home
+pagination: 
+  enabled: true
+---

data/examples/02-category/Gemfile

@@ -0,0 +1,28 @@
+source "https://rubygems.org"
+ruby RUBY_VERSION
+
+# Hello! This is where you manage which Jekyll version is used to run.
+# When you want to use a different version, change it below, save the
+# file and run `bundle install`. Run Jekyll with `bundle exec`, like so:
+#
+#     bundle exec jekyll serve
+#
+# This will help ensure the proper Jekyll version is running.
+# Happy Jekylling!
+gem "jekyll", "3.3.0"
+
+# This is the default theme for new Jekyll sites. You may change this to anything you like.
+gem "minima", "~> 2.0"
+
+# If you want to use GitHub Pages, remove the "gem "jekyll"" above and
+# uncomment the line below. To upgrade, run `bundle update github-pages`.
+# gem "github-pages", group: :jekyll_plugins
+
+source 'https://rubygems.org'
+
+group :jekyll_plugins do
+  gem "jekyll-paginate-v2"
+  gem "jekyll-feed"
+end
+
+gem 'wdm', '>= 0.1.0' if Gem.win_platform?

data/examples/02-category/README.md

@@ -0,0 +1,119 @@
+# Example 02::Category pagination
+This example website contains information about sports cars and has a single main paginated front page that lists all entries in the system. It also contains separate paginated category pages that list only subset of cars on the site.
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/sverrirs/jekyll-paginate-v2/master/examples/img/02-example-screenshot-main.png" />
+</p>
+
+The site is generated using the jekyll built in new command `jekyll new myblog` and it uses the [default `minima` theme](https://github.com/jekyll/minima).
+
+After generating the pagination gem was installed using
+```
+gem install jekyll-paginate-v2
+```
+
+## Structure
+The blog has two types of posts that can be found under `_posts/` and the `cars/_posts` folder. 
+
+> The `cars/_posts` folder structure is handy as it automatically assigns the category `cars` to all posts under it.
+
+Users can then assign other categories to their posts by editing each post's front-matter as they see fit.
+
+This site uses the same `_layouts/home.html` and `_includes/header.html` overrides as Example 01 does (please refer to that example project for details).
+
+The project also has additional pagination pages that only list subsets of the car list `toyota/index.md`, `categories/porsche.md`, `categories/byname.md`.
+
+> It is not advisable to have multiple pagination pages stored directly under the main site root. It makes it easy to mis-configure resulting in overwritten pagination pages unless developers remember to specify a unique `pagination: permalink: ''` override for each pagination page.
+
+
+### Toyota/index.md
+Simple category pagination page that only paginates cars having the category `sports` assigned to them. The configuration is simple being only
+
+``` yml
+---
+layout: home
+title: Toyota
+pagination: 
+  enabled: true
+  category: sports
+---
+```
+
+This configuration draws the paging permalink structure from the `_config.yml` file. Therefore the generated paging urls will be based on the folder name of the pagination page with the site configuration permalink added to it, like so:
+
+```
+Page 1: http://localhost:4000/toyota/
+Page 2: http://localhost:4000/toyota/page/2/
+Page N: http://localhost:4000/toyota/page/N/
+```
+
+### Categories/porsche.md
+This is a more complex category pagination including a permalink override for both the main page url and the pagination pages. The configuration for the page looks like this
+
+``` yml
+---
+layout: home
+title: Only Porsche
+permalink: /porsches/
+pagination: 
+  enabled: true
+  category: porsche
+  permalink: /:num/
+---
+```
+
+The paging will only list posts in the category `porsche`. The main difference here is that the url structure generated will look different because of the combined page and category permalink config in the main front-matter.
+
+```
+Page 1: http://localhost:4000/porsches/
+Page 2: http://localhost:4000/porsches/2/
+Page N: http://localhost:4000/porsches/N/
+```
+
+### Categories/byname.md
+This pagination page expands on the the first two examples by adding a custom sorting for the category pagination. It displays all cars but by alphabetical order by Car name.
+
+This configuration is achieved with the following front-matter configuration
+``` yml
+---
+layout: home
+title: By Name
+permalink: /name/
+pagination: 
+  enabled: true
+  category: cars
+  permalink: /:num/
+  sort_field: 'title'
+  sort_reverse: false
+---
+```
+
+The paging url structure will look similar to the example before
+
+```
+Page 1: http://localhost:4000/name/
+Page 2: http://localhost:4000/name/2/
+Page N: http://localhost:4000/name/N/
+```
+
+## Setup Configuration
+The gem is added to the `_config.yml` file under
+``` yml
+gems:
+  - jekyll-paginate-v2
+```
+
+as well as to the `Gemfile` into the main loop
+``` ruby
+group :jekyll_plugins do
+  gem "jekyll-paginate-v2"
+  gem "jekyll-feed"
+end
+```
+
+At this point is is advisable to delete the `Gemfile.lock` file to clear out any potential issues with gem caching and dependency issues (no worries this file will be auto generated for you again).
+
+
+Try building the site yourself using `jekyll build` or `jekyll serve`.
+
+Cheers :heart:

data/examples/02-category/_config.yml

@@ -0,0 +1,47 @@
+# Welcome to Jekyll!
+#
+# This config file is meant for settings that affect your whole blog, values
+# which you are expected to set up once and rarely edit after that. If you find
+# yourself editing these this file very often, consider using Jekyll's data files
+# feature for the data you need to update frequently.
+#
+# For technical reasons, this file is *NOT* reloaded automatically when you use
+# 'bundle exec jekyll serve'. If you change this file, please restart the server process.
+
+# Site settings
+# These are used to personalize your new site. If you look in the HTML files,
+# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
+# You can create any custom variable you would like, and they will be accessible
+# in the templates via {{ site.myvariable }}.
+title: Paginate Example - 02 Categories
+email: jekyll@sverrirs.com
+description: > # this means to ignore newlines until "baseurl:"
+  Shows how the jekyll-paginate-v2 gem can be used to paginate on categories.
+baseurl: "" # the subpath of your site, e.g. /blog
+url: "" # the base hostname & protocol for your site, e.g. http://example.com
+github_username:  sverrirs
+
+# Build settings
+markdown: kramdown
+theme: minima
+gems:
+  - jekyll-paginate-v2
+exclude:
+  - Gemfile
+  - Gemfile.lock
+  
+# Due to us using the categories for posts then it is advisable to explicitly specify a 
+# permalink structure for the site. Otherwise Jekyll attempts to organize the pages in folders
+# by the category names and it doesn't understand multi-categories to well :/
+permalink: /:year/:month/:title.html
+#permalink: pretty
+
+# Pagination Settings
+pagination:
+  enabled: true
+  per_page: 2
+  permalink: '/page/:num/'
+  title_suffix: ' - page :num'
+  limit: 0
+  sort_field: 'date'
+  sort_reverse: true

data/examples/02-category/_includes/header.html

@@ -0,0 +1,31 @@
+<header class="site-header" role="banner">
+
+  <div class="wrapper">
+
+    <a class="site-title" href="{{ "/" | relative_url}}">{{ site.title | escape }}</a>
+
+    <nav class="site-nav">
+      <span class="menu-icon">
+        <svg viewBox="0 0 18 15" width="18px" height="15px">
+          <path fill="#424242" d="M18,1.484c0,0.82-0.665,1.484-1.484,1.484H1.484C0.665,2.969,0,2.304,0,1.484l0,0C0,0.665,0.665,0,1.484,0 h15.031C17.335,0,18,0.665,18,1.484L18,1.484z"/>
+          <path fill="#424242" d="M18,7.516C18,8.335,17.335,9,16.516,9H1.484C0.665,9,0,8.335,0,7.516l0,0c0-0.82,0.665-1.484,1.484-1.484 h15.031C17.335,6.031,18,6.696,18,7.516L18,7.516z"/>
+          <path fill="#424242" d="M18,13.516C18,14.335,17.335,15,16.516,15H1.484C0.665,15,0,14.335,0,13.516l0,0 c0-0.82,0.665-1.484,1.484-1.484h15.031C17.335,12.031,18,12.696,18,13.516L18,13.516z"/>
+        </svg>
+      </span>
+
+      <div class="trigger">
+        {% for my_page in site.pages %}
+          <!--
+            my_page.autogen is populated by the pagination logic for all pages
+                            that are automatically created by the gem. Check for non-existence to exclude pagination pages from site.pages iterators
+          -->
+          {% if my_page.title and my_page.autogen == nil %}
+          <a class="page-link" href="{{ my_page.url | relative_url }}">{{ my_page.title | escape }}</a>
+          {% endif %}
+        {% endfor %}
+      </div>
+    </nav>
+
+  </div>
+
+</header>