j1_template_mde 2018.4.10

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

@@ -0,0 +1,60 @@
+---
+title:                                  Welcome to J1 Template
+tagline:                                Create Your Blog
+description:                            Auto-generated Welcome Article
+date:                                   <%= Time.now.strftime('%Y-%m-%d %H:%M:%S %z') %>
+
+tags:                                   [ Example, Post ]
+regenerate:                             false
+---
+
+// Enable the Liquid Preprocessor
+//
+:page-liquid:
+
+// Set other global page attributes here
+// -----------------------------------------------------------------------------
+:page-imagesdir:                        {{page.images.dir}}
+
+
+// Place an excerpt at the most top position
+// -----------------------------------------------------------------------------
+[role="mb-3"]
+image::{page-imagesdir}/img3.jpg[{{page.title}}]
+
+Welcome to Jekyll and J1 Template!
+
+You’ll find this example post, automatically generated, in *featured* posts
+folder under /collections/posts/featured/_posts. Go ahead and edit it 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.
+
+excerpt__end
+
+
+// Liquid procedures
+// -----------------------------------------------------------------------------
+{% capture set_env_entry_document %}themes/{{site.template.name}}/procedures/global/set_env_entry_document.proc{%endcapture%}
+
+// Initialize entry document paths
+//
+{% include {{set_env_entry_document}} init_folders=all %}
+
+// Load tags and urls
+//
+include::{includedir}/attributes.asciidoc[tag=tags]
+include::{includedir}/attributes.asciidoc[tag=urls]
+
+[[readmore]]
+== Add new posts
+
+To add new posts, simply add a file in the `posts\starter\_posts` directory
+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/featured/_posts/000_includes/attributes.asciidoc

@@ -0,0 +1,15 @@
+////
+Asciidoc includes
+////
+
+tag::urls[]
+
+:parker-blog:                           https://byparker.com/blog/2014/clearing-up-confusion-around-baseurl/
+
+end::urls[]
+
+tag::tags[]
+
+:figure-caption:                        Figure
+
+end::tags[]

data/lib/starter_web/collections/posts/featured/_posts/2017-05-01-confusion-about-base-url.adoc

