j1-template 2024.0.3 → 2024.1.0

data/lib/starter_web/assets/videos/vtt/captions/readme

@@ -0,0 +1,7 @@
+See: https://videojs.com/guides/text-tracks/#kind
+
+Captions (Transcription) of the dialogue, sound effects, musical cues, and
+other audio information for viewer who are deaf/hard of hearing, or the video
+is muted.
+
+Captions are shown over the video.

data/lib/starter_web/assets/videos/vtt/captions/video1.vtt

@@ -0,0 +1,31 @@
+WEBVTT
+
+NOTE Example of video captions
+NOTE https://developer.mozilla.org/en-US/docs/Web/API/WebVTT_API
+
+00:00:10.000 --> 00:00:13.000
+This is an example of captions over a video.
+
+00:00:13.000 --> 00:00:18.000
+Captions can be supplied by a simple text file in Web Video Text Track format (VTT).
+
+00:00:18.000 --> 00:00:21.000
+<i>Captions can be formatted with basic HTML styles.</i>
+
+00:00:21.000 --> 00:00:25.000
+<b>You can set captions font Bold.</b>
+
+00:00:25.000 --> 00:00:28.000
+<i>You can set captions font style Italic, for example.</i>
+
+00:00:28.000 --> 00:00:31.000
+<u>You can set captions text underlined!</u>
+
+00:00:31.000 --> 00:00:34.000
+You can use multiple formatting types for single caption!
+Now you see <i>italic</i> and <b>bold</b> text in one line.
+
+00:00:34.000 --> 00:00:40.000
+Multi
+Line
+Support.

data/lib/starter_web/assets/videos/vtt/chapters/readme

@@ -0,0 +1,5 @@
+See: https://videojs.com/guides/text-tracks/#kind
+
+Chapter titles that are used to create navigation within the video.
+Typically, these are in the form of a list of chapters that the viewer
+can use to navigate the video.

data/lib/starter_web/assets/videos/vtt/chapters/video1.vtt

@@ -0,0 +1,15 @@
+WEBVTT
+
+NOTE Chapter definitions (id, timespan, name)
+
+1
+00:00:08.000 --> 00:01:00.000
+Chapter 1
+
+2
+00:01:00.000 --> 00:01:30.000
+Chapter 2
+
+3
+00:01:30.000 --> 00:02:17.000
+Chapter 3

data/lib/starter_web/assets/videos/vtt/descriptions/readme

@@ -0,0 +1,7 @@
+See: https://videojs.com/guides/text-tracks/#kind
+
+Text descriptions of the action in the content for when the video portion
+isn't available or because the viewer is blind or not using a screen.
+
+Descriptions are read by a screen reader or turned into a separate audio
+track.

data/lib/starter_web/assets/videos/vtt/subtitles/readme

@@ -0,0 +1,6 @@
+See: https://videojs.com/guides/text-tracks/#kind
+
+Translations of the dialogue in the video for when audio is available but
+not understood.
+
+Subtitles are shown over the video.

data/lib/starter_web/collections/posts/public/featured/_posts/2023-10-18-url-types.adoc

@@ -71,28 +71,31 @@ endif::[]
 // Include sub-documents (if any)
 // -----------------------------------------------------------------------------
 [role="mt-5 mb-4"]
-The primary difference is that `https://domain` specifies the protocol
-*HTTPS* explicitly, while `//domain` *inherits* the protocol from the current
-webpage. Using `//domain` is a good practice to maintain consistency with the
-current page's protocol and *reduce* potential security issues related to
-*mixed content*.
+The primary difference is that +++<code>https://domain</code>+++ specifies
+the protocol *HTTPS* explicitly, while +++<code>//domain</code>+++ *inherits*
+the protocol from the current webpage. Using +++<code>//domain</code>+++ is a
+good practice to maintain consistency with the current page's protocol and
+*reduce* potential security issues related to *mixed content*.
 
 Absolute URL::
 
-URLs of type `https://domain` are *absolute* URLs, meaning they explicitly
-include the protocol or scheme -- in this case, "https://". When you use
-this format, you specify that the website should be accessed over *HTTPS*,
-a secure protocol for web communication. The browser will use the HTTPS
-protocol to connect to the specified domain.
+URLs of type +++<code>https://domain</code>+++ are *absolute* URLs, meaning
+they explicitly include the protocol or scheme -- in this case
++++<code>https://</code>+++. When you use this format, you specify that
+the website should be accessed over *HTTPS*, a secure protocol for web
+communication. The browser will use the HTTPS protocol to connect to the
+specified domain.
 
 Protocol-relative URL::
 
