A simple gem to add social networks sharing links on your Jekyll website.
Add this line to your application's Gemfile:
gem 'jekyll-sharelinks'
And then execute:
$ bundle
Or install it yourself as:
$ gem install jekyll-sharelinks
You need to define few configuration variables in your _config.yml file. A Facebook App ID is required and a Twitter account is optional (Twitter account is used as referer for the shared link.).
To get a Facebook app_id checkout this link.
url: "http://example.com" # the base hostname & protocol for your site
facebook:
app_id: 0123456789
twitter_username: john_doe
Just add {% sharelinks %} tag wherever you want to add share links for social networks :)
Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/jekyll-sharelinks. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
The gem is available as open source under the terms of the MIT License.
Everyone interacting in the Jekyll::Sharelinks project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.
FAQs
Unknown package
We found that jekyll-sharelinks demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.