wiki.fermenthings.be

Start with one project, read the full article before you touch any ingredients, and treat the wiki's background pieces as part of the instructions rather than optional reading. The Fermenthings Open Source Wiki ("A Curious Space for Cultured Things") is a collection of fermentation articles and recipes, and it works well as a beginner's path if you use it in a deliberate order: pick a single ferment, read the whole entry, then expand to related projects once that one succeeds.

What the wiki actually contains

The site describes itself as "a place to learn everything about fermentation," and its published entries mix practical recipes with cultural and historical context. From the visible content, the range includes:

Two things stand out for a beginner. First, several entries are explicitly framed as introductions (tempeh) or as comparisons (the three bottled ferments), which is exactly what you want before committing to equipment. Second, the wiki repeatedly connects a ferment to its cultural origin — tempeh to Java, kimchi and curtido to salted-cabbage traditions in different regions — so the context is part of the teaching, not decoration.

A beginner path through the wiki

Step 1: Choose one ferment, not five

The "Three Ways to Bottle a Summer" entry is useful precisely because it groups ginger bug, elderflower champagne, and kombucha together — but that grouping is a menu, not a to-do list. Pick one. A single successful batch teaches you more about temperature, timing, and signs of activity than three half-finished jars.

If you want a low-equipment starting point, a salt-based vegetable ferment (the kimchi or curtido entries) needs little beyond a jar, salt, and vegetables. If you want a project with a clear "is it working?" signal, tempeh is instructive because the visible mold growth tells you directly whether conditions were right.

Step 2: Read the entire entry before starting

This matters more than it sounds. The wiki's own kimchi stew entry describes a recipe that "sat in your head for years before it finally happened" and only came together once the right conditions existed — a daily miso soup production supplying living broth, plus deeply aged kimchi from friends. That is a real constraint: some recipes depend on having another ferment already running. Reading to the end tells you whether you need a prerequisite ferment, aged ingredients, or specific equipment before you begin.

Step 3: Note the conditions, not just the ingredient list

Fermentation outcomes depend on temperature, salt concentration, time, and cleanliness. When you read an entry, extract those variables into your own notes before you start:

• What temperature range does the article assume?
• How long should the ferment take, and what does "done" look like?
• What are the signs of normal activity versus a problem?
• Does the recipe assume a starter from a previous batch?

Step 4: Expand only after one success

Once one ferment works reliably, the wiki's cross-references become useful. Kimchi leads naturally to kimchi stew. A ginger bug leads into the bottled-summer comparison. Miso, once you have it, opens up the miso cookies entry — which makes the point that miso is "much more versatile" once you stop treating it as belonging to a fixed set of dishes.

Why the background articles are worth your time

The wiki's cultural and historical entries — Curtido, Master Of Spices — explain why a technique exists, not just how to repeat it. That matters practically: if you understand that salting cabbage is a preservation method that developed independently in Korea, Latin America, and Europe, you understand the mechanism (salt draws out water, selects for the microbes you want, and acidifies the environment) rather than memorizing one recipe. When a batch behaves unexpectedly, mechanism knowledge is what lets you diagnose it.

The Master Of Spices entry frames heat as something that "travels" along trade routes and through migrations, becoming taste and memory. For a beginner, the takeaway is that spice levels in a ferment are a design choice with a history, not a fixed rule — you can adjust them.

Common sticking points

• Starting with too many projects at once. The wiki's grouped entries invite this; resist it.
• Skipping to the ingredient list. Prerequisites like an existing living broth or aged kimchi are easy to miss.
• Ignoring the "done" criteria. Each ferment has its own visual, aromatic, and textural signals.
• Treating recipes as fixed. The miso cookies entry explicitly argues for treating an ingredient as flexible rather than tied to specific dishes.

What to do next

Open the wiki, pick the single entry that matches the equipment you already own, and read it start to finish before buying anything. If you have a jar and salt, start with the kimchi or curtido material. If you want a ferment with an unmistakable progress signal, start with the tempeh introduction. Then, and only then, use the bottled-summer comparison to choose your second project.

An open-source UI element library is a collection of individual, ready-made interface pieces—buttons, cards, inputs, toggles, loaders—that you copy into your own project and adapt. A UI framework, by contrast, is a structured system of components, conventions, and often a theming layer that governs how your whole interface is built. The practical difference: an element library gives you a snippet; a framework gives you a way of working. If you need a polished button in ten minutes, reach for the element library. If you're building a 40-screen product with a team, you probably want the framework.

