Skip to content
Vizitka docs

Guides

Ask AI

The prose an agent reads before it writes, by name: what each guide is called and what it is for. Served over MCP as vizitka://docs/guides, and by describe_vocabulary with topic=guides.

  • Build an app: live lists, rows that belong to people, and a chat: A site can be an app: pages that stay up to date while they are open, visitors who sign in with a name, and rows that belong to the people who wrote them.
  • Building a site for this owner: Read this before you build a new site or rebuild most of one: the authoring guides (vzk/authoring and the focused guides it names) make a page valid, and this one makes the site belong to the person whose name is on it.
  • Copying an existing site: Read this when the owner already has a site and asks you to bring it over: match its look, but put its content where the owner can edit it from the dashboard.
  • Agent instructions: This server edits the Vizitka sites owned by the person who authorized the connection.
  • Photographer playbook: What a photographer’s clients look for before they get in touch, which pages carry it, and the worked site to start from; read building first.
  • Plumber playbook: What a plumber’s customers look for before they ring, which pages carry it, and the worked site to start from; read building first.
  • Choose which rows are public: Publication is a table setting, independent of its fields and read access.
  • Writing a site in vzk: Read this guide before the first write: it holds how a site is laid out, the loop to work in, and how to read a refused write.
  • Client scripts and behaviours in vzk: Use this guide when a vzk site needs something to happen in the browser: a menu that opens, a gallery, a tab set.
  • A vzk site in several languages: Use this guide when a vzk site speaks more than one language.
  • Pages, layouts, components and fields in vzk: Use this guide for the structure of a vzk site: what a page, a layout and a component are, the fields an owner edits apart from the markup, links, and pictures.
  • Styling a vzk site: Use this guide when changing how a vzk site looks: the classes its markup wears, the site’s stylesheet and tokens, and a file’s own <style>.
  • Tables, listings, row pages and forms in vzk: Use this guide when a vzk site needs repeated content or visitor submissions: reading a table’s rows in a page, the page each row has, search and a form that saves a row.
  • Scenarios: a site proves what it does: Use this guide to write a site’s scenarios and to play them before a merge.