Compare commits

...

39 Commits

Author SHA1 Message Date
Jeff See
288acfacfa
Merge pull request #23 from forestryio/fix/ruby-3.0
fix: Ruby 3.0 Argument Error
2021-10-14 13:08:21 -07:00
Frank Taillandier
21607b627b
Merge pull request #20 from felnne/master
Fixing use double-splats for hash parameters error
2021-07-13 11:51:42 +02:00
Frank Taillandier
41b23d6568 fix: Ruby 3.0 Argument Error
See https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/
2021-07-13 11:46:26 +02:00
Felix Fennell
6c8b53eeb0
Fixing use double-splats for hash parameters error
Now an error from Ruby 3.0.0
2021-03-17 08:40:16 +00:00
Frank Taillandier
2ba953f41f
Minor bump 2019-08-22 17:59:40 +02:00
Frank Taillandier
ebafa6207a
Allow for Jekyll 4.0 2019-08-22 17:38:22 +02:00
Jordon Bedwell
4eeffa3021 Remove extra either. 2017-09-28 03:17:51 -05:00
Jordon Bedwell
34fd696fd6 Further clarifications on 1f020335bfe1e80e418042c1cf7912e8d2bc323f 2017-09-28 03:17:11 -05:00
Jordon Bedwell
1f020335bf Adjust the language of the installation instructions.
This updates the installation instructions to push users towards using Bundler of RubyGems, because it isolates gems, it's the industry standard in Ruby, and it will allow them to use many of the surface tools Jekyll has (like Jekyll Docker, and others.)  It also adjust the different types of installation to using headers to guide so that users can skim to win.
2017-09-28 03:09:22 -05:00
Jordon Bedwell
e6f021a666 Code blocks should be using lang identifiers. 2017-09-28 02:50:37 -05:00
chrisdmacrae
4bfea59378 Update README.md
Bundle add doesn't work because it doesn't add it to the jekyll plugins group.
2017-09-07 12:58:31 -03:00
chrisdmacrae
c157ba39a4 Merge pull request #9 from forestryio/documentation
Documentation
2017-08-31 15:26:28 -03:00
chrisdmacrae
3e8eb755e0 Update README.md 2017-08-30 12:58:39 -03:00
chrisdmacrae
f69126e4bb Update README.md 2017-08-29 16:28:21 -03:00
Christopher Macrae
f33b6afd7c Update README 2017-08-29 16:26:19 -03:00
Christopher Macrae
51ec3d866c Update README 2017-08-29 16:17:20 -03:00
Jordon Bedwell
fbcc9b9a48
📦 v0.6.0 2017-06-26 06:24:33 -05:00
Jordon Bedwell
94286c3317
Fix #8: Make sure we support Liquid 4. 2017-06-26 06:23:54 -05:00
Scott Gallant
4979b35fc4 Added setup instructions 2017-04-08 10:15:57 -03:00
Jordon Bedwell
d170b60841
Release v0.5.0. 2017-03-14 21:22:47 -05:00
Jordon Bedwell
c94954c525
Fix #4: Make sure we don't lead with _ 2017-03-14 15:47:04 -05:00
Jordon Bedwell
f4f7649ccf
💎 Release v0.4.0. 2017-02-13 09:46:35 -06:00
Jordon Bedwell
6145dc74e6
Use before_method instead of method_missing, drops don't like method_missing. 2017-02-13 09:45:25 -06:00
Jordon Bedwell
adaffc454b
Fix #5: Check for Class#data["ext"] before hitting Class#ext. 2017-02-13 09:45:09 -06:00
Jordon Bedwell
b699363013
💎 Release 0.3.0. 2017-01-24 20:39:50 -06:00
Jordon Bedwell
739ba03295
Fix #3: Use pages.docs.select instead of pages.select. 2016-12-17 22:31:15 -06:00
Jordon Bedwell
3e7d01c447
💎 Release v0.2.1 2016-11-23 12:45:08 -06:00
Jordon Bedwell
63977db5c1 Merge pull request #2 from forestryio/hash-not-object
fixed issue with trying to access hash as object
2016-11-22 18:50:14 -06:00
Jordan Patterson
40f0652f39
fixed issue with trying to access hash as object 2016-11-22 20:24:25 -04:00
Jordon Bedwell
6009087b44
💎 Release v0.2.0 2016-11-22 14:36:23 -06:00
Jordon Bedwell
05fcf28891
Guard against invalid menus and no _menus 2016-11-22 14:35:09 -06:00
Jordon Bedwell
02205eeb4a
💎 Release v0.1.0 2016-10-05 19:25:19 -05:00
volgorean
8ad3c3fe07 added collection menus and fixed data menu frontmatter = false 2016-10-05 15:23:09 -07:00
Jordon Bedwell
22d873d95e
Removing my Pry. 2016-10-05 15:03:26 -05:00
Jordon Bedwell
9af8cc15e2
Make sure the path is part of the identifier. 2016-10-05 15:00:53 -05:00
volgorean
0db6d7112c _frontmatter now set to relative path and fixed spelling error 2016-10-05 12:04:32 -07:00
Jordon Bedwell
0f08a5e7ca
💎 Release v0.0.5 2016-10-03 11:50:32 -05:00
Jordon Bedwell
c81b75c62b Merge pull request #1 from volgorean/patch-1
Fixed NameError, Util should be Utils
2016-10-03 11:49:20 -05:00
volgorean
4cf7b543fd Fixed NameError, Util should be Utils 2016-10-03 09:47:27 -07:00
6 changed files with 317 additions and 249 deletions

