j1-template 2021.0.16 → 2021.1.0

data/lib/starter_web/collections/posts/public/featured/_posts/{2020-05-01-top-site-generators.adoc → 2021-03-01-site-generators.adoc}

@@ -1,19 +1,22 @@
 ---
-title:                                  Free site generators
-tagline:                                top site generators
-date:                                   2020-05-01 00:00:00
+title:                                  Site Generators
+tagline:                                top open source tools
+date:                                   2021-03-01 00:00:00
 
-tags:                                   [ Jekyll, Generators ]
 categories:                             [ Featured ]
+tags:                                   [ Jekyll, Generators ]
 
-series:
-adsense:                                false
+series:                                 false
 image:                                  /assets/images/modules/attics/machine-generator-1920x1280.jpg
+
+adsense:                                false
+comments:                               false
+advertising:                            false
 toc:                                    true
 
 regenerate:                             false
 
-resources:                              []
+resources:                              [ lightbox ]
 resource_options:
   - attic:
       padding_top:                      400
@@ -43,8 +46,9 @@ resource_options:
 // Place an excerpt at the most top position
 // -----------------------------------------------------------------------------
 This article highlights top OpenSource projects providing static site
-generators, in many different programming languages. And Jekyll is only one of
-them. Have a look if an flull-blown CMS is (really) needed for your project!
+generators in many different programming languages. And Jekyll is only
+one of them. Have a look if a full-blown CMS is (really) needed for your
+project!
 
 // [role="clearfix mb-3"]
 excerpt__end
@@ -55,7 +59,7 @@ excerpt__end
 
 // Load page attributes
 // -----------------------------------------------------------------------------
-{% include {{load_attributes}} scope="global" %}
+{% include {{load_attributes}} scope="all" %}
 
 
 // Page content
@@ -65,22 +69,32 @@ excerpt__end
 // -----------------------------------------------------------------------------
 
 [[readmore]]
-== Static Site Generators
+== Dynamic page access
 
-[role="mb-3"]
-image::/assets/images/collections/blog/featured/markus-spiske-2.jpg[{{page.title}}]
+// [role="mb-3"]
+// image::/assets/images/collections/blog/featured/markus-spiske-2.jpg[{{page.title}}]
+
+A typical CMS-driven website works by building each and every page
+*dynamically*. That means fetching the content from a database to pass them
+over to a template system (engine) to load the page content, adding the
+required structure information (e.g., CSS styles) and Javascript components if
+needed. This means every page is assembled *on demand*.
 
-A typical CMS driven website works by building each and every page dynamically.
-That means fetching the content from a database to pass them over to a template
-system for adding the required structure information (e.g. CSS styles).
-This means each page is assembled on demand.
+.Accessing scheme for a CMS (dynamic web)
+lightbox::kickstart-wiad--dynamic-web-access[ 800, {data-kickstart-wiad--dynamic-web-access} ]
 
-=== Is an CMS needed?
+callout::1["Web Browser"]
+callout::2["Web Server"]
+callout::3["Rendering Engine (e.g. PHP-based)"]
+callout::4["Database (e.g. MySQL, Postgres)"]
+callout::5["Static content (Images, Videos, JS- and CSS files) and Caches", ml-2 mb-3]
 
-For many, many websites dynamic page generation is entirely unnecessary and
-adds unwanted risks in terms of complexity, performance losses and security
-issues. After all, the content of most websites changes only, when the content
-authors make changes. Why the hell should a web page always assembled on
+== Is a CMS needed?
+
+For many websites, dynamic page generation is entirely unnecessary and
+adds unwanted risks in terms of complexity, performance losses, and security
+issues. After all, the content of most websites changes, when the content
+authors make changes. Why the hell should a web page always assemble on
 demand if there are no changes?
 
 NOTE: To be fair, most CMS are providing caching systems for web pages to
@@ -89,16 +103,29 @@ a caching strategy, and in the very end, it adds the next level of
 complexity.
 
 A Static Site Generator takes a different approach and generates all the pages
-of the website upfront. That does not necessarily mean that a static website
+of the website *upfront*. That does not necessarily mean that a static website
 is always built from scratch. Modern generators support a so-called
-incremental build; like Jekyll does. When there are changes detected to the
+incremental build, as does. When there are changes detected to the
 content, only selected pages will rebuild.
 