What "open-source UI element library" actually means

The term gets used loosely, so it helps to separate the parts:

• Open-source: the code is publicly available, and the license tells you what you may do with it—copy, modify, redistribute, or use commercially.
• UI element: a single, self-contained piece of interface, usually small enough to read in one sitting. A button with hover states, a pricing card, a search field.
• Library: a browsable, searchable collection of those elements, typically contributed by many different people.

On a site like Uiverse, elements are shared by a community and written in plain CSS or Tailwind. You find one you like, copy the markup and styles, paste them into your project, and adjust colors, spacing, and text to fit. There's no package to install and no build step required—which is exactly the appeal, and also the source of most of the confusion.

Element library vs. UI framework: the core differences

The table isn't a verdict. It's a map of trade-offs. Element libraries win on speed and freedom; frameworks win on consistency and maintenance.

Licensing and attribution: what to check before you paste

This is where people get into trouble, and it's worth slowing down for.

1. Find the license. Every element or collection should state one. Common open-source licenses include MIT, Apache-2.0, and BSD. Some projects use copyleft licenses like GPL, which can impose obligations if you redistribute your code.
2. Understand what the license permits. MIT and Apache-2.0 are permissive: you can typically use the code in commercial and closed-source projects. Copyleft licenses may require you to release derivative source under the same terms.
3. Check attribution requirements. Permissive licenses usually require you to keep the copyright notice and license text somewhere in your project. That's a real obligation, not a formality.
4. Look for per-element terms. On community sites, the site's overall terms and the individual contributor's stated wishes may differ. If a contributor asks for credit, honor it.
5. When in doubt, ask or avoid. If a snippet has no license at all, you don't have clear permission to reuse it. Treat "no license" as "not open source," even if the code is publicly visible.

This article is general information, not legal advice. For commercial products with real exposure, have someone qualified review the licenses you're relying on.

How to use a community element in your project: a practical workflow

Here's a repeatable process that avoids most of the usual mess.

1. Start from a real need, not a browsing session

Decide what you need first—"a compact primary button with a loading state"—then search. Browsing aimlessly produces a pile of pretty snippets that don't fit together.

2. Copy the smallest version that works

Take the markup and the styles. Strip anything you don't need: demo wrappers, extra animations, decorative layers. Less code means fewer surprises.

3. Convert it to your conventions

If your project uses design tokens or CSS variables, replace hard-coded values:

