j1-template 2021.0.10 → 2021.0.11

data/lib/starter_web/pages/public/learn/roundtrip/400_asciidoc_extensions.adoc

@@ -282,9 +282,6 @@ mdi:font-awesome[2x, ml-3 mr-2 mb-2] Brand icon +
 mdi:apple[2x, md-indigo ml-3 mr-2] Brand icon (colored)
 ====
 
-Find all MDI Icons on page
-link:{previewer-mdi}[MDI Icon Previewer, {browser-window--new}].
-
 NOTE: Parameters `icon_size` and `modifier` are optional. If not given,
 the icons `size` is set to default  (`1x`), the color to `black` and no
 settings for the `modifier` are applied.
@@ -391,10 +388,6 @@ This is an example of how you can emoji:heart[2x, pulsed mt-1] Asciidoctor
 and Twitter Emoji emoji:smile[].
 ====
 
-Find all Twitter Emoji's build-in with J1 Template on page
-link:{previewer-emoji}[Emoji Icon Previewer, {browser-window--new}].
-
-
 == Blind Text (Lorem)
 
 The Ruby Gem Middleman, a Ruby-gem based static site generator, provides a

data/lib/starter_web/pages/public/learn/where_to_go.adoc

@@ -51,10 +51,10 @@ resource_options:
 
 // Page content
 // ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
 Welcome to the pages of J1 Template. If your here first time, a good decision
 you get on that page first. For sure, there is no better place to go.
 The crucial first step in to find your way to Jekyll is done. Congratulations.
-
 The *Learn* section contains all you need to learn what Jekyll and J1 can do
 for your website. For your new static web - if you like.
 
@@ -63,26 +63,16 @@ With this section you'll find a *tour* to show some of the main features of
 the template system *J1*. The tour covers how image data can be managed using
 J1, some background of the typography the template is using, discuss important
 extensions and some more what J1 can do. The roundtrip is a *visual* tour.
-No technical stuff, nothing academic.
-
-Asciidoc Skeletons::
-AsciiDoc is a human-readable document format using plain-text mark-up
-conventions. AsciiDoc documents can be created using any text editor and
-read *as-is*. J1 template renders Asciidoc code to HTML, your future awesome
-web pages. J1 is using *Asciidoc* for writing content. Documents in a web may
-simple in structure, but may also grow complex for e.g multi-chapter pages.
-The skeletons are discussed in the tutorial *Web in a Day* as a base for
-your content.
-
-You should go for *first* the *Roundtrip*. See what you will get. As an
+No technical stuff, nothing academic. See what you will get. As an
 overview of some of the main features of *J1*.  If you like, continue by
 walking through the roundtrip examples
 link:/pages/public/learn/roundtrip/present_images/[by starting the tour here].
 
+Web in a Day::
 To go deeper, your're invited to *Web in a Day*. This tutorial guides you
 through all the steps to build a website using Jekyll and the template system
 J1. The guide let you go more in-depth and make things real. You dive into
 the world of Jekyll. You'll have learned a lot at the end of that day about
-what Jekyll is, static webs and the template system J1 is all about.
-Try out the journey having some hours of fun at
+what Jekyll is, static webs and the template system J1 is all about. To go
+deeper, your're invited, try out the journey having some hours of fun at
 {url-j1-web-in-a-day--meet-and-greet}[Web in a Day, {browser-window--new}].

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

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

data/lib/starter_web/utilsrv/package.json