-This means overall, statically build web pages having no moving parts in the
-deployed website. This results in browser-side caching only, the performance
-goes up, and static sites are far more secure because they build already.
+.Accessing scheme for a static web
+lightbox::kickstart-wiad--static-web-access[ 800, {data-kickstart-wiad--static-web-access} ]
+
+callout::1["Web Browser"]
+callout::2["Web Server"]
+callout::3["Server-side rendered (prepared) static content", ml-2 mb-3]
+
+== Statically build web pages
+
+Overall, statically build web pages having no moving parts in the deployed
+website. This results in browser-side caching only, the performance
+goes up, and static sites are far more secure because they *build already*.
 To find out what OpenSource Static Site Generators are available today and
-their ranking in terms of popularity go for Jamstack You'll find the most
-complete list of generators used today.
+their ranking in terms of popularity, go for _Jamstack_. You'll find a
+comprehensive list of staic site generators used today.
+
+Check popular static site generators at {url-jamstack--generators}[Jamstack, {browser-window--new}]!
 
-Check with {url-jamstack--generators}[Jamstack, {browser-window--new}]!
+// .Current ratings at Jamstack (March 2021)
+[role="mb-3"]
+image::/assets/images/collections/blog/featured/jamstack-generators.gif["jamstack-generators"]

data/lib/starter_web/collections/posts/public/featured/_posts/2021-03-03-about-j1.adoc

