j1-template 2021.0.15 → 2021.1.3

data/lib/starter_web/collections/posts/public/featured/_posts/0000-00-00-welcome-to-j1.adoc.erb

@@ -1,18 +1,14 @@
 ---
 title:                                  Welcome
 tagline:                                jekyll for everyone
-date:                                   <%= Time.now.strftime('%Y-%m-%d') %> 00:00:00
+#date:                                  <%= Time.now.strftime('%Y-%m-%d') %> 00:00:00 +0100
 
-tags:                                   [ Example, Post ]
-categories:                             [ Featured ]
+categories:                             [ Featured, Post ]
+tags:                                   [ J1, Jekyll ]
 
-series:                                 false
-adsense:                                false
 image:                                  /assets/images/modules/attics/katie-moum-1920x1280.jpg
-toc:                                    true
 
 regenerate:                             false
-
 resources:                              []
 resource_options:
   - attic:
@@ -38,10 +34,11 @@ resource_options:
 
 // Place an excerpt at the most top position
 // -----------------------------------------------------------------------------
-All you're doing at the end of the day is writing your content and Jekyll does
-all the tricky things needed for a website: putting out HTML, Javascript and
-CSS. As a result, the site creation process gets out of your way. Sounds fun,
-isn't it?
+All you’re doing at the end of the day is writing your content, and the J1
+Template does all the tricky things: putting out HTML, Javascript, and CSS.
+As a result, the site creation process gets out of your way.
+
+Sounds fun, isn't it?
 
 // [role="clearfix mb-3"]
 excerpt__end
@@ -70,13 +67,10 @@ which use a database to load dynamic content, a static site will display
 the same content to every user as it will directly load the HTML files
 on the server.
 