-URLs of type `//domain` are *protocol-relative* URL or *network-path*
-references. It does not explicitly specify a particular protocol as *HTTP*
-or *HTTPS*. Instead, it inherits the protocol used in the *current webpage*.
+URLs of type +++<code>https://domain</code>+++ are *protocol-relative* URL
+or *network-path* references. It does not explicitly specify a particular
+protocol as *HTTP* or *HTTPS*. Instead, it inherits the protocol used in
+the *current webpage*.
 
 If the current webpage is loaded over HTTPS, the browser will use HTTPS to
 connect to the domain. If the current webpage is loaded over HTTP, it will
 use HTTP. Protocol-relative URLs often ensure that resources are loaded
 securely when a webpage can be accessed over HTTP and HTTPS without causing
-mixed content issues (e.g., loading insecure resources on a secure page).
+mixed content issues (for example loading insecure resources on a secure
+page).

data/lib/starter_web/index.html

@@ -6,10 +6,10 @@ title:                                  J1 Starter
 tagline:                                The Build-In Web
 
 date:                                   2023-01-01 00:00:00
-#last_modified:                         2023-07-18 00:00:00
+#last_modified:                         2023-12-27 00:00:00
 
 description: >
-                                        J1 Template gives provides a clean implementation
+                                        Jekyll One Template (J1) provides a clean implementation
                                         in Jekyll for starting new projects based on Bootstap V5.
                                         The template combines the best software for the Web.
                                         Jekyll One is open source, free to use, and the modules
@@ -29,7 +29,6 @@ image:
   path:                                 /assets/images/modules/attics/ideas-start-here-1920x1280.jpg
   width:                                1920
   height:                               1200
-  alt:                                  ideas-start-here-1920x1280.jpg
 
 tts:                                    true
 toc:                                    false

data/lib/starter_web/package.json

