Developers

How a Quorum site is built and handed over

This page covers two things. We explain how a client site is handed over, and we publish one API you can call. That API is for demonstration. A public API for real work is not listed here yet.

How a client site is built

It’s yours, and any web designer can take it on.

The code is in a repo

The site lives in a repository the client can open. It is not locked inside a website builder. Another designer can clone it and carry on.

Publishing a change

An automated deploy publishes a change without uploading files by hand. That is how the site stays easy to update after handover.

The shape of the build

Most sites are plain pages: HTML, CSS, and a little JavaScript. If a job needs a login or stored client details, the backend architecture is only what that job needs. Not a stack for the sake of it.

Where it runs

Foundational hosting is aimed at a free tier, so there is no monthly website bill. Expert and Expert Pro can use Cloudflare, Google Cloud, Azure, or AWS when the job needs that platform. Those names are tools, not partners.

  • GitHub

    The repo, and a way to publish a change.

  • Cloudflare

    Used when the job needs that edge. Not the free-tier host that comes with Foundational.

  • Google Cloud

    Expert or Expert Pro, when a job needs that cloud.

  • Microsoft Azure

    Expert or Expert Pro, when a job needs that cloud.

  • Amazon Web Services

    Expert or Expert Pro, when a job needs that cloud.

  • Domain registries

    Registrars and DNS. The domain is registered in the client’s name.

  • HTML, CSS, and JavaScript

    The languages the sites are built in.

One demonstration API

The card is the whole list. It is an echo we run, so you can see a JSON response. It is not a row of APIs we have not built.

  • for demonstration

    Echo

    A read-only route on this site. Send a short message and we send it back as JSON. Nothing is stored. It does not use a client login, and it does not call the account API.

    Rate limit: 30 calls from one network each minute. Past that, the response is 429 and Retry-After says how many seconds to wait. The limit lives in memory on one Worker isolate, so it is a guard for this demo, not a shared quota.

    Minimal spec

    GET /api/demo/echo?message=hello
    
    200 application/json
    {
      "ok": true,
      "demo": true,
      "purpose": "demonstration",
      "echo": "hello",
      "rateLimit": { "limit": 30, "windowSeconds": 60 }
    }

    Read the OpenAPI spec

    Calling the demo shows the JSON response. A message longer than 120 characters is cut to 120. An empty message comes back as hello.

What this page is for

The first section is the handover: the repo, how a change is published, and the domain in the client’s name. The API section is one demonstration echo, with the spec on the card.

Signing in on this website is for a client account. That login is not the demonstration API, and a public API for real work is not documented here yet.

Advice on microservices, APIs, gateways and cloud is on the architecture page. That is separate from a public API.

Register interest

Want an API for real work, past this echo? Use the same enquiry form as the rest of the site. The topic is filled in as API. We reply by email. It does not create an account, and it is not a mailing list.