j1-template 2020.0.21 → 2021.0.1

data/lib/starter_web/collections/posts/public/series/_posts/includes/documents/loop.sh

@@ -1,28 +0,0 @@
-#!/usr/bin/env bash
-
-FOLDER=/Users/jadams/test_files/
-TEST_FILES_PATH=${FOLDER}/files/
-FILE=name
-COUNT=3
-SIZE=1M
-SLICE=1M
-TYPE=random
-
-# Do write test of $COUNT files
-$(dd if=/dev/urandom bs=${SIZE} count=${COUNT} 2> ${FILE}.measures | split -b ${SLICE} - ${TEST_FILES_PATH}${FILE}.)
-
-dd_write=$(cat ${FILE}.measures | grep -v records | sed 's/.* s,//')
-echo ${dd_write}
-
-
-FILES=$(find ${TEST_FILES_PATH} -type f -print)
-
-for f in $FILES; do
-  # echo "Processing $f file..."
-  dd_read+=$(dd if=${f} of=/dev/null 2>&1 | grep -v records | sed 's/.* s,//')
-done
-
-echo ${dd_read}
-
-cd ..
-rm -f ${TEST_FILES_PATH}${FILE}\.*

data/lib/starter_web/collections/posts/public/test_posts/_posts/2020-09-11-test_post.adoc

