j1-template 2021.0.12 → 2021.1.0

data/lib/starter_web/collections/posts/public/featured/_posts/{2020-06-01-about-cookies.adoc → 2020-01-01-about-cookies.adoc}

@@ -1,16 +1,18 @@
 ---
 title:                                  Cookies
 tagline:                                good to know
-date:                                   2020-06-01 00:00:00
+date:                                   2020-01-01 00:00:00
 
-tags:                                   [ About, Cookies ]
 categories:                             [ Featured ]
+tags:                                   [ About, Cookies ]
 
-series:
-adsense:                                false
+series:                                 false
 image:                                  /assets/images/modules/attics/cookies-1920x1200-bw.jpg
-comments:                               true
-advertising:                            true
+
+adsense:                                false
+comments:                               false
+advertising:                            false
+toc:                                    true
 
 regenerate:                             false
 
@@ -47,10 +49,9 @@ resource_options:
 
 // Place an excerpt at the most top position
 // -----------------------------------------------------------------------------
-Is it needed for visitors to know what cookies are about? No doubts, your're
-requested to inform - in Europe for legal reasons. All users visiting web sites
-are bothered all the time to accept on cookies. Cookies are used by sites
-of today. For good reasons?
+Is it needed for visitors to know what cookies are about? No doubts, you're
+requested to inform - in Europe for legal reasons. All users visiting websites
+are bothered all the time to accept cookies. For good reasons?
 
 [role="clearfix mb-3"]
 excerpt__end
@@ -70,10 +71,10 @@ excerpt__end
 // Include sub-documents
 // -----------------------------------------------------------------------------
 
-[[readmore]]
+// [[readmore]]
 == What are cookies technically
 
-In short words. A cookie is a small piece of data that a website asks your
+In short: a  cookie is a small piece of data that a website asks your
 browser to store on your computer or mobile device. The cookie allows the
 website to "remember" your actions or preferences over time. All modern
 browsers support cookies, but users can set their browsers to decline them
@@ -88,35 +89,35 @@ General information storage::
 Remember users' custom preferences
 
 Support::
-Help users complete tasks without having to re‑enter information
-when browsing from one page to another or when visiting the site later.
+Help users complete tasks without re-entering information when browsing from
+one page to another or when visiting the site later.
 
-Track behavioural::
-Cookies can also be used for online behavioural target advertising and to
+Track behavioral::
+Cookies can also be used for online behavioral target advertising and to
 show adverts relevant to something that the user searched for in the past.
-The web server supplying the webpage can store a cookie on the user's
+The webserver supplying the webpage can store a cookie on the user's
 computer or mobile device.
 
-All these cookies are called http header cookies. Another way of storing
-cookies is through JavaScript code contained or referenced in that page.
-Each time the user requests a new page, the web server can receive the
+All these cookies are called HTTP header cookies. Another way of storing
+cookies is through JavaScript code contained or referenced on that page.
+Each time the user requests a new page, the webserver can receive the
 values of the cookies it previously set and return the page with content
-relating to these values. Similarly, JavaScript code is able to read a
-cookie belonging to its domain and perform an action accordingly.
+relating to these values. Similarly, JavaScript code can read a
+cookie belonging to its domain and act accordingly.
 
 .How are they used
 [NOTE]
 ====
 The web server supplying the webpage can store a cookie on the user's
-computer or mobile device. An external web server that manages files included
-or referenced in the webpage is also able to store cookies. All these
-cookies are called http header cookies. Another way of storing cookies is
-through JavaScript code contained or referenced in that page.
+computer or mobile device. An external web server that manages files
+included or referenced in the web page can store cookies. All these
+cookies are called HTTP header cookies. Another way of storing cookies
+is through JavaScript code contained or referenced on that page.
 
 Each time the user requests a new page, the web server can receive the
 values of the cookies it previously set and return the page with content
-relating to these values. Similarly, JavaScript code is able to read a
-cookie belonging to its domain and perform an action accordingly.
+relating to these values. Similarly, JavaScript code can read a
+cookie belonging to its domain and act accordingly.
 ====
 
 == Types of cookies