@@ -1,57 +1,40 @@
 {
-
   "private": true,
   "name": "j1",
-  "version": "2024.0.3",
+  "version": "2024.1.0",
   "description": "J1 Starter Web",
   "homepage": "https://your.site",
-
   "author": {
-
     "name": "Your Name",
     "email": "name@mail.site",
     "url": "https://your.site"
-
   },
-
   "license": "MIT",
-
   "bugs": {
     "url": "https://github.com/jekyll-one/j1-template-starter/issues"
   },
-
   "config": {
-
     "jekyll_app_interface": "0.0.0.0",
     "jekyll_app_port": "30010",
     "jekyll_app_url": "http://localhost:30010/",
-
     "jekyll_config_file": "_config.yml",
     "jekyll_port": "30000",
     "jekyll_livereload_port": "30001",
-
     "jekyll_option_livereload": "--livereload",
     "jekyll_option_watch": "--watch",
     "jekyll_option_initial_build": "--skip-initial-build",
     "jekyll_option_incremental": "--incremental",
-
     "ruby_gemfile": "Gemfile",
     "ruby_userize": "true",
     "ruby_vendorize": "true",
-
     "mode": "production",
     "loglevel": "silent"
-
   },
-
   "engines": {
-
     "node": ">=16",
     "npm": ">=8",
     "yarn": ">=1.22"
-
   },
-
   "keywords": [
     "Jekyll",
     "One",
@@ -59,20 +42,16 @@
     "Web",
     "Site"
   ],
-
   "scripts": {
-
     "app": "run-p -s app:*",
     "app:rackup": "cross-env INTERFACE=$npm_package_config_jekyll_app_interface PORT=$npm_package_config_jekyll_app_port bundle exec puma -C _data/puma/config.rb",
     "app:open": "npm run delay-3s && cross-var open-cli $npm_package_config_jekyll_app_url",
-
     "build": "run-s -s build:*",
     "build:info": "echo Build site incremental ..",
     "build:do": "bundle exec jekyll b --incremental",
     "postbuild": "run-s -s postbuild:*",
     "postbuild:finished": "echo .. build finished.",
     "postbuild:hint": "echo To open the site, run: yarn site",
-
     "bundle": "run-s -s bundler:*",
     "bundler:info": "echo Create bundle ..",
     "bundler:clean": "shx rm -f Gemfile.lock",
@@ -83,7 +62,6 @@
     "bundle_vendor:info": "echo Bundle Rubies using vendor path ..",
     "bundle_vendor:set-path": "bundle config set --local path ./vendor",
     "bundle_vendor:bundle": "bundle install",
-
     "clean": "run-s -s clean-site && run-s clean:*",
     "clean-site": "echo Clean up site files .. && bundle exec jekyll clean",
     "clean:start": "echo Clean up projects files ..",
@@ -92,16 +70,13 @@
     "clean:etc-folder": "echo Remove etc folder .. && shx rm -rf etc",
     "clean:logfiles": "echo Remove various log files .. && shx rm -f *.log",
     "clean:locks": "echo Remove lock files .. && shx rm -f *.lock && shx rm -f package-lock.json",
-
     "delay-1s": "node ./node_modules/npm-delay 1000",
     "delay-2s": "node ./node_modules/npm-delay 2000",
     "delay-3s": "node ./node_modules/npm-delay 3000",
     "delay-5s": "node ./node_modules/npm-delay 5000",
-
     "j1-app": "run-p -s app:*",
     "j1-site": "run-p -s j1-site:*",
     "j1-site:jekyll": "echo Startup the site .. && cross-var bundle exec jekyll serve --config $npm_package_config_jekyll_config_file --port $npm_package_config_jekyll_port --livereload-port $npm_package_config_jekyll_livereload_port $npm_package_config_jekyll_option_incremental $npm_package_config_jekyll_option_livereload $npm_package_config_jekyll_option_initial_build $npm_package_config_jekyll_option_watch --open 2>jekyll.log",
-
     "rebuild": "run-s -s rebuild:* && run-s -s post-rebuild:*",
     "rebuild:info": "echo Rebuild site incremental ..",
     "rebuild:clean": "echo Clean up site files .. && bundle exec jekyll clean",
@@ -109,12 +84,10 @@
     "post-rebuild": "run-s -s postrebuild:*",
     "post-rebuild:finished": "echo .. rebuild finished.",
     "post-rebuild:hint": "echo To open the site, run: yarn site",
-
     "reset": "run-s -s reset:*",
     "reset:start": "echo Reset project to factory state ..",
     "reset:base-clean-files": "echo Cleaning up .. && npm --silent run clean",
     "reset:finished": "echo done.",
-
     "setup": "npm --silent run setup-start && npm --silent run setup-base && run-s -s setup:*",
     "setup-start": "echo Setup project for first use ..",
     "setup-base": "echo Bootstrap base modules .. && echo J1 Project Base modules: > install.log && npm --silent install shx npm-run-all cross-var cross-env >> install.log && echo done.",
@@ -128,17 +101,12 @@
     "setup:node-modules-base": "echo Bootstrap project modules .. && echo J1 Project modules: >> install.log && npm --silent install >> install.log",
     "setup:detect-os": "echo Detect OS .. && cross-var 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"
-
   },
-
   "dependencies": {
-
     "getos": "^3.2.1",
     "getos-cli": "^1.0.0",
     "if-env": "^1.0.4",
     "npm-delay": "^1.0.4",
     "open-cli": "^7.0.1"
-
   }
-
-}
+}

data/lib/starter_web/pages/public/features/general.adoc

@@ -31,7 +31,7 @@ image:
 regenerate:                             false
 permalink:                              /pages/public/features/general_features/
 
-resources:                              [ animate, comments, rouge, lightbox, iconify ]
+resources:                              [ animate, clipboard, comments, rouge, lightbox, iconify ]
 resource_options:
   - toccer:
       collapseDepth:                    3
@@ -223,7 +223,7 @@ traffic on mobile phones has surged over the past decade. As of July 2021,
 more than 50 percent of all web traffic came through mobile devices.
 
 .Global mobile traffic, 2011-2021
-lightbox::broadbandsearch--global-mobile-traffic[ 800, {data-broadbandsearch--global-mobile-traffic} ]
+lightbox::broadbandsearch--global-mobile-traffic[ 1024, {data-broadbandsearch--global-mobile-traffic} ]
 
 Source: link:{url-broadbandsearch--mobile-internet-usage}[broadbandsearch.net, {browser-window--new}]
 
