Business buyers are different from individual consumers. They're spending company money, managing professional risk, and answering to stakeholders. Your leak strategy for B2B must address these realities. The trust-building process takes longer, but the rewards are greater.

B2B buyers rarely purchase impulsively. They research, compare, and consult colleagues before deciding. Your leaks must support this journey by providing the information they need at each stage. When done right, your content becomes part of their research process and positions you as the obvious choice.

B2B

Understanding the B2B Buyer Journey

B2B buyers follow a structured journey. They begin with problem identification, then research potential solutions, evaluate options, and finally make a decision involving multiple stakeholders. Your leaks must support each stage with appropriate content.

Stage 1: Problem Identification

Leak content that helps buyers recognize and understand their problem. Share industry research, common challenges, and the cost of inaction. At this stage, you're not selling solutions; you're helping them see they have a problem worth solving.

Stage 2: Solution Research

Leak content that explores solution approaches. Share frameworks, methodologies, and case studies. Help them understand what a good solution looks like. Position your approach as one of the viable options.

Stage 3: Evaluation

Leak content that helps them evaluate options. Share comparison frameworks, evaluation criteria, and detailed case studies with metrics. Provide the information they need to build a business case.

Stage Content Focus
Problem ID Research, challenges, costs
Research Frameworks, methodologies

Building Professional Authority

B2B buyers bet their careers on the vendors they choose. They need to trust that you're credible, reliable, and low-risk. Your leaks must demonstrate professional authority through depth, evidence, and professionalism.

Depth Over Breadth

B2B audiences value deep expertise. Go deep on specific topics rather than covering everything superficially. A comprehensive whitepaper on one topic builds more authority than ten superficial blog posts.

Evidence and Data

Support your claims with data. Share research, case studies with metrics, and client results. B2B buyers need evidence to justify their decisions to stakeholders. Provide the ammunition they need.

  • Deep expertise: Specialize and go deep
  • Evidence: Data, metrics, case studies
  • Professionalism: Polished, credible presentation

LinkedIn as Primary B2B Leak Channel

LinkedIn is the dominant platform for B2B content. Your leaks here should prioritize professional value and industry insight. Long-form posts, articles, and documents perform well. Engage in comments to build relationships with potential buyers.

Use LinkedIn's document feature to share PDFs directly in the feed. A well-designed whitepaper or case study can generate significant engagement and leads. Follow up with connection requests to move relationships forward.

LinkedIn B2B Leak Strategy:
- Post 3-4x weekly with insights
- Share 1 long-form article weekly
- Create 1 document/case study monthly
- Engage meaningfully in comments
- Connect with engaged readers
  

Lead Magnets for B2B

B2B lead magnets should reflect professional needs. Whitepapers, research reports, benchmarking studies, and ROI calculators work well. These assets provide the depth and evidence B2B buyers require while capturing their contact information.

Gate your most valuable content behind forms. A comprehensive industry report is worth an email address. But ensure the content delivers on its promise; disappointing gated content damages credibility.

Nurturing B2B Leads

B2B sales cycles are longer. Your email nurture must sustain engagement over months. Provide ongoing value through insights, research, and case studies. Gradually introduce your offers as buyers move through their journey.

Segment your list based on engagement and interests. Send different content to different segments. Track which content leads to meetings or sales. Refine your nurturing based on what works.

Sales Conversations From Leaks

Eventually, leaks lead to conversations. When a prospect reaches out, they're already educated about their problem and your approach. Your job is to understand their specific situation and determine if your solution fits.

Ask good questions. Listen more than you talk. Customize your approach to their needs. Your leaks have done the heavy lifting; now close by being helpful and authentic.

If you serve B2B clients, review your current content through their journey. Are you providing the information they need at each stage? Are you building the professional credibility they require? Adjust your leak strategy to serve business buyers and watch your pipeline grow.

Designing Category-Based Navigation for Jekyll Collections

Why Category Navigation Matters for Jekyll Collections

For content-heavy Jekyll sites—especially knowledge bases, documentation sets, or niche blogs—clear navigation is crucial. One of the most effective approaches is to organize content into categories and present those categories in a structured, navigable layout.

While Jekyll doesn’t provide category navigation out of the box for collections, we can build a flexible system using Liquid logic and YAML front matter.

