TiddlyWiki Guide to Getting Started Docker Themes and Alternatives

TiddlyWiki is a free, open-source personal wiki for creating connected notes and organizing information. You can use it as a self-contained HTML file in your browser or run it as a Node.js application. Its small, linked entries are called tiddlers.

My recommendation is to start with one useful collection, such as article research or business procedures. Learn how to save and recover that collection before adding themes, plugins or a server.

For entrepreneurs and bloggers, the real value is being able to find and reuse what you already know. This guide explains where TiddlyWiki fits, how to get started, what to check before a Docker deployment, and when another tool would be a better choice.

What is TiddlyWiki and who is it for

The official TiddlyWiki project describes a customizable wiki that works in a browser or under Node.js. The browser edition combines the application and its content in one HTML file.

That makes it worth considering for a personal knowledge base, research notebook, project reference library or digital garden. A digital garden is a collection of connected ideas that you develop over time.

I would shortlist it if you enjoy shaping your own workspace and want control over your files. I would compare other tools first if your immediate requirement is a ready-made team workspace with detailed permissions and minimal administration.

This guide covers TiddlyWiki 5. When following tutorials or installing extensions, check that they target this generation rather than TiddlyWiki Classic.

Understand tiddlers before adding more features

A tiddler is an individual unit of information. It can contain text and fields, with a title identifying it. You can connect related entries instead of putting everything into one long document.

For example, a small business research wiki might contain:

• Customer onboarding checklist
• Questions prospects ask before buying
• Website redesign notes
• Sources for a new article

Use clear titles that will still make sense six months later. “Questions prospects ask before buying” is easier to retrieve than “Meeting notes final 3.”

Links connect your notes

To link to another tiddler in WikiText, put its title inside double square brackets:

[[Customer onboarding checklist]]

The official linking guide also explains labelled links and external URLs. Add links when they explain a relationship, not simply because two notes mention the same word.

Tags group related material

Use a small, consistent set of tags such as Research, Procedures and Ideas. Decide what each means before creating dozens of near-duplicates.

A useful rule is to use links for specific relationships and tags for broader groupings. For example, a customer interview can link to a particular product idea while sharing the Research tag with other interviews.

Transclusion lets you reuse content

Transclusion displays content from one tiddler inside another. Changes to the source appear wherever that source is included.

Imagine maintaining a standard project handover checklist. You could display that checklist in several project reference notes while updating the source in one place. This is useful for reusable information, although a historical record may need a fixed copy of what was true at the time.

Choose the right TiddlyWiki setup

The GettingStarted documentation links to an empty wiki download, saving methods and Tiddlyhost, an independently operated hosting service.

For a first experiment, I would use a local file. It lets you evaluate whether connected notes suit your work before taking on server maintenance.

How to get started with TiddlyWiki

Download and name your wiki

Use the empty wiki download from the official getting-started page. Save it with a recognizable name, such as business-notes.html, and open it in a supported browser.

Choose a saving method that works with your browser and operating system. The official guide explicitly warns that the browser’s ordinary File or Save command is not a reliable way to save changes to TiddlyWiki.

Create a small working collection

Use the plus button to create a tiddler, enter a title and write a short note. Add a tag if useful, then confirm the edit. The creating and editing documentation explains these controls.

Start with five notes you would actually use. For a blogger, these could be an article idea, audience questions, source links, an outline and an editing checklist.

Link the outline to the source notes. Keep your own interpretation separate from quoted material, and record where each claim came from.

Test saving before entering important information

Confirming an edit and saving a durable copy of the wiki are separate concerns. Follow the saving guidance for your chosen setup.

My suggested test is simple:

1. Create a disposable tiddler with a distinctive sentence.

2. Save using TiddlyWiki’s configured saving method.

3. Open the saved result in a separate tab or window.

4. Check that the sentence and its latest edit are present.

5. Keep a separate backup before adding valuable material.

With a download-based saver, pay attention to filenames. A newly downloaded copy may sit beside an older file, making it easy to reopen the wrong one.

A practical content research workflow

Suppose you are preparing an article about customer retention. Instead of collecting unlabelled links, give each source its own note with a purpose.

This is a proposed workflow, not a claim that TiddlyWiki automatically fact-checks your research. You still need to read sources, confirm details and remove outdated information.

For business procedures, add an owner and review date to each important note. A clearly written process can still become unreliable when nobody maintains it.

If you are building an editorial system, my content marketing guides cover the broader work of planning useful content. TiddlyWiki can organize the research behind that work.

TiddlyWiki Docker setup and image selection

A TiddlyWiki Docker deployment runs the server application inside a container. It is useful when you already manage containers or want a repeatable service configuration.

You do not need Docker for a personal wiki. The project’s official Node.js installation guide provides a direct server route:

npm install -g tiddlywiki

tiddlywiki mywiki –init server

tiddlywiki mywiki –listen

With Node.js and npm installed, run these commands in a suitable working directory, then visit http://127.0.0.1:8080/ on that computer. Use a new folder name rather than experimenting inside an existing wiki.

Check the Docker image publisher

If you found this guide while searching for “ghcr.io/tiddlywiki/tiddlywiki docker,” check the image publisher before using that path.

During this research, I could not verify that exact image path as an officially documented TiddlyWiki image. That does not establish that it can never exist. It means I would not present it as an official installation command without a project source confirming it.

One separately documented option is henry40408’s TiddlyWiki image. Its maintainer explicitly identifies it as unofficial. Its registry path, configuration and storage directory belong to that particular image; they should not be assumed to apply to other images.

