Use case · labs.sagozen.digital
The studio is
the use case.
A custom product catalogue on ZeroHostCMS, with native editing tools and an explicit boundary between content and code.
Explore ZeroHostCMSFrom publication to public catalogue.
Publish the brief
The portal’s normal publication workflow writes a business profile and product items to this site’s EmDash database. The active publication pointer chooses the current edition.
Edit in EmDash
CMS editors can change the studio headline, introduction, and catalogue item descriptions. Drafts remain separate from published records.
Render the real records
The custom Astro homepage reads the active English profile and published, visible items belonging to that publication. There is no pretend database or static catalogue fallback.
Labs Theme, with a dedicated deployment.
Labs uses the Labs Theme starter and an explicit, trusted site customization. The saved theme identifier remains tradecraft so existing sites and publication history stay valid. The dedicated layout, product pages, localized legal pages, and design assets are deployed alongside the standard customer runtime.
Product detail and website policy pages are authored code. The homepage leads with ZeroHostCMS, then AvioBrand; published catalogue descriptions and the studio introduction remain CMS content. CMS-created pages and posts continue to use the customer publication lifecycle rather than a second content store.
If no profile has been published, the homepage returns an honest awaiting-publication response. It does not fabricate product cards from local seed data.
Useful native plugin work.
The Labs Catalogue plugin lives in the EmDash admin and product editor. It checks the current, unsaved draft for a name, description, category, publication identifier, display order, and a safe link.
It flags questionable availability and reminds editors to describe commercial status accurately. A successful technical check is not a claim that a product is released or a partner channel is approved.
Read-only by design.
The plugin reads allowlisted editor fields. It does not rewrite entries, publish content, contact third parties, or run affiliate tracking. Editors review findings and use the normal CMS save and publish controls.
The existing ZeroHost AI plugin and forms plugin remain installed. AI suggestions require the existing editor workflow. Partner applications on this site open a real email draft instead of claiming a form submission has reached a tracking platform.
One site’s infrastructure.
- Worker
- Customer runtime, CMS routes, and the inherited publication endpoint.
- D1
- Isolated site content, revisions, configuration, and publication state.
- R2
- The site’s uploaded CMS media, through the standard storage binding.
Isolation describes the deployment boundary. It is not a certification, uptime guarantee, or proof of a security audit.