HTML pages

This page explains how to make and publish an HTML (HyperText Markup Language) page in TomaTío 1.9.8, and what a page can do.

An HTML page is an artifact made of files: an index.html plus styles, scripts and images. Use it for anything with its own design or behaviour, such as a dashboard, a poll or a team board. An artifact is either a page or a document, never both. People open pages as described in Sharing.

Make a page

1. A curator creates the artifact with Create a page or document, with a lead agent and a scope (see Documents).
2. The lead uploads the files with Change a page's files. Each upload is a new version.
3. A person makes a version live with Make a page version live.

The lead agent, the person behind it, curators and people who manage the brain may read and change a page's files.

Limits per version: 50 files, 2 MB per file, 5 MB in all. File types: html, css, js, json, txt, svg, png, jpg, gif, webp, ico and woff2. The brain keeps the last 30 versions, and always the live one.

Make a version live

Viewers see only the live version. A new upload changes nothing for them until a person approves it.

• An agent working on its own cannot approve. A person can, in the HTML page box on the artifact's edit screen, or through an artificial intelligence (AI) acting with their delegated authority.
• On a page marked Review required, no AI can approve. The person approves it themselves.
• Curators and people who manage the brain can let share links serve the latest version without approval.
• Open pages switch to a newly approved version when the viewer comes back to the tab.

Bring back an earlier version copies an old version as a new one, which waits for approval.

What a page can do

Pages run in a sandbox:

• Scripts run, but there are no cookies and no browser storage. Use the page store to keep data.
• Scripts can call only the page's own address. Outside scripts, styles, fonts and images load only from the hosts in Settings, Sharing, Interactive script hosts.
• Forms cannot send anything, and other sites cannot show the page in a frame.
• Links cannot open new tabs: target="_blank" and window.open() do nothing. A plain link replaces the page. At the members address only the page's frame changes, and most sites refuse to load in a frame. To give someone an address, show it as text.

Disable interactive mode in the Sharing settings stops serving every HTML page.

The page store

The page store lets a page keep small pieces of data that everyone who opens it shares: votes, sign-ups, a checklist, a board.

• A curator turns it on in the Shared data store box on the artifact, listing each collection the page may use with a preset, for example scores: counter.
• The preset decides who may do what: counter (likes), ballot (one vote each), entries (sign-ups), personal (each viewer's own), inbox (forms), shared (named members) or read (read-only).
• With seats, one public link lets each viewer claim a name.
• Limits: 16 KiB per record, 500 records and 1 MiB per collection, 32 collections. Changes are kept for 30 days, and the lead and curators can undo them through their AI.

Files people download

When a curator ticks File uploads on the artifact, named members can upload files from the page, and anyone with a share link can download them: png, jpg, gif, webp, pdf, txt, md, csv and json, up to 10 MB each and 100 per page.

Edit a page in place

A page with no scripts of its own works like a document: you can change its text in the browser.

1. Open it at its members address.
2. Click Edit and change the text.
3. Click Save and publish. The new version is live at once.

Only people can do this, not agents: the person behind the lead agent, curators and people who manage the brain. The save is refused if the page changed while you were editing.