@@ -1,134 +0,0 @@
----
-title:                                  Test Post
-tagline:                                test post
-description:
-
-date:                                   2020-09-11 00:00:00 +0100
-series:
-
-tags:                                   [ Test, Posts ]
-index:                                  [ Test, Posts ]
-categories:                             []
-
-regenerate:                             false
-
-resources:                              []
-resource_options:
-  - attic:
-      padding_top:                      400
-      padding_bottom:                   50
-      opacity:                          0.5
-      slides:
-        - url:                          /assets/images/collections/blog/wikipedia/minneapolis.1200x400.jpg
-          alt:                          Minnesota
----
-
-// Page Initializer
-// =============================================================================
-// Enable the Liquid Preprocessor
-:page-liquid:
-
-// Place an excerpt at the most top position
-// -----------------------------------------------------------------------------
-Minneapolis is the largest city in the state of Minnesota in the United States,
-and the county seat of Hennepin County. According to the United States Census
-Bureau, the city has a total area of 151.3 km² (58.4 mi²). 142.2 km² (54.9 mi²)
-of it is land and 9.1 km² (3.5 mi²) of it (6.01%) is water.
-
-[role="clearfix mb-3"]
-excerpt__end
-
-//  Load Liquid procedures
-// -----------------------------------------------------------------------------
-{% capture load_attributes %}themes/{{site.template.name}}/procedures/global/attributes_loader.proc{%endcapture%}
-
-// Load page attributes (all)
-// -----------------------------------------------------------------------------
-{% include {{load_attributes}} scope="all" %}
-
-// Additional Asciidoc page attributes goes here
-// -----------------------------------------------------------------------------
-//:page-imagesdir:                        {{page.images.dir}}
-
-
-// Page content
-// -----------------------------------------------------------------------------
-[[readmore]]
-== Physical
-
-[role="mb-3"]
-image::{image__wikipedia--minneapolis}[{{page.title}}]
-
-image::/assets/images/collections/blog/wikipedia/minneapolis.1200x400.jpg[{{page.title}}]
-
-Read: link:{url__wikipedia-en--minneapolis}[From Wikipedia, the free encyclopedia, window="_blank"].
-
-The Mississippi, which runs to the southeast, directed the early growth of the
-city. Most early streets ran parallel to the river to maximize the amount of
-land that could be used. Eventually, growth of Minneapolis turned to north-south
-and east-west streets.
-
-Many unique  intersections like Seven Corners on the eastern periphery of
-downtown were formed to translate between the two layouts. Some streets,
-especially older and more traditionally important ones like Hennepin Avenue
-and Nicollet Avenue, have both orientations at different points.
-
-== Parks and lakes
-
-Minneapolis has a large park system consisting of ten square miles (26 km²)
-of land and water that is interlinked in many places. Theodore Wirth is often
-credited with the development of this system that brought a playground within
-the reach of most children and the canopy of trees and boulevards in much of
-the city. The Mississippi National River and Recreation Area connects regional
-parks and visitors centers.
-
-Theodore Wirth Park is the largest in the city, shared with Golden Valley,
-and is about 60% the size of Central Park in New York City. Minnehaha Park
-is one of the most famous, the site of Minnehaha Falls and cultural heritage
-events every year. Tower Hill Park in Prospect Park is the home of a 1913
-water tower, one of the highest points in Minneapolis.
-
-The Grand Rounds Scenic Byway circles through the city and many of the larger
-park areas including land along the Mississippi, lakes and scenic areas.
-A parkway for cars, a bikeway for riders, and a walkway for pedestrians run
-parallel paths along the 50-mile route. A growing number of bikeways and
-walkways crisscross the city and interconnect with neighboring cities.
-
-Twenty four small lakes are within the city limits. Among the largest
-freshwater lakes to the west are Lake Harriet, Lake Calhoun, Lake of the
-Isles, and Cedar Lake, known together as the "Chain of Lakes". Lake Nokomis
-and Lake Hiawatha are to the east. Connected by bike, running and walking
-paths, Minneapolis lakes are used for swimming, fishing, picnics and boating.
-
-== Flora and fauna
-
-The area now occupied by the Twin Cities generally consisted of a 155 foot
-(47 m) thick layer of St. Peter Sandstone, under a 16 foot (5 m) thick layer
-of shale, under a 35 foot (11 m) thick layer of Platteville limestone.[4]
-These layers were the result of an Ordovician Period sea which covered
-east-central Minnesota 500 million years ago. The hard limestone cap
-was formed from fossilized shell fish. About 20,000 years ago, the area
-was covered by the Superior Lobe of the Laurentide ice sheet, which left
-the St. Croix moraine on the Twin Cities as it receded.
-
-Later the Grantsburg Sublobe of the Des Moines Lobe also covered the area.
-Under these vast layers of ice, tunnel valleys were formed, cutting through the
-limestone layer with tremendous force, to release ice meltwater and glacier
-effluence. The result was a series of troughs in the limestone, which
-were filled by glacial till and outwash deposit as the glaciers receded.
-Sometimes the sediment would be mixed with huge chunks of ice, which would
-leave voids in the soil. These voids created basins for the Twin Cities Lakes,
-such as Harriet and Lake Calhoun. Connecting the city lakes in several
-north-south arteries are gorges cut through the bedrock, but filled with
-sand and sediment.
-
-When River Warren Falls receded past the confluence of the much smaller
-Upper Mississippi River, a new waterfall was created where that river entered
-the much-lower glacial River Warren. The new falls also receded upstream on
-the Mississippi, migrating eight miles (12875 m) over 9600 years to where
-Louis Hennepin first saw it and named St. Anthony Falls in 1680. Due to its
-value as a power source, this waterfall determined the location of Minneapolis.
-One branch of the river coming from the west, Minnehaha Creek receded only a
-few hundred yards from one of the channels of the Mississippi. Minnehaha Falls
-remains as a picturesque and informative relic of River Warren Falls, and the
-limestone-over-sandstone construction is readily apparent in its small gorge.

data/lib/starter_web/collections/posts/public/wikipedia/_posts/000_includes/tables/debug_variables.asciidoc