@@ -0,0 +1,102 @@
+---
+title:                                  Jekyll URL Configuration
+tagline:                                What is a baseurl
+description:                            Jekyll URL Configuration
+date:                                   2017-05-01 00:00:00
+
+tags:                                   [ Jekyll, Configuration, URL, base_url ]
+categories:                             featured
+regenerate:                             false
+---
+
+// Enable the Liquid Preprocessor
+//
+:page-liquid:
+
+// Set other global page attributes here
+// -----------------------------------------------------------------------------
+:page-imagesdir:                        {{page.images.dir}}
+
+
+// Place an excerpt at the most top position
+// -----------------------------------------------------------------------------
+[role="mb-3"]
+image::{page-imagesdir}/what-is-a-baseurl.jpg[{{page.title}}]
+
+Hey, so there’s been a bit of confusion about what the Jekyll configuration
+option called baseurl is. Part of the beauty of open-source and of Jekyll is
+that there’s a lot of flexibility. Unfortunately, much of this flexibility
+doesn’t apply to `baseurl`. Here’s a quick distillation of its intentions,
+and how to use it.
+
+[role="clearfix mb-3"]
+excerpt__end
+
+
+// Liquid procedures
+// -----------------------------------------------------------------------------
+{% capture set_env_entry_document %}themes/{{site.template.name}}/procedures/global/set_env_entry_document.proc{%endcapture%}
+
+// Initialize entry document paths
+//
+{% include {{set_env_entry_document}} init_folders=all %}
+
+// Load tags and urls
+//
+include::{includedir}/attributes.asciidoc[tag=tags]
+include::{includedir}/attributes.asciidoc[tag=urls]
+
+
+[[readmore]]
+== Mimic GitHub Pages
+
+See: link:{parker-blog}[Parker Moore, window="_blank"]
+
+The config parameter `baseurl` was originally added back in 2010 to allow
+“the user to test the website with the internal webserver under the same
+base url it will be deployed to on a production server”.
+
+So let’s say I come up with a cool new project. I want to make documentation
+for a project I’m working on called “example”, and I’ll be deploying it to
+GitHub Pages as a repo under the *@jekyll* username. Its documentation will
+be available at the URL http://jekyll.github.io/example.
+
+In this example, the term *base URL* refers to /example, which I place in
+my _config.yml as:
+
+[source, yaml]
+----
+baseurl: /example
+----
+
+When I go to develop my website, I run jekyll serve like normal, but this
+time I go to http://localhost:4000/example/. What this baseurl has done is
+specified a base path relative to the domain at which the site lives. If you
+navigate to just http://localhost:4000/, you will see an error message. If
+you have hooked up all your links correctly, then you will never see a URL
+in your testing without /example at the beginning of the path.
+
+You might see, for example:
+
+[source, smarty]
+----
+{{ page.path | prepend:site.baseurl }}
+----
+
+
+== Configuring Your Site Properly
+
+. Set baseurl in your _config.yml to match the production URL without
+the host (e.g. /example, not http://jekyll.github.io/example).
+
+. Run jekyll serve and go to `http://localhost:4000/your_baseurl/`, replacing
+`your_baseurl` with whatever you set baseurl to in your _config.yml - and not
+forgetting the trailing slash.
+
+. Make sure everything works. Feel free to prepend your urls with site.baseurl.
+. Push up to your host and see that everything works there, too!
+
+== Now what the heck is site.url?
+
+site.url is used in conjunction with site.baseurl when you want a link to
+something with the full URL to it. One common paradigm

data/lib/starter_web/collections/posts/featured/_posts/2017-06-01-top-open-source-static-site-generators.adoc

@@ -0,0 +1,79 @@
+---
+title:                                  Static Site Generators
+tagline:                                Top Open-Source Static Site Generators
+description:                            Static Site Generators
+date:                                   2017-06-01 00:00:00
+
+tags:                                   [ Open Source, Static, Site Generators ]
+categories:                             featured
+regenerate:                             false
+---
+
+// Enable the Liquid Preprocessor
+//
+:page-liquid:
+
+// Set other global page attributes here
+// -----------------------------------------------------------------------------
+:page-imagesdir:                        {{page.images.dir}}
+
+
+// Place an excerpt at the most top position
+// -----------------------------------------------------------------------------
+[role="mb-3"]
+image::{page-imagesdir}/staticgen.jpg[{{page.title}}]
+
+People sometimes ask if static sites make sense for anything beyond a one-pager.
+This leaderboard highlights the top open source projects, in many different
+languages, that make static sites not only viable, but an attractive option
+for creating sophisticated websites!
+
+The typical CMS driven website works by building each page on-demand, fetching
+content from a database and running it through a template engine. This means
+each page is assembled from templates and content on each request to the
+server.
+
+For most sites this is completely unnecessary overhead and only adds
+complexity, performance problems and security issues. After all, by far
+the most websites only change when the content authors or their design
+team makes changes.
+
+[role="clearfix mb-3"]
+excerpt__end
+
+// Liquid procedures
+// -----------------------------------------------------------------------------
+{% capture set_env_entry_document %}themes/{{site.template.name}}/procedures/global/set_env_entry_document.proc{%endcapture%}
+
+// Initialize entry document paths
+//
+{% include {{set_env_entry_document}} init_folders=all %}
+
+// Load tags and urls
+//
+include::{includedir}/attributes.asciidoc[tag=tags]
+include::{includedir}/attributes.asciidoc[tag=urls]
+
+
+[[readmore]]
+== Static Site Generators
+
+// Place the category image if configured
+//
+{% if page.images.category-image.size > 0 %}
+.{{page.tagline}}
+[role="mb-3"]
+image::{page-imagesdir}/{{page.images.category-image}}[{{page.title}}]
+{% endif %}
+
+A Static Site Generator takes a different approach and generate all the pages
+of the website once when there’s actually changes to the site. This means
+there’s no moving parts in the deployed website. Caching gets much easier,
+performance goes up and static sites are far more secure.
+
+To find out what Open-Source Static Site Generators are available today and
+their ranking in terms of popularity you should check https://www.staticgen.com/[StaticGen].
+
+On StaticGen, you'll will find the most complete list of generators!
+
+Have fun!

data/lib/starter_web/collections/posts/featured/_posts/2017-07-01-what-is-a-static-site.adoc

@@ -0,0 +1,146 @@
+---
+title:                                  What is a Static Site?
+tagline:                                About Jekyll and Static Webs
+description:                            Jekyll and Static Webs
+date:                                   2017-07-01 00:00:00
+
+tags:                                   [ Jekyll, Static, Web, Site, Security, Hosting ]
+categories:                             featured
+regenerate:                             false
+---
+
+// Enable the Liquid Preprocessor
+//
+:page-liquid:
+
+// Set other global page attributes here
+// -----------------------------------------------------------------------------
+:page-imagesdir:                        {{page.images.dir}}
+
+
+// Place an excerpt at the most top position
+// -----------------------------------------------------------------------------
+[role="mb-3"]
+image::{page-imagesdir}/jekyll.1200x400.png[{{page.title}}]
+
+If you’re not familiar with Jekyll (or other site generators), Jekyll is a
+so-called static site generator. Think of it like a content management system
+(CMS); without all the complexity and headache. No need to build a giant
+content-strangling Rube Goldberg machine to manage content.
+
+All you’re doing at the end of the day is writing your content and Jekyll does
+all the tricky things needed for a web site: putting out HTML, Javascript
+and CSS. As a result, the site creation process gets out of your way, it's done
+by Jekyll, and allows you to concentrate on what truly matters: your content.
+
+[role="clearfix mb-3"]
+excerpt__end
+
+// Liquid procedures
+// -----------------------------------------------------------------------------
+{% capture set_env_entry_document %}themes/{{site.template.name}}/procedures/global/set_env_entry_document.proc{%endcapture%}
+
+// Initialize entry document paths
+//
+{% include {{set_env_entry_document}} init_folders=all %}
+
+// Load tags and urls
+//
+include::{includedir}/attributes.asciidoc[tag=tags]
+include::{includedir}/attributes.asciidoc[tag=urls]
+
+
+[[readmore]]
+== What is a static site?
+
+// Place the category image if configured
+//
+{% if page.images.category-image.size > 0 %}
+.{{page.tagline}}
+[role="mb-3"]
+image::{page-imagesdir}/{{page.images.category-image}}[{{page.title}}]
+{% endif %}
+
+A static site serve 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.
+
+=== What is different ?
+
+What are the differences between a static site and a dynamic website?
+
+To make it simple, a dynamic website uses a database and PHP/MySQL to
+generate the content of a page when a user will request it. For example,
+building a website using WordPress CMS will result in having a dynamic
+website.
+
+=== Why use a static site?
+
+Wat 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
+comes the tree main advantages of using a static site over a dynamic
+one.
+
+Static: the better performance and a crazy fast load time!
+
+One the of the main advantages of using a static site is the fact that
+it is crazy fast to load. Indeed, when the user request a page, there is
+no need to request a database and various files in order 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 aspects
+
+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 less 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
+static site instead of having their website on Drupal or WordPress.
+
+== Building and 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 are 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 increase, your site will not
+go down contrary to a dynamic site which should request the database
+each time for each user.
+
+== Why use a site generator?
+
+Working with HTML files can sometimes be quite annoying. Indeed, if you
+need to make a modification you must manually change every file. If you
+have a website with 10 pages, it can be ok but imagine if you have a
+corporate site with 100+ pages or a blog with thousands of pages?! 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 are 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 wanted to switch from WordPress to Static I personally
+choose Jekyll as for me it is the best static site generator so far.
+This blog is powered under Jekyll.

data/lib/starter_web/collections/posts/series/_posts/000_includes/attributes.asciidoc

@@ -0,0 +1,66 @@
+// ~/document_base_folder/000_includes
+//  Asciidoc attribute includes:                 attributes.asciidoc
+// -----------------------------------------------------------------------------
+
+
+// URLs - Internal references and/or sources on the Internet
+// -----------------------------------------------------------------------------
+tag::urls[]
+
+:blogging-on-github-part-2:             http://digitaldrummerj.me/blogging-on-github-part-2-your-first-post/
+:blogging-on-github-part-3:             http://digitaldrummerj.me//blogging-on-github-part-3-adding-comments/
+:blogging-on-github-part-4:             http://digitaldrummerj.me//blogging-on-github-part-4-creating-additional-pages/
+
+:docker-install-toolbox-on-windows:     https://docs.docker.com/toolbox/toolbox_install_windows/
+:virtualbox-install-on-windows:         https://www.virtualbox.org/wiki/Downloads
+
+end::urls[]
+
+// Tags - Asciidoc attributes used internally
+// -----------------------------------------------------------------------------
+tag::tags[]
+
+:debug:                                           false
+ 
+:window:                                          window="_blank"
+:figure-caption:                                  Figure
+:y:                                               icon:check[role="green"]
+:n:                                               icon:times[role="red"]
+:c:                                               icon:file-alt[role="blue"]
+:arrow-r:                                         icon:arrow-right[role="blue"]
+:arrow-l:                                         icon:arrow-left[role="blue"]
+:arrow-t:                                         icon:arrow-top[role="blue"]
+:arrow-d:                                         icon:arrow-down[role="blue"]
+:beginner:                                        icon:battery-quarter[role="md-blue"]
+:inter:                                           icon:battery-half[role="md-blue"]
+:advanced:                                        icon:battery-full[role="md-blue"]
+:emdash:                                          —
+
+end::tags[]
+
+
+// Data - Data elements for Asciidoctor extensions
+// -----------------------------------------------------------------------------
+tag::data[]
+
+:docker-windows-kinematic-alpha-data:             "blog/series/j1_using_docker/kinematic_alpha.1280x600.png, Docker UI Kinematic on Windows"
+
+end::data[]
+
+
+
+// Product|Author - Document (e.g release) and Author information
+// -----------------------------------------------------------------------------
+tag::product_info[]
+
+:license:                                         MIT License
+:revdate:                                         2018
+:revnumber:                                       1.0.0
+
+end::product_info[]
+
+tag::authors[]
+
+:uri-author-juergen-adams:                        https://jekyll.one
+
+end::authors[]