Working product · Public release in development

Web StaticOps

The local-first system used to build this site. Web StaticOps combines visual editing with the less glamorous work that makes a site shippable: content and media review, localization, link and SEO checks, immutable build revisions, recovery, deployment evidence, CMS theme export and review-first AI workflows.

Local project 32 workspaces Static public output Versioned builds Review-first automation

The product is substantial and in daily use, but it is not yet distributed as a public release. You can inspect what exists today without being asked to treat a roadmap as finished software.

Inspect current Studio

Web StaticOps today

A working local-first operations system.

The product has moved far beyond its early page-builder prototype. Thirty-two focused workspaces now cover authoring, structured content, media, localization, quality, recovery, release and deployment evidence.

WorkLocal projectReadable content, data, rules and assets
ProveQuality and releaseAudits, acceptance, revisions and deploy evidence
ShipPortable outputStatic files for ordinary hosting without runtime lock-in
Studio cockpit previewStudio cockpit dark mode previewCurrent live UI

Dockable visual workspace

Studio cockpit

Arrange Canvas, Inspector, project status and specialist modules around the job at hand.

Inspect Studio overview

Why it exists

A static site still needs somewhere serious to work.

Static output is wonderfully simple. Keeping the source, media, translations, checks, releases and handoff evidence coherent over time is not. Web StaticOps handles that operational layer without turning the public site into a hosted CMS runtime.

Work locallyThe project remains a readable directory of content, data, rules, media and configuration.
Publish ordinary filesThe public result is HTML, CSS, JavaScript, images, feeds and indexes that can be hosted almost anywhere.
Check before shippingAudits, acceptance, accessibility, performance, links, SEO and deploy evidence are part of the workflow.
Recover without dramaBackups and immutable build revisions make change safer and rollback understandable.

Studio today

One cockpit, not one giant screen.

The dockable Studio presents the work as focused modules. Canvas and Inspector sit beside content, collections, media, localization, quality, release, project control and other specialist workspaces.

Web StaticOps Studio overview in light mode with project status, canvas palette and inspector Web StaticOps Studio overview in dark mode with project status, canvas palette and inspector
The same live workspace in light and dark themes. The screenshot reflects the current product, not the early May prototype previously shown here.

Visual where useful

Canvas, palette, inspector, preview sizes and theme switching shorten the feedback loop for page work.

Source remains real

The editor works with project files and schemas rather than hiding the website inside an opaque remote database.

Dock what the job needs

Modules can be arranged for writing, visual review, quality work or release preparation instead of forcing one layout on every task.

Inspectable gallery

Web StaticOps Studio in the active theme

Open five current Studio workspaces. Every thumbnail and full-size preview follows the site's light or dark theme.

Operational depth

Building the page is only one part of shipping it.

The current Studio has 32 module workspaces covering the full route from project setup to evidence-backed release.

Content and collections

Pages, legal content, documentation, structured data and static collections share one project model.

Responsive media

Registry-backed images, variants, dimensions and optimization keep public output fast and traceable.

Localization

Translation memory, terminology and XLIFF review support multilingual static sites without a public localization service.

Quality and release

Site Health, accessibility, SEO, links, performance budgets, acceptance and deploy audits create evidence before publishing.

Build revisions and recovery

Immutable revisions, backups, integrity checks and restore workflows make the generated output reproducible.

CMS theme export

Static projects can produce inspectable theme artifacts when a delivery target needs them, without changing the source model.

AI and agents

Useful assistance, with a review trail.

Web StaticOps can prepare structured work for local AI and coding agents, but the design does not treat autonomous mutation as magic. Scope, diffs, validation and handoff evidence remain visible.

Rules travel with the project

Generated agent guidance states product boundaries, allowed edit areas, safety rules and required checks.

Review before release

Agent output is still source work. It must pass the same build, audit and visual review as any other change.

No secret public brain

The published site stays static. Private project context and credentials do not become part of public output.

Product boundary

What Web StaticOps deliberately is not.

It is not a public CMS admin panel, application backend, customer database, auth provider, payment processor or excuse to lock a simple website behind a permanent platform fee. Dynamic needs connect to external providers through explicit adapters.

That boundary is a feature: the public site remains portable, cheap to host and easy to inspect.

Common questions

The short version.

Is Web StaticOps available now?

It is a working internal product in active use. A public release is still in development; there is no public download to promise today.

Does the public site need Web StaticOps running?

No. The generated site is static and works independently after deployment.

Can a static site still use forms or embeds?

Yes, through mail links, external endpoints and provider embeds. Web StaticOps does not quietly add a private submissions database.

Is this page built with it?

Yes. This Viken Data refresh is also a migration from an older project surface to the current Web StaticOps pipeline.

Web StaticOps

Interested in the product or a site built with it?

Write directly. We will distinguish what works now from what is still being prepared.

Email Viken Data Studio