--- name: web-dashboard description: Every action available in the browser dashboard. --- # Web dashboard The web dashboard at is the primary surface for non-CLI users. It lists every share you own, lets you publish new shares, and exposes a per-share actions menu for the post-publish edits the CLI also supports. ## The `/new` page Click **New share** from the dashboard, or navigate directly to . ### Input modes The form has two ways to provide content: - **Paste** — paste content into the textarea. The **Filename** field above it sets the filename, which drives content-type detection (`.md` → markdown, `.csv` → table, etc.). If you leave the filename empty, the server stores the share as markdown by default. - **Upload** — pick a file from disk. The browser sends both the file's bytes and its original filename. The filename field is ignored when an upload is present. You only fill in one — paste content OR upload a file, not both. ### Form fields - **Filename** — optional. Used for content-type detection when pasting. Has no effect when uploading. - **Content** — the paste textarea, or the file picker. - **Render as** — overrides the detected content type. Choose `Auto-detect from filename (default)` to leave it to the filename, or pick one of `markdown`, `code`, `json`, `yaml`, `csv`, `tsv`, `html`. - **Visibility** — `Secret` (default) makes the share unlisted and marked `noindex`. `Public` makes it indexable and listed on your public profile. - **Password** — optional. Only valid when visibility is `Secret`. Visitors must enter the password before the share renders. - **Slug** — optional. If set, the share lives at `//`. If empty, the server mints a random 8-character base36 id. Must match `^[a-z0-9](?:[a-z0-9-]{0,58}[a-z0-9])?$` — see [slug rules](/docs/slug-rules). Submit, and you land on a confirmation view with the canonical URL and a copy button. ## The `/dashboard` page The dashboard lists every share you own, most-recently-updated first. Each row has the title, slug, last-updated timestamp, recent activity, visibility badge, a primary **Copy URL** button, and an **Actions menu** (`⋯`). ### Actions menu Every row's `⋯` menu has the same items: - **Open in new tab** — opens the share's public URL. - **View analytics** — opens the analytics page for this share. Owner-only. - **Make public / Make unlisted** — toggles visibility between `public` and `unlisted`. Switching from password-protected to public clears the password (the form asks for confirmation first). To set a share to `members` visibility, use the CLI (`anchorify visibility members`) or the API — a three-tier dashboard control is not yet wired up. - **Set password / Change password** — opens an inline form. Submit with the password field empty to clear an existing password. Only valid on `unlisted` shares (passwords are mutually exclusive with `public` and `members`). - **Render as…** — opens an inline dropdown of the seven content types. Picks a new render type without touching the content. Useful for fixing paste-flow shares that got bucketed as markdown by default. - **Rename** — coming via CLI/API; the dashboard form for this lives on the row's edit page. - **Delete** — soft-deletes the share. The URL returns `410 Gone` immediately. Hard-deletion runs on a rolling 30-day cycle. The primary **Copy URL** button writes the share URL to the clipboard without opening the menu. ### Tokens panel The dashboard has a **CLI tokens** panel below the shares table. Use it to create tokens for `anchorify login` (see [CLI tokens](/docs/tokens)). ### Sign out The top-right menu has **Sign out**, which clears the session cookie and sends you back to the landing page. The CLI tokens are unaffected — sign-out is a browser-only action. ## Fixing a share's render type after publish If you publish a share with the wrong content type (the most common case is pasting JSON into the textarea without a filename, which buckets the share as markdown), open the dashboard, open the actions menu on the share's row, choose **Render as…**, pick the right type, and submit. The content stays the same; only the renderer changes. The same operation is available from the CLI as `anchorify type ` and via the API. ## Next steps - [Command-line](/docs/cli) — the same actions from the terminal. - [Visibility and passwords](/docs/visibility) — the visibility model in detail. - [Content types and rendering](/docs/content-types) — every renderer. - [Analytics](/docs/analytics) — what you see on a share's analytics page.