beautiful-jekyll-theme 2.0.0 → 2.2.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/LICENSE +2 -11
- data/README.md +46 -98
- data/_includes/disqus.html +1 -1
- data/_includes/footer.html +1 -1
- data/_includes/head.html +1 -1
- data/_includes/social-networks-links.html +12 -0
- data/_includes/staticman-comments.html +2 -2
- metadata +5 -3
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 13abeddaf7631ad4c6dd69586d347daa2efea67223809756ff4a72875e2af73e
|
4
|
+
data.tar.gz: 857382212af724f0ea8fd4f24fa3d122f37cddacd0284a537cec558fe1f35ec8
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 7eaac63fe4233d66e59494114dc9ff1489ee97acb49a5b6cf218fe0551e388d1c7c1da30679ebe89e8ba045b7067377edafc9ac3d626bad89f7c47392ca9f051
|
7
|
+
data.tar.gz: ff74408ddacd8eed700f44a68865cfecc98f8e9fec71c5e8fb21b212b3fcd58ea337f7b7aad0ba26d927eb1a2c0b78b48b5663b069f5cfdbe0166ccae79f5088
|
data/LICENSE
CHANGED
@@ -1,6 +1,6 @@
|
|
1
|
-
|
1
|
+
MIT License
|
2
2
|
|
3
|
-
Copyright (c)
|
3
|
+
Copyright (c) 2020 Dean Attali
|
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
|
@@ -19,12 +19,3 @@ 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
20
|
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
21
21
|
SOFTWARE.
|
22
|
-
|
23
|
-
|
24
|
-
|
25
|
-
staticman integration
|
26
|
-
=================================================================================
|
27
|
-
|
28
|
-
The MIT License (MIT)
|
29
|
-
|
30
|
-
Copyright (c) 2013-2018 Michael Rose
|
data/README.md
CHANGED
@@ -5,7 +5,7 @@
|
|
5
5
|
|
6
6
|
> *Copyright 2020 [Dean Attali](https://deanattali.com)*
|
7
7
|
|
8
|
-
**Beautiful Jekyll** is a ready-to-use template to help you create an awesome website quickly. Perfect for personal sites, blogs, or simple project websites. [Check out a demo](https://
|
8
|
+
**Beautiful Jekyll** is a ready-to-use template to help you create an awesome website quickly. Perfect for personal sites, blogs, or simple project websites. [Check out a demo](https://beautifuljekyll.com) of what you'll get after just two minutes. You can also look at [my personal website](https://deanattali.com) to see it in use, or see examples of websites other people created using this theme [below](#showcased-users-success-stories).
|
9
9
|
|
10
10
|
**If you enjoy this theme, please consider [supporting me](http://paypal.me/daattali) or [sponsoring me](https://github.com/sponsors/daattali) for developing and maintaining it for over 5 years.**
|
11
11
|
|
@@ -20,43 +20,65 @@
|
|
20
20
|
|
21
21
|
### Table of contents
|
22
22
|
|
23
|
+
- [Features](#features)
|
23
24
|
- [Build your website in 3 steps](#build-your-website-in-3-steps)
|
24
25
|
- [Add your own content](#add-your-own-content)
|
25
26
|
- [Last important thing: parameters for each page](#last-important-thing-parameters-for-each-page)
|
26
|
-
- [Features](#features)
|
27
27
|
- [Supported YAML front matter parameters](#supported-yaml-front-matter-parameters)
|
28
28
|
- [Showcased users (success stories!)](#showcased-users-success-stories)
|
29
|
-
- [Advanced: Using `remote_theme`](#advanced-using-remote_theme)
|
30
29
|
- [FAQ and support](#faq-and-support)
|
31
30
|
- [Credits and contributions](#credits)
|
32
31
|
|
32
|
+
## Features
|
33
|
+
|
34
|
+
- **SIMPLE**: The primary goal of Beautiful Jekyll is to allow literally *anyone* to create a website in a few minutes.
|
35
|
+
- **Mobile-first**: Designed to look great on both large-screen and small-screen (mobile) devices.
|
36
|
+
- **Highly customizable**: Many personalization settings such as changing the background colour/image, adding a logo.
|
37
|
+
- **Two-level navigation menu**: If you have many pages and your menu is getting cluttered, separate your menu into two levels.
|
38
|
+
- **Flexible usage**: Install Beautiful Jekyll directly from GitHub or using a Ruby gem - choose the right [development method](#build-your-website-in-3-steps) for you.
|
39
|
+
- **Battle-tested**: By using Beautiful Jekyll, you'll be joining tens of thousands of users who used this theme since 2015.
|
40
|
+
- **Links to your social media**: You can easily add links to any of your social media accounts in the footer of every page.
|
41
|
+
- **Comments support**: Add comments to any page using one of the supported commenting platforms: [Disqus](https://disqus.com/), [Facebook](https://developers.facebook.com/docs/plugins/comments), [Utterances](https://utteranc.es/), or [Staticman](https://staticman.net).
|
42
|
+
- **Sharing blog posts on social media**: By default, all blog posts have buttons to allow people to share on Twitter/Facebook/LinkedIn.
|
43
|
+
- **Tags**: Any blog post can be tagged with keywords, and an index page showing all the tags is automatically generated.
|
44
|
+
- **Tracking analytics**: Easily integrate Google Analytics, or other analytics platforms, to track visits to your website.
|
45
|
+
- **Photos support**: Any page can have a cover photo around its title, and any blog post can have an associated image.
|
46
|
+
- **More advanced features**: I wrote [a blog post](https://deanattali.com/2015/03/12/beautiful-jekyll-how-to-build-a-site-in-minutes/) describing some more advanced features that I used in my website that can be used in any beautiful-jekyll site.
|
47
|
+
|
33
48
|
## Build your website in 3 steps
|
34
49
|
|
50
|
+
There's a very easy way to use this theme, and there's a hard way. For most people (including myself!), I suggest going the easy route. If you're an advanced user and want to tinker with the hard way (using ruby gems), then [skip the easy way](https://github.com/daattali/beautiful-jekyll#the-hard-way-using-ruby-gems) if you know what you're doing.
|
51
|
+
|
52
|
+
### The easy way (recommended!)
|
53
|
+
|
35
54
|
Getting started is *literally* as easy as 1-2-3 :smile:
|
36
55
|
|
37
56
|
Scroll down to see the steps involved, but here is a 40-second video just as a reference as you work through the steps. If you don't already have a [GitHub account](https://github.com/join), you'll need to sign up.
|
38
57
|
|
39
58
|
![Installation steps](assets/img/install-steps.gif)
|
40
59
|
|
41
|
-
|
60
|
+
#### 1. Fork this project
|
42
61
|
|
43
62
|
Fork this project by clicking the __*Fork*__ button at the top right corner of this page. Forking means that you now copied this entire project and all the files into your account.
|
44
63
|
|
45
|
-
|
64
|
+
#### 2. Rename the project to `<yourusername>.github.io`
|
46
65
|
|
47
66
|
Click on __*Settings*__ at the top (the cog icon) and on that page you'll have an option to rename the project (*repository name*). This will create a website with the **Beautiful Jekyll** template that will be available at `https://<yourusername>.github.io` within a couple minutes. Check out the [FAQ](#faq-and-support) if you want to use a different project name.
|
48
67
|
|
49
|
-
|
68
|
+
#### 3. Customize your website settings
|
50
69
|
|
51
70
|
Edit the `_config.yml` file to change any settings you want. To edit the file, click on it to view the file and then click on the pencil icon to edit it (watch the video tutorial above if you're confused). The settings in the file are self-explanatory and I added comments inside the file to help you understand what each setting does. Any line that begins with a hashtag (`#`) is a comment, and the other lines are actual settings.
|
52
71
|
|
53
|
-
|
72
|
+
#### 4. Congratulations! You have a website!
|
54
73
|
|
55
74
|
After you save your changes to the config file (by clicking on *Commit changes* as the video tutorial shows), your website should be ready in a minute or two at `https://<yourusername>.github.io`. Every time you make a change to any file, your website will get rebuilt and should be updated in about a minute or so. Your website will be initialized with several sample blog posts and a couple other pages.
|
56
75
|
|
57
76
|
Note that in the video above I only edited one setting in the `_config.yml` file. **You should actually go through the rest of the settings as well. Don't be lazy, go through all the settings :)**
|
58
77
|
|
59
|
-
|
78
|
+
### The hard way (using ruby gems)
|
79
|
+
|
80
|
+
If you followed the easy method above, then you already have your site and you can skip this section! If you want to install beautiful-jekyll using ruby gems instead, follow the [advanced installation instructions](https://beautifuljekyll.com/getstarted/#install-steps-hard).
|
81
|
+
|
60
82
|
|
61
83
|
## Add your own content
|
62
84
|
|
@@ -90,55 +112,6 @@ You can look at the top of [`aboutme.md`](https://raw.githubusercontent.com/daat
|
|
90
112
|
|
91
113
|
If you don't include YAML then your file will not use this template.
|
92
114
|
|
93
|
-
## Features
|
94
|
-
|
95
|
-
### Mobile-first
|
96
|
-
|
97
|
-
**Beautiful Jekyll** is designed to look great on both large-screen and small-screen (mobile) devices. Load up your site on your phone or your gigantic iMac, and the site will work well on both, though it will look slightly different.
|
98
|
-
|
99
|
-
### Highly customizable
|
100
|
-
|
101
|
-
Many personalization settings in `_config.yml`, such as setting your name and site's description, changing the background colour/image, setting your avatar to add a little image in the navigation bar, customizing the links in the menus, customizing what social media links to show in the footer, etc.
|
102
|
-
|
103
|
-
### Allowing users to leave comments
|
104
|
-
|
105
|
-
If you want to enable comments on your site, Beautiful Jekyll supports several different commenting platforms you can choose from: [Disqus](https://disqus.com/), [Facebook](https://developers.facebook.com/docs/plugins/comments), [Utterances](https://utteranc.es/), and [Staticman](https://staticman.net). If any of these are set in the configuration file, then all blog posts will have comments turned on by default. To turn off comments on a particular blog post, add `comments: false` to the YAML front matter. If you want to add comments on the bottom of a non-blog page, add `comments: true` to the YAML front matter.
|
106
|
-
|
107
|
-
#### Disqus comments
|
108
|
-
|
109
|
-
To use Disqus, simply sign up to [Disqus](https://disqus.com/) and add your Disqus shortname to the `disqus` parameter in the `_config.yml` file.
|
110
|
-
|
111
|
-
#### Facebook comments
|
112
|
-
|
113
|
-
To use Facebook comments, create a Facebook app using [Facebook developers](https://developers.facebook.com/docs/apps/register), and add the Facebook App ID to the `fb_comment_id` parameter in `_config.yml`.
|
114
|
-
|
115
|
-
#### Utterances comments
|
116
|
-
|
117
|
-
To use [Utterances comments](https://utteranc.es/), follow these steps: (1) Enable Issues in your GitHub repository, (2) Install the Utterances app in your repository (go to https://github.com/apps/utterances), (3) Fill in the `repository` parameter in the utterances section of the `_config.yml` file.
|
118
|
-
|
119
|
-
#### Staticman comments
|
120
|
-
|
121
|
-
To use Staticman, you first need to invite `staticmanlab` as a collaborator to your repository (by going to your repository **Settings** page, navigate to the **Collaborators** tab, and add the username `staticmanlab`), and then accept the invitation by going to `https://staticman3.herokuapp.com/v3/connect/github/<username>/<repo-name>`. Lastly, fill in the `staticman` parameters in the Staticman section of `_config.yml`. You may also choose a different Staticman instance other than `staticmanlab`.
|
122
|
-
|
123
|
-
Optional: You may want to configure a webhook to prevent old inactive branches (representing approved comments) from stacking up. You can refer to [Staticman's documentation](https://staticman.net/docs/webhooks) for details. Make sure to input the **Payload URL** according to your chosen `endpoint`. For example, the default `endpoint` is `https://staticman3.herokuapp.com/v3/entry/github/`, so the corresponding **Payload URL** should be `https://staticman3.herokuapp.com/v1/webhook`.
|
124
|
-
|
125
|
-
|
126
|
-
### Adding Google Analytics to track page views
|
127
|
-
|
128
|
-
Beautiful Jekyll lets you easily add Google Analytics to all your pages. This will let you track all sorts of information about visits to your website, such as how many times each page is viewed and where (geographically) your users come from. To add Google Analytics, simply sign up to [Google Analytics](https://www.google.com/analytics/) to obtain your Google Tracking ID, and add this tracking ID to the `google_analytics` parameter in `_config.yml`.
|
129
|
-
|
130
|
-
### Sharing blog posts on social media
|
131
|
-
|
132
|
-
By default, all blog posts will have buttons at the bottom of the post to allow people to share the current page on Twitter/Facebook/LinkedIn. You can choose to enable/disable specific social media websites in the `_config.yml` file. You can also turn off the social media buttons on specific blog posts using `social-share: false` in the YAML front matter.
|
133
|
-
|
134
|
-
### Page types
|
135
|
-
|
136
|
-
- **post** - To write a blog post, add a markdown or HTML file in the `_posts` folder. As long as you give it YAML front matter (the two lines of three dashes), it will automatically be rendered like a blog post. Look at the existing blog post files to see examples of how to use YAML parameters in blog posts.
|
137
|
-
- **page** - Any page outside the `_posts` folder that uses YAML front matter will have a very similar style to blog posts.
|
138
|
-
- **home** - The home layout is meant to act as the homepage of your blog posts - it will display all your blog posts, sorted from newest to oldest. A file using the `home` layout must be named `index.html` (not `index.md` or anything else!).
|
139
|
-
- **minimal** - If you want to create a page with minimal styling (ie. without the bulky navigation bar and footer), assign `layout: minimal` to the YAML front matter.
|
140
|
-
- If you want to completely bypass the template engine and just write your own HTML page, simply omit the YAML front matter. Only do this if you know how to write HTML!
|
141
|
-
|
142
115
|
## Supported YAML front matter parameters
|
143
116
|
|
144
117
|
These are the main parameters you can place inside a page's YAML front matter that **Beautiful Jekyll** supports.
|
@@ -157,7 +130,7 @@ share-img | If you want to specify an image to use when sharing the page on Fa
|
|
157
130
|
social-share | If you don't want to show buttons to share a blog post on social media, use `social-share: false` (this feature is turned on by default).
|
158
131
|
use-site-title | If you want to use the site title rather than page title as HTML document title (ie. browser tab title), use `use-site-title: true`. When set, the document title will take the format `Site Title - Site Description` (eg. `My website - A virtual proof that name is awesome!`). By default, it will use `Page Title` if it exists, or `Site Title` otherwise.
|
159
132
|
language | HTML language code to be set on <html> element (see [W3Schools website](https://www.w3schools.com/tags/ref_language_codes.asp) for more info on this topic). Language can also be set site-wide in `_config.yml`.
|
160
|
-
layout | What type of page this is (default is `post` for blog posts and `page` for other pages.
|
133
|
+
layout | What type of page this is (default is `post` for blog posts and `page` for other pages). See _Page types_ section below for more information.
|
161
134
|
gh-repo | If you want to show GitHub buttons at the top of a post, this sets the GitHub repo name (eg. `daattali/beautiful-jekyll`). You must also use the `gh-badge` parameter to specify what buttons to show.
|
162
135
|
gh-badge | Select which GitHub buttons to display. Available options are: [star, watch, fork, follow]. You must also use the `gh-repo` parameter to specify the GitHub repo.
|
163
136
|
js | List of local JavaScript files to include in the page (eg. `/assets/js/mypage.js`)
|
@@ -166,9 +139,13 @@ css | List of local CSS files to include in the page
|
|
166
139
|
ext-css | List of external CSS files to include in the page. External CSS files using SRI (see `ext-js` parameter) are also supported.
|
167
140
|
googlefonts | List of Google fonts to include in the page (eg. `["Monoton", "Lobster"]`)
|
168
141
|
|
169
|
-
###
|
142
|
+
### Page types
|
170
143
|
|
171
|
-
|
144
|
+
- **post** - To write a blog post, add a markdown or HTML file in the `_posts` folder. As long as you give it YAML front matter (the two lines of three dashes), it will automatically be rendered like a blog post. Look at the existing blog post files to see examples of how to use YAML parameters in blog posts.
|
145
|
+
- **page** - Any page outside the `_posts` folder that uses YAML front matter will have a very similar style to blog posts.
|
146
|
+
- **home** - The home layout is meant to act as the homepage of your blog posts - it will display all your blog posts, sorted from newest to oldest. A file using the `home` layout must be named `index.html` (not `index.md` or anything else!).
|
147
|
+
- **minimal** - If you want to create a page with minimal styling (ie. without the bulky navigation bar and footer), assign `layout: minimal` to the YAML front matter.
|
148
|
+
- If you want to completely bypass the template engine and just write your own HTML page, simply omit the YAML front matter. Only do this if you know how to write HTML!
|
172
149
|
|
173
150
|
## Showcased users (success stories!)
|
174
151
|
|
@@ -208,33 +185,6 @@ Beautiful Jekyll has been used in over 500 websites in its first 6 months, and t
|
|
208
185
|
| [ocram85.com](https://ocram85.com) | Marco Blessing | A personal blog about PowerShell and automation |
|
209
186
|
| [khanna.cc](https://khanna.cc/) | Harry Khanna | Law and software |
|
210
187
|
|
211
|
-
## Advanced: Using `remote_theme`
|
212
|
-
|
213
|
-
Instead of forking this repository, it's possible to use GitHub's `remote_theme` feature. This is an advanced feature only suitable for people who are familiar with GitHub's remote themes feature and who know how to write jekyll sites from scratch. You can either use remote themes directly on GitHub or a Jekyll plugin - you should look up the official documentation for whichever method you want to use.
|
214
|
-
|
215
|
-
Regardless of which of the two methods you choose, after setting up beautiful-jekyll as a remote theme you'll need to:
|
216
|
-
|
217
|
-
- Edit the `_config.yml` file (or create it if it doesn't exist) and add a line `remote_theme: daattali/beautiful-jekyll` (make sure to remove any previous `theme` or `remote_theme` parameters that may have been there before).
|
218
|
-
- Go through beautiful-jekyll's `_config.yml` file and copy any settings you want to use into your project's config file.
|
219
|
-
- Some features will not work because of missing files that you'll need to copy from beautiful-jekyll into your project. To enable the `tags` feature, you need to copy `tags.html`. To enable the RSS feed, copy `feed.xml`. If you use staticman comments, copy `staticman.yml` and `_data/ui-text.yml`.
|
220
|
-
- Create any pages/blog posts using the YAML parameters and layouts available in Beautiful-Jekyll that are mentioned above.
|
221
|
-
- If you want the home page to include a feed of all blog posts, create an `index.html` file and use `layout: home` in its YAML.
|
222
|
-
- If you want to replace any file served from beautiful-jekyll (such as a CSS file, a layout, or an include), you'll need to place it with the exact same path in your own jekyll repo (e.g. `/assets/css/main.css`)
|
223
|
-
|
224
|
-
Below is a summary of the steps required to set up a site with remote themes:
|
225
|
-
|
226
|
-
#### Remote themes with a GitHub repository
|
227
|
-
|
228
|
-
- Create a new repository or go to an existing repository.
|
229
|
-
- Go to _Settings_, scroll down to the _GitHub Pages_ section, and choose "master branch" as the source (not "master branch /docs folder"!).
|
230
|
-
|
231
|
-
#### Remote themes with a Ruby Jekyll site
|
232
|
-
|
233
|
-
- Create a new jekyll site using `jekyll new <projectname>`.
|
234
|
-
- Add `gem "jekyll-remote-theme"` to your Gemfile and then run `bundle install` to install the plugin.
|
235
|
-
- Add `- jekyll-remote-theme` to the plugins section of your `_config.yml` file to activate the plugin.
|
236
|
-
- Serve the jekyll site as usual (e.g. `bundle exec jekyll serve -H 0.0.0.0`)
|
237
|
-
|
238
188
|
## FAQ and support
|
239
189
|
|
240
190
|
If you need any help, I suggest heading over to the [Jekyll support forum](https://talk.jekyllrb.com/).
|
@@ -245,7 +195,9 @@ Beautiful Jekyll is actively used by thousands of people with wildly varying deg
|
|
245
195
|
|
246
196
|
Every GitHub user can have one repository (repository = project) named `<yourusername>.github.io` and the website for that repository will be `https://<yourusername>.github.io`.
|
247
197
|
|
248
|
-
If you want your project to be named something else, for example `MyAwesomeProject`, that's no problem! All you have to do is go to _Settings_ at the top right corner of the page, and rename your repository to `MyAwesomeProject` (remember to click on the _Rename_ button to confirm
|
198
|
+
If you want your project to be named something else, for example `MyAwesomeProject`, that's no problem! All you have to do is go to _Settings_ at the top right corner of the page, and rename your repository to `MyAwesomeProject` (remember to click on the _Rename_ button to confirm). Then you need to scroll down to the _GitHub Pages_ section and choose "master branch" as the source (not "master branch /docs folder"!).
|
199
|
+
|
200
|
+
Now your website will be at `https://<yourusername>.github.io\MyAwesomeProject`.
|
249
201
|
|
250
202
|
#### How do I change the number of posts per page OR the colour of the navigation bar OR the image in the navigation bar OR ...?
|
251
203
|
|
@@ -267,21 +219,17 @@ Unfortunately, this is a no-answer! There isn't a one-size-fits-all solution to
|
|
267
219
|
|
268
220
|
MathJax can be easily integrated into your website with a one-line addition. You can see [this discussion](https://github.com/daattali/beautiful-jekyll/issues/195) for more information.
|
269
221
|
|
270
|
-
##
|
222
|
+
## Contributions
|
271
223
|
|
272
|
-
|
273
|
-
- [Barry Clark](https://github.com/barryclark) and his project [Jekyll Now](https://github.com/barryclark/jekyll-now), from whom I've taken several ideas and code snippets, as well as some documenation tips.
|
274
|
-
- [Iron Summit Media](https://github.com/IronSummitMedia) and their project [Bootstrap Clean Blog](https://github.com/IronSummitMedia/startbootstrap-clean-blog), from which I've used some design ideas and some of the templating code for posts and pagination.
|
224
|
+
Thank you to [all past contributors](https://github.com/daattali/beautiful-jekyll/graphs/contributors). If you find any problems or would like to contribute in any way, feel free to create a pull request/open an issue/send me a message. Any comments are welcome!
|
275
225
|
|
276
|
-
|
226
|
+
You can also contribute by becoming an [official sponsor](https://github.com/sponsors/daattali) to help keep beautiful-jekyll well-maintained.
|
277
227
|
|
278
|
-
##
|
279
|
-
|
280
|
-
If you find anything wrong or would like to contribute in any way, feel free to create a pull request/open an issue/send me a message. Any comments are welcome!
|
228
|
+
## Credits
|
281
229
|
|
282
|
-
|
230
|
+
This template was not made *entirely* from scratch. I'd like to give special thanks to [Jekyll Now](https://github.com/barryclark/jekyll-now) and [Bootstrap Clean Blog](https://github.com/IronSummitMedia/startbootstrap-clean-blog), from whom I've taken several ideas initially.
|
283
231
|
|
284
|
-
|
232
|
+
I'd also like to thank [Dr. Jekyll's Themes](https://drjekyllthemes.github.io/), [Jekyll Themes](http://jekyllthemes.org/), and another [Jekyll Themes](http://jekyllrc.github.io/jekyllthemes/) for featuring Beautiful Jekyll in their Jekyll theme directories.
|
285
233
|
|
286
234
|
## Known limitations
|
287
235
|
|
data/_includes/disqus.html
CHANGED
@@ -13,7 +13,7 @@
|
|
13
13
|
(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
|
14
14
|
})();
|
15
15
|
</script>
|
16
|
-
<noscript>Please enable JavaScript to view the <a href="
|
16
|
+
<noscript>Please enable JavaScript to view the <a href="https://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>
|
17
17
|
</div>
|
18
18
|
</div>
|
19
19
|
{%- endif -%}
|
data/_includes/footer.html
CHANGED
@@ -25,7 +25,7 @@
|
|
25
25
|
<!-- Please don't remove this, keep my open source work credited :) -->
|
26
26
|
<p class="theme-by text-muted">
|
27
27
|
Theme by
|
28
|
-
<a href="https://
|
28
|
+
<a href="https://beautifuljekyll.com">beautiful-jekyll</a>
|
29
29
|
</p>
|
30
30
|
</div>
|
31
31
|
</div>
|
data/_includes/head.html
CHANGED
@@ -127,7 +127,7 @@
|
|
127
127
|
|
128
128
|
{% if page.comments and site.staticman.repository and site.staticman.branch %}
|
129
129
|
<!-- Staticman -->
|
130
|
-
<link rel="stylesheet" href="{{ "/css/staticman.css" | relative_url }}" />
|
130
|
+
<link rel="stylesheet" href="{{ "/assets/css/staticman.css" | relative_url }}" />
|
131
131
|
{% endif %}
|
132
132
|
|
133
133
|
</head>
|
@@ -24,6 +24,18 @@
|
|
24
24
|
</li>
|
25
25
|
{%- endif -%}
|
26
26
|
|
27
|
+
{%- if site.social-network-links.telegram -%}
|
28
|
+
<li>
|
29
|
+
<a href="https://t.me/{{ site.social-network-links.telegram }}" title="Telegram">
|
30
|
+
<span class="fa-stack fa-lg" aria-hidden="true">
|
31
|
+
<i class="fas fa-circle fa-stack-2x"></i>
|
32
|
+
<i class="fab fa-telegram-plane fa-stack-1x fa-inverse"></i>
|
33
|
+
</span>
|
34
|
+
<span class="sr-only">Telegram</span>
|
35
|
+
</a>
|
36
|
+
</li>
|
37
|
+
{%- endif -%}
|
38
|
+
|
27
39
|
{%- if site.social-network-links.github -%}
|
28
40
|
<li>
|
29
41
|
<a href="https://github.com/{{ site.social-network-links.github }}" title="GitHub">
|
@@ -75,9 +75,9 @@
|
|
75
75
|
<!-- doing something a bit funky here because I want to be careful not to include JQuery twice! -->
|
76
76
|
<script>
|
77
77
|
if (typeof jQuery == 'undefined') {
|
78
|
-
document.write('<script src="{{ "/js/jquery-1.11.2.min.js" | relative_url }}"></scr' + 'ipt>');
|
78
|
+
document.write('<script src="{{ "/assets/js/jquery-1.11.2.min.js" | relative_url }}"></scr' + 'ipt>');
|
79
79
|
}
|
80
80
|
</script>
|
81
|
-
<script src="{{ "/js/staticman.js" | relative_url }}"></script>
|
81
|
+
<script src="{{ "/assets/js/staticman.js" | relative_url }}"></script>
|
82
82
|
</div>
|
83
83
|
{% endif %}
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: beautiful-jekyll-theme
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 2.
|
4
|
+
version: 2.2.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Dean Attali
|
@@ -144,10 +144,12 @@ files:
|
|
144
144
|
- assets/js/staticman.js
|
145
145
|
- feed.xml
|
146
146
|
- tags.html
|
147
|
-
homepage: https://
|
147
|
+
homepage: https://beautifuljekyll.com
|
148
148
|
licenses:
|
149
149
|
- MIT
|
150
|
-
metadata:
|
150
|
+
metadata:
|
151
|
+
changelog_uri: https://github.com/daattali/beautiful-jekyll/blob/master/CHANGELOG.md
|
152
|
+
documentation_uri: https://github.com/daattali/beautiful-jekyll#readme
|
151
153
|
post_install_message:
|
152
154
|
rdoc_options: []
|
153
155
|
require_paths:
|