Meta · Site Guide

How to publish.

Most reports belong in ClickUp Docs. Interactive dashboards can't — so they end up as HTML files on your desktop, with nowhere to go.

TypeSite guide

ForAnyone publishing

Reading time~2 minutes

Code META·25·001

Where does the artifact go?

Claude built you a dashboard — it's on your desktop, finished, exactly right. But ClickUp can't render it, you can't email it like a doc link, and most people can't open it. The artifact just sits there, with nowhere to go.

A real home for the artifact

Uplive Publications is where the artifact goes. Hand it the HTML — or the prompt that built it — and it gets a real link in three prompts. No terminal, no git, no hosting.

What changes for you

The artifact gets a real link anyone can open — not emailed or screenshotted back.
A non-technical person can publish one, on their own — no terminal, no git.
Every page reads as one searchable publication — same look, searchable from the homepage.

Here's how to start

Three steps, in order: get access once, set up once, publish every time.

Step 1 — get GitHub access (do this once, before Step 2)

If you don't have a GitHub account yet, create one at github.com — it's a normal sign-up.

Email giang.nguyen@uplive.zone with your GitHub username and ask to be added to Uplive Publications.

Once you're added, log in on this computer — you only need to do this once per computer. Paste this into Claude:

Please help me log into GitHub on this computer, so I can publish to Uplive Publications later:

1. Check if the GitHub CLI (`gh`) is installed. If it isn't, install it.
2. Run `gh auth login` and walk me through every step -- if it asks me to open a link and enter a code, tell me exactly what to open and what to type.
3. Once I'm logged in, run `gh auth setup-git` so regular git commands use this login too.

Tell me plainly when it's done.

Step 2 — set up access (do this once)

Paste it into any Claude Code session — the folder doesn't matter. Claude creates the folder and confirms setup.

Please set up my access to Uplive Publications:

1. Clone https://github.com/uplive-z/publications.git into ~/uplive-publications (skip this if that folder already exists and is already a clone of this repo).
2. Confirm it worked by showing me the folder contents.

Then tell me plainly: "Setup done -- now open a new Claude Code session inside ~/uplive-publications to publish something."

When setup is done, open a new Claude Code session inside that folder — that's where you publish from.

Here's how:

Open a terminal.
Type cd ~/uplive-publications and press Enter.
Type claude and press Enter.

If you usually use an app or IDE instead, open ~/uplive-publications as your workspace there — same idea.

Step 3 — publish your artifact (do this every time)

With Claude Code open in the folder, paste this:

Please read .claude/skills/uplive-publish/SKILL.md in this repo and follow it exactly to publish the following.

Team: [liveops / ua / creative / or a new team name]
Title: [your title]

Content:
[Attach or paste your finished HTML file. If you don't have a file yet, describe what you want and Claude will draft it.]

Fill in the three bracketed parts:

Team — liveops, ua, or creative. If none fit, type a new name and Claude creates the folder.
Title — your artifact's name. Claude turns it into the URL.
Content — paste text, notes, markdown, or just describe what you want.

Press Enter. Claude writes the page and hands you a link — live in a minute or two.

How it works, if you're curious

The three prompts above are the whole workflow — skip this section if you just want to publish. What's below is a short tour for anyone who'd like to know what's actually happening.

What's behind the three prompts

Login: Claude sets up GitHub auth on your computer. Setup: Claude creates the folder that holds the site. Publish: Claude writes a new page under your team's folder, named from your title — live in a minute or two. No CMS, no approval queue: if your computer has write access to the folder, you can publish.

Updating an existing artifact

Paste the publish prompt again with the same team and title — Claude replaces the page at the same link. Duplicate titles get disambiguated automatically.

What you can put in the Content field

Finished prose, raw notes, a Slack thread, bullets, markdown — any of those works. Don't polish first. To give one artifact a different look, say so in the prompt.

What you don't have to do

Write any HTML. Claude produces the page. You produce the content.
Run a build. Nothing compiles locally. The site rebuilds automatically on every publish.
Edit the homepage. New artifacts appear in the site's search automatically. You never touch the homepage to "add" an artifact.
Ask anyone for approval. If you can paste a prompt into Claude and Claude has folder access, you can publish.
Maintain the search index. It's regenerated automatically on every publish. You never touch it.