Sites
1001 - Your first site
Ask the agent for a website and it publishes one: a site with a private working copy called dev, an address of its own, and a first release you open in a browser after signing in. What a site is, what a release holds, who may create one, and why nothing the agent publishes is public until a person decides it is.
1002 - Dev, promote, roll back
Agents change dev and nothing else. People promote the exact release they reviewed, one environment at a time, to the environments other people use, and roll back by pointing an environment at a release it served before. A release is an immutable set of files, so a promotion copies nothing, rebuilds nothing, and takes effect at once.
1003 - Private environments, public domains
Who opens an environment is decided per environment and who reaches an address per address, so one site is a working copy, a client review room, an intranet and a public website at the same time. Sharing with people and personas, opening an environment to everyone internal, the sign-in every pages address asks for, and the owner’s decision that makes a domain public.
1004 - Your own domain
Every environment has an address from the moment it exists, and every one of them asks for a sign-in. A domain you add in the portal puts your own name on an environment, private until the owner makes it public. The main address, the per-environment addresses, adding a domain, making it public, and the names a site cannot take.
1005 - Layouts and records
A site with a layouts folder is rendered when it is published. The agent keeps content as records, one file per store, product or post, and the platform generates the pages, the paged lists and the category indexes from them. Layouts, includes, front matter, for_each and per_page, and why a render is a function of the source and nothing else.
1006 - Editing a live site
To change a site, ask. The agent reads the site’s files in place, patches the one that needs to change, and the patch becomes a new release in dev with a number, a note and a diff. Outline, locate, patch, dry run and overlay, the check that refuses an edit made against a release that has moved, and the promotion that takes several edits live in one step.
1007 - Capstone: moving an existing site onto Plexara
A crawl copies a site you already run into a release in dev: every page at the address it answered at, every redirect as a rule, the stylesheets, scripts, images and fonts each page loads, and its forms replaced by Plexara forms. A larger site moves from its source, with its images in a media folder. The series assembled end to end: copy, review, share, promote, put the domain on it and make it public, and release it with the application behind it.
900 · Applications
Whole systems your agent builds: a database of its own, the automations and pages that do the work, and releases an administrator makes and can roll back.
Up nextInsights
Editorial pieces on architecture decisions, comparisons against the alternatives, and where this market is going. Read in any order.







