j1-template 2023.0.2 → 2023.0.5

data/lib/starter_web/pages/public/bookshelf/whats_up.adoc

@@ -0,0 +1,287 @@
+---
+layout:                                 page
+
+title:                                  What's up
+tagline:                                Jekyll Collections Overview
+date:                                   2020-11-03 12:00:00
+description: >
+                                        Jekyll Collections Overview
+categories:                             [ Jekyll, Collection ]
+tags:                                   [ Info, Overview ]
+
+fam:                                    true
+fam_menu_id:                            open_toc
+
+permalink:                              /pages/public/collections/whats_up/
+regenerate:                             false
+
+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
+---
+
+// Page Initializer
+// =============================================================================
+// Enable the Liquid Preprocessor
+:page-liquid:
+
+// Set page (local) attributes here
+// -----------------------------------------------------------------------------
+// :page--attr:                         <attr-value>
+
+// Place an excerpt at the most top position
+// -----------------------------------------------------------------------------
+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_.
+
+[role="clearfix mb-3"]
+excerpt__end
+
+
+// Content
+// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+[[readmore]]
+== Traditional - Posts and pages
+
+Source: https://ben.balter.com/2015/02/20/jekyll-collections/[Ben Balter: Jekyll Collections]
+
+{% 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 `&#x5F;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
+`&#x5F;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
+`&#x5F;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
+`&#x5F;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 `&#x5F;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 `&#x5F;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
+OpenSource 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/&#x5F;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 `&#x5F;config.yml` file that
+looks something like this:
+
+[source,yaml]
+----
+collections:
+  - cupcakes
+  - cookies
+----
+
+This tells Jekyll to look in the `&#x5F;cupcakes` and `&#x5F;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 `&#x5F;config.yml`
+a bit:
+
+[source,yaml]
+----
+collections:
+  cupcakes:
+    output: true
+    permalink: /cupcakes/:path/
+----
+
+That way, `&#x5F;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 OpenSource 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!

data/lib/starter_web/pages/public/previewer/preview_bootstrap_theme.adoc

@@ -2986,6 +2986,7 @@ endif::[]
   theme_slogans.UnoLight  = 'A touch of light';
   theme_slogans.UnoDark   = 'A night mode style';
   theme_slogans.Bootstrap = 'Bootstrap V5 default theme';
+  theme_slogans.Agency    = 'A popular Bootstrap V5 theme from StartBootstrap';
 
   theme_slogans.Cerulean  = 'A calm blue sky';
   theme_slogans.Cosmo     = 'An ode to Metro';

data/lib/starter_web/utilsrv/_defaults/package.json

@@ -1,7 +1,7 @@
 {
   "private": true,
   "name": "utls",
-  "version": "2023.0.2",
+  "version": "2023.0.5",
   "description": "J1 Theme Utility Server",
   "homepage": "https://jekyll.one",
   "author": {

data/lib/starter_web/utilsrv/package.json

@@ -1,7 +1,7 @@
 {
   "private": true,
   "name": "utls",
-  "version": "2023.0.2",
+  "version": "2023.0.5",
   "description": "J1 Theme Utility Server",
   "homepage": "https://jekyll.one",
   "author": {

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: j1-template
 version: !ruby/object:Gem::Version
-  version: 2023.0.2
+  version: 2023.0.5
 platform: ruby
 authors:
 - juergen_jekyll_one
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2023-01-05 00:00:00.000000000 Z
+date: 2023-01-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: jekyll
@@ -266,6 +266,7 @@ files:
 - _includes/themes/j1/procedures/blocks/footer/boxes/social_media_icons.proc
 - _includes/themes/j1/procedures/blocks/get_wave.proc
 - _includes/themes/j1/procedures/collections/create_collection_article_preview.proc
+- _includes/themes/j1/procedures/collections/pager.proc
 - _includes/themes/j1/procedures/global/attributes_loader.proc
 - _includes/themes/j1/procedures/global/collect_frontmatter_options.proc
 - _includes/themes/j1/procedures/global/collect_page_options.proc
@@ -916,22 +917,14 @@ files:
 - assets/themes/j1/core/css/icon-fonts/fontawesome.min.css
 - assets/themes/j1/core/css/icon-fonts/iconify.css
 - assets/themes/j1/core/css/icon-fonts/iconify.min.css
-- assets/themes/j1/core/css/icon-fonts/materialdesign-light.css
-- assets/themes/j1/core/css/icon-fonts/materialdesign-light.min.css
-- assets/themes/j1/core/css/icon-fonts/materialdesign.css
-- assets/themes/j1/core/css/icon-fonts/materialdesign.min.css
 - assets/themes/j1/core/css/icon-fonts/mdi.css
 - assets/themes/j1/core/css/icon-fonts/mdi.min.css
 - assets/themes/j1/core/css/icon-fonts/mdil.css
 - assets/themes/j1/core/css/icon-fonts/mdil.min.css
-- assets/themes/j1/core/css/icon-fonts/twemoji.css
-- assets/themes/j1/core/css/icon-fonts/twemoji.min.css
 - assets/themes/j1/core/css/nbinteract-tutorial/styles.css
 - assets/themes/j1/core/css/nbinteract-tutorial/styles.min.css
 - assets/themes/j1/core/css/themes/bootstrap/bootstrap.css
 - assets/themes/j1/core/css/themes/bootstrap/bootstrap.min.css
-- assets/themes/j1/core/css/themes/theme_vapor/bootstrap.css
-- assets/themes/j1/core/css/themes/theme_vapor/bootstrap.min.css
 - assets/themes/j1/core/css/themes/unodark/bootstrap.css
 - assets/themes/j1/core/css/themes/unodark/bootstrap.min.css
 - assets/themes/j1/core/css/themes/unolight/bootstrap.css
@@ -1585,6 +1578,7 @@ files:
 - assets/themes/j1/modules/sponsors/css/plans.css
 - assets/themes/j1/modules/themeSwitcher/LICENSE
 - assets/themes/j1/modules/themeSwitcher/README.md
+- assets/themes/j1/modules/themeSwitcher/js/_unsued/switcher.1.js
 - assets/themes/j1/modules/themeSwitcher/js/switcher.js
 - assets/themes/j1/modules/themeSwitcher/js/switcher.min.js
 - assets/themes/j1/modules/translator/css/translator.css
@@ -1902,6 +1896,7 @@ files:
 - lib/starter_web/_plugins/seo/j1-feed.rb
 - lib/starter_web/_plugins/seo/j1-seo-tags.rb
 - lib/starter_web/_plugins/seo/j1-sitemap.rb
+- lib/starter_web/assets/images/backgrounds/triangles-bg.png
 - lib/starter_web/assets/images/badges/configBinder.png
 - lib/starter_web/assets/images/badges/docsBinder.png
 - lib/starter_web/assets/images/badges/notebookBinder.png
@@ -1997,6 +1992,10 @@ files:
 - lib/starter_web/assets/images/icons/os/windows/windows_flags_color.ico
 - lib/starter_web/assets/images/icons/os/windows/windows_hdd.ico
 - lib/starter_web/assets/images/icons/os/windows/windows_store.ico
+- lib/starter_web/assets/images/icons/scalable/facebook.svg
+- lib/starter_web/assets/images/icons/scalable/google.svg
+- lib/starter_web/assets/images/icons/scalable/ibm.svg
+- lib/starter_web/assets/images/icons/scalable/microsoft.svg
 - lib/starter_web/assets/images/icons/social/amazon.png
 - lib/starter_web/assets/images/icons/social/behance.png
 - lib/starter_web/assets/images/icons/social/blogger.png
@@ -2418,7 +2417,6 @@ files:
 - lib/starter_web/assets/images/quotes/people.jpg
 - lib/starter_web/assets/images/sticker/600x600/sticker-new-version.png
 - lib/starter_web/assets/images/sticker/scalable/readme
-- lib/starter_web/assets/images/triangles-bg.png
 - lib/starter_web/assets/videos/gallery/dailymotion/meditation.jpg
 - lib/starter_web/assets/videos/gallery/dailymotion/pilates.jpg
 - lib/starter_web/assets/videos/gallery/html5/video1.mp4
@@ -2444,6 +2442,13 @@ files:
 - lib/starter_web/assets/videos/headers/present_videos/underground-broadway.mp4
 - lib/starter_web/assets/videos/tiktok/einhorn.jpg
 - lib/starter_web/assets/videos/tiktok/waluschka.jpg
+- lib/starter_web/collections/_biography/a-life-in-questions.adoc
+- lib/starter_web/collections/_biography/becoming.adoc
+- lib/starter_web/collections/_biography/born-to-run.adoc
+- lib/starter_web/collections/_biography/forty-autumns.adoc
+- lib/starter_web/collections/_biography/not-dead-yet.adoc
+- lib/starter_web/collections/_biography/princess-diarist-the.adoc
+- lib/starter_web/collections/_biography/when-breath-becomes-air.adoc
 - lib/starter_web/collections/asciidoc_skeletons/simple-post/_posts/yyyy-mm-dd-your-post-name.asciidoc
 - lib/starter_web/collections/posts/private/_posts/readme
 - lib/starter_web/collections/posts/protected/_posts/readme
@@ -2512,6 +2517,8 @@ files:
 - lib/starter_web/pages/public/blog/navigator/archive/dateview.html
 - lib/starter_web/pages/public/blog/navigator/archive/tagview.html
 - lib/starter_web/pages/public/blog/navigator/index.html
+- lib/starter_web/pages/public/bookshelf/viewer_biography.adoc
+- lib/starter_web/pages/public/bookshelf/whats_up.adoc
 - lib/starter_web/pages/public/features/general.adoc
 - lib/starter_web/pages/public/features/template.adoc
 - lib/starter_web/pages/public/learn/roundtrip/_includes/attributes.asciidoc