@@ -1,48 +0,0 @@
-ifeval::["{debug}" == "true"]
-.Liquid variables
-[cols="2,4,6a, options="header", role="table-responsive, full-width"]
-|===============================================================================
-|name |value |description 
-
-|`page.path`
-|{{ page.path }}
-|The path to the raw post or page. Example usage: Linking back to the page 
-or post's source on GitHub. This can be overridden in the `YAML Front Matter`.
-
-|`site.collections_dir`
-|{{ site.collections_dir }}
-|lorem:sentences[1]
-
-|`page.images.dir`
-|{{ page.images.dir }}
-|Image path set pagewise. See FRONTMATTER defaults in `_config.yml` for the 
-images path specified by: `images.dir` for specific page *type*. See the 
-example below for a page of type *pages*.
-[source, yaml]
-----
-defaults:
-  - scope:
-      path:          pages
-      type:          pages
-
-    values:
-      images:
-        dir:        /assets/images/pages
-----
-
-|`page-imagesdir`
-|{{ page-imagesdir }}
-| Images path set in the page by `:page-imagesdir:`. 
-
-|`template`
-|{{ site.template.name }}
-|Name of the template used for rendering a page. Settings are taken from 
-sitewide configuration defined by `_config.yml`.
-
-|`includedir`
-|{{ includedir }}
-|lorem:sentences[1]
-
-|===============================================================================
-endif::[]
-

data/lib/starter_web/pages/public/bookshelf/100_whats_up.adoc

@@ -1,281 +0,0 @@
----
-layout:                                 page
-
-title:                                  What's up
-tagline:                                Jekyll Collections Overview
-description:                            Most powerful but least understood feature
-
-tags:                                   [ collections  ]
-index:                                  [ Jekyll, Collections, Overview]
-categories:                             [ collections ]
-
-permalink:                              /pages/public/collections/whats_up/
-regenerate:                             false
-
-tags:                                   [ Jekyll, Collections, Feature, Overview ]
-
-
-
-resource_options:
-  - attic:
-      padding_top:                      400
-      padding_bottom:                   50
-      opacity:                          0.5
-      slides:
-        - url:                          /assets/images/modules/attics/giammarco-boscaro-1920x1280.jpg
-          alt:                          giammarco-boscaro-1920x1280
-
-regenerate:                             false
----
-
-// Enable the Liquid Preprocessor
-//
-:page-liquid:
-
-// Set other global page attributes here
-// -------------------------------------------------------------------
-
-
-Collections are Jekyll's most powerful and simultaneously least understood
-feature. Collections add another possibility, or use-case, outside of Jekyll's
-post- and page-publishing functionality. Collections have the potential to
-bring Jekyll's zen-like simplicity to all sorts of other types of content that
-aren't ordered as with posts (ordered by date), but have a set *relationship*
-with one another - hence the name: _collection_.
-
-excerpt__end
-
-Source: https://ben.balter.com/2015/02/20/jekyll-collections/[Ben Balter: Jekyll Collections]
-
-[[readmore]]
-== Traditional - Posts and pages
-
-{% if page.image.name %}
-.{{page.tagline}}
-[role="mb-5"]
-image::{{page.image.name}}[{{page.title}}]
-{% endif %}
-
-Most Jekyll sites are organized around two types of content, posts (ordered)
-and pages (un-ordered).
-
-* *http://jekyllrb.com/docs/posts/[Posts]* are organized reverse
-chronologically. You might use them for blog posts on a personal blog,
-or articles on a news site. You can recognize a post by its filename.
-Posts live in the `_posts` folder, and are always named in the form of
-`YYYY-MM-DD-post-title.md`. Because posts are dated, they're
-traditionally not updated regularly once published.
-
-* *http://jekyllrb.com/docs/pages/[Pages]* are documents that don't have
-a relationship with one another. They can live anywhere within the
-site's source directory and don't have a set naming pattern. If you have
-a personal blog, you might have an `index.html` page
-(https://ben.balter.com/[the site's main page which is used to list
-posts]), or https://ben.balter.com/about/[an about me page], to name two
-examples. Because pages aren't date specific, pages are often updated
-over time to maintain accuracy.
-
-The problem is, not everything you might want to publish using a Jekyll
-falls cleanly into the those two categories of content. As I noted in
-https://github.com/jekyll/jekyll/issues/1941[the original pitch], "If
-people are using blog posts for a non-blog post thing, Jekyll has
-already failed". That's where Jekyll's
-http://jekyllrb.com/docs/collections/[collections] come in.
-
-
-== Not a post, a page - but a collection?
-
-Collections add another possibility, or use-case, outside of Jekyll's
-post- and page-publishing functionality. Collections have the potential to
-bring Jekyll's zen-like simplicity to all sorts of other types of content that
-aren't ordered as with posts (ordered by date), but have a set _relationship_
-with one another - hence the name: _collection_. If you're familiar with
-traditional CMS's, you can think of collections like
-http://codex.wordpress.org/Post_Types[WordPress custom post types] or
-https://www.drupal.org/node/774728[Drupal custom content types], except
-you do not need to program a specific class, learn any back-end
-languages, and the syntax used to specify them is very easily readable.
-
-What then, might you use collections for? Let's say you're making a
-website for a bakery and want to list the different cupcakes varieties
-you sell. You might use a collection called *cupcakes*. You'd create a
-`_cupcakes` folder, and would add `chocolate.md` or `vanilla.md` to it.
-And just like posts or pages, your list of cupcakes would be accessible
-as `site.cupcakes`.
-
-You wouldn't want to use posts here, because cupcakes aren't
-chronological, and likely wouldn't want to just use a page here, because
-it's a notably different animal than a document that lists your location
-and hours. Each cupcake in the cupcakes collection is related to
-one-another in the sense that they're all cupcakes.
-
-[NOTE]
-====
-Collections are a very new feature to Jekyll, and according to the
-official documentation may be subject to change
-http://jekyllrb.com/docs/collections/[Jekyll Documentation on
-Collections]; but you should not let that put you off of using them,
-because Jekyll is open-source, which means you should trust the
-community to work-together for the best common-case solution.
-====
-
-
-=== Collections in practice
-
-But what if one day you decided to expand your offerings and sell
-cookies in addition to cupcakes. Simply introduce a "cookies"
-collection, adding `chocolate-chip.md` and `peanut-butter.md` to a
-`_cookies` directory, exposing the cookies as `site.cookies`. You'll
-notice the collections concept start to show its value here. Pages
-wouldn't make sense here, because you'd want to be able to list cupcakes
-and cookies separately, and besides for both being baked goods, the one
-cookie doesn't really share a relationship with a cupcake, at least not
-in the same sense that cookies share with one another.
-
-Of course you could at this stage, choose to have a more generic
-collection `products`, which you could develop liquid layouts for, so
-that you and other developers could get the basic functionality needed
-to display all products, with specific includes for `cupcakes` and
-`cookies`.
-
-Abstractly, because they're not outputted by default, you can think of
-collections somewhat like http://jekyllrb.com/docs/datafiles/[Jekyll's
-`_data` folder support], but with the potential to generate content, and
-be placed into their own specific part of your Jekyll site, so a lot
-more robust. Like `_data` files, they can support arbitrary key/values
-through frontmatter, but they also support a full content body (like
-posts and pages), and can be broken out into separate files. If I wanted
-to break out my bakery's hours, I might have a `_data/hours.yml` file
-that looked something like this:
-
-[source,yaml]
-----
-monday: 9-5
-tuesday: 9-5
-wednesday: 9-5
-thursday: 9-5
-friday: 9-3
-----
-
-That makes sense, because my bakery's hours is a relatively small
-dataset. But trying to represent all my baked goods in that format (or
-worse posts), would quickly get out of hand. That type of information is
-better represented as individual markdown files with front matter, not
-one giant YAML file that will quickly become unwieldy with complexity;
-and rather than create the data, and pages to display the data, or the
-data and a plugin to turn it into pages; using collections allows the
-site owner to focus on the content.
-
-For a more concrete example, take a look at
-https://github.com/github/choosealicense.com[the source] for
-http://choosealicense.com[choosealicense.com] a site which helps explain
-open source licenses like the MIT or GPL license. There are pages like
-"about" and "terms of service", but the actual licenses live in
-https://github.com/github/choosealicense.com/tree/gh-pages/_licenses[a
-licenses collection] and are displayed via
-https://github.com/github/choosealicense.com/blob/gh-pages/licenses.html[a
-licensed page].
-
-=== Other use-cases
-
-Of course this is not the only use-case, which is one of the benefits of
-collections. You can turn on content generation to have the collection
-contents automatically generated, or use the where syntax to get the
-contents of specific collections to add common content, or devices to
-your site.
-
-
-== Using collections
-
-The examples above were a slight simplification. There's one other step.
-Before you can use a collection, you need to tell Jekyll about it. Going
-back to our bakery example above, I might have a `_config.yml` file that
-looks something like this:
-
-[source,yaml]
-----
-collections:
-  - cupcakes
-  - cookies
-----
-
-This tells Jekyll to look in the `_cupcakes` and `_cookies` folders
-for documents, and to read them into the appropriate collection, including
-http://jekyllrb.com/docs/frontmatter/[YAML front matter], just as it
-would posts (but again, without the date, because collection documents
-aren't date specific).
-
-By default, collections are read in (and exposed as `site.[collection]`,
-an alias per-collection), but not included in the final site; at least
-not individually like you might expect posts or pages to. If you wanted
-a page for each type of cupcake, you'd have to modify the `_config.yml`
-a bit:
-
-[source,yaml]
-----
-collections:
-  cupcakes:
-    output: true
-    permalink: /cupcakes/:path/
-----
-
-That way, `_cupcakes/chocolate.md` is outputted as
-`cupcakes/chocolate/index.html` when the site is built and would be
-accessible as `example.com/cupcakes/chocolate/`. The other advantage,
-is, because the data is now structured and machine readable (rather than
-in plain text), you could also use the `jsonify` filter to output that
-same information as an API for use elsewhere.
-
-
-=== When to use a post, a page, or a collection
-
-I like to think the decision looks roughly like this:
-
-[source,console]
-----
-+-------------------------------------+         +----------------+
-| Can the things be logically grouped?|---No--->|    Use pages   |
-+-------------------------------------+         +----------------+
-                |
-               Yes
-                |
-                V
-+-------------------------------------+         +----------------+
-|      Are they grouped by date?      |---No--->|Use a collection|
-+-------------------------------------+         +----------------+
-                |
-               Yes
-                |
-                V
-+-------------------------------------+
-|            Use posts                |
-+-------------------------------------+
-----
-
-So if you're not about to open a bakery (if you do, please send
-cookies); what might you use collections for? In short, any discrete
-group of "things" that can be logically grouped by a common theme
-(that's not their date). Here's a few examples:
-
-* Listing employees on your company's "about" page (or a project's
-maintainers)
-* Documenting methods in an open source project (or the project's that
-use it, or the plugins available)
-* Organizing jobs on your résumé (or talks given, papers written)
-* https://github.com/blog/1939-how-github-uses-github-to-document-GitHub[Articles
-on a support site]
-* Recipes on your personal blog (or restaurant reviews, or dishes on a
-menu)
-* Students in a class (or courses being offered, or listing the faculty)
-* Cheats, tips, tricks and walkthroughs for games (by platform)
-* Creating re-usable content snippets for your site such as
-testimonials, forms, sentences, buzz-words or call-outs
-* And honestly just about anything else
-
-Collections are a powerful (and often misunderstood) Jekyll feature, but
-hopefully you've now got an idea or two for your next Jekyll project. Of
-course, if you're looking to dig in to collections, be sure to check out
-http://jekyllrb.com/docs/collections/[the formal documentation] for a
-much more in-depth explanation.
-
-Happy Jekylling!