@@ -0,0 +1,125 @@
+---
+title:                                  J1 Template
+tagline:                                first version is out
+date:                                   2021-03-03 00:00:00
+
+categories:                             [ Featured ]
+tags:                                   [ About, J1 ]
+
+series:                                 false
+image:                                  /assets/images/modules/attics/runner-1920x1200.jpg
+
+adsense:                                false
+comments:                               false
+advertising:                            false
+fam_menu_id:                            default
+toc:                                    false
+
+regenerate:                             false
+
+resources:                              []
+resource_options:
+  - attic:
+      padding_top:                      400
+      padding_bottom:                   50
+      opacity:                          0.5
+      slides:
+        - url:                          /assets/images/modules/attics/runner-1920x1200.jpg
+          alt:                          Photo by Alex Holyoake on Unsplash
+          badge:
+            type:                       unsplash
+            author:                     Alex Holyoake
+            href:                       https://unsplash.com/@stairhopper
+---
+
+// Page Initializer
+// =============================================================================
+// Enable the Liquid Preprocessor
+:page-liquid:
+
+// Set (local) page attributes here
+// -----------------------------------------------------------------------------
+// :page--attr:                         <attr-value>
+:badges-enabled:                        false
+
+
+// Place an excerpt at the most top position
+// -----------------------------------------------------------------------------
+The template system was initially developed to create a simple but fully
+configurable website creation toolset for document servers. Document servers
+provide websites or other content formats like PDF, projects, software
+documentation, or similar approaches.
+
+[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
+// -----------------------------------------------------------------------------
+{% include {{load_attributes}} scope="global" %}
+
+
+// Page content
+// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+// Include sub-documents
+// -----------------------------------------------------------------------------
+
+ifeval::[{badges-enabled} == true]
+{badge-j1--license} {badge-j1--version-latest} {badge-j1-gh--last-commit} {badge-j1--downloads}
+endif::[]
+
+// [[readmore]]
+Many large today's companies like {url-docker--docs}[Docker, {browser-window--new}]
+are using template-based systems to create their documentation sites. Or like
+{url-oreilly-atlas--home}[O'Reilly Atlas, {browser-window--new}],
+to provide a fully-featured writers platform for writing books or extensive
+documentation.
+
+All these platforms are technically different, but they share common ideas:
+
+* the layout of all content (pages) is based on a standard skeleton but
+  separated from the content
+* content is written using a neutral meta-language
+* the final output is not predefined
+* the result is automatically generated by engines (robots)
+
+To make these real, a lot of things are to be managed. You can imagine.
+The approaches of Docker or O'Reilly points to a possible solution: a template
+system based on _Bootstrap_ for the CCS framework, _Jekyll_ and _Liquid_ for
+the core engines, and _Asciidoc_ (Asciidoctor) for a neutral meta-language
+writing content.
+
+The next thought comes to my mind. Why developing a toolset for only
+document servers? Documentation webs of today are complex websites. Some
+features used for general web design may be not needed for documentation
+systems, but a lot of components are required that are wanted in general:
+
+* a powerful CSS and Javascript framework
+* a modular approach for dynamic content and apps
+* a configuration system to separate content from the layout and to automate
+  creation processes following the development pattern *MVC*
+  (https://blog.codinghorror.com/understanding-model-view-controller/[Model–View–Controller, {browser-window--new}])
+
+A plan was made in 2016, based on Jekyll V3 and Bootstrap V3, to create a
+template-based robot system that can be used for all types of websites, for
+all standard formats to create digital content.
+
+I was too optimistic about how long it would take to build such a system:
+
+* easy to use by developers and non-technical people
+* modular, powerful and stable
+* supporting modern content design
+* usable on common computer hardware, available to the public
+* less in components, using well-known software
+* entirely usable on small PCs locally as well as on powerful remote systems
+  on the Internet
+
+It took me nearly four years. Now, in early 2021, I can present the first
+version of J1 Template for the public. Hopefully, most of the objectives
+are achieved.
+
+Have fun!

data/lib/starter_web/collections/posts/public/featured/_posts/_includes/attributes.asciidoc

@@ -18,6 +18,10 @@ end::tags[]
 // DATA, local references to data elements (asciidoc extensions)
 // -----------------------------------------------------------------------------
 tag::data[]
+
+:data-kickstart-wiad--static-web-access:          "collections/blog/featured/static-web-access.png, Accessing scheme for a static web"
+:data-kickstart-wiad--dynamic-web-access:         "collections/blog/featured/dynamic-web-access.png, Accessing scheme for a CMS (dynamic web)"
+
 end::data[]
 
 // DOCUMENTS, local document resources (macro include::)

data/lib/starter_web/collections/posts/public/series/_posts/2020-01-02-post-test-series.adoc

@@ -5,8 +5,8 @@ date:                                   2020-01-02 00:00:00
 description: >
                                         Testing series elements
 
-tags:                                   [ Post, Test ]
 categories:                             [ Series ]
+tags:                                   [ Post, Test ]
 
 series:                                 test-series
 adsense:                                false

data/lib/starter_web/collections/posts/public/series/_posts/2020-01-03-post-test-series.adoc

@@ -5,8 +5,8 @@ date:                                   2020-01-03 00:00:00
 description: >
                                         Testing series elements
 
-tags:                                   [ Post, Test ]
 categories:                             [ Series ]
+tags:                                   [ Post, Test ]
 
 series:                                 test-series
 adsense:                                false

data/lib/starter_web/collections/posts/public/series/_posts/2020-01-04-post-test-series.adoc

@@ -5,8 +5,8 @@ date:                                   2020-01-04 00:00:00
 description: >
                                         Testing series elements
 
-tags:                                   [ Post, Test ]
 categories:                             [ Series ]
+tags:                                   [ Post, Test ]
 
 series:                                 test-series
 adsense:                                false

data/lib/starter_web/collections/posts/public/wikipedia/_posts/2016-11-20-minneapolis.adoc

@@ -3,8 +3,8 @@ title:                                  Minneapolis
 tagline:                                largest city in the state of minnesota
 date:                                   2016-11-20 19:16:49 +0100
 
-tags:                                   [ USA, Minnesota, City, Minneapolis ]
 categories:                             [ Wikipedia ]
+tags:                                   [ USA, Minnesota, City, Minneapolis ]
 
 regenerate:                             false
 

data/lib/starter_web/collections/posts/public/wikipedia/_posts/2016-11-24-narcisse-snake-dens.adoc

@@ -3,8 +3,8 @@ title:                                  Narcisse Snake Dens
 tagline:                                largest snake population
 date:                                   2016-11-24 00:00:00 +0100
 
-tags:                                   [ Canada, Cities ]
 categories:                             [ Wikipedia ]
+tags:                                   [ Canada, Cities ]
 
 regenerate:                             false
 

data/lib/starter_web/collections/posts/public/wikipedia/_posts/2016-11-26-columbia-river.adoc

@@ -3,8 +3,8 @@ title:                                  Columbia River
 tagline:                                largest river in the pacific northwest region
 date:                                   2016-11-26 00:00:00 +0100
 
-tags:                                   [ USA, Rivers ]
 categories:                             [ Wikipedia ]
+tags:                                   [ USA, Rivers ]
 
 regenerate:                             false
 

data/lib/starter_web/dot.gitattributes

@@ -13,5 +13,5 @@
 # ------------------------------------------------------------------------------
 
 # Enforce Unix newlines, all text files
-#
+# ------------------------------------------------------------------------------
 * text=auto eol=lf

data/lib/starter_web/dot.gitignore

@@ -14,6 +14,8 @@ Gemfile.lock
 
 Passengerfile.json
 
+google*.html
+
 tmp/
 
 \.bundle/
@@ -30,6 +32,8 @@ tmp/
 
 **/*.log
 
+**/*.current
+
 **/*.swp
 
 **/*_backup
@@ -38,7 +42,7 @@ tmp/
 # Never publish your sensitive personal and/or OAuth
 # data to any repo - not to public, not to any private.
 # ------------------------------------------------------------------------------
-.env
+private.yml
 
 
 # Unneeded files for the generated site

data/lib/starter_web/package.json

@@ -1,7 +1,7 @@
 {
   "private": true,
   "name": "j1_starter",
-  "version": "2021.0.16",
+  "version": "2021.1.0",
   "description": "J1 Template Starter Web",
   "homepage": "https://your.site",
   "author": {
@@ -58,6 +58,7 @@
     "app:rackup": "cross-env SINATRA_ACTIVESUPPORT_WARNING=false WEBSERVER=$npm_package_jekyll_opt_webserver INTERFACE=$npm_package_jekyll_opt_interface PORT=$npm_package_jekyll_opt_app_port j1 rackup",
     "app:jekyll": "cross-var cross-env JEKYLL_ENV=$npm_package_config_mode BUNDLE_GEMFILE=$npm_package_ruby_gemfile bundle exec jekyll b -c $npm_package_jekyll_configfile $npm_package_jekyll_opt_incremental --watch",
     "app:open": "npm run delay-3s && cross-var opn $npm_package_jekyll_opt_app_url",
+
     "delay-1s": "node ./node_modules/npm-delay 1000",
     "delay-2s": "node ./node_modules/npm-delay 2000",
     "delay-3s": "node ./node_modules/npm-delay 3000",
@@ -123,7 +124,7 @@
     "setup:detect-os": "echo Detect OS .. && cross-env if-env OS=Windows_NT && cross-var echo \"OS detected: $OS\" || OS=$(echo $(getos)) && echo \"OS detected: $OS\" && echo done.",
     "setup:site": "run-s -s build",
 
-    "site": "run-s site:*",
+    "site": "run-p -s site:*",
     "site:jekyll": "echo Startup the site .. && cross-env SINATRA_ACTIVESUPPORT_WARNING=false bundle exec jekyll s --incremental --livereload --livereload-port $npm_package_jekyll_opt_livereload_port --open",
     "site:utilsrv": "npm --prefix ./utilsrv --silent run utilsrv",
 

data/lib/starter_web/pages/public/asciidoc_skeletons/_templates/asciidoc-extensions/gallery.asciidoc

@@ -1,5 +1,5 @@
 // Find (JustifieGallery, jg) gallery configuration with:
-// ~/_data/apps/justified_gallery.yml
+// ~/_data/apps/justifiedGallery.yml
 
 //.Title
 gallery::jg_example[]

data/lib/starter_web/pages/public/asciidoc_skeletons/book/200_chapter.adoc

@@ -14,7 +14,7 @@ tags:                                   [ Skeleton, Book ]
 permalink:                              /pages/public/skeleton/book/chapter_2/
 regenerate:                             false
 
-resources:                              [ lightbox, light_gallery, justified_gallery ]
+resources:                              [ lightbox, lightGallery, justifiedGallery ]
 resource_options:
   - toccer:
       collapseDepth:                    3

data/lib/starter_web/pages/public/asciidoc_skeletons/book/book.adoc

@@ -16,7 +16,7 @@ tags:                                   [ Knowledge, Skeleton, Book ]
 permalink:                              /pages/public/skeleton/book/
 regenerate:                             false
 
-resources:                              [ lightbox, light_gallery, justified_gallery ]
+resources:                              [ lightbox, lightGallery, justifiedGallery ]
 resource_options:
   - toccer:
       collapseDepth:                    4

data/lib/starter_web/pages/public/asciidoc_skeletons/multi-document/200_chapter.asciidoc

@@ -14,7 +14,7 @@ tags:                                   [ Skeleton, Document ]
 permalink:                              /pages/public/skeleton/book/chapter_2/
 regenerate:                             false
 
-resources:                              [ lightbox, light_gallery, justified_gallery ]
+resources:                              [ lightbox, lightGallery, justifiedGallery ]
 resource_options:
   - toccer:
       collapseDepth:                    3

data/lib/starter_web/pages/public/asciidoc_skeletons/multi-document/multi.adoc

@@ -15,7 +15,7 @@ tags:                                   [ Knowledge, Skeleton, Document ]
 permalink:                              /pages/public/skeleton/multi/
 regenerate:                             false
 
-resources:                              [ lightbox, light_gallery, justified_gallery ]
+resources:                              [ lightbox, lightGallery, justifiedGallery ]
 resource_options:
   - toccer:
       collapseDepth:                    4