Sonta as Your Site Backend
Connect the site you already have: read your catalog and write leads, orders, and bookings into the same records.
- GuideUsing Sonta as your site's backendSonta is the backend for a site you already have — not a site builder or host. You connect your site, grant it access to specific collections, and it reads your catalog to show it and writes leads, orders, and bookings back into the same records your team works. One model, two audiences: your team inside, your visitors outside.
- ArticleHow collections power a siteYour site sees your collections through a permission grid you control: for each collection you decide whether the site may read, write, or delete. Nothing is granted by default. Beyond that, an entry's published status decides what is publicly visible — so the grid says which collections, and status says which entries.
- ArticleSEO fields and metadataSonta gives every entry a URL-safe identifier, and everything else about SEO is fields you add yourself — a search title, a description, a social image — which your site reads and puts in the page's metadata. There is no hidden SEO feature: model the fields, and let the site use them.
- ArticleModeling compatibility between products and equipmentTo model which products fit which equipment, keep products and equipment as two collections and connect them. A multi-reference on the product is enough when a fit is a plain yes or no; when a fit carries facts of its own, such as axle position or whether it is the factory size, give each fit its own entry in a compatibility collection that references both sides.
- ArticleReviews and rating rollups on a productKeep reviews in their own collection, each referencing the product it is about, with a number field for the rating. Add rollups to the product that count its reviews and average their ratings, filtered to published reviews, so the product always shows current numbers and an unapproved review never moves them.
- ArticleCapture leads and orders from your websiteTo capture leads, orders, or bookings from your website, give the site permission to create entries in that collection. A form submission then becomes an entry the moment it is sent, goes through the same checks as one created by hand, arrives without an owner, and can start an automation, which by default listens to exactly this source.
- ArticleRebuild your site when entries changeTo rebuild your site when content changes, create an automation that runs when an entry is published, unpublished, or edited, and give it a webhook step that calls your site's rebuild address. To avoid a rebuild for every single edit, have the trigger collect changes into one run every 15, 30, 60, or 240 minutes, or once a day.