Jekyll::Hive

Liquid tag for displaying Hive content in Jekyll sites: {% hive %}.

Add this line to your application's Gemfile:

gem 'jekyll-hive'

And then execute:

bundle

Or install it yourself as:

gem install jekyll-hive

Then add the following to your site's _config.yml:

plugins:
  - jekyll-hive

💡 If you are using a Jekyll version less than 3.5.0, use the gems key instead of plugins.

Use the tag as follows in your Jekyll pages, posts and collections:

{% hive author/permlink %}

This will place the associated content on the page.

⚠️ The post body is published as-is, including any raw HTML the post contains. jekyll-hive does not sanitize it, so only embed posts you trust. The source link uses the post's canonical_url metadata when it is an http/https URL, otherwise the post's hive.blog URL.

As of version 2.0.0, jekyll-hive uses HAFBE-backed post retrieval and emits structured embed markup instead of injecting per-post scripts and styles.

As of version 2.0.0, the {% hive %} tag emits structured embed markup and expects rendering dependencies to be loaded once by your site layout instead of being injected for every post.

At minimum, load your renderer and any supporting scripts/styles in a shared include such as _includes/head.html or your main layout. For example:

<script src='https://unpkg.com/steem-content-renderer'></script>
<script src='/assets/javascript/universal-bridge-against-phishing.js'></script>
<script src='/assets/javascript/lazysizes.min.js' async></script>

Then run a single page-level bootstrap pass against the generated embed targets, such as elements marked with data-hive-render-target="true".

If jekyll-hive detects cache entries created by the older inline-script / inline-style output format, it will warn once per build and recommend deleting .jekyll-hive-cache so the cache can be regenerated in the version 2.0.0 format.

The repo now includes a small synthetic diff-match-patch corpus under spec/fixtures/diff_match_patch_vectors.json to complement the real HAFBE history fixtures.

Purpose:

• pin down diff-match-patch semantics more surgically than the full history fixtures
• verify that percent-encoded inserted text remains literal when appropriate
• compare the Ruby dimapa path against optional external engines when available

Current helper layout:

• script/dmp_engine_ruby.rb — always-available Ruby helper used by the spec suite
• script/dmp_engine_python.py — optional Python helper using the diff_match_patch package
• spec/fixtures/diff_match_patch_frozen_witnesses.json — frozen external-engine witness outputs for durable regression coverage

If .venv-dmp/ exists, the spec prefers that repo-local Python for the optional live Python agreement check. Otherwise it falls back to python3 and cleanly skips the live Python comparison if the module is unavailable.

These synthetic vectors are not meant to replace the real HAFBE history fixtures; they exist to isolate patch semantics and cross-engine agreement.

When building your site with jekyll, you can continue to use the default command:

jekyll build

If you would like to provide an alternate HAFBE endpoint:

HAFBE_API_URL=https://api.hive.blog/hafbe-api jekyll build

To completely rebuild your site without cache:

rm -rf .jekyll-hive-cache && jekyll clean && jekyll build

Retrying: author/permlink (HAFBE request failed for @author/permlink: HTTP 404)
.
.
.
Gave up on: author/permlink

Check your internet connection, confirm the post exists, or provide an alternate HAFBE endpoint:

HAFBE_API_URL=https://api.hive.blog/hafbe-api jekyll build

The cached copy is out of date. Try deleting the related post from the cache or remove the entire cache:

rm -rf .jekyll-hive-cache

1. Fork it ( https://github.com/inertia186/jekyll-hive/fork )
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request

If you're using Jekyll::Hive, I'd love to hear from you. Drop me a line and tell me what you think! I'm @inertia on Hive.

I don't believe in intellectual "property". If you do, consider Jekyll::Hive as licensed under a Creative Commons License.