Core Concepts

A handful of ideas explain almost everything in SpiderPublish. Read this once and the rest of the manual will make sense.

Workspace and project

  • A workspace is your account. It holds your billing, your team, and your API keys. Its identifier starts with cli_.

  • A project is one website inside a workspace. It has its own pages, posts, docs, settings, and domain. Its identifier starts with proj_.

Every workspace has a default project, so if you only run one site you never have to think about this. If you run several sites, each is a separate project under the same workspace.

Content types

SpiderPublish has three kinds of content, each with its own editor and its own URLs:

  • Pages — standalone pages built from visual blocks (hero, features, pricing, and so on). Published to /<slug>.

  • Posts — blog articles with a rich-text body, an author, tags, and categories. Published under /blog.

  • Docs — documentation pages organized into a nested tree of sections. Published under /docs (this manual is docs).

Blocks and components

A page is an ordered list of blocks. Each block is an instance of a component — a reusable, self-contained piece of UI (a hero, a pricing table, an FAQ) with its own styling. You fill in a block's fields; the component renders it. The marketplace ships dozens of ready-made components, and you can create your own.

Themes and templates

  • A theme is a complete set of design templates — the page layout, the header, the footer, the blog and docs layouts — plus your color and font settings. Apply a theme and your whole site takes on its look.

  • A template is one Liquid file inside a theme. Advanced users can override a single template (say, the footer) without rebuilding the whole theme.

Forms and booking

A form is a multi-step, conversational data-collection flow — contact forms, lead-gen quizzes, surveys, intake forms. A booking flow is the same idea wired to a calendar for scheduling. Both render at the canonical URL /f/<flow_id> and can be embedded anywhere.

Deploy

Editing content does not change your live site by itself. Deploying pushes your current content and templates to the edge. Deploys are a safe, two-step preview-then-confirm action and complete in a few seconds. See Deploying Your Site.

Domains

A project is reachable on a free *.sites.spideriq.ai subdomain immediately. Connect a custom domain to serve the site on your own address with automatic HTTPS. See Custom Domains.

Ways to drive it

Everything above is available through four surfaces, all backed by the same API:

  • The dashboard — the visual editor in your browser.

  • The CLI — spideriq commands in your terminal.

  • MCP — tools that let AI agents operate your site.

  • The VS Code extension — pull, edit, and push content from your editor.

Pick whichever fits the moment; they all change the same content.

Next steps