jekyll-base 0.0.1 → 0.0.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/Gemfile +4 -3
- data/Gemfile.lock +79 -0
- data/{LICENSE.txt → LICENSE} +6 -6
- data/README.md +2 -26
- data/_config.yml +114 -0
- data/_includes/categories.html +23 -0
- data/_includes/feed.html +16 -0
- data/_includes/footer.html +4 -0
- data/_includes/head.html +18 -0
- data/_includes/header.html +27 -0
- data/_includes/theme-list.html +36 -0
- data/_layouts/blog.html +53 -0
- data/_layouts/default.html +38 -0
- data/_layouts/page.html +38 -0
- data/_layouts/post.html +38 -0
- data/_posts/2023-03-15-github-templates.md +14 -0
- data/_posts/2023-03-24-Installing-themes.md +23 -0
- data/_posts/2023-04-03-config.md +72 -0
- data/_posts/2023-04-04-Setup-Jekyll.md +35 -0
- data/about.md +9 -0
- data/assets/css/main.css +0 -0
- data/assets/imgs/ruby.png +0 -0
- data/blog.md +10 -0
- data/index.md +13 -0
- metadata +27 -13
- data/CHANGELOG.md +0 -5
- data/CODE_OF_CONDUCT.md +0 -84
- data/Rakefile +0 -4
- data/jekyll-base.gemspec +0 -31
- data/lib/jekyll/base/version.rb +0 -7
- data/lib/jekyll/base.rb +0 -10
- data/sig/jekyll/base.rbs +0 -6
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 50ddf9d17039e0679aea68fcf588d789e44a7a2ef4533afe73d80380ea00d06e
|
4
|
+
data.tar.gz: 7da73225e740f75a82b0be8fda1e358f85aa0342aeac40f86d262b6d28eb9fe1
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: ab856ef8a09b48ee9437fd9d911e2dae332cffcb1bd4b93e79280354c852ee80e6b924468f5097f0bce018322cc5e10a9a9c2f5ea30213df35e6ba281bf174c8
|
7
|
+
data.tar.gz: 01aa1c1fafd3c0711334888f945761582ca9275eff23afff8e0e3256d834d207accaae60f17e8ea02ea110a5a3de878e73910f9d5bee277dffddd1121a6e7329
|
data/Gemfile
CHANGED
@@ -14,10 +14,11 @@ gem "jekyll", "~> 4.3.2"
|
|
14
14
|
# This is the default theme for new Jekyll base site
|
15
15
|
# You may change this to anything you like.
|
16
16
|
|
17
|
-
|
17
|
+
gem "jekyll-base"
|
18
18
|
|
19
|
-
# If you want to use GitHub Pages, remove the "gem "jekyll""
|
20
|
-
# uncomment the line below. To upgrade, run
|
19
|
+
# If you want to use GitHub Pages, remove the "gem "jekyll""
|
20
|
+
# above and uncomment the line below. To upgrade, run
|
21
|
+
# `bundle update github-pages`.
|
21
22
|
#
|
22
23
|
# gem "github-pages", group: :jekyll_plugins
|
23
24
|
|
data/Gemfile.lock
ADDED
@@ -0,0 +1,79 @@
|
|
1
|
+
GEM
|
2
|
+
remote: https://rubygems.org/
|
3
|
+
specs:
|
4
|
+
addressable (2.8.1)
|
5
|
+
public_suffix (>= 2.0.2, < 6.0)
|
6
|
+
colorator (1.1.0)
|
7
|
+
concurrent-ruby (1.2.2)
|
8
|
+
em-websocket (0.5.3)
|
9
|
+
eventmachine (>= 0.12.9)
|
10
|
+
http_parser.rb (~> 0)
|
11
|
+
eventmachine (1.2.7)
|
12
|
+
ffi (1.15.5)
|
13
|
+
forwardable-extended (2.6.0)
|
14
|
+
google-protobuf (3.22.0-x86_64-linux)
|
15
|
+
http_parser.rb (0.8.0)
|
16
|
+
i18n (1.12.0)
|
17
|
+
concurrent-ruby (~> 1.0)
|
18
|
+
jekyll (4.3.2)
|
19
|
+
addressable (~> 2.4)
|
20
|
+
colorator (~> 1.0)
|
21
|
+
em-websocket (~> 0.5)
|
22
|
+
i18n (~> 1.0)
|
23
|
+
jekyll-sass-converter (>= 2.0, < 4.0)
|
24
|
+
jekyll-watch (~> 2.0)
|
25
|
+
kramdown (~> 2.3, >= 2.3.1)
|
26
|
+
kramdown-parser-gfm (~> 1.0)
|
27
|
+
liquid (~> 4.0)
|
28
|
+
mercenary (>= 0.3.6, < 0.5)
|
29
|
+
pathutil (~> 0.9)
|
30
|
+
rouge (>= 3.0, < 5.0)
|
31
|
+
safe_yaml (~> 1.0)
|
32
|
+
terminal-table (>= 1.8, < 4.0)
|
33
|
+
webrick (~> 1.7)
|
34
|
+
jekyll-feed (0.17.0)
|
35
|
+
jekyll (>= 3.7, < 5.0)
|
36
|
+
jekyll-sass-converter (3.0.0)
|
37
|
+
sass-embedded (~> 1.54)
|
38
|
+
jekyll-watch (2.2.1)
|
39
|
+
listen (~> 3.0)
|
40
|
+
kramdown (2.4.0)
|
41
|
+
rexml
|
42
|
+
kramdown-parser-gfm (1.1.0)
|
43
|
+
kramdown (~> 2.0)
|
44
|
+
liquid (4.0.4)
|
45
|
+
listen (3.8.0)
|
46
|
+
rb-fsevent (~> 0.10, >= 0.10.3)
|
47
|
+
rb-inotify (~> 0.9, >= 0.9.10)
|
48
|
+
mercenary (0.4.0)
|
49
|
+
pathutil (0.16.2)
|
50
|
+
forwardable-extended (~> 2.6)
|
51
|
+
public_suffix (5.0.1)
|
52
|
+
rake (13.0.6)
|
53
|
+
rb-fsevent (0.11.2)
|
54
|
+
rb-inotify (0.10.1)
|
55
|
+
ffi (~> 1.0)
|
56
|
+
rexml (3.2.5)
|
57
|
+
rouge (4.1.0)
|
58
|
+
safe_yaml (1.0.5)
|
59
|
+
sass-embedded (1.58.3)
|
60
|
+
google-protobuf (~> 3.21)
|
61
|
+
rake (>= 10.0.0)
|
62
|
+
terminal-table (3.0.2)
|
63
|
+
unicode-display_width (>= 1.1.1, < 3)
|
64
|
+
unicode-display_width (2.4.2)
|
65
|
+
webrick (1.8.1)
|
66
|
+
|
67
|
+
PLATFORMS
|
68
|
+
x86_64-linux
|
69
|
+
|
70
|
+
DEPENDENCIES
|
71
|
+
http_parser.rb (~> 0.6.0)
|
72
|
+
jekyll (~> 4.3.2)
|
73
|
+
jekyll-feed (~> 0.12)
|
74
|
+
tzinfo (>= 1, < 3)
|
75
|
+
tzinfo-data
|
76
|
+
wdm (~> 0.1.1)
|
77
|
+
|
78
|
+
BUNDLED WITH
|
79
|
+
2.4.7
|
data/{LICENSE.txt → LICENSE}
RENAMED
@@ -1,6 +1,6 @@
|
|
1
|
-
|
1
|
+
MIT License
|
2
2
|
|
3
|
-
Copyright (c) 2023
|
3
|
+
Copyright (c) 2023 Jekyllgems.dev
|
4
4
|
|
5
5
|
Permission is hereby granted, free of charge, to any person obtaining a copy
|
6
6
|
of this software and associated documentation files (the "Software"), to deal
|
@@ -9,13 +9,13 @@ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
9
|
copies of the Software, and to permit persons to whom the Software is
|
10
10
|
furnished to do so, subject to the following conditions:
|
11
11
|
|
12
|
-
The above copyright notice and this permission notice shall be included in
|
13
|
-
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
13
|
+
copies or substantial portions of the Software.
|
14
14
|
|
15
15
|
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
16
16
|
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
17
17
|
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
18
18
|
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
19
19
|
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
20
|
-
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
21
|
-
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
21
|
+
SOFTWARE.
|
data/README.md
CHANGED
@@ -1,27 +1,3 @@
|
|
1
|
-
#
|
1
|
+
# base
|
2
2
|
|
3
|
-
|
4
|
-
|
5
|
-
Happy Jekylling :)
|
6
|
-
|
7
|
-
## Installation
|
8
|
-
|
9
|
-
Install the gem and add to the application's Gemfile by executing:
|
10
|
-
|
11
|
-
$ bundle add jekyll-base
|
12
|
-
|
13
|
-
If bundler is not being used to manage dependencies, install the gem by executing:
|
14
|
-
|
15
|
-
$ gem install jekyll-base
|
16
|
-
|
17
|
-
## Contributing
|
18
|
-
|
19
|
-
Bug reports and pull requests are welcome on GitHub at https://github.com/jekyllgems/base. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/jekyllgems/docs).
|
20
|
-
|
21
|
-
## License
|
22
|
-
|
23
|
-
The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
|
24
|
-
|
25
|
-
## Code of Conduct
|
26
|
-
|
27
|
-
Everyone interacting in the Jekyll::Base project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/jekyllgems/docs).
|
3
|
+
Base files to make it simple to create sites with Jekyll. Usually when you install a new site via the jekyll tool `jekyll new blog` it ships with minima, but not even an actual copy of minima. It is stripped down and barely works unless the user knows how to theme a jekyll site. This gem will resolve that issue for others. This isn't really a theme per se, but more just the base files you need to set up a simple Jekyll site. See it in action so you can demo it by going to https://jekyllgems.github.io/base
|
data/_config.yml
ADDED
@@ -0,0 +1,114 @@
|
|
1
|
+
repository : jekyllgems/base
|
2
|
+
github : [metadata]
|
3
|
+
|
4
|
+
# This is a base template for Jekyll. The starter template that
|
5
|
+
# ships with "jekyll new sitename" is complete trash.
|
6
|
+
#
|
7
|
+
# It is not good for a person coming to Jekyll with no knowledge
|
8
|
+
# of programming or themeing as is the general purpose of the Jekyll
|
9
|
+
# framework according to their own statments.
|
10
|
+
#
|
11
|
+
# If you need any help feel free to reach out on discord or email
|
12
|
+
# me and I will help in any way you need. If you want a custom theme
|
13
|
+
# or plugin built you can hop on discord and we can discuss it.
|
14
|
+
#
|
15
|
+
# =============
|
16
|
+
# SOCIAL LINKS
|
17
|
+
# =============
|
18
|
+
#
|
19
|
+
# This section handles your social network links displayed across
|
20
|
+
# your site in liquid tags as site.social.NAME feel free to reach
|
21
|
+
# out to me using these if you need any help.
|
22
|
+
|
23
|
+
social:
|
24
|
+
twitter : jekyllcoder
|
25
|
+
github : leatheresque
|
26
|
+
email : jekyllcoder@gmail.com
|
27
|
+
discord : leatheresque#3820
|
28
|
+
support_server : https://discord.gg/8uc5FyPdHk
|
29
|
+
|
30
|
+
# ==========
|
31
|
+
# SITE TITLE
|
32
|
+
# ==========
|
33
|
+
#
|
34
|
+
# This is the title of your website for example, "The Moo York Times" :)
|
35
|
+
|
36
|
+
title: Your New Site
|
37
|
+
|
38
|
+
description: >- # this means to ignore newlines until "baseurl:"
|
39
|
+
Welcome to your new site, replace this description
|
40
|
+
|
41
|
+
# =======
|
42
|
+
# BASEURL
|
43
|
+
# =======
|
44
|
+
#
|
45
|
+
# This is the subpath of your site, e.g. /blog if you want users to
|
46
|
+
# access your site at https://example.com/blog
|
47
|
+
#
|
48
|
+
# If you are using a gh-pages site this will be empty if your site
|
49
|
+
# is on https://username.github.io if your repo using this theme is
|
50
|
+
# named "foobar" then change this to /foobar and when you serve
|
51
|
+
# it using the pages setting it will be live at
|
52
|
+
#
|
53
|
+
# https://username.github.io/foobar
|
54
|
+
|
55
|
+
baseurl : "/base"
|
56
|
+
|
57
|
+
# ===
|
58
|
+
# URL
|
59
|
+
# ===
|
60
|
+
#
|
61
|
+
# This is the base hostname & protocol for your site, as you see
|
62
|
+
# I use https://jekyllgems.github.io because this is a template
|
63
|
+
# and served live on my gh-pages site.
|
64
|
+
#
|
65
|
+
# Use localhost for local development
|
66
|
+
# http://localhost:4000
|
67
|
+
|
68
|
+
|
69
|
+
url : "https://jekyllgems.github.io"
|
70
|
+
|
71
|
+
# =================
|
72
|
+
# EXCERPT_SEPARATOR
|
73
|
+
# =================
|
74
|
+
#
|
75
|
+
# This is used in your blog posts, you can see an example in any
|
76
|
+
# of the example blog posts included in this theme. It functions
|
77
|
+
# to trim your posts when displaying them so it doesnt show the
|
78
|
+
# entire post like on the front page. Feel free to change where
|
79
|
+
# the excerpt ends.
|
80
|
+
|
81
|
+
excerpt_separator: <!--more-->
|
82
|
+
|
83
|
+
# ==============
|
84
|
+
# BUILD SETTINGS
|
85
|
+
# ==============
|
86
|
+
#
|
87
|
+
# These are build settings needed for when you run "jekyll serve"
|
88
|
+
# commands. You can change these, but be careful because they can
|
89
|
+
# cause your site to break.
|
90
|
+
#
|
91
|
+
# COLLECTIONS
|
92
|
+
# ===========
|
93
|
+
#
|
94
|
+
# Collections are Jekylls way to handle things like tags, categories,
|
95
|
+
# authors. Any type of data you can iterate over. Here is how you add
|
96
|
+
# categories to your blog. Uncomment this to have it assign links for
|
97
|
+
# your categories
|
98
|
+
#
|
99
|
+
# collections:
|
100
|
+
# categories: # This will create your category links
|
101
|
+
# output: true
|
102
|
+
# permalink: /:categories/:title/
|
103
|
+
#
|
104
|
+
# =======
|
105
|
+
# PLUGINS
|
106
|
+
# =======
|
107
|
+
#
|
108
|
+
# This is just one of the plugins you can use with jekyll
|
109
|
+
# you can find more useful plugins I have created at:
|
110
|
+
#
|
111
|
+
# https://github.com/jekyllgems/plugins
|
112
|
+
|
113
|
+
plugins:
|
114
|
+
- jekyll-feed
|
@@ -0,0 +1,23 @@
|
|
1
|
+
<div class="col-md-6">
|
2
|
+
<h2 class="text-body-emphasis">Categories</h2>
|
3
|
+
<p>These can be enabled by uncommenting the section in the config file. You can then link to the category and the user will see all posts on the blog with categories in the front matter.</p>
|
4
|
+
|
5
|
+
<ul class="list-unstyled ps-0">
|
6
|
+
{% assign all_categories = "" %}
|
7
|
+
{% for post in site.posts %}
|
8
|
+
{% for category in post.categories %}
|
9
|
+
{% if all_categories contains category %}
|
10
|
+
{% continue %}
|
11
|
+
{% endif %}
|
12
|
+
{% assign all_categories = all_categories | append: category | append: "," %}
|
13
|
+
<li>
|
14
|
+
<a class="text-danger icon-link mb-1">
|
15
|
+
<i class="fa-solid fa-book-open-reader"></i>
|
16
|
+
{{ category }}
|
17
|
+
</a>
|
18
|
+
</li>
|
19
|
+
{% endfor %}
|
20
|
+
{% endfor %}
|
21
|
+
</ul>
|
22
|
+
|
23
|
+
</div>
|
data/_includes/feed.html
ADDED
@@ -0,0 +1,16 @@
|
|
1
|
+
<div class="col-md-6">
|
2
|
+
<h2 class="text-body-emphasis">Jekyll Starter Guides</h2>
|
3
|
+
<p>Read more detailed instructions and documentation on using or contributing to Jekyllgems themes and plugins on my blog. These posts will also ship with your theme / template so you can read them on your own site.</p>
|
4
|
+
<ul class="list-unstyled ps-0">
|
5
|
+
|
6
|
+
{% for post in site.posts %}
|
7
|
+
<li>
|
8
|
+
<a class="text-danger icon-link mb-1" href="{{site.url}}{{site.baseurl}}{{post.url}}">
|
9
|
+
<i class="fa-solid fa-book-open-reader"></i>
|
10
|
+
{{ post.title }}
|
11
|
+
</a>
|
12
|
+
</li>
|
13
|
+
{% endfor %}
|
14
|
+
|
15
|
+
</ul>
|
16
|
+
</div>
|
@@ -0,0 +1,4 @@
|
|
1
|
+
<footer class="pt-5 my-5 text-body-secondary text-center">
|
2
|
+
<hr class=" col-12 border border-danger">
|
3
|
+
Created by <a href="https://github.com/leatheresque" class="text-decoration-none" target="_blank"><span class="fw-bold text-danger">leatheresque</span></a> © 2023
|
4
|
+
</footer>
|
data/_includes/head.html
ADDED
@@ -0,0 +1,18 @@
|
|
1
|
+
<head>
|
2
|
+
<meta charset="utf-8">
|
3
|
+
<meta name="viewport" content="width=device-width, initial-scale=1">
|
4
|
+
<meta name="description" content="{{site.description}}">
|
5
|
+
<meta name="author" content="{{site.author}}">
|
6
|
+
|
7
|
+
<title>{{site.title}}</title>
|
8
|
+
|
9
|
+
<!-- Bootstrap v5.3 CSS -->
|
10
|
+
<link href="https://getbootstrap.com/docs/5.3/dist/css/bootstrap.min.css" rel="stylesheet" integrity="sha384-KK94CHFLLe+nY2dmCWGMq91rCGa5gtU4mk92HdvYe+M/SXH301p5ILy+dN9+nJOZ" crossorigin="anonymous">
|
11
|
+
|
12
|
+
<!-- Font Awesome v6.4.0 CSS -->
|
13
|
+
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.0/css/all.min.css" integrity="sha512-iecdLmaskl7CVkqkXNQ/ZH/XLlvWZOJyj7Yy7tcenmpD1ypASozpmT/E0iPtmFIB46ZmdtAc9eNBvH0H/ZpiBw==" crossorigin="anonymous" referrerpolicy="no-referrer" />
|
14
|
+
|
15
|
+
<!-- Favicons -->
|
16
|
+
<link rel="icon" href="{{ '/assets/imgs/ruby.png' | absolute_url }}" sizes="32x32" type="image/png">
|
17
|
+
|
18
|
+
</head>
|
@@ -0,0 +1,27 @@
|
|
1
|
+
<header class="d-flex">
|
2
|
+
<nav class="navbar navbar-expand-lg w-100">
|
3
|
+
<div class="container-fluid">
|
4
|
+
<a class="navbar-brand" href="#">
|
5
|
+
<img src="{{ '/assets/imgs/ruby.png' | absolute_url }}" height="32" alt="logo">
|
6
|
+
<span class="fs-4"> {{site.title}}</span>
|
7
|
+
</a>
|
8
|
+
<button class="navbar-toggler" type="button" data-bs-toggle="collapse" data-bs-target="#navbarNav" aria-controls="navbarNav" aria-expanded="false" aria-label="Toggle navigation">
|
9
|
+
<span class="navbar-toggler-icon"></span>
|
10
|
+
</button>
|
11
|
+
<div class="collapse navbar-collapse" id="navbarNav">
|
12
|
+
<ul class="navbar-nav ms-auto">
|
13
|
+
<li class="nav-item">
|
14
|
+
<a class="nav-link fw-bold" href="{{ '/' | absolute_url }}">Home</a>
|
15
|
+
</li>
|
16
|
+
<li class="nav-item">
|
17
|
+
<a class="nav-link fw-bold" href="{{ '/blog' | absolute_url }}">Blog</a>
|
18
|
+
</li>
|
19
|
+
<li class="nav-item">
|
20
|
+
<a class="nav-link fw-bold" href="{{ '/about' | absolute_url }}">About</a>
|
21
|
+
</li>
|
22
|
+
</ul>
|
23
|
+
</div>
|
24
|
+
</div>
|
25
|
+
</nav>
|
26
|
+
|
27
|
+
</header>
|
@@ -0,0 +1,36 @@
|
|
1
|
+
<div class="col-md-6">
|
2
|
+
<h2 class="text-body-emphasis">Starter Projects</h2>
|
3
|
+
<p>Ready to beyond the base template? Check out these other open source jekyll themes that you can quickly duplicate to a new GitHub repository by using the template. These all are also <code>gems</code> so you can simply <code>gem install themename</code></p>
|
4
|
+
<ul class="list-unstyled ps-0">
|
5
|
+
<li>
|
6
|
+
<a class="text-danger icon-link mb-1" href="https://github.com/jekyllgems/newspaper" rel="noopener" target="_blank">
|
7
|
+
<i class="fa-solid fa-circle-right"></i>
|
8
|
+
Newspaper Theme
|
9
|
+
</a>
|
10
|
+
</li>
|
11
|
+
<li>
|
12
|
+
<a class="text-danger icon-link mb-1" href="https://github.com/jekyllgems/resume" rel="noopener" target="_blank">
|
13
|
+
<i class="fa-solid fa-circle-right"></i>
|
14
|
+
Resume Theme
|
15
|
+
</a>
|
16
|
+
</li>
|
17
|
+
<li>
|
18
|
+
<a class="text-danger icon-link mb-1" href="https://github.com/jekyllgems/portfolio" rel="noopener" target="_blank">
|
19
|
+
<i class="fa-solid fa-circle-right"></i>
|
20
|
+
Portfolio Theme
|
21
|
+
</a>
|
22
|
+
</li>
|
23
|
+
<li>
|
24
|
+
<a class="text-danger icon-link mb-1" href="https://github.com/jekyllgems/documentation" rel="noopener" target="_blank">
|
25
|
+
<i class="fa-solid fa-circle-right"></i>
|
26
|
+
Documentation Theme
|
27
|
+
</a>
|
28
|
+
</li>
|
29
|
+
<li>
|
30
|
+
<a class="text-danger icon-link mb-1" href="https://github.com/jekyllgems/bs5" rel="noopener" target="_blank">
|
31
|
+
<i class="fa-solid fa-circle-right"></i>
|
32
|
+
Starter Theme
|
33
|
+
</a>
|
34
|
+
</li>
|
35
|
+
</ul>
|
36
|
+
</div>
|
data/_layouts/blog.html
ADDED
@@ -0,0 +1,53 @@
|
|
1
|
+
<!doctype html>
|
2
|
+
<html lang="en" class="h-100">
|
3
|
+
|
4
|
+
{% include head.html %}
|
5
|
+
|
6
|
+
<body class="d-flex flex-column h-100">
|
7
|
+
|
8
|
+
<div class="col-lg-8 mx-auto p-4 py-md-5">
|
9
|
+
|
10
|
+
{% include header.html %}
|
11
|
+
|
12
|
+
<main>
|
13
|
+
<hr class="col-12 mb-5 border border-danger">
|
14
|
+
|
15
|
+
{{ content }}
|
16
|
+
|
17
|
+
<div class="mb-5">
|
18
|
+
{% for post in site.posts %}
|
19
|
+
|
20
|
+
<ul class="list-unstyled">
|
21
|
+
<li>
|
22
|
+
<a class="text-decoration-none text-danger" href="{{site.url}}{{site.baseurl}}{{ post.url }}">
|
23
|
+
<h3 class="lh-1">{{post.title}} - <span class="fs-5">{{post.date | date: "%B %d, %Y" }}</span></h3>
|
24
|
+
<p class="text-secondary">By: {{ post.author }}</p>
|
25
|
+
</a>
|
26
|
+
</li>
|
27
|
+
</ul>
|
28
|
+
|
29
|
+
{% endfor %}
|
30
|
+
</div>
|
31
|
+
|
32
|
+
<hr class="col-3 col-md-5 mb-5 border border-danger">
|
33
|
+
|
34
|
+
|
35
|
+
<div class="row g-5">
|
36
|
+
|
37
|
+
<!-- Begin Jekyllgems Themes -->
|
38
|
+
{% include theme-list.html %}
|
39
|
+
<!-- //End Jekyllgems Themes -->
|
40
|
+
|
41
|
+
<!-- Begin Categories -->
|
42
|
+
{% include categories.html %}
|
43
|
+
<!-- //End Categories -->
|
44
|
+
</div>
|
45
|
+
</main>
|
46
|
+
|
47
|
+
{% include footer.html %}
|
48
|
+
|
49
|
+
<script src="https://getbootstrap.com/docs/5.3/dist/js/bootstrap.bundle.min.js" integrity="sha384-w76AqPfDkMBDXo30jS1Sgez6pr3x5MlQ1ZAGC+nuZB+EYdgRZgiwxhTBTkF7CXvN" crossorigin="anonymous"></script>
|
50
|
+
|
51
|
+
</body>
|
52
|
+
|
53
|
+
</html>
|
@@ -0,0 +1,38 @@
|
|
1
|
+
<!doctype html>
|
2
|
+
<html lang="en" class="h-100">
|
3
|
+
|
4
|
+
{% include head.html %}
|
5
|
+
|
6
|
+
<body class="d-flex flex-column h-100">
|
7
|
+
|
8
|
+
<div class="col-lg-8 mx-auto p-4 py-md-5">
|
9
|
+
|
10
|
+
{% include header.html %}
|
11
|
+
|
12
|
+
<main>
|
13
|
+
<hr class="col-12 mb-5 border border-danger">
|
14
|
+
|
15
|
+
{{ content }}
|
16
|
+
|
17
|
+
<hr class="col-3 col-md-5 mb-5 border border-danger">
|
18
|
+
|
19
|
+
|
20
|
+
<div class="row g-5">
|
21
|
+
|
22
|
+
<!-- Begin Jekyllgems Themes -->
|
23
|
+
{% include theme-list.html %}
|
24
|
+
<!-- //End Jekyllgems Themes -->
|
25
|
+
|
26
|
+
<!-- Begin Jekyllgems Blog Posts -->
|
27
|
+
{% include feed.html %}
|
28
|
+
<!-- //End Blog Posts -->
|
29
|
+
</div>
|
30
|
+
</main>
|
31
|
+
|
32
|
+
{% include footer.html %}
|
33
|
+
|
34
|
+
<script src="https://getbootstrap.com/docs/5.3/dist/js/bootstrap.bundle.min.js" integrity="sha384-w76AqPfDkMBDXo30jS1Sgez6pr3x5MlQ1ZAGC+nuZB+EYdgRZgiwxhTBTkF7CXvN" crossorigin="anonymous"></script>
|
35
|
+
|
36
|
+
</body>
|
37
|
+
|
38
|
+
</html>
|
data/_layouts/page.html
ADDED
@@ -0,0 +1,38 @@
|
|
1
|
+
<!doctype html>
|
2
|
+
<html lang="en" class="h-100">
|
3
|
+
|
4
|
+
{% include head.html %}
|
5
|
+
|
6
|
+
<body class="d-flex flex-column h-100">
|
7
|
+
|
8
|
+
<div class="col-lg-8 mx-auto p-4 py-md-5">
|
9
|
+
|
10
|
+
{% include header.html %}
|
11
|
+
|
12
|
+
<main>
|
13
|
+
<hr class="col-12 mb-5 border border-danger">
|
14
|
+
|
15
|
+
{{ content }}
|
16
|
+
|
17
|
+
<hr class="col-3 col-md-5 mb-5 border border-danger">
|
18
|
+
|
19
|
+
|
20
|
+
<div class="row g-5">
|
21
|
+
|
22
|
+
<!-- Begin Jekyllgems Themes -->
|
23
|
+
{% include theme-list.html %}
|
24
|
+
<!-- //End Jekyllgems Themes -->
|
25
|
+
|
26
|
+
<!-- Begin Jekyllgems Blog Posts -->
|
27
|
+
{% include feed.html %}
|
28
|
+
<!-- //End Blog Posts -->
|
29
|
+
</div>
|
30
|
+
</main>
|
31
|
+
|
32
|
+
{% include footer.html %}
|
33
|
+
|
34
|
+
<script src="https://getbootstrap.com/docs/5.3/dist/js/bootstrap.bundle.min.js" integrity="sha384-w76AqPfDkMBDXo30jS1Sgez6pr3x5MlQ1ZAGC+nuZB+EYdgRZgiwxhTBTkF7CXvN" crossorigin="anonymous"></script>
|
35
|
+
|
36
|
+
</body>
|
37
|
+
|
38
|
+
</html>
|
data/_layouts/post.html
ADDED
@@ -0,0 +1,38 @@
|
|
1
|
+
<!doctype html>
|
2
|
+
<html lang="en" class="h-100">
|
3
|
+
|
4
|
+
{% include head.html %}
|
5
|
+
|
6
|
+
<body class="d-flex flex-column h-100">
|
7
|
+
|
8
|
+
<div class="col-lg-8 mx-auto p-4 py-md-5">
|
9
|
+
|
10
|
+
{% include header.html %}
|
11
|
+
|
12
|
+
<main>
|
13
|
+
<hr class="col-12 mb-5 border border-danger">
|
14
|
+
|
15
|
+
{{ content }}
|
16
|
+
|
17
|
+
<hr class="col-3 col-md-5 mb-5 border border-danger">
|
18
|
+
|
19
|
+
|
20
|
+
<div class="row g-5">
|
21
|
+
|
22
|
+
<!-- Begin Categories -->
|
23
|
+
{% include categories.html %}
|
24
|
+
<!-- //End Categories -->
|
25
|
+
|
26
|
+
<!-- Begin Jekyllgems Blog Posts -->
|
27
|
+
{% include feed.html %}
|
28
|
+
<!-- //End Blog Posts -->
|
29
|
+
</div>
|
30
|
+
</main>
|
31
|
+
|
32
|
+
{% include footer.html %}
|
33
|
+
|
34
|
+
<script src="https://getbootstrap.com/docs/5.3/dist/js/bootstrap.bundle.min.js" integrity="sha384-w76AqPfDkMBDXo30jS1Sgez6pr3x5MlQ1ZAGC+nuZB+EYdgRZgiwxhTBTkF7CXvN" crossorigin="anonymous"></script>
|
35
|
+
|
36
|
+
</body>
|
37
|
+
|
38
|
+
</html>
|
@@ -0,0 +1,14 @@
|
|
1
|
+
---
|
2
|
+
layout: post
|
3
|
+
title: Using Jekyllgems Templates On Github
|
4
|
+
author: leatheresque
|
5
|
+
categories: themes jekyll
|
6
|
+
---
|
7
|
+
|
8
|
+
# {{ page.title }}
|
9
|
+
On: {{ page.date | date: "%B %d, %Y" }}
|
10
|
+
|
11
|
+
{:. .col-lg-8}
|
12
|
+
* * *
|
13
|
+
|
14
|
+
When you navigate to the repository for one of the gems I made you will see the green button in the repo says "Use This Template". If you press that button it will create a new repo for you which will use the template to create all the files you need. Then you edit your files, go into Settings > Pages and serve it up. It really is a simple process
|
@@ -0,0 +1,23 @@
|
|
1
|
+
---
|
2
|
+
layout: post
|
3
|
+
title: Installing Jekyllgems Themes On Your Site
|
4
|
+
author: leatheresque
|
5
|
+
categories: themes
|
6
|
+
---
|
7
|
+
|
8
|
+
# {{ page.title }}
|
9
|
+
On: {{ page.date | date: "%B %d, %Y" }}
|
10
|
+
|
11
|
+
{:. .col-lg-8}
|
12
|
+
* * *
|
13
|
+
|
14
|
+
If you already have a site installed on your server and you want to use one of my themes, you should save your posts first. Save your data files, and then in your Gemfile edit the line where you find this comment:
|
15
|
+
|
16
|
+
```yaml
|
17
|
+
# This is the default theme for new Jekyll base site
|
18
|
+
# You may change this to anything you like.
|
19
|
+
|
20
|
+
gem "jekyll-base"
|
21
|
+
```
|
22
|
+
|
23
|
+
It may be some other gem being used if you have already been running a site. Just change it to `jekyll-base` and when you run `bundle install` it will pull the gem you need along with the files you need and install everything. Then you run `bundle exec jekyll serve` and it will serve up your site.
|
@@ -0,0 +1,72 @@
|
|
1
|
+
---
|
2
|
+
layout: post
|
3
|
+
title: How To Configure A jekyll Site
|
4
|
+
author: leatheresque
|
5
|
+
categories: jekyll configuration
|
6
|
+
---
|
7
|
+
|
8
|
+
# {{ page.title }}
|
9
|
+
On: {{ page.date | date: "%B %d, %Y" }}
|
10
|
+
|
11
|
+
{:. .col-lg-8}
|
12
|
+
* * *
|
13
|
+
|
14
|
+
Jekyll is a popular static site generator that allows you to build fast and secure websites without the need for a database. It is easy to set up and use, and it's perfect for personal blogs or small business websites. In this tutorial, we will guide you through the process of configuring your Jekyll site's _config.yml file.
|
15
|
+
|
16
|
+
### Step 1: Creating the _config.yml file
|
17
|
+
The _config.yml file is the main configuration file for your Jekyll site. It contains settings that control how your site is generated and displayed. To create the file, open your favorite text editor and create a new file called _config.yml in the root directory of your Jekyll site.
|
18
|
+
|
19
|
+
### Step 2: Setting the site title and description
|
20
|
+
The first settings you should configure in your _config.yml file are the site title and description. These settings control the text that appears in your site's header and in search engine results.
|
21
|
+
|
22
|
+
```
|
23
|
+
title: My Jekyll Site
|
24
|
+
description: A simple Jekyll site
|
25
|
+
```
|
26
|
+
|
27
|
+
### Step 3: Configuring the site URL
|
28
|
+
The url setting specifies the base URL of your site. This is used to generate links throughout your site and is also used by Jekyll to construct the site's sitemap.
|
29
|
+
|
30
|
+
```
|
31
|
+
url: https://example.com
|
32
|
+
```
|
33
|
+
|
34
|
+
### Step 4: Setting the permalink structure
|
35
|
+
The permalink setting specifies the URL structure for your site's pages and posts. By default, Jekyll uses a simple structure that includes the page or post title and the date it was created. However, you can customize this structure to suit your needs.
|
36
|
+
|
37
|
+
```ruby
|
38
|
+
permalink: /:categories/:title/
|
39
|
+
```
|
40
|
+
This setting will generate URLs that include the post's category and title.
|
41
|
+
|
42
|
+
### Step 5: Configuring the theme
|
43
|
+
Jekyll allows you to use pre-built themes to quickly set up the look and feel of your site. To use a theme, you'll need to specify it in your _config.yml file.
|
44
|
+
|
45
|
+
```
|
46
|
+
theme: minima
|
47
|
+
```
|
48
|
+
This setting will use the "Minima" theme, which is the default theme for new Jekyll sites.
|
49
|
+
|
50
|
+
### Step 6: Configuring other settings
|
51
|
+
Jekyll has many other settings that you can configure in your _config.yml file. Here are a few examples:
|
52
|
+
|
53
|
+
```
|
54
|
+
# Exclude files or directories from the site
|
55
|
+
exclude:
|
56
|
+
- Gemfile
|
57
|
+
- Gemfile.lock
|
58
|
+
- README.md
|
59
|
+
|
60
|
+
# Configure plugins
|
61
|
+
plugins:
|
62
|
+
- jekyll-seo-tag
|
63
|
+
|
64
|
+
# Set the default language for the site
|
65
|
+
lang: en
|
66
|
+
|
67
|
+
# Set the timezone
|
68
|
+
timezone: America/New_York
|
69
|
+
```
|
70
|
+
|
71
|
+
### Conclusion
|
72
|
+
Configuring your Jekyll site's _config.yml file is an important step in setting up your site. By following the steps in this tutorial, you should now have a basic understanding of how to configure your site's settings. If you want to learn more about Jekyll, check out the official documentation. To see an example of a full configuration file and a very minimal one, go to this [_config.yml Gist](https://gist.github.com/leatheresque/07bc464eccfd2bae98f959fa55354086)
|
@@ -0,0 +1,35 @@
|
|
1
|
+
---
|
2
|
+
layout: post
|
3
|
+
title: How To Setup Ruby & Jekyll
|
4
|
+
author: leatheresque
|
5
|
+
categories: jekyll ruby installation
|
6
|
+
---
|
7
|
+
|
8
|
+
# {{ page.title }}
|
9
|
+
On: {{ page.date | date: "%B %d, %Y" }}
|
10
|
+
|
11
|
+
{:. .col-lg-8}
|
12
|
+
* * *
|
13
|
+
|
14
|
+
In this post you will learn how to setup Ruby and Jekyll on your Linux server in order to use this theme. I use Ubuntu Linux so I will walk you through setting up on that system. First you need to run:
|
15
|
+
|
16
|
+
```bash
|
17
|
+
sudo apt-get install ruby-full build-essential zlib1g-dev
|
18
|
+
```
|
19
|
+
|
20
|
+
Avoid installing RubyGems packages (called gems) as the root user. Instead, set up a gem installation directory for your user account. The following commands will add environment variables to your `~/.bashrc` file to configure the gem installation path:
|
21
|
+
|
22
|
+
```bash
|
23
|
+
echo '# Install Ruby Gems to ~/gems' >> ~/.bashrc
|
24
|
+
echo 'export GEM_HOME="$HOME/gems"' >> ~/.bashrc
|
25
|
+
echo 'export PATH="$HOME/gems/bin:$PATH"' >> ~/.bashrc
|
26
|
+
source ~/.bashrc
|
27
|
+
```
|
28
|
+
|
29
|
+
Finally, install Jekyll and Bundler:
|
30
|
+
|
31
|
+
```bash
|
32
|
+
gem install jekyll bundler
|
33
|
+
```
|
34
|
+
|
35
|
+
That’s it! You’re ready to start using Jekyll. Read the next guide to learn "How To Configure Your Site _config.yml"
|
data/about.md
ADDED
data/assets/css/main.css
ADDED
File without changes
|
Binary file
|
data/blog.md
ADDED
@@ -0,0 +1,10 @@
|
|
1
|
+
---
|
2
|
+
layout: blog
|
3
|
+
title: Blog
|
4
|
+
permalink: /blog
|
5
|
+
---
|
6
|
+
|
7
|
+
# {{ page.title }}
|
8
|
+
|
9
|
+
{:. .col-lg-6}
|
10
|
+
These posts have been written as a guide to help you get your site up and running. If you should have any issues or errors feel free to reach out. Once you have your site up and running you can view more plugins and helpful tips for your blog on my site.
|
data/index.md
ADDED
@@ -0,0 +1,13 @@
|
|
1
|
+
---
|
2
|
+
layout: default
|
3
|
+
title: Home
|
4
|
+
---
|
5
|
+
|
6
|
+
<h1 class="text-body-emphasis">Get started with Jekyll</h1>
|
7
|
+
<p class="fs-5 col-md-8">Quickly and easily get started with Jekyll using Bootstrap's compiled, production-ready files with this barebones example featuring some basic HTML and helpful links. Download more Jekyll themes, called <code>gems</code> from jekyllgems free for the community to get started.</p>
|
8
|
+
|
9
|
+
<div class="mb-5">
|
10
|
+
<a href="https://github.com/jekyllgems/themes" target="_blank" class="btn btn-danger px-4">
|
11
|
+
<i class="fa-solid fa-up-right-from-square"></i> More Themes
|
12
|
+
</a>
|
13
|
+
</div>
|
metadata
CHANGED
@@ -1,33 +1,46 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: jekyll-base
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.0.
|
4
|
+
version: 0.0.2
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Joseph Parkton
|
8
8
|
autorequire:
|
9
9
|
bindir: exe
|
10
10
|
cert_chain: []
|
11
|
-
date: 2023-04-
|
11
|
+
date: 2023-04-06 00:00:00.000000000 Z
|
12
12
|
dependencies: []
|
13
|
-
description:
|
14
|
-
minima
|
13
|
+
description:
|
15
14
|
email:
|
16
15
|
- jekyllcoder@gmail.com
|
17
16
|
executables: []
|
18
17
|
extensions: []
|
19
18
|
extra_rdoc_files: []
|
20
19
|
files:
|
21
|
-
- CHANGELOG.md
|
22
|
-
- CODE_OF_CONDUCT.md
|
23
20
|
- Gemfile
|
24
|
-
-
|
21
|
+
- Gemfile.lock
|
22
|
+
- LICENSE
|
25
23
|
- README.md
|
26
|
-
-
|
27
|
-
-
|
28
|
-
-
|
29
|
-
-
|
30
|
-
-
|
24
|
+
- _config.yml
|
25
|
+
- _includes/categories.html
|
26
|
+
- _includes/feed.html
|
27
|
+
- _includes/footer.html
|
28
|
+
- _includes/head.html
|
29
|
+
- _includes/header.html
|
30
|
+
- _includes/theme-list.html
|
31
|
+
- _layouts/blog.html
|
32
|
+
- _layouts/default.html
|
33
|
+
- _layouts/page.html
|
34
|
+
- _layouts/post.html
|
35
|
+
- _posts/2023-03-15-github-templates.md
|
36
|
+
- _posts/2023-03-24-Installing-themes.md
|
37
|
+
- _posts/2023-04-03-config.md
|
38
|
+
- _posts/2023-04-04-Setup-Jekyll.md
|
39
|
+
- about.md
|
40
|
+
- assets/css/main.css
|
41
|
+
- assets/imgs/ruby.png
|
42
|
+
- blog.md
|
43
|
+
- index.md
|
31
44
|
homepage: https://github.com/jekyllgems/base
|
32
45
|
licenses:
|
33
46
|
- MIT
|
@@ -53,5 +66,6 @@ requirements: []
|
|
53
66
|
rubygems_version: 3.3.7
|
54
67
|
signing_key:
|
55
68
|
specification_version: 4
|
56
|
-
summary:
|
69
|
+
summary: Jekyll Base is a a simple gem to replace the minima theme. It includes Bootstrap
|
70
|
+
v5.3 and Font Awesome v6.4.0.
|
57
71
|
test_files: []
|
data/CHANGELOG.md
DELETED
data/CODE_OF_CONDUCT.md
DELETED
@@ -1,84 +0,0 @@
|
|
1
|
-
# Contributor Covenant Code of Conduct
|
2
|
-
|
3
|
-
## Our Pledge
|
4
|
-
|
5
|
-
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
|
6
|
-
|
7
|
-
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
|
8
|
-
|
9
|
-
## Our Standards
|
10
|
-
|
11
|
-
Examples of behavior that contributes to a positive environment for our community include:
|
12
|
-
|
13
|
-
* Demonstrating empathy and kindness toward other people
|
14
|
-
* Being respectful of differing opinions, viewpoints, and experiences
|
15
|
-
* Giving and gracefully accepting constructive feedback
|
16
|
-
* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
|
17
|
-
* Focusing on what is best not just for us as individuals, but for the overall community
|
18
|
-
|
19
|
-
Examples of unacceptable behavior include:
|
20
|
-
|
21
|
-
* The use of sexualized language or imagery, and sexual attention or
|
22
|
-
advances of any kind
|
23
|
-
* Trolling, insulting or derogatory comments, and personal or political attacks
|
24
|
-
* Public or private harassment
|
25
|
-
* Publishing others' private information, such as a physical or email
|
26
|
-
address, without their explicit permission
|
27
|
-
* Other conduct which could reasonably be considered inappropriate in a
|
28
|
-
professional setting
|
29
|
-
|
30
|
-
## Enforcement Responsibilities
|
31
|
-
|
32
|
-
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
|
33
|
-
|
34
|
-
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
|
35
|
-
|
36
|
-
## Scope
|
37
|
-
|
38
|
-
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
|
39
|
-
|
40
|
-
## Enforcement
|
41
|
-
|
42
|
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at creekhippybear@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
|
43
|
-
|
44
|
-
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
|
45
|
-
|
46
|
-
## Enforcement Guidelines
|
47
|
-
|
48
|
-
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
|
49
|
-
|
50
|
-
### 1. Correction
|
51
|
-
|
52
|
-
**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
|
53
|
-
|
54
|
-
**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
|
55
|
-
|
56
|
-
### 2. Warning
|
57
|
-
|
58
|
-
**Community Impact**: A violation through a single incident or series of actions.
|
59
|
-
|
60
|
-
**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
|
61
|
-
|
62
|
-
### 3. Temporary Ban
|
63
|
-
|
64
|
-
**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
|
65
|
-
|
66
|
-
**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
|
67
|
-
|
68
|
-
### 4. Permanent Ban
|
69
|
-
|
70
|
-
**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
|
71
|
-
|
72
|
-
**Consequence**: A permanent ban from any sort of public interaction within the community.
|
73
|
-
|
74
|
-
## Attribution
|
75
|
-
|
76
|
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
|
77
|
-
available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
|
78
|
-
|
79
|
-
Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
|
80
|
-
|
81
|
-
[homepage]: https://www.contributor-covenant.org
|
82
|
-
|
83
|
-
For answers to common questions about this code of conduct, see the FAQ at
|
84
|
-
https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
|
data/Rakefile
DELETED
data/jekyll-base.gemspec
DELETED
@@ -1,31 +0,0 @@
|
|
1
|
-
# frozen_string_literal: true
|
2
|
-
|
3
|
-
require_relative "lib/jekyll/base/version"
|
4
|
-
|
5
|
-
Gem::Specification.new do |spec|
|
6
|
-
spec.name = "jekyll-base"
|
7
|
-
spec.version = "0.0.1"
|
8
|
-
spec.authors = ["Joseph Parkton"]
|
9
|
-
spec.email = ["jekyllcoder@gmail.com"]
|
10
|
-
|
11
|
-
spec.summary = "This is a minimalist base jekyll site."
|
12
|
-
spec.description = "This is a replacement site for using in new Jekyll projects instead of minima"
|
13
|
-
spec.homepage = "https://github.com/jekyllgems/base"
|
14
|
-
spec.license = "MIT"
|
15
|
-
spec.required_ruby_version = ">= 2.6.0"
|
16
|
-
|
17
|
-
spec.metadata["homepage_uri"] = spec.homepage
|
18
|
-
spec.metadata["source_code_uri"] = spec.homepage
|
19
|
-
spec.metadata["changelog_uri"] = "https://changelog.jekyllgems.dev"
|
20
|
-
|
21
|
-
# Specify which files should be added to the gem when it is released.
|
22
|
-
# The `git ls-files -z` loads the files in the RubyGem that have been added into git.
|
23
|
-
spec.files = Dir.chdir(__dir__) do
|
24
|
-
`git ls-files -z`.split("\x0").reject do |f|
|
25
|
-
(File.expand_path(f) == __FILE__) || f.match(%r{\A(?:(?:bin|test|spec|features)/|\.(?:git|circleci)|appveyor)})
|
26
|
-
end
|
27
|
-
end
|
28
|
-
spec.bindir = "exe"
|
29
|
-
spec.executables = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
|
30
|
-
spec.require_paths = ["lib"]
|
31
|
-
end
|
data/lib/jekyll/base/version.rb
DELETED
data/lib/jekyll/base.rb
DELETED