Case Study: Multi-Category Knowledge Base

Let’s assume we have a Jekyll collection named _kb representing a knowledge base. Each entry belongs to one or more categories defined in its front matter like this:

---
title: How to Use Front Matter
categories: [getting-started,configuration]
summary: Understand the basics of front matter in Jekyll pages.
---

We want to build a sidebar or sectioned layout that groups all entries by category, sorted alphabetically and linked automatically.

Step 1: Normalize and Extract Categories

In Jekyll, categories are simply a list of strings. To build category-based navigation, we need to:

  1. Extract all unique categories from the collection
  2. Sort them
  3. Loop over each category and list associated entries

Create a layout or include where you render the navigation block:

{% raw %}
{% assign all_categories = site.kb | map: "categories" | uniq | join: ',' | split: ',' | sort_natural %}
{% for category in all_categories %}
  

{{ category | capitalize }}

    {% for entry in site.kb %} {% if entry.categories contains category %}
  • {{ entry.title }}
  • {% endif %} {% endfor %}
{% endfor %} {% endraw %}

This ensures that even if an entry has multiple categories, it will be included in each appropriate section.

Step 2: Creating a Category Navigation Page

Add a dedicated page that loads this logic. For example, create categories.html:

---
layout: default
title: Categories
permalink: /categories/
---

{% include category-nav.html %}

Where _includes/category-nav.html contains the loop logic from earlier.

Step 3: Optional - Show Count Per Category

To show how many entries each category has:

{% raw %}
{% assign all_categories = site.kb | map: "categories" | join: ',' | split: ',' | uniq | sort_natural %}
{% for cat in all_categories %}
  {% assign count = 0 %}
  {% for entry in site.kb %}
    {% if entry.categories contains cat %}
      {% assign count = count | plus: 1 %}
    {% endif %}
  {% endfor %}
  

{{ cat | capitalize }} ({{ count }})

    {% for entry in site.kb %} {% if entry.categories contains cat %}
  • {{ entry.title }}
  • {% endif %} {% endfor %}
{% endfor %} {% endraw %}

This makes it easier for visitors to gauge which categories are most populated.

Step 4: Styling for Better UX

Here’s a minimal CSS suggestion to style your navigation panel:


.categories-index {
  max-width: 600px;
  margin: 0 auto;
}

.categories-index h3 {
  margin-top: 1.5em;
  font-size: 1.2em;
  color: #333;
}

.categories-index ul {
  padding-left: 1.2em;
}

.categories-index li {
  margin-bottom: 0.5em;
}

Using Includes for Reusability

If you want to show category-based navigation on multiple pages (like a sidebar or homepage), wrap the logic inside a reusable include:


{% include category-nav.html %}

This keeps your layout clean and improves maintainability.

Alternative Approach: Grouping by Front Matter Field

You can adapt the same pattern to group by other metadata fields such as tags, difficulty, status, or language. Just replace categories with the relevant field.

Grouping by Language Example

{% raw %}
{% assign langs = site.kb | map: "lang" | uniq | sort %}
{% for lang in langs %}
  

{{ lang | upcase }}

    {% for item in site.kb %} {% if item.lang == lang %}
  • {{ item.title }}
  • {% endif %} {% endfor %}
{% endfor %} {% endraw %}

This is useful if you’re building multilingual sites or topic-specific learning paths.

Bonus: Add Anchor Links for Each Category

If your list is long, add anchors so users can quickly navigate to a category:




{% for cat in all_categories %}
  

{{ cat | capitalize }}

    {% for entry in site.kb %} {% if entry.categories contains cat %}
  • {{ entry.title }}
  • {% endif %} {% endfor %}
{% endfor %}

This improves the experience, especially on mobile or long pages.

Conclusion

Dynamic category-based navigation using Liquid opens up powerful content organization capabilities in Jekyll, all while staying within the limits of GitHub Pages’ static hosting. Whether for documentation, courses, or knowledge libraries, you can offer your visitors intuitive pathways to explore your content by topic.

Artikel selanjutnya akan membahas bagaimana membangun sistem tag-based navigation untuk Jekyll collections yang lebih fleksibel dan ideal untuk filter konten dinamis tanpa JavaScript tambahan.