Solopreneurs face unique challenges. You wear every hat: creator, marketer, salesperson, accountant. Your time is limited, your resources constrained, your energy precious. A value ladder for solopreneurs must account for these realities while building sustainable income.

The good news is that solopreneurs also have unique advantages. You're nimble, authentic, and directly connected to your audience. Your personal brand is your greatest asset. Your ladder can leverage these strengths while minimizing the burdens of solo operation.

🎩 🎩 Solopreneur

The Solopreneur's Reality

As a solopreneur, your time is your most limited resource. Every hour spent creating content is an hour not spent on delivery, sales, or rest. Your ladder must be efficient, generating maximum impact per unit of effort.

You also carry the full weight of your business. Burnout is a real threat. Your ladder must be sustainable, allowing you to maintain energy and enthusiasm over years. Short-term gains aren't worth long-term exhaustion.

  • Limited time: Efficiency is essential
  • Multiple roles: Systems reduce burden
  • Burnout risk: Sustainability matters

Leveraging Your Personal Brand

Your greatest asset is you. Your personality, story, and perspective differentiate you from competitors. Leak content that reveals who you are, not just what you know. Personal connection builds trust faster than generic expertise.

Share your journey, including struggles and failures. Let your personality shine through your content. People buy from people they like and trust. Your authentic self is your competitive advantage.

Asset How to Leverage
Personality Show authentic self
Story Share journey authentically

Simple Ladder Structures for Solopreneurs

Complexity is the enemy of execution. A simple ladder with clear rungs works better than an elaborate structure you can't maintain.

The 3-Rung Ladder

Rung 1: Free content (social, newsletter). Rung 2: Low-ticket digital product ($20-50). Rung 3: High-ticket service ($500+). This simple structure covers the essentials without overwhelming you or your audience.

The 4-Rung Ladder

Add a mid-ticket group program between low and high. Rung 1: Free. Rung 2: Digital product. Rung 3: Group coaching/course. Rung 4: 1:1 service. This provides an intermediate step for those not ready for one-on-one. 

Simple Solopreneur Ladder:
- Free: Daily value leaks
- $27: Digital product
- $197: Group program
- $1000+: 1:1 service

Products That Scale

As a solopreneur, your time is finite. Products that scale are essential. Digital products (courses, templates, memberships) can sell infinitely with no additional time. Group programs scale better than one-on-one. Design your ladder to include scalable offers.

Your one-on-one service is your highest-touch, highest-price offer. But you can only serve so many people this way. Use scalable products to serve more people and generate income without trading time for money.

Systems for the Solo Operator

Systems are your employees. Automate what you can: email sequences, scheduling, payment processing, content distribution. Document processes so you can delegate later. Build systems that let you focus on high-value work.

Start with simple tools that solve specific problems. A email service provider automates nurturing. A scheduler handles meeting booking. A payment processor handles transactions. Each system saves you time and mental energy.

Community and Collaboration

Solopreneurs don't have to go it alone. Build relationships with other creators. Collaborate on content, cross-promote, and support each other. A community of peers provides accountability, ideas, and encouragement.

Consider mastermind groups with other solopreneurs at similar stages. Regular calls to share challenges and solutions reduce isolation and accelerate growth. Your peers become invaluable resources.

Protecting Your Energy

You are your business. Protect your energy accordingly. Set boundaries around work hours. Take real time off. Nurture your creativity through rest and experiences. A burned-out solopreneur has no business at all.

Build your ladder to support your life, not consume it. Sustainable growth beats rapid burnout every time. Your business should serve you, not the other way around.

If you're a solopreneur, review your ladder through the lens of efficiency and sustainability. Are you leveraging your personal brand? Do you have scalable products? Are your systems reducing burden? Simplify where needed and protect your most valuable asset: you.

jekyll versioned docs routing

Oleh -

Versioning documentation is essential when your product evolves, especially if breaking changes occur between releases. Users may be on different versions and need access to the documentation that matches their deployed software. Jekyll offers a lightweight way to organize and serve versioned content using folder-based routing.