View File

@ -12,14 +12,14 @@ Gem::Specification.new do |spec|
spec.description = "Menus (site navigation) for your Jekyll website"
spec.summary = "Menus (navigation) for your very own Jekyll website."
spec.files = %W(Gemfile) + Dir["lib/**/*"]
spec.required_ruby_version = ">= 2.1.0"
spec.required_ruby_version = ">= 2.4.0"
spec.email = ["jordon@envygeeks.io"]
spec.require_paths = ["lib"]
spec.name = "jekyll-menus"
spec.has_rdoc = false
spec.license = "MIT"
spec.add_runtime_dependency("jekyll", "~> 3.1")
spec.add_runtime_dependency("jekyll", ">= 3.6", "< 5.0" )
spec.add_development_dependency(
"rspec", ">= 3", "< 4"
)

373
README.md
View File

@ -1,196 +1,219 @@
# Jekyll Menus
Complex, and infinite Hugo-like menus for Jekyll.
A robust, simple-to-use menu plugin for Jekyll that allows for infinitely nested menus.
## Installation
To install and use Jekyll Menus, you should have Ruby, and either [RubyGems](https://jekyllrb.com/docs/installation/#install-with-rubygems), or we recommend using [Bundler](https://bundler.io/#getting-started). Bundler is what Jekyll will prefer you to use by default if you `jekyll new`.
### Using Bundler
You can add our gem to the `jekyll_plugins` group in your `Gemfile`:
```ruby
group :jekyll_plugins do
gem "jekyll-menus"
end
```
And then install from shell.
```sh
bundle install
# --path vendor/bundle
```
***If you are using Jekyll Docker, you do not need to perform this step, Jekyll Docker will perform it on your behalf when you launch the image, you only need to perform this step if you are working directly on your system.***
### Using RubyGems
```sh
sudo gem install jekyll-menus
sudo gem update jekyll-menus
```
Once installed, add the Gem to your `_config.yml`:
```yaml
plugins:
- jekyll-menus
```
***Note in earlier versions of Jekyll, `plugins` should instead be `gems`***
## Usage
In Jekyll Menus you can create `_data/menus.yml`, or add menu items via your front-matter in pages as well! Both are merged into the same menus if the identifiers match so you can even split off menus between the two, and so that you can have menus that have internal and external links.
Jekyll Menus allows you to create menus by attaching posts and pages to menus through their front matter, or by defining custom menu items via `_data/menus.yml`.
### Front-Matter Examples
#### Using a String key to add an item to the menu
Jekyll Menus adds a new option to the site variable called `site.menus`, which can be looped over just like pages, posts, and other content:
You can add an item to any menu by simply doing `menus: identifier` inside of your front-matter. If you do it this way, the string is the identifier (the menu you wish to place the item on) and all the other data is inferred from Jekyll, such as the items own identifier (take from the files slug,) title, and it defaults the weight to `-1` for you, making it so that your menu item is pretty much automatic aside from needing to add itself.
##### Example
```yml
---
menus: main
---
```
#### Using an array to add an item to multiple menus
Like string keys, you can create an array of string keys, that allows you place an item on multiple identifiers at once, and like the string version, it will infer the data from Jekyll.
##### Example
```yml
---
menus:
- header
- footer
---
```
#### Adding a menu item with data
Jekyll Menus uses the keys, `title`, `weight`, `identifier` (slug), and `url`, you can customize said data and even add your own data, to do that you make the menu item hash with the data and any data you do not override is inferred like the other ways to add menu items. And like adding it to multiple identifiers with an array, you can do the same here by turning menus into an array and adding multiple hashes.
##### Examples
```yml
---
menus:
main:
url: "/custom-url"
---
```
```yaml
menus:
- header
- main:
url: "/custom-url"
```
### Using `_data/menus.yml`
***All data within _menus.yml must provide `url`, `title`, `identifier`, with `weight` being optional.***
Menu items within data files must follow a key array format, or a key hash format, we do not accept string formats because we cannot infer data and to do so would be pretty expensive.
#### Examples
```yml
main:
- title: Title
identifier: title
url: url
```
```yml
main:
title: Title
identifier: title
url: url
```
***It should be noted that _data/menus.yml are both read and merged, so you can have one, or both... we won't judge you if you happen to use both of these files at once, it's your choice!***
### Adding menu items to menu items
In Jekyll-Menus each item has it's own identifier (slug) that identifier can be used to have other items on it, and is used to find associated menus. So you can create your own base identifiers (like header, footer, main or otherwise) and each item on that has it's own identifier.
So given you have a file called `about.html` or `about.md`, and you do the following:
```yaml
menus: main
```
and, then you have `about/person.md`, you can add that to the `about` item with the following front-matter:
```yaml
menus: about
```
... Because `about.md` didn't have it's own identifier, the identifier was extracted from the page name (slug) so the identifier would be `about`, if you have `my-custom-page.md` or `my_custom_page.md` then the identifiers would be those without the file extension.
#### Customizing the identifier on an item
You can customize the identifier on any item (the base identifiers are already custom as you have to create them yourself by adding an item onto an identifier that doesn't exist.) To customize the identifier you just add the identifier key like the following:
```
menus:
main:
identifier: my-identifier
```
At that point, you can add sub-menus or items onto that identifier by using it as the identifier for in your front-matter (or even inside of your data files if it really pleases you.)
### Custom Menu Data
You can add any amount of custom data you wish to an item, we do not remove
data, and we do not block it, we will pass any data you wish to put into the
into the menu item. It is up to you what data you put there, we only check
that our own keys exist, and if they don't then we fail in certain scenarios.
#### Example
```
menu:
main:
weight: 4
customData: value
```
## Outputting the menu's
### A basic menu
Given you have several pages with the following:
```yaml
menu: header
```
You can output those with the following:
```html
<header>
<nav>
<ul>
{% for item in site.menus.header %}
<li><a href="{{ item.url }}">
{{ item.title }}
</a></li>
{% endfor %}
</ul>
</nav>
</header>
```
### Recursive Menu output
If you want to output recursive menus efficiently you should start working with an include, so you can recurse on that include and have infinite menus if you ***really*** want.
#### Example
`_includes/menus.html`
```html
```liquid
<ul>
{% for item in menu %}
<li>
<span>
<a href="{{ item.url }}">
{{ item.title }}
</a>
</span>
{% if item.children %}
{% assign menu = item.children %}
{% include
_menus.html
%}
{% endif %}
{% endfor %}
{% for item in site.menus.header %}
<li class="menu-item-{{ loop.index }}">
<a href="{{ item.url }}" title="Go to {{ item.title }}">{{ item.title }}</a>
</li>
{% endfor %}
</ul>
```
`_layouts/default.html`
## Menus via Front Matter
```html
The easiest way to use Jekyll Menus is to start building menus using your existing posts and pages. This can be done by adding a `menus` variable to your front matter:
```markdown
---
title: Homepage
menus: header
---
```
This will create the `header` menu with a single item, the homepage. The `url`, `title`, and `identifier` for the homepage menu item will be automatically generated from the pages title, file path, and permalink.
You can optionally set any of the available [menu item variables](#menu-items) yourself to customize the appearance and functionality of your menus. For example, to set a custom title and weight:
```markdown
---
title: Homepage
menus:
header:
title: Home
weight: 1
---
```
## Custom Menu Items via `_data/menus.yml`
The other option for configuring menus is creating menus using `_data/menus.yml`. In this scenario, you can add custom menu items to external content, or site content that isnt handled by Jekyll.
In this file, you provide the menu key and an array of custom menu items. Custom menu items in the data file must have `url`, `title`, and `identifier` variable:
```markdown
---
header:
- url: /api
title: API Documentation
identifier: api
---
```
## Sub-menus
Jekyll Menus supports infinitely nested menu items using the `identifier` variable. Any menu item can be used as a parent menu by using its identifier as the menu.
For example, in `_data/menus.yml`:
```yaml
header:
- url: /api
title: API Documentation
identifier: api
```
In a content file called `/api-support.html`:
```markdown
---
title: Get API Support
menus: api
---
```
Which can then be used in your templates by looping over the menu items `children` variable:
```liquid
<ul>
{% for item in site.menus.header %}
<li class="menu-item-{{ loop.index }}">
<a href="{{ item.url }}" title="Go to {{ item.title }}">{{ item.title }}</a>
{% if item.children %}
<ul class="sub-menu">
{% for item in item.children %}
<li class="menu-item-{{ loop.index }}">
<a href="{{ item.url }}" title="Go to {{ item.title }}">{{ item.title }}</a>
</li>
{% endfor %}
</ul>
{% endif %}
</li>
{% endfor %}
</ul>
```
You can also do this [recursively using a re-usable include](#recursive-menus), allowing for easily managed infinitely nested menus.
## Variables
Jekyll Menus has the following variables:
### Menus
| Variable | Description |
|---|---|
| menu.menu | Returns a JSON object with all of the menus items. |
| menu.identifier | The unique identifier for the current menu, generated from the menu key. Allows for nested menu items. |
| menu.parent | The parent menu. Resolves to the site.menus object for top-level menus. |
### Menu Items
| Variable | Description |
|---|---|
| item.title | The display title of the menu item. Automatically set as the post or page title if no value is provided in front matter. |
| item.url | The URL the menu item links to. Automatically set to the post or page URL if no value is provided in front matter. |
| item.weight | Handles the order of menu items through a weighted system, starting with 1 being first. |
| item.identifier | The unique identifier for the current menu item. Allows for nested menu items. Automatically resolved to the pages file path and filename if not provided in front matter. |
| item.parent | The parent menu. |
| item.children | An array of any child menu items. Used to create sub-menus. |
## Custom Variables
Menu items also support custom variables, which you add to each menu item in the front matter or data file.
For example, adding a `pre` or `post` variable to add text or HTML to your menu items:
```markdown
---
title: Homepage
menus:
header:
pre: <i class="icon-home"></i>
post: " · "
---
```
## Recursive Menus
If youre looking to build an infinitely nested menu (or a menu that is nested more than once up to a limit) then you should set up a reusable menu include that will handle this for you.
In `_includes/menu.html` :
```liquid
{% if menu %}
<ul>
{% for item in menu %}
<li class="menu-item-{{ loop.index }}">
<a href="{{ item.url }}" title="Go to {{ item.title }}">{{ item.title }}</a>
{% if item.children %}
{% assign menu = item.children %}
{% include menu.html %}
{% endif %}
</li>
{% endfor %}
</ul>
{% endif %}
```
In `_layouts/default.html` (or any layout file):
```liquid
<html>
<body>
<header>
<nav>
{% assign menu = site.menus.main %}
{% include
_menus.html
%}
{% assign menu = site.menus.header %}
{% include menus.html %}
</nav>
</header>
{{ content }}
</body>
</html>

View File

@ -14,9 +14,9 @@ module Jekyll
#
def menus
Util.deep_merge(
_data_menus, _page_menus
)
Utils.deep_merge(_data_menus, Utils.deep_merge(
_page_menus, _collection_menus
))
end
#
@ -32,25 +32,28 @@ module Jekyll
def _data_menus
out = {}
@site.data["menus"].each do |key, menu|
if menu.is_a?(Hash) || menu.is_a?(Array)
(menu = [menu].flatten).each do |item|
_validate_config_menu_item(
item
if @site.data["menus"] && @site.data["menus"].is_a?(Hash)
then @site.data["menus"].each do |key, menu|
if menu.is_a?(Hash) || menu.is_a?(Array)
(menu = [menu].flatten).each do |item|
_validate_config_menu_item(
item
)
item["_frontmatter"] = false
end
else
_throw_invalid_menu_entry(
menu
)
end
else
_throw_invalid_menu_entry(
menu
merge = { key => menu }
out = Utils.deep_merge(
out, merge
)
end
merge = { key => menu }
merge["_fronmatter"] = false
out = Utils.deep_merge(
out, merge
)
end
out
@ -63,70 +66,93 @@ module Jekyll
@site.pages.select { |p| p.data.keys.grep(/menus?/).size > 0 }.each_with_object({}) do |page|
[page.data["menus"], page.data["menu"]].flatten.compact.map do |menu|
out = _front_matter_menu(menu, page, out)
end
end
out
end
#
def _collection_menus
out = {}
@site.collections.each do |collection, pages|
pages.docs.select { |p| p.data.keys.grep(/menus?/).size > 0 }.each_with_object({}) do |page|
[page.data["menus"], page.data["menu"]].flatten.compact.map do |menu|
out = _front_matter_menu(menu, page, out)
end
end
end
out
end
#
def _front_matter_menu(menu, page, out={})
# --
# menu: key
# menu:
# - key1
# - key2
# --
if menu.is_a?(Array) || menu.is_a?(String)
_simple_front_matter_menu(menu, **{
:mergeable => out, :page => page
})
#
elsif menu.is_a?(Hash)
menu.each do |key, item|
out[key] ||= []
# --
# menu: key
# menu:
# - key1
# - key2
# key: identifier
# --
if menu.is_a?(Array) || menu.is_a?(String)
_simple_front_matter_menu(menu, {
:mergeable => out, :page => page
if item.is_a?(String)
out[key] << _fill_front_matter_menu({ "identifier" => item }, **{
:page => page
})
#
# --
# menu:
# key:
# url: /url
# --
elsif menu.is_a?(Hash)
menu.each do |key, item|
out[key] ||= []
# --
# menu:
# key: identifier
# --
if item.is_a?(String)
out[key] << _fill_front_matter_menu({ "identifier" => item }, {
:page => page
})
# --
# menu:
# key:
# url: /url
# --
elsif item.is_a?(Hash)
out[key] << _fill_front_matter_menu(item, {
:page => page
})
# --
# menu:
# key:
# - url: /url
# --
else
_throw_invalid_menu_entry(
item
)
end
end
elsif item.is_a?(Hash)
out[key] << _fill_front_matter_menu(item, **{
:page => page
})
# --
# menu:
# key: 3
# key:
# - url: /url
# --
else
_throw_invalid_menu_entry(
menu
item
)
end
end
# --
# menu:
# key: 3
# --
else
_throw_invalid_menu_entry(
menu
)
end
out
@ -152,7 +178,7 @@ module Jekyll
else
mergeable[menu] ||= []
mergeable[menu] << _fill_front_matter_menu(nil, {
mergeable[menu] << _fill_front_matter_menu(nil, **{
:page => page
})
end
@ -166,15 +192,26 @@ module Jekyll
val ||= {}
val["url"] ||= page.url
val["identifier"] ||= File.basename(page.name, page.ext)
val["identifier"] ||= slug(page)
val["_frontmatter"] = page.relative_path # `page.url` can be changed with permalink frontmatter
val["title"] ||= page.data["title"]
val["_frontmatter"] = true
val["weight"] ||= -1
val
end
#
private
def slug(page)
ext = page.data["ext"] || page.ext
out = File.join(File.dirname(page.path), File.basename(page.path, ext))
out.tr("^a-z0-9-_\\/", "").gsub(/\/|\-+/, "_").gsub(
/^_+/, ""
)
end
#
private
def _validate_config_menu_item(item)
if !item.is_a?(Hash) || !item.values_at("url", "title", "identifier").compact.size == 3

View File

@ -56,16 +56,15 @@ module Jekyll
#
def method_missing(method, *args)
if args.size == 0 && @item.has_key?(method.to_s)
def before_method(method)
if @item.has_key?(method.to_s)
return @item[
method.to_s
]
else
super
end
end
alias_method :liquid_method_missing, :before_method
end
end
end

View File

@ -4,6 +4,6 @@
module Jekyll
class Menus
VERSION = "0.0.4"
VERSION = "0.6.1"
end
end

View File

@ -0,0 +1,9 @@
---
title: Array of Strings
layout: default
menu:
- header
- footer
---
A Page