@@ -253,7 +253,7 @@ your vistors easy access to all of your content pages on a mouse-click.
 ----
 
 .Desktop Web Navigation
-lightbox::images--desktop-navigation[ 800, {data-images--desktop-navigation} ]
+lightbox::images--desktop-navigation[ 1024, {data-images--desktop-navigation} ]
 
 [role="mt-4"]
 === Mobile Web Navigation
@@ -282,4 +282,4 @@ level.
 
 [role="mb-7"]
 .Google Lighthouse Scores (Starter Web at Github)
-lightbox::images--google-lighthouse[ 800, {data-images--google-lighthouse} ]
+lightbox::images--google-lighthouse[ 1024, {data-images--google-lighthouse} ]

data/lib/starter_web/pages/public/features/template.adoc

@@ -79,6 +79,7 @@ using HTML, CSS, and Javascript is required.
 
 J1 is different: easy to use, no programming is needed.
 
+
 // Include sub-documents (if any)
 // -----------------------------------------------------------------------------
 [role="mt-5"]
@@ -160,7 +161,7 @@ functions for a webpage. FABs are increasingly used on the web and serves to
 enable important actions for a page, but separated from the main navigation.
 
 .FAB (Menu)
-lightbox::images--fab[ 800, {data-images--fab} ]
+lightbox::images--fab[ 1920, {data-images--fab} ]
 
 The template system supports Floating Action Buttons for in-page navigation.
 When the FAB is pressed, it provides more related actions like showing the
@@ -174,7 +175,7 @@ through all documents. FTS promises fast retrieval of data with advanced
 indexing and more intuitive search results based on relevance.
 
 .Full-text search
-lightbox::images--full-text-search[ 800, {data-images--full-text-search} ]
+lightbox::images--full-text-search[ 1920, {data-images--full-text-search} ]
 
 J1 implements Lunr for indexing the whole website. The engine is designed
 to be small but full-featured. Lunr enables developers to provide visitors
@@ -190,7 +191,7 @@ compliant with the *ePrivacy* regulations of the European Unions and
 associated countries.
 
 .Cookie Consent
-lightbox::images--cookie-consent[ 800, {data-images--cookie-consent} ]
+lightbox::images--cookie-consent[ 1920, {data-images--cookie-consent} ]
 
 Under the GDPR, *most cookies* will fall into the category of *personal data*
 because they can identify visitors and can be used to provide website
@@ -212,7 +213,7 @@ just ranked 3rd in terms of the highest number of native speakers among all
 languages worldwide.
 
 .Native speakers by language
-lightbox::lingohub--speakers-by-language[ 600, {data-lingohub--speakers-by-language} ]
+lightbox::lingohub--speakers-by-language[ 1920, {data-lingohub--speakers-by-language} ]
 
 Source: link:{url-lingohub--speakers-by-language}[lingohub.com, {browser-window--new}]
 
@@ -245,7 +246,7 @@ to get a larger number of international audiences, translating your site can
 help target your global audience more easily and quickly.
 
 .Google Translator
-lightbox::images--translator[ 800, {data-images--translator} ]
+lightbox::images--translator[ 1920, {data-images--translator} ]
 
 GT is fully integrated with the GDPR-compatible Cookie Consent module. If your
 visitors do not agree on cookies required to use Google Translate, GT gets
@@ -263,7 +264,7 @@ Attics may contains (dynamic) *Text*, *Images* or *Videos* to support a page
 for the content presented.
 
 .Master Header (image-based)
-lightbox::images--master-header[ 800, {data-images--master-header} ]
+lightbox::images--master-header[ 1920, {data-images--master-header} ]
 
 [role="mt-4"]
 === Clipboard
@@ -319,7 +320,7 @@ J1 Template is a multi-purpose navigation builder based on the _Bootstrap_ V5
 Framework.
 
 .Navigation Module (NAV)
-lightbox::images--nav-module[ 800, {data-images--nav-module} ]
+lightbox::images--nav-module[ 1920, {data-images--nav-module} ]
 
 The NAV module for J1 consists of four configurable sub-modules:
 
@@ -546,7 +547,7 @@ generates different views to explore articles by Categoy, Date, or all posts
 from an Archive View.
 
 .Blog Post Navigator