Common Use Cases

  • APIs that release breaking changes per version
  • Software libraries with long-term support (LTS) releases
  • Educational material where previous versions need to remain accessible

Folder-Based Routing Strategy

The simplest way to manage versions in Jekyll is by creating separate folders for each version of the documentation inside a root directory like /docs.

docs/
├── v1.0/
│   ├── index.md
│   ├── installation.md
│   └── api.md
├── v2.0/
│   ├── index.md
│   ├── installation.md
│   └── api.md

Permalink Control

You can define permalinks in front matter for clean URL generation:

---
title: "API Reference"
permalink: /docs/v1.0/api/
layout: doc
---

Default Version Redirection

Use the root /docs to redirect to the latest version:

---
redirect_to: /docs/v2.0/
---

Automating Navigation Between Versions

Create a global navigation that allows users to switch versions easily. Define available versions in _data/versions.yml:

- version: v1.0
  path: /docs/v1.0/
- version: v2.0
  path: /docs/v2.0/

Dynamic Version Switcher

In your layout file:

<select onchange="location = this.value;">
  {% for ver in site.data.versions %}
    <option value="{{ ver.path }}" {% if page.url contains ver.version %}selected{% endif %}>{{ ver.version }}</option>
  {% endfor %}
</select>

Shared Layouts and Includes

Even though the content lives in separate folders per version, you can share the same layout and includes:

layouts/
├── doc.html
_includes/
├── toc.html

This keeps visual consistency across all versions.

Use Collections for More Control

If you prefer Jekyll collections over raw folders, define each version as a separate collection in _config.yml:

collections:
  v1_0:
    output: true
    permalink: /docs/v1.0/:path/
  v2_0:
    output: true
    permalink: /docs/v2.0/:path/

Then store content in _v1_0 and _v2_0 folders. This approach provides better metadata access and collection-wide iteration.

Version-specific TOC (Table of Contents)

Each version's TOC can be stored in _data/toc-v1_0.yml, _data/toc-v2_0.yml, and so on.

- title: "Getting Started"
  url: /docs/v1.0/index/
- title: "API"
  url: /docs/v1.0/api/

Search Integration per Version

To limit client-side search to the current version only, preload only the JSON index for that version. For example:

<script src="/docs/v2.0/search.json"></script>

This ensures search relevance and prevents results from older versions showing up unexpectedly.

Version Badging

Highlight the current version prominently using a badge:

<div class="version-badge">Version: {{ page.url | split: '/' | slice: 2,1 | first }}</div>

Versioning Guidelines for Authors

  • Copy from latest stable version when starting a new one.
  • Minimize duplication by using includes when content is identical.
  • Label breaking changes clearly across versions.

Managing Redirects Between Versions

In cases where pages have moved or renamed across versions, use Jekyll's jekyll-redirect-from plugin:

---
redirect_from: /docs/v1.0/old-feature/
permalink: /docs/v2.0/new-feature/
---

Benefits of Folder-Based Versioning

  • Straightforward organization and intuitive navigation.
  • Works well with static hosting like GitHub Pages.
  • Enables version-specific URLs for SEO and clarity.
  • Can be enhanced with version switchers and GitHub Actions.

Scaling Up: Automation and GitHub Actions

To automate the creation of a new version, use a script that:

  • Duplicates the latest version folder or collection.
  • Updates version number in all front matter.
  • Commits changes to GitHub for immediate deploy.

Conclusion

Building versioned documentation in Jekyll using folder-based routing is an elegant solution for maintaining scalable, user-friendly documentation. It requires a thoughtful structure but rewards you with clarity, maintainability, and complete control. Whether your product evolves monthly or yearly, this structure ensures your users are never left behind.

Next Ideas

  • Create version-aware breadcrumbs dynamically.
  • Build a diff tool to compare two versions of a document.
  • Implement version-based conditional rendering in templates.

Jekyll gives you the tools to scale your documentation—how you structure them is up to your creativity and discipline.