You can always make more money. You can never make more time. A time billionaire understands this and designs their life accordingly. Their ladder serves their life, not the other way around.

The time billionaire ladder moves from time poverty to time wealth to time abundance. Each rung increases your freedom to live on your own terms.

$ TIME BILLIONAIRE

The True Currency

Time is non-renewable:

  • Money lost can be regained
  • Time lost is gone forever
  • Every hour spent is an hour you'll never get back
  • The richest person is one with time freedom
  • Design your ladder to buy you time, not consume it
Resource Renewable?
Money Yes
Time No

Time Auditing

Know where your time goes:

  • Track your time for one week
  • Categorize activities (creation, admin, rest, etc.)
  • Identify time drains
  • Calculate your effective hourly rate
  • Ask: Is this worth my time?

Leverage and Systems

Build systems that multiply your time:

  • Automate repetitive tasks
  • Delegate what others can do
  • Create content that works 24/7
  • Build passive income streams
  • Use technology as a lever

Essentialism in Creation

Focus on what matters most:

  • Create less, but better
  • Say no to more opportunities
  • Focus on your zone of genius
  • Eliminate low-impact activities
  • Protect your creative energy

Boundaries as Freedom

Boundaries protect your time:

  • Set working hours and stick to them
  • Communicate availability clearly
  • Batch similar tasks
  • Schedule rest deliberately
  • Protect deep work time

Designing Your Ideal Week

Proactively design your time:

  • What does your ideal week look like?
  • How much time for creation?
  • How much for rest and relationships?
  • How much for learning and growth?
  • Build your ladder to support this design

The Ultimate Wealth

Time billionaire isn't about having endless time. It's about:

  • Spending your limited time on what matters
  • Not trading life for money you don't need
  • Being present in the moments you have
  • Building a ladder that serves your life
  • Recognizing that this moment is all there is

Audit your current relationship with time. Does your ladder serve your life or consume it? What would change if you treated time as your most valuable currency? Design one change this week that gives you more time for what matters.

multilingual support in jekyll sites without plugins

Oleh -

Why Multilingual Support Matters for Static Blogs

Expanding your blog’s reach to non-English speakers or supporting multiple languages can greatly improve accessibility and user experience. However, traditional methods often rely on Ruby plugins or dynamic backends, which are not compatible with GitHub Pages or fully static deployments. This guide explains how to build multilingual Jekyll sites without plugins or JavaScript, using only native features.

Approach Overview

We’ll use a folder-based approach where each language gets its own root-level directory. For example:

/_index.html
/en/index.html
/fr/index.html
/id/index.html
_layouts/
/_includes/
/_posts/en/
/_posts/fr/

This method is fully static and works flawlessly on GitHub Pages. It allows full control over routing, SEO metadata, and localized content presentation.

Step-by-Step Setup

Step 1: Define Your Languages

Start by deciding which languages you want to support. For example: English (en), French (fr), and Indonesian (id). You’ll create separate folders for each and route content accordingly.

Step 2: Organize the Directory Structure

Create a folder per language with its own index.html and subpages. You can also separate blog posts by language by creating language-specific collections or post folders.

/en/index.html
/en/about.html
/fr/index.html
/fr/a-propos.html
/id/index.html
/id/tentang.html

Step 3: Set Up Navigation

In your navigation bar or header include language switcher links:

<nav>
  <a href="/en/">English</a>
  <a href="/fr/">Français</a>
  <a href="/id/">Bahasa</a>
</nav>

Step 4: Use Includes for Translatable Layouts

Put your layout logic in _includes and inject translated text from front matter or data files.

{% raw %}
<p>{{ page.title }}</p>
<p>{{ site.data.translations[page.lang].welcome }}</p>
{% endraw %}

Step 5: Create a Translations Data File

Use _data/translations.yml to store translated strings:

en:
  welcome: "Welcome to my blog"
fr:
  welcome: "Bienvenue sur mon blog"
id:
  welcome: "Selamat datang di blog saya"

Step 6: Add Language Metadata

Each page or post should include the language code in its front matter for indexing and translation logic:

---
layout: default
title: "Tentang Saya"
lang: id
permalink: /id/tentang/
---

Managing SEO for Multilingual Pages

To help search engines identify content languages, add hreflang tags in the <head> section:

<link rel="alternate" hreflang="en" href="/en/" />
<link rel="alternate" hreflang="fr" href="/fr/" />
<link rel="alternate" hreflang="id" href="/id/" />

Also consider localized metadata like descriptions and titles in each page’s front matter for better indexing in local search engines.

Case Study: A Travel Blog With Three Languages

A travel blogger maintaining a static site on GitHub Pages wanted to cater to English, French, and Indonesian readers. Instead of relying on any plugin, they created a subfolder structure for each language and used data files to manage translations. As a result, their bounce rate decreased by 30% in non-English regions and they saw increased traffic from local Google search variations.

Handling Posts Per Language

You can use a folder naming convention like:

/_posts/en/2024-06-01-best-spots-london.md
/posts/fr/2024-06-01-meilleurs-endroits-paris.md

Then load these using custom collections per language or by filtering via the path in Liquid.

Performance and Accessibility

  • Fully static approach ensures blazing fast page loads
  • Does not require JavaScript, making it accessible for screen readers
  • Works out-of-the-box with GitHub Pages and Netlify
  • Optimized for search engines in each language

Drawbacks and Considerations

Managing content in multiple languages manually can be time-consuming, especially if your blog has frequent updates. For larger sites, a headless CMS or automated localization workflow might eventually be needed.

Conclusion

Jekyll is fully capable of serving multilingual content without requiring any plugins. By leveraging directory structures, data files, and basic Liquid templating, you can create a powerful, SEO-friendly multilingual site that’s fast, accessible, and suitable for free hosting platforms like GitHub Pages.