It is worth knowing that henry40408’s image is not the only unofficial option either. A search of active community images turns up several more, including nicolaw/tiddlywiki, elasticdog/tiddlywiki and djmaze/tiddlywiki-docker, each maintained independently, on different registries, with different storage paths and environment variables. None of them is the TiddlyWiki project itself publishing an official image. If you arrived here searching the specific path ghcr.io/tiddlywiki/tiddlywiki, treat that as a sign to double-check whichever source suggested it, rather than a path to run directly; it did not turn up as a maintained image from the TiddlyWiki project or from any of the community maintainers found during this research.

A local Docker Compose example

The following example adapts that community image’s documented storage path. It is for a local evaluation on your own computer with a current Docker installation and Docker Compose. Confirm that the image supports your machine’s architecture before pulling it.

Create a new project folder and save this as compose.yaml:

services:
  wiki:
    image: ghcr.io/henry40408/tiddlywiki5:latest
    ports:
      – “127.0.0.1:8080:8080”
    volumes:
      – wiki-data:/var/lib/tiddlywiki
volumes:
  wiki-data:

Start the service from that folder:

docker compose up -d

Then open http://127.0.0.1:8080/ on the same computer.

This example follows the maintainer’s documentation and startup script; it has not been runtime-tested for this article. The latest tag is used for the demonstration. For ongoing use, inspect the actual version and pin a verified tag or image digest after testing.

The explicit 127.0.0.1 binding limits the published port to the Docker host under Docker’s documented networking behavior. It does not add a login. See Docker’s port-publishing documentation before changing the binding for network access.

Verify storage before relying on the container

Create a test note, restart the service, then check that the note remains:

docker compose restart

The named volume stores the wiki separately from the container. Docker’s volume documentation explains persistence, backup and restore. A persistent volume is not a backup of itself.

For a practical recovery plan, stop editing, take a consistent backup of the wiki data, and test restoring it separately. Keep a record of the image version and configuration. Avoid commands that remove volumes, including docker compose down -v, unless you intend to delete the stored data.

Plan access before hosting it publicly

The standard TiddlyWiki web server documentation describes simple authentication and recommends an external proxy before internet exposure.

A public deployment needs deliberate authentication, authorization and HTTPS configuration. Do not turn this local example into a public service by simply removing 127.0.0.1.

For multiple users, distinguish the standard server from MultiWikiServer. The latter is a separate development effort; its documentation currently flags user-security limitations. Review its current status before choosing it for business information.

TiddlyWiki themes and appearance options

TiddlyWiki themes change the interface, while colour palettes control named colours. A palette change may be enough if your main concern is readability.

The official appearance guidance recommends exploring themes, palettes and the Control Panel before using custom stylesheets. The palette documentation explains the palette switcher in the sidebar Tools tab.

Themes worth exploring

The official community themes directory lists these examples:

These are options to evaluate, not a claim that every older theme works perfectly with every current release. Follow the directory’s links and check the theme’s own instructions and recent compatibility reports.

Older search results also surface TiddlyWiki Classic theme collections. Confirm the supported TiddlyWiki generation before importing anything.

Install themes in a copy first

For a single-file wiki, follow the theme author’s import instructions and review the items being imported. Save and reopen the test copy, then check editing, navigation and mobile readability.

For Node.js, installation can involve the themes section of tiddlywiki.info and a server restart. Follow the project’s Node.js plugin and theme instructions, plus any instructions specific to a community theme.

My advice is to solve one interface problem at a time. If your notes are hard to find, improve titles and organization before redesigning the whole wiki.

TiddlyWiki alternatives and when I would choose them

There is no single best replacement for every workflow. Compare the task you need to complete, the format you prefer and the administration you can support.

Obsidian emphasizes local notes, linking, themes and plugins. I would evaluate it when someone wants a dedicated app for connected thinking without TiddlyWiki’s browser-file saving workflow.

Notion’s workspace guide explains shared and private content and collaboration. I would compare it when team adoption and a shared workspace matter more than carrying the application in one file. Check current plan limits against your needs.

Joplin offers rich-text and Markdown editing, web clipping, desktop and mobile apps, and several synchronization options. It belongs on the shortlist when capturing information across devices is the main requirement.

BookStack uses a books, chapters and pages structure and includes roles and permissions. I would consider it for an internal procedures library where staff benefit from a predictable hierarchy.

Before moving a large collection, test a small export and import. Titles, tags, attachments and links may not translate cleanly between different data models.

Common mistakes that make a personal wiki harder to maintain

Customizing before establishing a useful habit

A complicated dashboard cannot rescue notes you never review. Start with one recurring activity and measure whether you can find the information more easily.

Treating cloud synchronization as a backup

Synchronized changes can include unwanted edits. Keep recoverable copies and test them. Avoid editing the same single-file wiki independently on two devices and expecting every change to merge automatically.

Assuming every feature is built in

A theme, plugin, hosted service and server edition can behave differently. Record which additions you install and why. That makes troubleshooting easier when the interface changes.

Migrating everything immediately

Run a small pilot first. Include ordinary text, a long note, an attachment and several linked entries. Try your normal search, editing and recovery tasks before expanding the collection.

My recommendation for getting useful results

Start with five notes, one clear purpose and a saving method you have checked. Use the wiki for a real project before deciding whether you need a new theme or a server.

Choose TiddlyWiki because its approach helps you organize and reuse information. If another tool makes your team’s daily work easier, choose that tool instead. You can explore more practical software walkthroughs in my app guides.

Frequently asked questions