Read in:
English

Build your website with Obsidian in seconds — trip2g

  1. Sign Up or install on your server
  2. Open a home page
  3. Download a demo vault and open it in Obsidian
  4. Write your content
  5. Sync!

How trip2g works

Your Obsidian vault becomes a website the moment you sync. That is the core of what trip2g does. Everything else — Telegram publishing, monetization, AI assistant, federation — is the same system running in a wider context.

This page explains the full end-to-end picture: what happens to a note from the moment you write it to the moment a reader or AI agent reads it.

Getting started

Your Obsidian vault becomes a website in under a minute. Write in Obsidian, sync, and notes are live — with Telegram publishing, monetization, and an AI assistant built in. Try the demo or see how people use it.

14 KB page size

The full styled HTML of a trip2g page gzips to ~11.7 KB — inside the TCP initial congestion window of ~14 KB. The browser receives the complete, styled page in a single round-trip.

Two-Way Sync

By default the plugin syncs one way: you write in Obsidian, changes go to the server. The server never modifies your files.

Two-way sync sends changes in both directions. If a file is updated on the server, the plugin downloads it to your vault automatically.

One HTML page

Sometimes a page needs to be pure HTML — a product landing, a custom homepage, or a demo. In trip2g, this is done through layouts: all HTML lives in a template file, and the note just points to it.

Note: raw HTML in a note body does not work. goldmark (the markdown engine) strips block-level HTML and replaces it with <!-- raw HTML omitted -->. Put HTML only in the layout file.

Templates

Templates control how your notes look — sidebar, header, footer, and layout.

A template is an HTML file stored in _layouts/. It receives the note's content and frontmatter, then produces a complete page. Your markdown stays clean; the template decides how it's presented.

Webhooks

Webhooks let trip2g notify external services when notes change, or trigger actions on a schedule.

Two types are available: change webhooks fire when a note is created, updated, or deleted; cron webhooks fire on a schedule you define.