Pages

A page is a folder. Quickish gives it a live URL and serves every file inside.

On a personal account your home page is <you>.quickish.site/, with optional sub-pages at /name/. Publish a sub-page by naming it: quickish ./site deck serves at /deck/.

Your URL on a work account

On a workspace (Google Workspace) account, you publish to your own page under the company space, keyed by your email handle:

jane@acme.com  →  acme.quickish.space/jane/

A plain quickish with no page name lands there, so you never overwrite a teammate. Add sub-pages under your handle by naming them.

The bare company root <company>.quickish.space/ is the company homepage. It is reserved for the workspace admin (whoever verified the domain) on the Workspace Unlimited plan; until it is claimed, members see a placeholder there.

Folders & index.html

Drop a whole folder and links between files in it just work, relative paths and all. Keep an index.html at the root so the page has a homepage. If there isn't one, Quickish picks your most recently edited HTML file as the homepage and tells you which.

Documents render automatically

Publish a single document with no page of its own — a lone PDF, Markdown, text, CSV, or image — and Quickish builds a clean, in-browser viewer for it instead of handing over a bare file. A Download button for the original is always one click away.

File	You get
`.pdf`	A paged PDF reader (rendered to canvas, so nothing in the file can run).
`.md` `.markdown`	The Markdown rendered as a styled article (sanitized — no embedded scripts).
`.csv` `.tsv`	A sortable table.
`.txt` `.log`	A clean monospace reading view.
images	A centered, full-bleed viewer.

$ quickish ./resume.pdf     # a single PDF → a real PDF reader at your URL
$ quickish ./notes.md       # Markdown → a styled, readable page

It only kicks in when the document is the whole publish (no index.html). The viewer inherits the page's visibility like anything else, so a private PDF stays private — the reader and the file are both behind your sharing settings. Each viewer loads only what it needs, served first-party (no third-party CDN).

How many render

On the free plan, one HTML file per site renders (its index.html); CSS, JS, and images always load, so single-page sites work perfectly. Paid plans render every HTML page in the folder, so multi-page sites navigate freely.

Across sites, free keeps your latest published page live; the rest stay saved and come back the moment you upgrade. Paid serves them all at once.