@@ -1,7 +1,7 @@
 {
   "private": true,
   "name": "utls",
-  "version": "2021.0.10",
+  "version": "2021.0.11",
   "description": "J1 Template 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: 2021.0.10
+  version: 2021.0.11
 platform: ruby
 authors:
 - juergen_jekyll_one
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2021-02-20 00:00:00.000000000 Z
+date: 2021-02-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: jekyll
@@ -852,7 +852,6 @@ files:
 - lib/j1/log_helper.rb
 - lib/j1/patches/rubygems/eventmachine-1.2.7-x64-mingw32/lib/2.6/fastfilereaderext.so
 - lib/j1/patches/rubygems/eventmachine-1.2.7-x64-mingw32/lib/2.6/rubyeventmachine.so
-- lib/j1/templates/posts/0000-00-00-welcome-to-j1-template.adoc.erb
 - lib/j1/utils.rb
 - lib/j1/utils/ansi.rb
 - lib/j1/utils/exec.rb
@@ -1058,12 +1057,14 @@ files:
 - lib/starter_web/assets/images/modules/attics/ideas-start-here-1920x1280-bw.jpg
 - lib/starter_web/assets/images/modules/attics/jason-rosewell-1920x1280.jpg
 - lib/starter_web/assets/images/modules/attics/jessica-ruscello-1920x1280.jpg
+- lib/starter_web/assets/images/modules/attics/joel-filipe-1920x1280.jpg
 - lib/starter_web/assets/images/modules/attics/katie-moum-1920x1280.jpg
 - lib/starter_web/assets/images/modules/attics/lianhao-1920x1280.jpg
 - lib/starter_web/assets/images/modules/attics/library-1920x1280-bw.jpg
 - lib/starter_web/assets/images/modules/attics/machine-generator-1920x1280.jpg
 - lib/starter_web/assets/images/modules/attics/mae-mue-1920x1280-v.jpg
 - lib/starter_web/assets/images/modules/attics/mae-mue-1920x1280.jpg
+- lib/starter_web/assets/images/modules/attics/markus-spiske3-1920x1280.jpg
 - lib/starter_web/assets/images/modules/attics/matthaeus-1920x1280.jpg
 - lib/starter_web/assets/images/modules/attics/modules-apps-1920x1280.jpg
 - lib/starter_web/assets/images/modules/attics/nicola-styles-1920x1280.jpg
@@ -1379,7 +1380,6 @@ files:
 - lib/starter_web/collections/posts/public/featured/_posts/0000-00-00-welcome-to-j1.adoc.erb
 - lib/starter_web/collections/posts/public/featured/_posts/2020-05-01-top-site-generators.adoc
 - lib/starter_web/collections/posts/public/featured/_posts/2020-06-01-about-cookies.adoc
-- lib/starter_web/collections/posts/public/featured/_posts/2021-01-01-welcome-to-j1.adoc
 - lib/starter_web/collections/posts/public/featured/_posts/_includes/attributes.asciidoc
 - lib/starter_web/collections/posts/public/featured/_posts/_includes/documents/readme
 - lib/starter_web/collections/posts/public/featured/_posts/_includes/tables/readme
@@ -1477,17 +1477,10 @@ files:
 - lib/starter_web/pages/public/learn/roundtrip/_includes/documents/419_advanced_modals_demo.asciidoc
 - lib/starter_web/pages/public/learn/roundtrip/_includes/documents/tables/bs_modal_examples.asciidoc
 - lib/starter_web/pages/public/learn/where_to_go.adoc
-- lib/starter_web/pages/public/legal/de/100_impress.adoc
-- lib/starter_web/pages/public/legal/de/200_terms_of_use.adoc
-- lib/starter_web/pages/public/legal/de/300_privacy.adoc
-- lib/starter_web/pages/public/legal/de/400_license_agreement.adoc
-- lib/starter_web/pages/public/legal/de/500_support.adoc
 - lib/starter_web/pages/public/legal/en/000_copyright.adoc
 - lib/starter_web/pages/public/legal/en/100_impress.adoc
 - lib/starter_web/pages/public/legal/en/200_terms_of_use.adoc
 - lib/starter_web/pages/public/legal/en/300_privacy.adoc
-- lib/starter_web/pages/public/legal/en/400_license_agreement.adoc
-- lib/starter_web/pages/public/legal/en/500_support.adoc
 - lib/starter_web/pages/public/legal/en/eu/cookie.policy.asciidoc
 - lib/starter_web/pages/public/panels/intro_panel/panel.adoc
 - lib/starter_web/pages/public/previewer/_includes/attributes.asciidoc

data/lib/j1/templates/posts/0000-00-00-welcome-to-j1-template.adoc.erb

@@ -1,72 +0,0 @@
----
-title:                                  Welcome
-tagline:                                jekyll to everyone
-description:                            Auto-generated welcome post
-
-date:                                   <%= Time.now.strftime('%Y-%m-%d %H:%M:%S %z') %>
-series:
-image:                                  /assets/images/modules/attics/welcome-1920x1280-bw.png
-
-tags:                                   [ Example, Post ]
-index:                                  []
-categories:                             [ featured ]
-
-#permalink:
-regenerate:                             false
-
-resources:                              []
-resource_options:
-  - attic:
-      padding_top:                      350
-      padding_bottom:                   50
-      opacity:                          0.5
-      slides:
-        - url:                          /assets/images/modules/attics/welcome-1920x1280-bw.png
-          alt:                          welcome-1920x1280-bw
----
-
-// TODO:  For POSTS, currently the include:: macro does NOT work.
-// Path calculation needes to be fixec (includes the document file name) 
-// -----------------------------------------------------------------------------
-
-// NOTE:  General Asciidoc page attributes settings
-// -----------------------------------------------------------------------------
-:page-liquid:
-
-// Additional Asciidoc page attributes goes here
-// -----------------------------------------------------------------------------
-// :page-imagesdir: {{page.images.dir}}
-
-
-// NOTE: Place an excerpt at the most top position
-// -----------------------------------------------------------------------------
-Welcome to Jekyll and J1 Template!
-
-You’ll find this example post, automatically generated, in *featured* posts
-folder under /collections/posts/public/featured/_posts. Go ahead and edit and  
-re-build the site to see your changes.
-
-You can rebuild the site in many different ways, but the most common way is
-to run `jekyll serve`, which launches a web server and auto-regenerates your
-site when a file is updated.
-
-[role="clearfix mb-3"]
-excerpt__end
-
-
-// Page content
-// -----------------------------------------------------------------------------
-[[readmore]]
-== Add new posts
-
-[role="mb-3"]
-// image::{{page.image}}[{{page.title}}]
-// image::/assets/images/modules/attics/runner-1920x1200-bw.png[{{page.title}}, 800]
-
-To add new posts, simply add a file in the directory 
-`/collections/posts/public/featured/_posts` that follows the convention 
-`YYYY-MM-DD-name-of-post.ext` and includes the necessary front matter.
-
-Have a look at the source for this post to get an idea about how it works.
-
-Happy Jekylling!

data/lib/starter_web/collections/posts/public/featured/_posts/2021-01-01-welcome-to-j1.adoc

@@ -1,167 +0,0 @@
----
-title:                                  Welcome
-tagline:                                jekyll for everyone
-date:                                   2021-01-01 00:00:00
-
-tags:                                   [ Example, Post ]
-categories:                             [ Featured ]
-
-series:                                 false
-adsense:                                false
-image:                                  /assets/images/modules/attics/katie-moum-1920x1280.jpg
-toc:                                    true
-
-regenerate:                             false
-
-resources:                              []
-resource_options:
-  - attic:
-      padding_top:                      400
-      padding_bottom:                   50
-      opacity:                          0.5
-      slides:
-        - url:                          /assets/images/modules/attics/katie-moum-1920x1280.jpg
-          alt:                          Photo by Katie Moum on Unsplash
-          alignY:                       0.3
-          badge:
-            type:                       unsplash
-            author:                     Katie Moum
-            href:                       https://unsplash.com/@katiemoum
----
-
-// Page Initializer
-// =============================================================================
-// Enable the Liquid Preprocessor
-:page-liquid:
-
-// 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?
-
-[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
-// -----------------------------------------------------------------------------
-
-[[readmore]]
-== What is a static site?
-
-A static site serves the content straight to the user as it is stored on
-the server-side. To put it in another way, in opposition to WordPress
-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.
-
-In the last few years, static sites have greatly increased in popularity.
-This surge is primarily due to advances in developer tools (languages and
-libraries) and a stronger desire among businesses to optimize website
-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.
-
-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
-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.
-
-=== 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
-one.
-
-Performance::
-*The better performance and a crazy fast load time*.
-One of the main advantages of using a static site is the fact that
-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
-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
-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.
-
-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.
-
-Control::
-*You're the master*. 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?
-
-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
-generator, you will only need to make the modification once, and the
-generator will apply it to all your pages.
-
-=== Why Jekyll?
-
-As the popularity of static sites is growing, there are plenty of static
-site generators available on the market. The more famous is Jekyll,
-Middleman and Hugo. Each one has its own specificities and may suits you
-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
-powered by Jekyll. For good reasons.

data/lib/starter_web/pages/public/legal/de/100_impress.adoc

@@ -1,98 +0,0 @@
----
-title:                                  Impressum
-tagline:                                Angaben gemäß § 5 TMG
-description:                            Impressum
-
-tags:                                   [ Impressum ]
-index:                                  []
-categories:                             [ pages ]
-
-permalink:                              /pages/public/legal/de/impress/
-regenerate:                             false
-exclude_from_search:                    true
-
-toc:                                    false
-resources:                              []
-resource_options:                       []
----
-
-.Postadresse
-----
-  Max Mustermann
-  Musterstraße 111
-  Gebäude 44
-  90210 Musterstadt
-----
-
-.Kontakt
-----
-E-Mail:	mustermann@musterfirma.de
-----
-
-.Verantwortlich für den Inhalt nach § 55 Abs. 2 RStV:
-----
-  Beate Beispielhaft
-
-  Musterstraße 110
-  Gebäude 33
-  90210 Musterstadt
-----
-
-/////
-
-== Haftungsausschluss
-
-Die Inhalte des Internetauftritts wurden mit größtmöglicher Sorgfalt und nach
-bestem Gewissen erstellt. Dennoch übernimmt der Anbieter dieser Webseite keine
-Gewähr für die Aktualität, Vollständigkeit und Richtigkeit der bereitgestellten
-Seiten und Inhalte.
-
-=== Haftung für Inhalte
-
-Als Diensteanbieter sind wir gemäß § 7 Abs.1 TMG für eigene Inhalte auf
-diesen Seiten nach den allgemeinen Gesetzen verantwortlich. Nach §§ 8 bis 10 TMG
-sind wir als Diensteanbieter jedoch nicht verpflichtet, übermittelte oder
-gespeicherte fremde Informationen zu überwachen oder nach Umständen zu
-forschen, die auf eine rechtswidrige Tätigkeit hinweisen.
-
-Verpflichtungen zur Entfernung oder Sperrung der Nutzung von Informationen
-nach den allgemeinen Gesetzen bleiben hiervon unberührt. Eine diesbezügliche
-Haftung ist jedoch erst ab dem Zeitpunkt der Kenntnis einer konkreten
-Rechtsverletzung möglich. Bei Bekanntwerden von entsprechenden
-Rechtsverletzungen werden wir diese Inhalte umgehend entfernen.
-
-=== Haftung für Links
-
-Unser Angebot enthält Links zu externen Webseiten Dritter, auf deren Inhalte
-wir keinen Einfluss haben. Deshalb können wir für diese fremden Inhalte
-auch keine Gewähr übernehmen. Für die Inhalte der verlinkten Seiten ist
-stets der jeweilige Anbieter oder Betreiber der Seiten verantwortlich.
-
-Die verlinkten Seiten wurden zum Zeitpunkt der Verlinkung auf mögliche
-Rechtsverstöße überprüft. Rechtswidrige Inhalte waren zum Zeitpunkt der
-Verlinkung nicht erkennbar.
-
-Eine permanente inhaltliche Kontrolle der verlinkten Seiten ist jedoch
-ohne konkrete Anhaltspunkte einer Rechtsverletzung nicht zumutbar. Bei
-Bekanntwerden von Rechtsverletzungen werden wir derartige Links umgehend
-entfernen.
-
-== Urheberrecht
-
-Die durch die Seitenbetreiber erstellten Inhalte und Werke auf diesen
-Seiten unterliegen dem deutschen Urheberrecht. Die Vervielfältigung,
-Bearbeitung, Verbreitung und jede Art der Verwertung außerhalb der
-Grenzen des Urheberrechtes bedürfen der schriftlichen Zustimmung des
-jeweiligen Autors bzw. Erstellers.
-
-Downloads und Kopien dieser Seite sind nur für den privaten, nicht
-kommerziellen Gebrauch gestattet.
-
-Soweit die Inhalte auf dieser Seite nicht vom Betreiber erstellt wurden,
-werden die Urheberrechte Dritter beachtet. Insbesondere werden Inhalte
-Dritter als solche gekennzeichnet. Sollten Sie trotzdem auf eine
-Urheberrechtsverletzung aufmerksam werden, bitten wir um einen
-entsprechenden Hinweis. Bei Bekanntwerden von Rechtsverletzungen werden
-wir derartige Inhalte umgehend entfernen.
-
-/////