bulma-clean-theme 0.12 → 0.13

Sign up to get free protection for your applications and to get access to all the features.
Files changed (76) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +10 -687
  3. data/_includes/head.html +1 -1
  4. data/_includes/header.html +1 -1
  5. data/_includes/image-modal.html +1 -1
  6. data/_includes/notification.html +2 -2
  7. data/node_modules/.package-lock.json +4 -9
  8. data/node_modules/bulma-block-list/changelog.txt +3 -0
  9. data/node_modules/bulma-block-list/docs/Gemfile +1 -1
  10. data/node_modules/bulma-block-list/docs/_data/menu.yaml +2 -0
  11. data/node_modules/bulma-block-list/docs/index.html +10 -2
  12. data/node_modules/bulma-block-list/package.json +3 -10
  13. data/package-lock.json +10 -22
  14. data/package.json +2 -2
  15. metadata +10 -65
  16. data/node_modules/bulma-block-list/node_modules/bulma/CHANGELOG.md +0 -1390
  17. data/node_modules/bulma-block-list/node_modules/bulma/LICENSE +0 -21
  18. data/node_modules/bulma-block-list/node_modules/bulma/README.md +0 -130
  19. data/node_modules/bulma-block-list/node_modules/bulma/bulma.sass +0 -9
  20. data/node_modules/bulma-block-list/node_modules/bulma/css/bulma.css +0 -10855
  21. data/node_modules/bulma-block-list/node_modules/bulma/css/bulma.css.map +0 -1
  22. data/node_modules/bulma-block-list/node_modules/bulma/css/bulma.min.css +0 -1
  23. data/node_modules/bulma-block-list/node_modules/bulma/package.json +0 -77
  24. data/node_modules/bulma-block-list/node_modules/bulma/sass/base/_all.sass +0 -5
  25. data/node_modules/bulma-block-list/node_modules/bulma/sass/base/generic.sass +0 -142
  26. data/node_modules/bulma-block-list/node_modules/bulma/sass/base/helpers.sass +0 -281
  27. data/node_modules/bulma-block-list/node_modules/bulma/sass/base/minireset.sass +0 -79
  28. data/node_modules/bulma-block-list/node_modules/bulma/sass/components/_all.sass +0 -15
  29. data/node_modules/bulma-block-list/node_modules/bulma/sass/components/breadcrumb.sass +0 -75
  30. data/node_modules/bulma-block-list/node_modules/bulma/sass/components/card.sass +0 -79
  31. data/node_modules/bulma-block-list/node_modules/bulma/sass/components/dropdown.sass +0 -81
  32. data/node_modules/bulma-block-list/node_modules/bulma/sass/components/level.sass +0 -77
  33. data/node_modules/bulma-block-list/node_modules/bulma/sass/components/list.sass +0 -39
  34. data/node_modules/bulma-block-list/node_modules/bulma/sass/components/media.sass +0 -50
  35. data/node_modules/bulma-block-list/node_modules/bulma/sass/components/menu.sass +0 -57
  36. data/node_modules/bulma-block-list/node_modules/bulma/sass/components/message.sass +0 -99
  37. data/node_modules/bulma-block-list/node_modules/bulma/sass/components/modal.sass +0 -113
  38. data/node_modules/bulma-block-list/node_modules/bulma/sass/components/navbar.sass +0 -441
  39. data/node_modules/bulma-block-list/node_modules/bulma/sass/components/pagination.sass +0 -150
  40. data/node_modules/bulma-block-list/node_modules/bulma/sass/components/panel.sass +0 -119
  41. data/node_modules/bulma-block-list/node_modules/bulma/sass/components/tabs.sass +0 -151
  42. data/node_modules/bulma-block-list/node_modules/bulma/sass/elements/_all.sass +0 -15
  43. data/node_modules/bulma-block-list/node_modules/bulma/sass/elements/box.sass +0 -24
  44. data/node_modules/bulma-block-list/node_modules/bulma/sass/elements/button.sass +0 -323
  45. data/node_modules/bulma-block-list/node_modules/bulma/sass/elements/container.sass +0 -24
  46. data/node_modules/bulma-block-list/node_modules/bulma/sass/elements/content.sass +0 -155
  47. data/node_modules/bulma-block-list/node_modules/bulma/sass/elements/form.sass +0 -1
  48. data/node_modules/bulma-block-list/node_modules/bulma/sass/elements/icon.sass +0 -21
  49. data/node_modules/bulma-block-list/node_modules/bulma/sass/elements/image.sass +0 -71
  50. data/node_modules/bulma-block-list/node_modules/bulma/sass/elements/notification.sass +0 -43
  51. data/node_modules/bulma-block-list/node_modules/bulma/sass/elements/other.sass +0 -39
  52. data/node_modules/bulma-block-list/node_modules/bulma/sass/elements/progress.sass +0 -67
  53. data/node_modules/bulma-block-list/node_modules/bulma/sass/elements/table.sass +0 -127
  54. data/node_modules/bulma-block-list/node_modules/bulma/sass/elements/tag.sass +0 -128
  55. data/node_modules/bulma-block-list/node_modules/bulma/sass/elements/title.sass +0 -70
  56. data/node_modules/bulma-block-list/node_modules/bulma/sass/form/_all.sass +0 -8
  57. data/node_modules/bulma-block-list/node_modules/bulma/sass/form/checkbox-radio.sass +0 -21
  58. data/node_modules/bulma-block-list/node_modules/bulma/sass/form/file.sass +0 -180
  59. data/node_modules/bulma-block-list/node_modules/bulma/sass/form/input-textarea.sass +0 -64
  60. data/node_modules/bulma-block-list/node_modules/bulma/sass/form/select.sass +0 -85
  61. data/node_modules/bulma-block-list/node_modules/bulma/sass/form/shared.sass +0 -55
  62. data/node_modules/bulma-block-list/node_modules/bulma/sass/form/tools.sass +0 -205
  63. data/node_modules/bulma-block-list/node_modules/bulma/sass/grid/_all.sass +0 -4
  64. data/node_modules/bulma-block-list/node_modules/bulma/sass/grid/columns.sass +0 -504
  65. data/node_modules/bulma-block-list/node_modules/bulma/sass/grid/tiles.sass +0 -34
  66. data/node_modules/bulma-block-list/node_modules/bulma/sass/layout/_all.sass +0 -5
  67. data/node_modules/bulma-block-list/node_modules/bulma/sass/layout/footer.sass +0 -9
  68. data/node_modules/bulma-block-list/node_modules/bulma/sass/layout/hero.sass +0 -145
  69. data/node_modules/bulma-block-list/node_modules/bulma/sass/layout/section.sass +0 -13
  70. data/node_modules/bulma-block-list/node_modules/bulma/sass/utilities/_all.sass +0 -8
  71. data/node_modules/bulma-block-list/node_modules/bulma/sass/utilities/animations.sass +0 -5
  72. data/node_modules/bulma-block-list/node_modules/bulma/sass/utilities/controls.sass +0 -50
  73. data/node_modules/bulma-block-list/node_modules/bulma/sass/utilities/derived-variables.sass +0 -106
  74. data/node_modules/bulma-block-list/node_modules/bulma/sass/utilities/functions.sass +0 -110
  75. data/node_modules/bulma-block-list/node_modules/bulma/sass/utilities/initial-variables.sass +0 -77
  76. data/node_modules/bulma-block-list/node_modules/bulma/sass/utilities/mixins.sass +0 -261
