jekyll-stickyposts 1.0.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.gitignore +12 -0
- data/.rspec +3 -0
- data/.travis.yml +5 -0
- data/CODE_OF_CONDUCT.md +74 -0
- data/Gemfile +6 -0
- data/LICENSE.txt +21 -0
- data/README.md +115 -0
- data/Rakefile +6 -0
- data/bin/console +14 -0
- data/bin/setup +8 -0
- data/jekyll-stickyposts.gemspec +27 -0
- data/lib/jekyll/stickyposts.rb +93 -0
- data/lib/jekyll/stickyposts/version.rb +5 -0
- metadata +87 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA1:
|
3
|
+
metadata.gz: 2af17204ace97a1999dc4091992a8d72811c0eeb
|
4
|
+
data.tar.gz: 1319ca3797cb5670080e2ac2164b5d66de7b9e0a
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: 2cd32659de834bb7dcfd533a39f0a452601542c3a83a6062c60608fcef61330645d14d1640e646c75e79dafbef64f25b495c253b0465f3d83b41a5c6526b3e4b
|
7
|
+
data.tar.gz: ec84a2520f6e6e362d86b1f28f49e61015f7c2f2c50082b69e775e42bc21a0f387f6f1a8e6daf4327514bffa0e390eda1a1a2bf37a59da54604621520f640e7c
|
data/.gitignore
ADDED
data/.rspec
ADDED
data/.travis.yml
ADDED
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,74 @@
|
|
1
|
+
# Contributor Covenant Code of Conduct
|
2
|
+
|
3
|
+
## Our Pledge
|
4
|
+
|
5
|
+
In the interest of fostering an open and welcoming environment, we as
|
6
|
+
contributors and maintainers pledge to making participation in our project and
|
7
|
+
our community a harassment-free experience for everyone, regardless of age, body
|
8
|
+
size, disability, ethnicity, gender identity and expression, level of experience,
|
9
|
+
nationality, personal appearance, race, religion, or sexual identity and
|
10
|
+
orientation.
|
11
|
+
|
12
|
+
## Our Standards
|
13
|
+
|
14
|
+
Examples of behavior that contributes to creating a positive environment
|
15
|
+
include:
|
16
|
+
|
17
|
+
* Using welcoming and inclusive language
|
18
|
+
* Being respectful of differing viewpoints and experiences
|
19
|
+
* Gracefully accepting constructive criticism
|
20
|
+
* Focusing on what is best for the community
|
21
|
+
* Showing empathy towards other community members
|
22
|
+
|
23
|
+
Examples of unacceptable behavior by participants include:
|
24
|
+
|
25
|
+
* The use of sexualized language or imagery and unwelcome sexual attention or
|
26
|
+
advances
|
27
|
+
* Trolling, insulting/derogatory comments, and personal or political attacks
|
28
|
+
* Public or private harassment
|
29
|
+
* Publishing others' private information, such as a physical or electronic
|
30
|
+
address, without explicit permission
|
31
|
+
* Other conduct which could reasonably be considered inappropriate in a
|
32
|
+
professional setting
|
33
|
+
|
34
|
+
## Our Responsibilities
|
35
|
+
|
36
|
+
Project maintainers are responsible for clarifying the standards of acceptable
|
37
|
+
behavior and are expected to take appropriate and fair corrective action in
|
38
|
+
response to any instances of unacceptable behavior.
|
39
|
+
|
40
|
+
Project maintainers have the right and responsibility to remove, edit, or
|
41
|
+
reject comments, commits, code, wiki edits, issues, and other contributions
|
42
|
+
that are not aligned to this Code of Conduct, or to ban temporarily or
|
43
|
+
permanently any contributor for other behaviors that they deem inappropriate,
|
44
|
+
threatening, offensive, or harmful.
|
45
|
+
|
46
|
+
## Scope
|
47
|
+
|
48
|
+
This Code of Conduct applies both within project spaces and in public spaces
|
49
|
+
when an individual is representing the project or its community. Examples of
|
50
|
+
representing a project or community include using an official project e-mail
|
51
|
+
address, posting via an official social media account, or acting as an appointed
|
52
|
+
representative at an online or offline event. Representation of a project may be
|
53
|
+
further defined and clarified by project maintainers.
|
54
|
+
|
55
|
+
## Enforcement
|
56
|
+
|
57
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
58
|
+
reported by contacting the project team at TODO: Write your email address. All
|
59
|
+
complaints will be reviewed and investigated and will result in a response that
|
60
|
+
is deemed necessary and appropriate to the circumstances. The project team is
|
61
|
+
obligated to maintain confidentiality with regard to the reporter of an incident.
|
62
|
+
Further details of specific enforcement policies may be posted separately.
|
63
|
+
|
64
|
+
Project maintainers who do not follow or enforce the Code of Conduct in good
|
65
|
+
faith may face temporary or permanent repercussions as determined by other
|
66
|
+
members of the project's leadership.
|
67
|
+
|
68
|
+
## Attribution
|
69
|
+
|
70
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
71
|
+
available at [http://contributor-covenant.org/version/1/4][version]
|
72
|
+
|
73
|
+
[homepage]: http://contributor-covenant.org
|
74
|
+
[version]: http://contributor-covenant.org/version/1/4/
|
data/Gemfile
ADDED
data/LICENSE.txt
ADDED
@@ -0,0 +1,21 @@
|
|
1
|
+
The MIT License (MIT)
|
2
|
+
|
3
|
+
Copyright (c) 2017 TODO: Write your name
|
4
|
+
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
7
|
+
in the Software without restriction, including without limitation the rights
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
10
|
+
furnished to do so, subject to the following conditions:
|
11
|
+
|
12
|
+
The above copyright notice and this permission notice shall be included in
|
13
|
+
all copies or substantial portions of the Software.
|
14
|
+
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
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
|
+
THE SOFTWARE.
|
data/README.md
ADDED
@@ -0,0 +1,115 @@
|
|
1
|
+
# Jekyll::StickyPosts
|
2
|
+
|
3
|
+
*Version 1.0.0*
|
4
|
+
|
5
|
+
*StickyPosts* is a plugin for [Jekyll](https://jekyllrb.com/) that sticks/pins posts marked `sticky: true` to the top, i.e. it moves them before all others. Optionally, the posts could also appear where they normally would.
|
6
|
+
|
7
|
+
### Why do this?
|
8
|
+
|
9
|
+
1. You want to keep important announcements, etc. at the top of your home page
|
10
|
+
|
11
|
+
## Installation
|
12
|
+
|
13
|
+
Add the gem to your application's Gemfile:
|
14
|
+
|
15
|
+
```ruby
|
16
|
+
group :jekyll_plugins do
|
17
|
+
# other plugins here
|
18
|
+
gem 'jekyll-stickyposts'
|
19
|
+
end
|
20
|
+
```
|
21
|
+
|
22
|
+
And then execute:
|
23
|
+
|
24
|
+
$ bundle
|
25
|
+
|
26
|
+
Or install it yourself:
|
27
|
+
|
28
|
+
$ gem install jekyll-stickyposts
|
29
|
+
|
30
|
+
## Configuration
|
31
|
+
|
32
|
+
No configuration is required to run *StickyPosts*. If you want to tweak its behavior, you may set the following options in `_config.yml`:
|
33
|
+
|
34
|
+
```yaml
|
35
|
+
stickyposts:
|
36
|
+
#enabled: false # Enable StickyPosts; default: true
|
37
|
+
debug: true # Show additional info; default: false
|
38
|
+
sort: "blah" # Optional sort field; default: "date", use "none" to avoid sorting
|
39
|
+
reverse: true # Ascending order, default: false
|
40
|
+
retain: true # Also show sticky posts in their original positions; default: false
|
41
|
+
```
|
42
|
+
|
43
|
+
> Note: if you set `sort` to `"none"` and don't sort as described in the next section, Jekyll will re-sort the documents by date. This may move the sticky posts out of position.
|
44
|
+
|
45
|
+
## Usage
|
46
|
+
|
47
|
+
If you're not using a paginator, use something like:
|
48
|
+
|
49
|
+
```html
|
50
|
+
{% assign sorted = site.posts | sort: "stickiness" %}
|
51
|
+
{% for post in sorted %}
|
52
|
+
...etc...
|
53
|
+
{% endfor %}
|
54
|
+
```
|
55
|
+
|
56
|
+
If you're using a paginator that allows sorting on fields, e.g. [jekyll-paginate-v2](https://github.com/sverrirs/jekyll-paginate-v2/), you need to edit your `_config.yml` a bit:
|
57
|
+
|
58
|
+
```yaml
|
59
|
+
pagination:
|
60
|
+
# ...
|
61
|
+
sort_field: "stickiness"
|
62
|
+
reverse: false
|
63
|
+
# ...
|
64
|
+
|
65
|
+
# ...etc...
|
66
|
+
|
67
|
+
stickyposts:
|
68
|
+
#sort: "date" # or your original pagination sort_field
|
69
|
+
#reverse: true # ditto for the pagination reverse
|
70
|
+
# ...etc...
|
71
|
+
```
|
72
|
+
|
73
|
+
No changes will be required in your pagination setup:
|
74
|
+
|
75
|
+
```html
|
76
|
+
{% for post in paginator.posts %}
|
77
|
+
...etc...
|
78
|
+
{% endfor %}
|
79
|
+
```
|
80
|
+
## Additional configuration
|
81
|
+
|
82
|
+
You may want to mark sticky posts with e.g. a pin from [FontAwesome](http://fontawesome.io/):
|
83
|
+
|
84
|
+
```html
|
85
|
+
{% if post.sticky %}
|
86
|
+
<span class="sticky"><i class="fa fa-thumb-tack" aria-hidden="true"></i></span>
|
87
|
+
{% endif %}
|
88
|
+
```
|
89
|
+
|
90
|
+
## Demo
|
91
|
+
|
92
|
+
See the [author's blog](https://ibrado.org/) for a (possible) demo.
|
93
|
+
|
94
|
+
## Contributing
|
95
|
+
|
96
|
+
1. Fork this project: [https://github.com/ibrado/jekyll-stickyposts/fork](https://github.com/ibrado/jekyll-stickyposts/fork)
|
97
|
+
1. Clone it (`git clone git://github.com/your_user_name/jekyll-stickyposts.git`)
|
98
|
+
1. `cd jekyll-stickyposts`
|
99
|
+
1. Create a new branch (e.g. `git checkout -b my-bug-fix`)
|
100
|
+
1. Make your changes
|
101
|
+
1. Commit your changes (`git commit -m "Bug fix"`)
|
102
|
+
1. Build it (`gem build jekyll-stickyposts.gemspec`)
|
103
|
+
1. Install and test it (`gem install ./jekyll-stickyposts-*.gem`)
|
104
|
+
1. Repeat from step 3 as necessary
|
105
|
+
1. Push the branch (`git push -u origin my-bug-fix`)
|
106
|
+
1. Create a Pull Request, making sure to select the proper branch, e.g. `my-bug-fix` (via https://github.com/*your_user_name*/jekyll-stickyposts)
|
107
|
+
|
108
|
+
Bug reports and pull requests are welcome on GitHub at [https://github.com/ibrado/jekyll-stickyposts](https://github.com/ibrado/jekyll-stickyposts). This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
|
109
|
+
|
110
|
+
## License
|
111
|
+
|
112
|
+
The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
|
113
|
+
|
114
|
+
## Code of Conduct
|
115
|
+
Everyone interacting in the Jekyll::StickyPosts project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/jekyll-stickyposts/blob/master/CODE_OF_CONDUCT.md).
|
data/Rakefile
ADDED
data/bin/console
ADDED
@@ -0,0 +1,14 @@
|
|
1
|
+
#!/usr/bin/env ruby
|
2
|
+
|
3
|
+
require "bundler/setup"
|
4
|
+
require "jekyll/stickyposts"
|
5
|
+
|
6
|
+
# You can add fixtures and/or initialization code here to make experimenting
|
7
|
+
# with your gem easier. You can also use a different console, if you like.
|
8
|
+
|
9
|
+
# (If you use this, don't forget to add pry to your Gemfile!)
|
10
|
+
# require "pry"
|
11
|
+
# Pry.start
|
12
|
+
|
13
|
+
require "irb"
|
14
|
+
IRB.start(__FILE__)
|
data/bin/setup
ADDED
@@ -0,0 +1,27 @@
|
|
1
|
+
|
2
|
+
lib = File.expand_path("../lib", __FILE__)
|
3
|
+
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
|
4
|
+
require "jekyll/stickyposts/version"
|
5
|
+
|
6
|
+
Gem::Specification.new do |spec|
|
7
|
+
spec.name = "jekyll-stickyposts"
|
8
|
+
spec.version = Jekyll::StickyPosts::VERSION
|
9
|
+
spec.authors = ["Alex Ibrado"]
|
10
|
+
spec.email = ["alex@ibrado.org"]
|
11
|
+
|
12
|
+
spec.summary = %q{StickyPosts: Sticky/pinned posts for Jekyll}
|
13
|
+
spec.description = %q{This Jekyll plugin sticks/pins posts tagged sticky: true, i.e. moves them before all others. Optionally, the posts could also appear where they normally would. Sorting and ordering options are available. Compatible with pagination.}
|
14
|
+
spec.homepage = "https://github.com/ibrado/jekyll-stickyposts"
|
15
|
+
spec.license = "MIT"
|
16
|
+
|
17
|
+
spec.files = `git ls-files -z`.split("\x0").reject do |f|
|
18
|
+
f.match(%r{^(test|spec|features)/})
|
19
|
+
end
|
20
|
+
spec.bindir = "exe"
|
21
|
+
spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
|
22
|
+
spec.require_paths = ["lib"]
|
23
|
+
|
24
|
+
spec.add_runtime_dependency "jekyll", "~> 3.0"
|
25
|
+
|
26
|
+
spec.add_development_dependency "bundler", "~> 1.16"
|
27
|
+
end
|
@@ -0,0 +1,93 @@
|
|
1
|
+
require "jekyll/stickyposts/version"
|
2
|
+
|
3
|
+
module Jekyll
|
4
|
+
module StickyPosts
|
5
|
+
def self.debug_state(state)
|
6
|
+
@debug = state
|
7
|
+
end
|
8
|
+
|
9
|
+
def self.info(msg)
|
10
|
+
Jekyll.logger.info "StickyPosts:", msg
|
11
|
+
end
|
12
|
+
|
13
|
+
def self.debug(msg)
|
14
|
+
self.info msg if @debug
|
15
|
+
end
|
16
|
+
|
17
|
+
class Generator < Jekyll::Generator
|
18
|
+
attr_reader :posts
|
19
|
+
priority :low
|
20
|
+
|
21
|
+
def generate(site)
|
22
|
+
config = site.config["stickyposts"] || {}
|
23
|
+
# Defaults:
|
24
|
+
# sort = date
|
25
|
+
# reverse = false
|
26
|
+
# enabled = true
|
27
|
+
# retain = false
|
28
|
+
|
29
|
+
return if !(config["enabled"].nil? || config["enabled"])
|
30
|
+
|
31
|
+
debug = config["debug"]
|
32
|
+
StickyPosts::debug_state debug
|
33
|
+
|
34
|
+
collection = config["collection"] || "posts";
|
35
|
+
|
36
|
+
sort_field = config["sort"] || 'date'
|
37
|
+
sort_reverse = config["reverse"]
|
38
|
+
|
39
|
+
sorted = site.collections[collection].docs #.clone
|
40
|
+
|
41
|
+
unless config["sort"] == "none"
|
42
|
+
StickyPosts::debug "Sorting by #{sort_field}, reverse: #{sort_reverse ? "true" : "false"}"
|
43
|
+
sorted.sort! { |docB, docA|
|
44
|
+
a = docA.data[sort_field]
|
45
|
+
b = docB.data[sort_field]
|
46
|
+
|
47
|
+
if a.nil? && !b.nil?
|
48
|
+
-1
|
49
|
+
elsif !a.nil? && b.nil?
|
50
|
+
1
|
51
|
+
end
|
52
|
+
|
53
|
+
if a.respond_to?('to_datetime') && b.respond_to?('to_datetime')
|
54
|
+
a.to_datetime <=> b.to_datetime
|
55
|
+
end
|
56
|
+
|
57
|
+
a <=> b
|
58
|
+
}
|
59
|
+
|
60
|
+
sorted.reverse! if sort_reverse
|
61
|
+
end
|
62
|
+
|
63
|
+
remove = config["retain"].nil? || !config["retain"]
|
64
|
+
|
65
|
+
sticky = []
|
66
|
+
sorted.delete_if do |post|
|
67
|
+
if post.data['sticky']
|
68
|
+
StickyPosts::debug "\"#{post.data['title']}\" is sticky, #{remove ? "removing" : "retaining"} copy"
|
69
|
+
if remove
|
70
|
+
sticky << post
|
71
|
+
else
|
72
|
+
copy = Jekyll::Document.new(post.path, { :site => site, :collection => site.posts })
|
73
|
+
copy.merge_data!(post.data)
|
74
|
+
sticky << copy
|
75
|
+
end
|
76
|
+
remove
|
77
|
+
end
|
78
|
+
end
|
79
|
+
|
80
|
+
sorted.unshift(*sticky)
|
81
|
+
|
82
|
+
order = 0;
|
83
|
+
sorted.each do |post|
|
84
|
+
post.data["stickiness"] = order
|
85
|
+
order += 1
|
86
|
+
end
|
87
|
+
|
88
|
+
StickyPosts::info "#{sticky.length} post(s) pinned"
|
89
|
+
|
90
|
+
end
|
91
|
+
end
|
92
|
+
end
|
93
|
+
end
|
metadata
ADDED
@@ -0,0 +1,87 @@
|
|
1
|
+
--- !ruby/object:Gem::Specification
|
2
|
+
name: jekyll-stickyposts
|
3
|
+
version: !ruby/object:Gem::Version
|
4
|
+
version: 1.0.0
|
5
|
+
platform: ruby
|
6
|
+
authors:
|
7
|
+
- Alex Ibrado
|
8
|
+
autorequire:
|
9
|
+
bindir: exe
|
10
|
+
cert_chain: []
|
11
|
+
date: 2017-12-13 00:00:00.000000000 Z
|
12
|
+
dependencies:
|
13
|
+
- !ruby/object:Gem::Dependency
|
14
|
+
name: jekyll
|
15
|
+
requirement: !ruby/object:Gem::Requirement
|
16
|
+
requirements:
|
17
|
+
- - "~>"
|
18
|
+
- !ruby/object:Gem::Version
|
19
|
+
version: '3.0'
|
20
|
+
type: :runtime
|
21
|
+
prerelease: false
|
22
|
+
version_requirements: !ruby/object:Gem::Requirement
|
23
|
+
requirements:
|
24
|
+
- - "~>"
|
25
|
+
- !ruby/object:Gem::Version
|
26
|
+
version: '3.0'
|
27
|
+
- !ruby/object:Gem::Dependency
|
28
|
+
name: bundler
|
29
|
+
requirement: !ruby/object:Gem::Requirement
|
30
|
+
requirements:
|
31
|
+
- - "~>"
|
32
|
+
- !ruby/object:Gem::Version
|
33
|
+
version: '1.16'
|
34
|
+
type: :development
|
35
|
+
prerelease: false
|
36
|
+
version_requirements: !ruby/object:Gem::Requirement
|
37
|
+
requirements:
|
38
|
+
- - "~>"
|
39
|
+
- !ruby/object:Gem::Version
|
40
|
+
version: '1.16'
|
41
|
+
description: 'This Jekyll plugin sticks/pins posts tagged sticky: true, i.e. moves
|
42
|
+
them before all others. Optionally, the posts could also appear where they normally
|
43
|
+
would. Sorting and ordering options are available. Compatible with pagination.'
|
44
|
+
email:
|
45
|
+
- alex@ibrado.org
|
46
|
+
executables: []
|
47
|
+
extensions: []
|
48
|
+
extra_rdoc_files: []
|
49
|
+
files:
|
50
|
+
- ".gitignore"
|
51
|
+
- ".rspec"
|
52
|
+
- ".travis.yml"
|
53
|
+
- CODE_OF_CONDUCT.md
|
54
|
+
- Gemfile
|
55
|
+
- LICENSE.txt
|
56
|
+
- README.md
|
57
|
+
- Rakefile
|
58
|
+
- bin/console
|
59
|
+
- bin/setup
|
60
|
+
- jekyll-stickyposts.gemspec
|
61
|
+
- lib/jekyll/stickyposts.rb
|
62
|
+
- lib/jekyll/stickyposts/version.rb
|
63
|
+
homepage: https://github.com/ibrado/jekyll-stickyposts
|
64
|
+
licenses:
|
65
|
+
- MIT
|
66
|
+
metadata: {}
|
67
|
+
post_install_message:
|
68
|
+
rdoc_options: []
|
69
|
+
require_paths:
|
70
|
+
- lib
|
71
|
+
required_ruby_version: !ruby/object:Gem::Requirement
|
72
|
+
requirements:
|
73
|
+
- - ">="
|
74
|
+
- !ruby/object:Gem::Version
|
75
|
+
version: '0'
|
76
|
+
required_rubygems_version: !ruby/object:Gem::Requirement
|
77
|
+
requirements:
|
78
|
+
- - ">="
|
79
|
+
- !ruby/object:Gem::Version
|
80
|
+
version: '0'
|
81
|
+
requirements: []
|
82
|
+
rubyforge_project:
|
83
|
+
rubygems_version: 2.5.1
|
84
|
+
signing_key:
|
85
|
+
specification_version: 4
|
86
|
+
summary: 'StickyPosts: Sticky/pinned posts for Jekyll'
|
87
|
+
test_files: []
|