--- title: "Bisque Types" description: "A Markdown document, an HTML page, or a presentation." canonical: https://bisque.cloud/docs/artifacts/types --- # Types A Markdown document, an HTML page, or a presentation. Page: https://bisque.cloud/docs/artifacts/types An Artifact is a Markdown document, an HTML page, or a presentation. You ask for one by name, or let the agent choose from what you describe. | Type | What it is | Ask for | | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ | | Markdown | A document: a plan, a report, meeting notes. Rendered as a readable page, with comments on the passages people select. | "as a Markdown Artifact" | | HTML | A complete page: a dashboard, a diagram, a form, a tracker. The page runs in a sandbox with no network, and it can remember what people do on it. | "as an HTML Artifact" | | Presentation | A presentation that plays with narration. The [Present](/docs/present) skill makes these. On a Markdown or HTML Artifact you own, **Present this** asks for a presentation made from the page. | "present this" | ## Markdown A Markdown Artifact is a document. Ask for one when the result is something people read top to bottom: a plan, a write-up, a status report, notes from a thread. > Write up the migration plan as a Markdown Artifact. The page is rendered for reading, in light or dark to match the reader's setting. Tables, code blocks, and images get the full width; prose keeps a comfortable measure. People who can open it comment on a selected passage, and the comment stays pinned to that passage. The owner, or anyone added as an editor, can also edit the document in the browser, and a save is a new version at the same link. ## HTML An HTML Artifact is a complete page the agent writes: a dashboard, a chart, a form, a checklist, a poll. Ask for one when the result is something people look at or interact with rather than read. > Make a dashboard page from these numbers as an HTML Artifact. > Make a sign-up sheet for Friday that remembers who signed up. The page runs in a sandbox. Its styles and scripts are inline, images are embedded in the page, and it has no network access, so it cannot call out to other services or load anything from elsewhere. That is what makes it safe to open a page an agent wrote. A page can remember what people do on it. A checklist keeps its ticks, a sign-up sheet keeps the names, a poll keeps the votes, and everyone with the page open sees the change. Who may read and write which part of that data is set when the page is made, so a poll can let each person cast one vote and only the owner see the tally, or a team checklist can let everyone who opens it tick a box. Say what the page should remember and who should see it: > Make a poll on the offsite dates. Everyone on the team votes once; only I see the results. A page that only shows things does not need any of this, and the agent leaves it out. ## Presentation A presentation is a page that plays: slides with narration, watchable in any browser. The [Present](/docs/present) skill makes these from whatever you point it at, and the result is an Artifact like the other two, with the same link, the same sharing, and the same versions. On a Markdown or HTML Artifact you own, **Present this** asks for a presentation made from the page as it is published right now. Who can watch the presentation matches who can open the Artifact, and never reaches further: an Artifact shared with named people or with your organization gets a presentation only you can watch, and an Artifact open to anyone with the link gets one anyone with its link can watch. If who can open the Artifact changes between the ask and the confirmation, you are asked to confirm again. A presentation Artifact cannot itself be presented again.