-lightbox::images--blog-post-navigator[ 600, {data-images--blog-post-navigator} ]
+lightbox::images--blog-post-navigator[ 1920, {data-images--blog-post-navigator} ]
 
 [role="mt-4"]
 === Block elements
@@ -556,10 +557,10 @@ used for home and landing pages. Examples how to use banners and panels
 can be found with the included starter web for the homepage.
 
 .Teaser Banner
-lightbox::images--teaser-banner[ 600, {data-images--teaser-banner} ]
+lightbox::images--teaser-banner[ 1920, {data-images--teaser-banner} ]
 
 .Intro Panel
-lightbox::images--intro-panel[ 600, {data-images--intro-panel} ]
+lightbox::images--intro-panel[ 1920, {data-images--intro-panel} ]
 
 [role="mt-4"]
 === Asciidoctor extensions
@@ -592,7 +593,7 @@ included with the J1 Template. Many real-world examples for your content
 could be taken from these pages and are easy to use with your website.
 
 .Example Content (Icon Fonts)
-lightbox::images--example-content[ 600, {data-images--example-content} ]
+lightbox::images--example-content[ 1920, {data-images--example-content} ]
 
 [role="mt-4"]
 === Royalty Free Images
@@ -626,7 +627,7 @@ mdi:vimeo[2x, md-blue ml-3 mr-2]
 [role="mt-4"]
 === Bootstrap Themes
 
-The Themes for the template system J1 are based on the free and open-source
+The Themes for the template system J1 are based on the free and Open Source
 CSS front-end framework _Bootstrap_ of version V5. Using _Bootstrap_ base style
 only results in a uniform appearance for the content in terms of the overall
 layout, text, tables, and form elements across all modern web browsers
@@ -639,7 +640,7 @@ all the _Bootstrap_ variables, and rebuild the framework files to create a new
 theme.
 
 .Bootswatch Themes (Minty)
-lightbox::images--bootswatch-themes[ 600, {data-images--bootswatch-themes} ]
+lightbox::images--bootswatch-themes[ 1920, {data-images--bootswatch-themes} ]
 
 Many different styles are available. What is already available at
 link:{url-bootswatch--home}[Bootswatch, {browser-window--new}] is at least a
@@ -659,7 +660,7 @@ Hyvor (HVC). The comment interfaces from the supported providers can be
 integrated by pure configuration.
 
 .Comments by Hyvor Talk
-lightbox::images--comments-hyvor[ 800, {data-images--comments-hyvor} ]
+lightbox::images--comments-hyvor[ 1920, {data-images--comments-hyvor} ]
 
 Enable the provider you want to use and add your access credentials to the
 configuration, and you're done. On all posts or pages you want to use for

data/lib/starter_web/pages/public/learn/bookshelf/jekyll_collections.adoc

@@ -148,7 +148,7 @@ Collections are a very young feature to Jekyll, and according to the
 official documentation may be subject to change Jekyll Documentation on
 http://jekyllrb.com/docs/collections/[Collections, {browser-window--new}]],
 you should not let that put you off of using them, because Jekyll is
-open-source, which means you should trust the community to work-together
+Open Source, which means you should trust the community to work-together
 for the best common-case solution.
 ====
 
@@ -203,7 +203,7 @@ For a more concrete example, take a look at
 https://github.com/github/choosealicense.com[the source, {browser-window--new}]
 for
 http://choosealicense.com[choosealicense.com, {browser-window--new}]
-a site which helps explain OpenSource licenses like the MIT or GPL license.
+a site which helps explain Open Source licenses like the MIT or GPL license.
 There are pages like *about* and *terms of service*, but the actual licenses
 live in
 https://github.com/github/choosealicense.com/tree/gh-pages/licenses[a licenses collection, {browser-window--new}]
@@ -294,7 +294,7 @@ group of "things" that can be logically grouped by a common theme
 
 * Listing employees on your company's "about" page (or a project's
   maintainers)
-* Documenting methods in an OpenSource project (or the project's that
+* Documenting methods in an Open Source project (or the project's that
   use it, or the plugins available)
 * Organizing jobs on your résumé (or talks given, papers written)
 * https://github.com/blog/1939-how-github-uses-github-to-document-GitHub[Articles on a support site, {browser-window--new}]