data/README.md CHANGED
@@ -10,32 +10,7 @@ The theme uses [Alpine.js](https://github.com/alpinejs/alpine) for its interacti
10
10
  ## Contents
11
11
 
12
12
  * [Installation](#installation)
13
- * [Usage](#usage)
14
- * [Lang](#lang)
15
- * [Pages](#pages)
16
- * [Page Hero](#page-hero)
17
- * [Table Of Contents](#table-of-contents)
18
- * [Posts](#posts)
19
- * [Post Excerpt and Summary](#post-excerpt-and-summary)
20
- * [Series](#series)
21
- * [Navigation](#navigation)
22
- * [Colours and Styles](#colours-and-styles)
23
- * [Sidebar Visibility](#sidebar-visibility)
24
- * [Menubar](#menubar)
25
- * [Tabs](#tabs)
26
- * [Notifications](#notifications)
27
- * [Tags](#tags)
28
- * [Google Analytics](#google-analytics)
29
- * [Footer](#footer)
30
- * [Products](#products)
31
- * [Scripts](#scripts)
32
- * [Callouts](#callouts)
33
- * [Favicon](#favicon)
34
- * [Showcases](#showcases)
35
- * [Sponsors](#sponsors)
36
- * [Gallery](#gallery)
37
- * [Disqus](#disqus)
38
- * [Recipe](#recipe)
13
+ * [Documentation](#documentation)
39
14
  * [Contributing](#contributing)
40
15
  * [Development](#development)
41
16
  * [Licence](#licence)
@@ -43,8 +18,6 @@ The theme uses [Alpine.js](https://github.com/alpinejs/alpine) for its interacti
43
18
 
44
19
  ## Installation
45
20
 
46
- **This theme requires Jekyll 3.9 to be compatible with GitHub Pages.**
47
-
48
21
  Add this line to your Jekyll site's `Gemfile`:
49
22
 
50
23
  ```ruby
@@ -57,674 +30,24 @@ And add this line to your Jekyll site's `_config.yml`:
57
30
  theme: bulma-clean-theme
58
31
  ```
59
32
 
60
- And then execute:
61
-
62
- $ bundle
63
-
64
- Or install it yourself as:
65
-
66
- $ gem install bulma-clean-theme
67
-
68
- ## Usage
69
-
70
- ### Lang
71
-
72
- The html lang attribute is set to `en` by default but you can override this in the _config.yml file `lang: en`
73
-
74
- ### Pages
75
-
76
- Create your pages as individual Markdown files and use `layout: page` for normal pages. Set the page's title and subtitle in the front matter and it will appear in the hero.
77
-
78
- #### Page Hero
79
-
80
- **New in 0.2** - Heros can now display a background image if you provide a `hero_image: /path/to/image.jpg` setting in your page front matter, or in the [defaults](https://jekyllrb.com/docs/configuration/front-matter-defaults/) in your site's `_config.yml`.
81
-
82
- You can also set the height of the hero by providing a Bulma hero height class in your front matter, such as `hero_height: is-fullwidth`. If you do not provide this, it will revert to `is-medium`.
83
-
84
- **New in 0.5.4** - If you would like to add a call to action button in the hero then add `hero_link` and `hero_link_text` to the page's front matter.
85
-
86
- **New in 0.5.7** - If you would like to hide the hero, you can set `hide_hero: true` in the page's front matter.
87
-
88
- **New in 0.7.1** - If you would like to darken the hero so the title stands out more, you can set `hero_darken: true` in the page's front matter. You can overwrite the default background colour by setting the `$hero-darken` sass variable.
89
-
90
- #### Table Of Contents
91
-
92
- **New in 0.5.8** - If you want to display a table of contents (toc) then add `toc: true` to your page's front matter. You can customise the default table of contents title by setting `toc_title: My Custom Title` in the page's front matter.
93
-
94
- **New in 0.10.3** - If you would prefer to display the contents in the menubar at the side of the page, then use `menubar_toc: true` instead of `toc: true`. This will also override the page's `menubar` setting.
95
-
96
- ### Posts
97
-
98
- If you want posts, create a `_posts` directory to store your posts as per normal Jekyll usage, with `layout: post`. Next, create a `blog` directory with an index.html file that has `layout: blog`.
99
-
100
- Set `paginate` and `paginate_path` in your site's `_config.yaml` to configure the posts per page and blog pagination path.
101
-
102
- ```yaml
103
- paginate: 5
104
- paginate_path: "/blog/page:num"
105
- ```
106
-
107
- **New in 0.2** - It will now display an image in the blog page if you set `image: /path/to/image.jpg` in your post's or page's front matter, or in the [defaults](https://jekyllrb.com/docs/configuration/front-matter-defaults/) in your site's `_config.yml`.
108
-
109
- You can also set the height of the hero by providing a Bulma hero height class in your front matter, such as `hero_height: is-fullwidth`. If you do not provide this, it will revert to `is-medium`.
110
-
111
- #### Post Excerpt and Summary
112
-
113
- By default, the blog page and the latest posts will use the automatically generated post excerpt. If you would like to override this you can set the summary in the post's front matter.
114
-
115
- ```yaml
116
- layout: post
117
- title: The post title
118
- summary: |-
119
- This is the custom summary for the post.
120
-
121
- It can be in **Markdown format** if required.
122
- ```
123
-
124
- #### Series
125
-
126
- From version 0.12, you can now make a post a part of a series of posts, linking to the other posts in the series, by creating a `series` data file and then setting the series in each of the post's front matter.
127
-
128
- The current post in the list is highlighted to help give context of where you are in the series.
129
-
130
- ##### Blog Series Data File
131
-
132
- Start by creating a yml file in the _data directory, for example `my_blog_series.yml`. Give the series a title and, optionally, a description.
133
-
134
- ##### Sections
135
-
136
- Next add sections. Each section can have a label (optional) and items. Each item is the title of an existing blog post. If the title is not found then the link will be empty.
137
-
138
- If you just want one list without labels, then omit the label and just add the items.
139
-
140
- ```yaml
141
- title: The series title
142
- sections:
143
- - items:
144
- - title: Why use a static site generator
145
- - title: Getting started with Bulma Clean Theme for Jekyll
146
- ```
147
-
148
- Here is a full example with multiple sections with labels.
149
-
150
- ```yaml
151
- title: The series title
152
- description: The series description text
153
- sections:
154
- - label: The first section
155
- items:
156
- - title: Why use a static site generator
157
- - title: Getting started with Bulma Clean Theme for Jekyll
158
- - label: Another section
159
- items:
160
- - title: Introducing some new layouts to Bulma Clean Theme
161
- - title: Creating a docs site with Bulma Clean Theme
162
- - title: Creating a post series
163
- ```
164
-
165
- ##### Update your posts
166
-
167
- Finally, add the series setting to your front matter in each post you want the series to show in.
168
-
169
- ```yaml
170
- series: my_blog_series
171
- ```
172
-
173
- #### Social Share Buttons
174
-
175
- Share buttons will be displayed on your posts unless you hide them by adding `hide_share_buttons: true` to your config file.
176
-
177
-
178
- ### Navigation
179
-
180
- For the top navigation, create a navigation.yml file in the `_data` directory with the following format with the pages you want to include in the top navigation. You can now also add items to a dropdown menu.
181
-
182
- ```yaml
183
- - name: Page 1
184
- link: /page-1/
185
- - name: Blog
186
- link: /blog/
187
- dropdown:
188
- - name: Page 2
189
- link: /page-2/
190
- ```
191
-
192
- For the current page to have an active class, ensure the `link:` format matches your [permalink](https://jekyllrb.com/docs/permalinks/#extensionless-permalinks) format. The above example will work with a `permalink: pretty` setting in your `_config.yml`.
193
-
194
- #### Fixed Navbar
195
-
196
- To have a fixed navbar on the top or bottom of your site, you can set `fixed_navbar: top` or `fixed_navbar: bottom` respectively in your
197
- `_config.yml`.
198
-
199
- ### Colours and Styles
200
-
201
- To overwrite the primary theme colour, set a sass variable in `assets/css/app.scss` before importing `main`.
202
-
203
- ```
204
- ---
205
- ---
206
- $primary: #333333;
207
- // Import Main CSS file from theme
208
- @import "main";
209
- ```
210
-
211
- You can overwrite any of the [Bulma initial variables](http://versions.bulma.io/0.7.0/documentation/overview/variables/) in this way as long as they are declared before the `@import "main";`.
212
-
213
- #### Theme Color Meta Tag
214
-
215
- If you want to update the theme color meta tag then set `theme_color: '#333333'` in your `_config.yml` file.
216
-
217
- ### Sidebar Visibility
218
-
219
- **New in 0.2** - If you want to show the sidebar with latest posts then set `show_sidebar: true` in the page's frontmatter, or in the [defaults](https://jekyllrb.com/docs/configuration/front-matter-defaults/) in your site's `_config.yml`.
220
-
221
- ### Menubar
222
-
223
- **New in 0.3** - The menubar gets its content from a data file in your site's `_data` directory. Simply set the name of your data file in the page's menubar setting in the frontmatter.
224
-
225
- ```yaml
226
- show_sidebar: false
227
- menubar: example_menu
228
- ```
229
-
230
- You will probably want to disable `show_sidebar`. Otherwise there will be little room for the page content.
231
-
232
- #### Creating a menubar data file
233
-
234
- Create a data file in the `_data` directory and use the following format (if using yml).
235
-
236
- ```yaml
237
- - label: Example Menu
238
- items:
239
- - name: Home
240
- link: /
241
- - name: Pages
242
- link: #
243
- items:
244
- - name: Page With Sidebar
245
- link: /page-1/
246
- - name: Page Without Sidebar
247
- link: /page-2/
248
- - name: Page With Menubar
249
- link: /page-3/
250
- - name: Blog
251
- link: /blog/
252
- ```
253
-
254
- For the current page to have an active class, ensure the `link:` format matches your [permalink](https://jekyllrb.com/docs/permalinks/#extensionless-permalinks) format. The above example will work with `permalink: pretty` setting in your `_config.yml`.
255
-
256
- #### Multiple menus
257
-
258
- You may make multiple menus in the same file, separated by labels.
259
-
260
- ```yaml
261
- - label: Menu Label
262
- items:
263
- - name: Example item
264
- link: /example-item/
265
- - label: Second Menu Label
266
- items:
267
- - name: Parent Item
268
- link: /parent-item/
269
- items:
270
- - name: Sublink
271
- link: /sublink/
272
- - name: Sublink 2
273
- link: /sublink2/
274
- - label: Third Menu Label
275
- items:
276
- - name: Another example item
277
- link: /another-example-item/
278
- ```
279
-
280
- ### Tabs
281
-
282
- **New in 0.4** - `tabs` gets its content from a data file in your site's `_data` directory. Simply set the name of your data file in the page's menubar setting in the front matter.
283
-
284
- ```yaml
285
- title: Page with tabs
286
- subtitle: Demo page with tabs
287
- layout: page
288
- show_sidebar: false
289
- menubar: example_menu
290
- tabs: example_tabs
291
- ```
292
-
293
- Tabs can be used in conjunction with menubar and/or sidebar if you wish.
294
-
295
- #### Creating a tabs data file
296
-
297
- Create a data file in the `_data` directory and use the following format (if using yml).
33
+ If you are deploying to GitHub pages, then you can also install the [GitHub Pages gem](https://github.com/github/pages-gem) and use `remote_theme` instead of `theme` in your `_config.yml`. **Note that the GitHub Pages gem requires Jekyll version 3.9.**
298
34
 
299
35
  ```yaml
300
- alignment: is-left
301
- style: is-boxed
302
- size: is-large
303
- items:
304
- - name: Tabs
305
- link: /page-4/
306
- icon: fa-smile-wink
307
- - name: Sidebar
308
- link: /page-1/
309
- icon: fa-square
310
- - name: No Sidebar
311
- link: /page-2/
312
- icon: fa-ellipsis-v
313
- - name: Menubar
314
- link: /page-3/
315
- icon: fa-bars
316
- ```
317
-
318
- #### Settings
319
-
320
- You can control the alignment, style, and size of tabs by using the relevant [Bulma tabs classes](https://bulma.io/documentation/components/tabs/).
321
-
322
- #### Active Tab Highlighting
323
-
324
- It will automatically mark the active tab based on the current page.
325
-
326
- #### Icons
327
-
328
- You can add icons to your tab by passing in the [Font Awesome icon class](https://fontawesome.com/icons?d=gallery). If you don't wish to show icons then simply omit the option from your yaml file.
329
-
330
- ### Notifications
331
-
332
- You can include a notification in a page or post using the below include. The message is required but the status defaults to 'is-warning' and the icon defaults to 'fas fa-exclamation-circle', but can be overwritten by setting the values in the includes. The message can also be written in Markdown format.
333
-
334
- ```liquid
335
- {% include notification.html message="This is the message for the notification" %}
336
- ```
337
-
338
- #### Dismissible Notifications
339
-
340
- To set a notification to be dismissible, set dismissible to 'true'
341
-
342
- ```liquid
343
- {% include notification.html
344
- message="This notification is dismissable"
345
- dismissable="true" %}
346
- ```
347
-
348
- #### Iconless Notifications
349
-
350
- Omit the icon by setting icon to 'false'
351
-
352
- ```liquid
353
- {% include notification.html
354
- message="This notification does not have an icon."
355
- icon="false" %}
356
- ```
357
-
358
- ### Tags
359
-
360
- To include a tag use the following include.
361
-
362
- ```liquid
363
- {% include tag.html tag="The tag text" %}
36
+ # With GitHub Pages Gem
37
+ remote_theme: chrisrhymes/bulma-clean-theme
364
38
  ```
365
39
 
366
- You can overwrite the default style (is-primary) by passing in the style in the include tag.
367
-
368
- ```liquid
369
- {% include tag.html tag="The tag text" style="is-light" %}
370
- ```
371
-
372
- ### Google Analytics
373
-
374
- **New in 0.2** - To enable Google Analytics add `google_analytics: UA-xxxxxxxx` to your `_config.yml` replacing the UA-xxxxxxxx with your Google Analytics property.
375
-
376
- ### Footer
377
-
378
- **New in 0.4.1** - To add some footer links, create a yaml file in the `_data` directory using the following format.
379
-
380
- ```yaml
381
- - name: Blog
382
- link: /blog/
383
- - name: About
384
- link: /about/
385
- - name: Privacy Policy
386
- link: /privacy-policy/
387
- ```
388
-
389
- Then add the name of your yaml file (without the .yml extension) into the `footer_menu` setting in the `_config.yml`.
390
-
391
- ```yaml
392
- footer_menu: example_footer_menu
393
- ```
394
-
395
- #### Hiding the footer
396
-
397
- **New in 0.5.2** - If you would like to hide the footer on a particular page then set `hide_footer: true` in the page's frontmatter.
398
-
399
- ### Products
400
-
401
- **New in 0.5** - Now you can add simple product pages to your site using collections.
402
-
403
- #### Product pages
404
-
405
- Start by creating a `_products` directory to hold your product pages and create a new page for each product, such as `product1.md`. In the front matter for this page you can set the standard settings, such as your title, subtitle, description (for meta-description), hero_image, as well as the additional product settings such as price, product_code, image, features, and rating.
406
-
407
- ```yaml
408
- title: Product 1 Name
409
- subtitle: Product 1 tagline here
410
- description: This is a product description
411
- hero_image: /img/hero-img.jpg
412
- product_code: ABC124
413
- layout: product
414
- image: https://via.placeholder.com/640x480
415
- price: £1.99 + VAT
416
- features:
417
- - label: Great addition to any home
418
- icon: fa-location-arrow
419
- - label: Comes in a range of styles
420
- icon: fa-grin-stars
421
- - label: Available in multiple sizes
422
- icon: fa-fighter-jet
423
- rating: 3
424
- ```
425
-
426
- The text you write for the page content will be displayed as the product description.
427
-
428
- Next, add the following to your `_config.yml` to use collections to process the product pages and output them as individual pages.
429
-
430
- ```yaml
431
- collections:
432
- products:
433
- output: true
434
- layout: product
435
- image: https://via.placeholder.com/800x600
436
- show_sidebar: false
437
- ```
438
-
439
- You can also set default product page values here if you like, such as the layout or image.
440
-
441
- #### Product Reviews
442
-
443
- To add reviews to your product page, create a `reviews` directory in the `_data` directory and add a yaml file with the name of the product_code from the product page, for example `_data/reviews/ABC124.yml`. Create the reviews using the following format:
444
-
445
- ```yaml
446
- - name: Mr E Xample
447
- rating: 4
448
- title: Great product, highly recommended
449
- date: 2019-01-01
450
- avatar: https://bulma.io/images/placeholders/128x128.png
451
- description: >
452
- The product worked really well. I would recommend this to most people to use. Delivery was quick and reasonable.
453
- Would recommend this to my friends.
454
- - name: Mrs R E View
455
- rating: 5
456
- title: Nice, really liked this
457
- date: 2019-02-02
458
- description: >
459
- The product worked exactly as described.
460
- ```
461
-
462
- If you don't want to display an avatar image then a default user icon will be displayed. If you don't want to display a rating then omit it from the yaml file.
463
-
464
- #### Product Category Page
465
-
466
- To create a page listing your products you will need to create a product category page. Create a page, for example `products.md`, with the `layout: product-category` in the frontmatter. You can set the sort order of the products using `sort: title` to sort by the title, or by any setting in your product pages, such as price, rating or any custom frontmatter tags you wish to set.
467
-
468
- ```yaml
469
- title: Products
470
- subtitle: Check out our range of products
471
- layout: product-category
472
- show_sidebar: false
473
- sort: title
474
- ```
475
-
476
- ### Scripts
477
-
478
- **New in 0.5.2** - There are two new files within the includes directory called `head-scripts.html` and `footer-scripts.html`. These are empty files by default but allow you to add any additional JavaScript to your site, such as the script for AddThis share buttons, in the `<head>` or after the `<footer>` of the page.
479
-
480
- ### Callouts
481
-
482
- **New in 0.5.4** - You can now add callouts to a page to make a landing page style layout.
483
-
484
- * [Example of page with callouts - notice the 'calls to action' below the header.](http://www.csrhymes.com/bulma-clean-theme/landing/)
485
-
486
- #### Create a callout data file
487
-
488
- Create a data file following the below format. The style is for classes to set the background colour and sizes you would like to use of the Bulma hero container for the callouts.
489
-
490
- **New in 0.5.7** - You can set the height of the callouts in the data file, such as `is-small`, `is-medium`, or `is-large`. If unset it will be `is-medium` by default.
491
-
492
- The items have six fields, but only the title and subtitle are required. If the icon is a brand icon, such as GitHub in the below example, set `icon_brand: true`.
493
-
494
- ```yaml
495
- style: is-light
496
- height: is-medium
497
- items:
498
- - title: Example callout 1
499
- subtitle: Example subtitle 1
500
- icon: fa-github
501
- icon_brand: true
502
- description: >
503
- The example description text goes here and can be multiple lines.
504
-
505
- For example, such as this.
506
- call_to_action_name: Call to action 1
507
- call_to_action_link: /page-1/
508
- ```
509
-
510
- #### Set the callouts in the frontmatter
511
-
512
- To display the callouts on your page, add a `callouts` property in the frontmatter and set it to the name of your data file without the extension.
513
-
514
- ```yaml
515
- layout: page
516
- title: Example Landing Page
517
- subtitle: This is an example landing page
518
- callouts: example_callouts
519
- ```
520
-
521
- ### Favicon
522
-
523
- The default favicon path is `{{ site.baseurl }}/favicon.png` but you can overwrite it in the site's `_config.yml` like this `favicon: /path/to/favicon.png`
524
-
525
- ### Showcases
526
-
527
- Showcases allow you to display your work to others using a simple layout.
528
-
529
- #### Creating A Showcase Datafile
530
-
531
- Create a datafile in your site's `_data` directory in the following format. Subtitle, features and tags are not required.
532
-
533
- The description text accepts Markdown and is run through the markdownify filter on the page.
534
-
535
- The `image_ratio` will default to `is-16by9` if it is not defined and accepts the [Bulma image](https://bulma.io/documentation/elements/image/) classes.
536
-
537
- To display GitHub Stars, Forks, and Watchers badges, add your GitHub user and repo name to the `github` setting, such as `chrisrhymes/bulma-clean-theme`.
538
-
539
- To change the default styles of the features, set `features_styles`. This uses the styles from [bulma-block-list](https://www.csrhymes.com/bulma-block-list/) npm package.
540
-
541
- ```yaml
542
- intro: |-
543
- This is some introduction text for the showcases.
544
-
545
- ## Example Heading
546
- It can convert Markdown format
547
-
548
- items:
549
- - title: Example showcase item
550
- subtitle: Example subtitle
551
- description: |-
552
- This is the example description for this item that you are showcasing and has an image, title, description, tags and a link.
553
- features:
554
- - This is a feature
555
- - This is a feature
556
- features_styles: is-centered is-outlined is-primary
557
- image: https://via.placeholder.com/1024x788
558
- image_ratio: is-16by9
559
- link: http://www.example.com
560
- link_text: View example
561
- tags: PHP,CSS,JavaScript
562
- github: user/repo-name
563
- ```
564
-
565
- #### Displaying the Showcase
566
-
567
- Set the showcase in the page's front matter to be the name of the showcase data file without the extension. This gives you the ability to create multiple showcases to be used on different pages.
568
-
569
- ```yaml
570
- title: Showcase
571
- subtitle: An example showcase page
572
- layout: page
573
- showcase: showcase_example
574
- show_sidebar: false
575
- ```
576
-
577
- ### Sponsors
578
-
579
- #### Sponsor link in navbar
580
-
581
- If you have a GitHub sponsors account set up, you can add your username to `gh_sponsor` in the `_config.yml` file and it will display a link to your profile on the right of the navbar.
582
-
583
- ```yaml
584
- gh_sponsor: chrisrhymes
585
- ```
586
-
587
- #### Creating a Sponsors Datafile
588
-
589
- If you would like to create a page to thank your sponsors then create a data file, such as my_sponsors.yml file with the following structure:
590
-
591
- ```yaml
592
- - tier_name: Platinum Sponsors
593
- size: large
594
- description: |-
595
- This is the description for the Platinum Tier
596
- sponsors:
597
- - name: Dave McDave
598
- profile: https://github.com/
599
- - name: Sarah Lee-Cheesecake
600
- profile: https://github.com/
601
- - tier_name: Gold Sponsors
602
- description: |-
603
- This is the description for the Gold Tier
604
- sponsors:
605
- - name: Dave McDave
606
- profile: https://github.com/
607
- ```
608
-
609
- The `tier_name` and `description` are required. The `size` is not required, but can be overwritten to 'large' or 'small' to increase or decrease the size of the box and the text size.
610
-
611
- The sponsors require a name, but not a profile link.
612
-
613
- #### Displaying the Sponsors
614
-
615
- To display the sponsors on your page, set the sponsors to the filename without the extension in the page's front matter
616
-
617
- ```yaml
618
- layout: page
619
- title: My Sponsors Page
620
- sponsors: my_sponsors
621
- ```
622
-
623
- ### Gallery
624
-
625
- Display a simple image gallery on a page, with image descriptions.
626
-
627
- #### Create an image gallery data file
628
-
629
- Start by creating a gallery data file using the below format, for example `my_gallery.yml`.
630
-
631
- ```yaml
632
- - title: Image Gallery Title
633
- images:
634
- - link: https://via.placeholder.com/800x450
635
- large_link: https://via.placeholder.com/1200x675
636
- alt: The alt text for the image
637
- description: |-
638
- The image description can be written in **Markdown** if required
639
- ratio: is-16by9
640
- - link: https://via.placeholder.com/800x600
641
- large_link: https://via.placeholder.com/1200x675
642
- alt: The alt text for the image
643
- description: The image description
644
- ratio: is-4by3
645
- ```
646
-
647
- * If a ratio is not provided it will default to 16 by 9. Use [Bulma image](https://bulma.io/documentation/elements/image/) classes to define the image ratio required.
648
- * The description can be plaintext or it can be Markdown if required.
649
- * The alt will be used as the image's alt text.
650
- * The large_link displays in a modal when the image is clicked.
651
-
652
- #### Displaying the gallery
653
-
654
- In your page's front matter add a gallery with the datafile's filename without the extension.
655
-
656
- ```yaml
657
- layout: page
658
- title: My Image Gallery
659
- gallery: my_gallery
660
- ```
661
-
662
- ### Disqus
663
-
664
- Disqus comments are available for posts. To be able to use them, you need to set your disqus shortname in `_config.yml`.
665
- ```
666
- disqus.shortname=<example-com.disqus.com>
667
- ```
668
-
669
- Need help finding your Disqus Shortname? [See this helpful post by Disqus on the matter.](https://help.disqus.com/en/articles/1717111-what-s-a-shortname)
670
-
671
- Then you need to set your Jekyll environment to production:
672
-
673
- ```JEKYLL_ENV=production bundle exec jekyll build```.
674
-
675
- Comments are enabled by default. If you want to disable them, set in the front matter this setting:
676
-
677
- ```markdown
678
- comments: false
679
- ```
680
-
681
- ### Recipe
40
+ And then execute:
682
41
 
683
- You can make a single page using the recipe layout, or you can use it in your blog by specifying the `layout: recipe` instead of post.
42
+ $ bundle
684
43
 
685
- You probably want to hide the sidebar, so the recipe takes up the whole page width. If you add any additional content to the page it will appear below the recipe details.
44
+ Or install it yourself as:
686
45
 
687
- Create a list in the front matter for the ingredients, then the method steps and it will automatically be added to the page.
46
+ $ gem install bulma-clean-theme
688
47
 
689
- The front matter will also be added to the page as schema data that is used by search engines. Please see the below example for all of the schema options available.
48
+ ## Documentation
690
49
 
691
- ```yaml
692
- layout: recipe
693
- title: An Example Recipe Page
694
- subtitle: Tastes great and easy to cook
695
- author: CS Rhymes
696
- date: 2021-03-02
697
- show_sidebar: false
698
- image: /bulma-clan-theme/img/recipe-example.jpg
699
- hero_image: /bulma-clean-theme/img/recipe-example.jpg
700
- ingredients:
701
- - 1tsp vegetable oil
702
- - 2 Carrots, finely diced
703
- - 1 Onion, finely dices
704
- - 1 Celery stick, finely diced
705
- - 2 Cloves of Garlic, crushed
706
- - 400g lean Minced Beef
707
- - 400g tin of Chopped Tomatoes
708
- - 2tbsp Tomato Puree
709
- - 300ml Beef Stock
710
- - 1tsp Worcestershire Sauce
711
- - 2tsp Italian Herbs
712
- - Salt and Pepper
713
- method:
714
- - Heat the vegetable oil in a large pan on a medium heat, then add the carrots, onion and celery and cook for five to ten minutes to soften, stirring occasionally
715
- - Add the crushed garlic and cook for 2 more minutes, stiffing occasionally
716
- - Add the minced beef to the pan, breaking it up with a wooden spoon and cook until browned off
717
- - Add the chopped tomatoes, tomato puree, beef stock, worcestershire sauce and italian herbs and stir. Add a pinch of salt and pepper then stir through
718
- - Bring to a gentle simmer and cook for 30 minutes
719
- prep_time: PT0H10M
720
- cook_time: PT1H
721
- total_time: PT1H10M
722
- keywords: recipe,cooking
723
- recipe_yield: 4
724
- recipe_category: Main course
725
- recipe_cuisine: Italian
726
- calories: 500 calories
727
- ```
50
+ Check out the demo site for the [Documentation](https://www.csrhymes.com/bulma-clean-theme/docs/)
728
51
 
729
52
  ## Contributing
730
53