# Pages

> Publish the interactive pages your agent builds to pages.flisk.si/@you/name. Free and public, no keys, no database: every space is a git branch.

## Pages

- [About and FAQ](https://pages.flisk.si/about): how publishing works and what a space may contain
- [All spaces as JSON](https://pages.flisk.si/spaces.json): every space with its title, publisher and source
- [Oleksandr Dykyi: developer portfolio](https://pages.flisk.si/@odykyi/portfolio/): by @odykyi: Oleksandr Dykyi, Founding Engineer: 87 dev tools rated, with the skill shape, best-fit roles and every tool on the radar and compass.
- [Adoption Radar | DevEx Roadmap](https://pages.flisk.si/@odykyi/devex-radar/): by @odykyi: Adopt means use it. Trial means try it. Assess means watch it. Hold means avoid for now. Each tool links the proof.
- [Oleksandr Dykyi](https://pages.flisk.si/@anon/2uzc3bwnuf/): by @anon: Founding Engineer · 56% match
First engineer at a startup. Does a bit of everything, picks the stack.
Also fits: Forward Deployed Engineer (55%), Staff Engineer (54%), Platform Engineer (53%)
Skill…
- [How GPUs work](https://pages.flisk.si/@odykyi/how-gpus-work/): by @odykyi: Why a GPU with thousands of slow cores beats a CPU with a few fast ones on graphics and AI: an interactive explainer you can play with.
- [Ship a launch in a week](https://pages.flisk.si/@odykyi/ship-in-a-week/): by @odykyi: How we planned Pages for Product Hunt: score the ideas, cut the scope, ship the smallest thing that is real.

## FAQ

- How do I publish a page? Add the plugin to Claude Code (claude plugin marketplace add flisk-sh/pages, then claude plugin install pages@flisk-pages) and ask your agent to publish a folder. Without an agent: clone github.com/flisk-sh/pages and run node bin/pages.mjs publish ./folder --slug name. Both need the GitHub CLI signed in.
- What happens when I publish? Your folder goes into a pull request from your fork. A check reads every file; when it passes, the space is committed to its own branch, space/<you>/<name>, and goes live at pages.flisk.si/@you/name within a minute or two. The pull request is closed with the link.
- What can a space contain? An index.html with its scripts, styles, data and images, or an index.md that is rendered like a GitHub README. Up to 300 files and 10 MB. Scripts may come from the space itself or from cdnjs, jsDelivr, unpkg, esm.sh and Tailwind's CDN.
- Is a space private? No. Every space is public, and so is its source on GitHub. Do not publish anything you would not post in a public repository.
- Where are the versions? Each publish is a commit on the space's branch, so its history on GitHub is the list of versions. Publishing the same name again adds a version.
- Are there comments? Pages runs no comment service and holds no keys. Add giscus to your page with your own repository and settings; giscus.app is allowed.
- How do I take a space down? Open an issue titled 'Remove @you/name' with the Remove template; it is removed at once when you are the publisher. To report someone else's page, use the Report link on it.
- What is not allowed? Password fields, forms that send to other sites, scripts or frames from unlisted hosts, fetches to unlisted hosts, wallet prompts, miners and redirects away. Every page also carries a Content-Security-Policy that blocks them in the browser.

## Optional

- [Source](https://github.com/flisk-sh/pages)