Publish Your Content to the Public

Mikipage lets you publish notes and pages to the open web — no account required for your readers. This guide walks you through setting up a public site, from a personal blog to a collaborative wiki.

How publishing works

Everything public on Mikipage lives inside a public group. To publish content:

Create a Group and set it to public.
Set an alias for the group (at least 6 characters). Your site will be live at:
```
https://mikipage.com/public/<your_group_alias>
```
Post notes and pages to the group. Anything posted to a public group is publicly viewable at:
```
https://mikipage.com/public/<your_group_alias>/<note_or_page>
```

That's it — no separate "publish" button. The group's visibility is what makes content public.

Content aliases

When a note or page is first posted to a public group, it is automatically assigned a unique alias within the group — that alias is what appears in its public URL.

You can change the alias to anything you like (for example, a friendly slug like getting-started), as long as it stays unique within the group.

Setting a home page

If you set a Miki page's alias to / or home, that page becomes the home page of your site — it's what visitors see when they open:

https://mikipage.com/public/<your_group_alias>

You can give instructions describing how a sidebar should be generated. The system will generate a sidebar and show it alongside the page — useful for navigation, an index of your notes, or highlighting key pages.

Sidebars are not only for published pages. Any page can have one: on a public page it sits beside the content for your visitors, and on a page only you can see it opens from the toolbar button on the page itself. Ask for one the same way either way — describe it in the page's instructions.

On a public page opened at its named address (/public/<group>/<alias>), the sidebar starts with a link back to the page it belongs to, so readers always have a way "up". On your site's home page that link returns to the home page; on any other page it returns to that page, not to the home page — so a reader deep inside a section stays in the section.

The mental model: Groups, Pages, and Notes

Here's how the three pieces fit together:

Group — the container. It hosts everything in it, and you can invite people to contribute. For public groups, the group is your site.
Page — a "view", or a subset, of the notes in the group. AI reads the relevant notes and synthesizes them into a coherent page.
Notes — the raw content you post to the group. Only the note's owner can edit a note. Notes feed into pages.

Write freely in notes; let pages organize and present them.

Example 1: A personal blog

Suppose you want a personal blog site:

Create a group called My Blog and make it public.
Create a Miki page called "Daniel's Blog" in the group.
Write your blog posts as notes and share them to the group.

The Miki page picks up your notes as blog posts and presents them. Later, if you want a second blog focused specifically on your board game hobby, just create another page — "Daniel's Board Game Blog" — and it will automatically pick up the board-game-related notes from the same group.

Example 2: A fan wiki

Suppose you want a fan-built wiki for Game of Thrones:

Create a public group and invite others who might contribute.
Create Miki pages (they work like wiki pages) for the characters — Jon Snow, Daenerys, and so on.
Everyone just writes notes to the group.

Each Miki page summarizes from all the relevant notes, so the wiki grows as contributors add notes — no manual curation needed.

Example 3: This documentation site

The documentation you're reading right now is published exactly this way — it lives as notes in a public group on Mikipage. More details coming soon.