/* Before: hard-coded */
.button { background: #4f46e5; border-radius: 8px; }

/* After: token-based */
.button { background: var(--color-primary); border-radius: var(--radius-md); }

This one step is what keeps a copied element from looking like a foreign object in your UI.

4. Check accessibility before you ship

Community elements vary widely here. Verify at minimum:

• Keyboard focus is visible and the element is reachable by Tab.
• Color contrast meets WCAG AA (4.5:1 for normal text).
• Interactive elements use semantic HTML (<button>, not a clickable <div>).
• Form inputs have associated labels.
• Motion respects prefers-reduced-motion.

5. Test in context

Paste it into a real page with real content. Long labels, small screens, and dark mode break more copied elements than anything else.

6. Note where it came from

Keep a short comment or an internal credits file: source, license, date. Future you—and your legal reviewer—will be grateful.

Where element libraries genuinely shine

• Prototypes and demos: you need something clickable today, not a design system.
• Landing pages and marketing sites: a handful of distinctive elements, each custom.
• Filling gaps: your framework lacks one specific component, and you don't want to build it from scratch.
• Learning: reading well-made CSS is one of the fastest ways to improve.
• Small projects: a personal site doesn't need a theming architecture.

Where they fall short

• Consistency at scale: ten elements from ten contributors rarely look like one product.
• Maintenance: you own every copy. When your design changes, you edit each one.
• Accessibility debt: you inherit whatever the contributor did or didn't do.
• No upstream fixes: a bug fixed in the original won't reach your copy.
• Integration friction: different naming conventions, different units, different assumptions about resets.

When to choose which

Choose an element library when the scope is small, the timeline is short, or you need a few distinctive pieces rather than a whole system.

Choose a framework or design system when multiple people build multiple screens over months, when consistency is a product requirement, or when accessibility and theming need to be guaranteed rather than checked.

A hybrid works well for many teams: adopt a framework for the structural components—forms, navigation, layout—and borrow individual elements for the places where you want personality. Just route every borrowed element through the same token and accessibility checks, so it lands as part of your system rather than beside it.

The short version: open-source UI element libraries are a fast, flexible way to get good-looking interface pieces into a project. They are not a substitute for a design system, and the license and accessibility details are the part worth reading carefully.

"Open source" on the Fermenthings wiki describes how the site presents and shares its fermentation knowledge rather than a software license you can look up in a code repository. The wiki publishes its articles and recipes openly, so anyone can read them, learn from them, and apply the techniques at home. What it does not automatically tell you is the exact legal terms for reusing or republishing the text and images — those terms live on the site itself, and you should check them before copying content elsewhere.

What the site actually is

Ferment Lab: Fermenthings Open Source Wiki describes itself as "a place to learn everything about fermentation" and frames its collection as "a curious space for cultured things." It is a knowledge-sharing project built around written articles and recipes, not a product with a paywall or account requirement described in the available material.

The content is organized as individual posts, each covering one fermentation project or idea. Examples visible on the site include:

• Miso Cookies — treating miso as a general ingredient rather than something limited to soups and marinades
• Three Ways to Bottle a Summer — ginger bug, elderflower champagne, and kombucha
• Introduction to Tempeh Making — tempeh's origins on Java and its role in preserving soybeans in a warm, humid climate
• Chinese Cabbage Kimchi (Baechu Kimchi)
• Fermenthings' Kimchi Stew
• Master of Spices — chili, heat, and the history of spicy preservation
• Curtido — described as the Latin cousin of sauerkraut and kimchi

Each entry mixes practical method with context: where a ferment comes from, why it developed, and how the technique fits into a broader food tradition.

What "open source" means here

In practice, an open-source wiki usually implies three things:

The first two are the spirit of the project. The third is where you should not assume. "Open source" in common usage suggests reusability, but the actual permissions — whether you can republish a recipe on your own site, translate it, or use photos commercially — depend on the terms the site publishes. Read those before reusing anything.

Why open sharing matters for fermentation

Fermentation knowledge has always spread through sharing. The wiki's own framing reflects this: heat "travels" along trade routes and through migrations, and cabbage salting appears independently in Korean kimchi, Latin American curtido, and European sauerkraut. An openly readable collection continues that pattern — a home fermenter in one country can follow a technique documented from another, test it, and feed observations back.

For a beginner, this means you can start with a single recipe, learn the underlying principle, and then adapt it. For someone with experience, it means the collection works as a reference to compare traditions rather than a fixed rulebook.

How to use the wiki

1. Pick one project that matches what you have. If you have cabbage, start with kimchi or curtido. If you have soybeans, look at the tempeh introduction.
2. Read the full entry, not just the ingredient list. The context sections explain why steps matter, which helps when your conditions differ from the author's.
3. Check the site's own terms if you plan to republish, translate, or reuse images.
4. Treat dates as a signal. Entries carry publication dates, so you can see how recently a topic was covered.

The main limitation to keep in mind: an open wiki reflects its contributors. Coverage is uneven, and a topic you need may be thin or missing. Where an entry is detailed, it tends to be because someone documented a process they actually worked through — which is usually the most useful kind of fermentation writing.

The Fermenthings wiki (wiki.fermenthings.be) is an open-source fermentation knowledge base that mixes practical recipes with the culture and science behind them. Based on the articles currently visible on the site, you can find content spanning miso, tempeh, kimchi, fermented drinks, and Latin American cabbage ferments — each written as a dated article rather than a standardized database entry. The exact catalog changes over time, so treat the list below as a snapshot of what the wiki covers, not a fixed index.

What kinds of content does the wiki publish?

The site describes itself as "a place to learn everything about fermentation" and "a curious space for cultured things." Two content types appear consistently:

• Recipes with a specific angle — e.g., miso cookies, kimchi stew, or three different bottled summer drinks.
• Explanatory and cultural articles — e.g., the history of chili and preservation, or how cabbage fermentation travels across cultures.

Articles carry publication dates and thematic titles, so you can browse chronologically or by topic. The writing tends to connect a technique to a broader story rather than just listing ingredients.

Fermentation categories covered

Miso and umami-forward ferments

The wiki's miso content goes beyond soup. One article, "Miso Cookies: When Umami Meets the Shortbread Biscuit," argues that once you treat miso as a general ingredient rather than something tied to savory dishes, it becomes far more versatile — with a butter cookie as the example. This is useful if you already make miso and want non-traditional uses.

Tempeh

"Introduction to ... Tempeh making" frames tempeh as fermentation "doing exactly what it is meant to do: transform simple ingredients into something nourishing, stable, and deeply satisfying." It notes tempeh originated on the island of Java in Indonesia as a way to preserve soybeans in a warm, humid climate. Expect a foundational introduction rather than an advanced troubleshooting guide.

Kimchi and cabbage ferments

Cabbage fermentation is a recurring theme:

• Chinese Cabbage Kimchi (Baechu Kimchi) — a dedicated recipe article.
• Fermenthings' Kimchi Stew — a recipe built on aged kimchi and living broth, described as an idea that took years and the right conditions to realize.
• Curtido — presented as "the Latin cousin of sauerkraut and kimchi," a story of cabbage, culture, and quiet fermentation.

If your interest is salted-cabbage ferments across cultures, this is the strongest cluster on the site.

Fermented drinks

"Three Ways to Bottle a Summer: Ginger Bug, Elderflower Champagne & Kombucha" groups three drink projects around a single question: how do you capture a season in a bottle? The article ties this to the broader human practice of preserving abundance through drying, salting, smoking, or fermenting. This is a good starting point if you want carbonated, low-equipment ferments.

Spices, heat, and preservation

"Master Of Spices: Global Heat and The Art Of Spicy Preservations" explores chili, spice, and the history of heat — how capsaicin, sanshool, and isothiocyanates become taste, culture, and memory as they move along trade routes and across generations. This is background reading rather than a step-by-step recipe.

Quick reference

How to use the wiki

1. Start from a category you already cook. If you make cabbage dishes, the kimchi and curtido articles connect directly to what you know.
2. Read the framing before the recipe. These articles often explain why a ferment works before telling you what to do, which helps when you adapt a recipe to your own ingredients.
3. Check the date. Articles are dated (the visible ones range from late 2025 into 2026), so newer posts may reflect updated methods.
4. Verify current coverage on the site itself. The visible article list is a sample; the wiki may add or reorganize topics, and no pricing or login requirements are stated in the available material.

If your interest is a specific ferment not listed here — say, koji, vinegar, or dairy — confirm it exists on the site before assuming coverage, since the evidence only supports the categories above.

Ferment Lab: Fermenthings Open Source Wiki is an open-source fermentation knowledge wiki published by Fermenthings, described as "a place to learn everything about fermentation." It is a reference and recipe space for people who want to make fermented foods at home or understand the culture and history behind them. The site is in English, and its visible content mixes practical recipes, step-by-step guides, and longer cultural essays rather than acting as a single-subject blog.

What the site covers

The homepage presents itself as "A Curious Space for Cultured Things." Its visible entries span several fermentation traditions and formats:

• Miso — including a recipe that treats miso as a general ingredient, such as miso cookies where umami meets a shortbread biscuit.
• Tempeh — an introduction to tempeh making, framed as "growing protein, binding culture," with its origins on the island of Java in Indonesia.
• Kimchi — a Chinese cabbage kimchi (baechu kimchi) recipe, plus a kimchi stew that uses aged kimchi and a living miso broth.
• Kombucha and other bottled ferments — a piece on bottling summer with ginger bug, elderflower champagne, and kombucha.
• Chili and spice preservation — an exploration of chili, spice, preservation, and the history of heat.
• Curtido — described as the Latin cousin of sauerkraut and kimchi, a salted cabbage ferment.

What kind of content to expect

The entries are not limited to ingredient lists and timings. They typically combine:

1. Recipes — concrete preparations such as miso cookies, baechu kimchi, or kimchi stew.
2. Guides — instructional introductions, for example to tempeh making.
3. Cultural and historical context — essays on how heat travels along trade routes and migrations, or how salting cabbage became kimchi in Korea and curtido in Latin America.

This mix means the wiki works both as a place to follow a method and as background reading on why a ferment exists in a given cuisine.

Who it is for

It suits home fermenters, cooks curious about fermentation beyond a single recipe, and readers interested in the food-culture side of preservation. Because the content is open source and organized as a wiki, it is also relevant to anyone who wants to see how a fermentation knowledge base is structured, or who might want to contribute to one.

Practical notes

The visible pages are dated, with entries running from late 2025 into 2026, so the wiki is actively added to rather than archived. The site does not display pricing or login requirements in the material available here; treat access and any contribution rules as things to confirm on the site itself rather than assuming they are free or open to edit.