@@ -124,7 +125,7 @@ cookie belonging to its domain and perform an action accordingly.
 HTTP cookies are essential to the modern Internet but potentially a
 vulnerability to your privacy. As a necessary part of web browsing, cookies
 help web developers give you more personal, convenient website visits.
-Cookies let websites remember you, your website logins, shopping carts and
+Cookies let websites remember you, your website logins, shopping carts, and
 more. But they can also be a treasure trove of private info for criminals
 to spy on.
 
@@ -152,37 +153,38 @@ period of time.
 Cookies classified by the *domain* to which it belongs, are either of:
 
 First-party cookie::
-First-party cookie cookies are set by the web server of the visited page
-and share the *same domain* you're visting. These are generally safer, as
+First-party cookie cookies are set by the webserver of the visited page
+and share the *same domain* you're visiting. These are generally safer, as
 long as users are browsing reputable websites or ones that have not been
 compromised.
 
 Third-party cookies::
 Third-party cookies are stored by a *different* domain to the visited page.
-This can happen when the webpage references a files located outside its domain.
+This can happen when the webpage references a file located outside its domain.
 Third-party cookies let advertisers or analytics companies track the user's
 browsing history across the web on *any* sites that contain their ads.
 
+
 == Security aspects on using cookies
 
-Without cookies the web would not work as it does today. However, since the
-mid 90ies when cookies were invented, the web changed quite a lot and so did
-the attack methods on web applications; as mentioned the internet is not a
+Without cookies, the web would not work as it does today. However, since the
+mid 90ies when cookies were invented, the web changed quite a lot, and so did
+the attack methods on web applications; as mentioned, the Internet is not a
 friendly place.
 
-A well-known attack method is known as Cross Site Request Forgery, or short
+A well-known attack method is known as Cross-Site Request Forgery or short
 *CSRF*. CSRF is an attack, a criminal act, that forces an end user to execute
-unwanted actions. Cookie may play a *role* in such scenarios but they are
-not generally *unsafe*. If you want you can read more about that in the
+unwanted actions. A cookie may play a *role* in such scenarios, but they are
+not generally *unsafe* if you want, you can read more about that on the
 CRSF Page on {url-owasp-attacks--csrf}[OWASP, {browser-window--new}].
 
 == How to control cookies
 
 Users can take control, used or *not* used, or delete cookies. For more
 details, see {url-about-cookies--home}[AboutCookies]. You can delete
-all cookies that are already on your computer and you can set most
+all cookies that are already on your computer, and you can set most
 browsers to prevent them from being placed.
 
 If you do this, however, you may have to manually adjust some preferences
-every time you visit a site and some services and functionalities may not
+every time you visit a site, and some services and functionalities may not
 work.

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,10 +46,11 @@ 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"]
+// [role="clearfix mb-3"]
 excerpt__end
 
 //  Load Liquid procedures
@@ -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-01-post-test-series.adoc

@@ -4,14 +4,14 @@ tagline:                                testing series elements
 date:                                   2020-01-01 00:00:00
 description: >
 
-tags:                                   [ Post, Test ]
 categories:                             [ Series ]
+tags:                                   [ Post, Test ]
 
 series:                                 test-series
 adsense:                                false
 comments:                               false
 toc:                                    true
-exclude_from_search:                    true
+exclude_from_search:                    false
 
 regenerate:                             false
 
@@ -39,9 +39,12 @@ resource_options:
 
 // Place an excerpt at the most top position
 // -----------------------------------------------------------------------------
-Testing series elements.
 
-[role="clearfix mb-3"]
+This post is a *test series element*. Post series can help to split larger
+posts into a group of smaller articles. This may helpful, if a large post
+should be split into several *main chapters* but grouped together.
+
+// [role="clearfix"]
 excerpt__end
 
 //  Load Liquid procedures
@@ -59,7 +62,7 @@ excerpt__end
 // Include sub-documents
 // -----------------------------------------------------------------------------
 
-[[readmore]]
+// [[readmore]]
 == The Extremes of Good and Evil
 
 .Release Loeb Classical Library, Harvard University Press, edition, 1931