myOS

Public Site & Publishing

Everything in myOS is private by default. But when you want to share something — a blog post, a report, a portfolio page, or just a quick link to a file — publishing makes it accessible to anyone without authentication.

Overview

myOS gives you two ways to publish content:

Full Site

A complete static website powered by a site generator. You publish notes or files as pages with titles, URLs, and layouts. The site supports customizable themes, navigation links, footer text, and social links. It lives at a dedicated URL on your instance and rebuilds automatically when you publish or update content.

The full site is ideal for:

  • Blog posts and articles
  • Portfolio pages
  • Public documentation
  • Content you want to maintain and update over time

Quick Publish

Drop any file into a public directory and get an instant, direct URL. No pages, no themes, no build step — just a raw file accessible without authentication.

Quick publish is ideal for:

  • Sharing a report or dashboard with someone
  • Hosting a one-off HTML page
  • Making an asset publicly accessible
  • Anything temporary or standalone

What You Can Do

Ask Your Assistant

Your AI can handle both publishing methods:

Full site:

  • "Publish my quarterly review as a blog post" — converts the note to a page, picks a slug, and rebuilds the site
  • "Update the about page on my site" — edits the existing page content and rebuilds
  • "Set up my site with a clean theme, my name in the header, and links to Twitter and GitHub" — configures the site settings
  • "Unpublish the draft post I published yesterday" — removes the page and rebuilds

Quick publish:

  • "Make this report public" — copies the file to the public directory and returns a shareable link
  • "Publish this HTML dashboard so anyone can see it" — instant public URL
  • "Remove the published report" — deletes from the public directory
Ask Your Assistant

Try asking: "Take my note about productivity systems and publish it as a blog post on my site with the slug 'my-system'." Your AI converts the note to markdown, creates a page at /site/my-system/, and rebuilds the site. You get a public URL you can share anywhere.

From the UI

  • Publish button — notes and files have a "Publish to Site" action that creates a page with one click
  • Site config — set your site title, description, theme, navigation links, social links, and footer text
  • Page management — view all published and draft pages, publish or unpublish individual pages
  • Live preview — see your public site at its URL anytime

Examples

Personal blog

You write a note about a topic you're passionate about. From the note panel, you click "Publish to Site" — it becomes a page at yoursite.com/site/my-post/. You ask your AI to add navigation links for "Home," "Blog," and "About" to the site header. Over time, you publish more notes and build a collection of public writing.

Sharing a report

Your AI generates a quarterly health report as an HTML file with charts and insights. You say "make this public so I can share it with my trainer." The file gets a direct URL — yoursite.com/public/health-report.html — that you send over. No login required.

Automated publishing

You set up a workflow: every Monday, your AI generates a "Week in Review" summary note and publishes it to your site. Your public blog updates itself every week without you lifting a finger.

Tips

Tip

The full site and quick publish serve different purposes. Use the full site for content you want to maintain with consistent styling and navigation. Use quick publish for one-off shares where you just need a link.

Tip

Published pages stay linked to their source notes or files. When you update the original note, you can re-publish to sync the changes to your public site.

Info

Quick-published files are served directly by your web server — no build step, no processing. This makes them available instantly, but they also don't get the site's theme or navigation. They're just the raw file at a public URL.