-A static website uses server-side rendering to serve pre-built HTML, CSS,
-and JavaScript files to a web browser, in contrast to traditional dynamic
-sites that work by rendering the webpage at the time of the request.
-Static sites enable you to decouple your content repository and front-end
-interface, giving you greater flexibility in how your content is served.
-Cost-efficiency is another reason companies migrate to a static site because
-static files are lightweight and often faster and cheaper to serve.
+A static site serves the content straight to the user as it is stored on
+the server-side. In opposition to WordPress, which uses a database to load
+dynamic content, a static site will display the same content to every user
+as it will directly load the HTML files on the server.
 
 In the last few years, static sites have greatly increased in popularity.
 This surge is primarily due to advances in developer tools (languages and
@@ -85,15 +79,14 @@ performance beyond the limits of a database-driven site.
 
 === What's different?
 
-To make it simple, a dynamic website uses a database and PHP/MySQL to
-generate the content of a page when a user requests it. For example,
-building a website using WordPress CMS will result in having a dynamic
-Website.
+A dynamic website uses a database and PHP/MySQL to generate the content of
+a page when a user requests it. For example, building a website using
+WordPress CMS will result in having a dynamic Website.
 
 Static sites can be written almost exclusively in HTML and serve a fixed
 set of data that renders the same for every site visitor. Static sites use
 server-side rendering to serve pre-built HTML, CSS, and JavaScript files to
-a web browser. Dynamic sites operate in a completely different way, by
+a web browser. Dynamic sites operate in a completely different way by
 leveraging HTML and CSS as well as server-side scripting languages like PHP
 to build webpages on the fly and serve different content to each site
 visitor.
@@ -101,9 +94,9 @@ visitor.
 === Why use a static site?
 
 What are the advantages of a static website over a dynamic site?
-You may be wondering *Why should I build a static site when I could do a
-WordPress?*. Well, having a database implies a lot of downsides. Here
-come the main advantages of using a static site over a dynamic
+You may be wondering *Why should I build a static site when I could do the
+same by using WordPress?*. Well, having a database implies a lot of downsides.
+Here come the main advantages of using a static site over a dynamic
 one.
 
 Performance::
@@ -113,45 +106,45 @@ it is crazy fast to load. Indeed, when the user requests a page, there is
 no need to request a database and various files to generate the
 page itself as all the content is already placed in a one and only file:
 an HTML one. That’s why by using a static site, you will get a boost in
-your loading time that will provide great user experience for the
+your loading time that will provide a great user experience for the
 internauts. Moreover, we know that more and more people are surfing the
-web using their smartphones with, sometimes, poor internet connections,
-that’s why having fast loading times will participate in making your
+web using their smartphones with, sometimes, poor internet connections.
+That’s why having fast loading times will participate in making your
 website mobile-friendly.
 
 Security::
 *Having a static website: say goodbye to hacking and security issues*.
-Tired of getting WordPress notifications about security issues and
-updates every week? No worries, as a static site has no database, there
-are close to no hack possible compared to a WordPress website. Indeed,
-your site will have way fewer footprints and security issues since it
-will only load plain HTML and CSS files. The security gain in having a
-static website is one the main reason why many famous brands switch to
-a static site instead of having their website on Drupal or WordPress.
+Are you tired of getting WordPress notifications about security issues and
+updates every week? No worries, as a static site has no database, there are
+close to no hack possible compared to a WordPress website. Indeed, your
+site will have way fewer footprints and security issues since it will
+only load plain HTML and CSS files. The security gain in having a static
+website is one of the main reasons why many famous brands switch to a
+static site instead of having their website on Drupal or WordPress.
 
 Hosting::
 *Building a static site and hosting: you will save you money*.
-Using a static site, you will only have most of the time only HTML and
-CSS files to host. This kind of files is super light which also means
-that you will not need a powerhouse hosting to have a static site up and
-running. Moreover, if your traffic suddenly increases, your site will not
-go down contrary to a dynamic site which should request the database
-each time for each user.
+Using a static site, you will only have most of the time only HTML and CSS
+files to host. This kind of file is super light which also means that you
+will not need a powerhouse hosting to have a static site up and running.
+Moreover, if your traffic suddenly increases, your site will not go down,
+contrary to a dynamic site that should request the database each time
+for each user.
 
 Control::
-*You're the master*. Using a CMS means, giving control over your site to others.
-Simple like this.
+*You're the master*. You were using a CMS means, giving control over your
+site to others. Simple like this.
 
 == Why use a site generator?
 
 Working with pure HTML files is annoying; senseless today. Indeed, if you need
 to make a modification on your *self-managed* pages, you have to manually
 change every file. That's monkey's work from the early days of static websites.
-If your site comes with 10 pages, it can be manageable but imagine if your site
-is providing 100+ pages or the blog planned for hundreds of articles?
+If your site comes with ten pages, it can be manageable but imagine if your
+site is providing 100+ pages or the blog planned for hundreds of articles?
 
 Using a static site generator will solve this issue as it separates the
-content and the template. To say it another way, by using a static site
+content and the Template. To say it another way, by using a static site
 generator, you will only need to make the modification once, and the
 generator will apply it to all your pages.
 
@@ -164,6 +157,6 @@ better depending on the programming languages you already are familiar with.
 Which static site generator should I use?
 
 When I decided to go for a blog based on a static web, I personally
-choose Jekyll as for me. It's a well known static site generator, good support
-in case of trouble and the software gets regularly updated. This website is
+choose Jekyll as for me. It's a well-known static site generator, good support
+in case of trouble, and the software gets regularly updated. This website is
 powered by Jekyll. For good reasons.

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

@@ -1,16 +1,11 @@
 ---
 title:                                  Cookies
 tagline:                                good to know
-date:                                   2020-06-01 00:00:00
 
-tags:                                   [ About, Cookies ]
-categories:                             [ Featured ]
+categories:                             [ Featured, Post ]
+tags:                                   [ Cookies ]
 
-series:
-adsense:                                false
 image:                                  /assets/images/modules/attics/cookies-1920x1200-bw.jpg
-comments:                               true
-advertising:                            true
 
 regenerate:                             false
 
@@ -47,12 +42,11 @@ 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"]
+[role="clearfix mb-3"]
 excerpt__end
 
 //  Load Liquid procedures
@@ -70,10 +64,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 +82,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 +118,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 +146,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,15 @@
 ---
-title:                                  Free site generators
-tagline:                                top site generators
-date:                                   2020-05-01 00:00:00
+title:                                  Site Generators
+tagline:                                top open source tools
 
+categories:                             [ Featured, Post ]
 tags:                                   [ Jekyll, Generators ]
-categories:                             [ Featured ]
 
-series:
-adsense:                                false
 image:                                  /assets/images/modules/attics/machine-generator-1920x1280.jpg
-toc:                                    true
 
 regenerate:                             false
 
-resources:                              []
+resources:                              [ lightbox ]
 resource_options:
   - attic:
       padding_top:                      400
@@ -43,8 +39,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 +52,7 @@ excerpt__end
 
 // Load page attributes
 // -----------------------------------------------------------------------------
-{% include {{load_attributes}} scope="global" %}
+{% include {{load_attributes}} scope="all" %}
 
 
 // Page content
@@ -65,22 +62,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 +96,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 with {url-jamstack--generators}[Jamstack, {browser-window--new}]!
+Check popular static site generators at {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"]