Sanity CMS development that makes your website easier to update.

Sanity stores content in a dataset inside a Sanity project, apart from the website code. The Studio and its field definitions are code, so they can be kept in Git with the rest of the project; on this site they sit in a studio folder beside the website. We record where the production code, infrastructure, accounts, data, documentation, and operating responsibility live after launch. On the behavioral health network build, each location's Next.js app reads from one Sanity backend, and all infrastructure was handed to client-owned accounts.

We review your existing pages, decide how they should be organized, and plan how to move the text, images, and metadata. We preserve URLs where practical and map redirects where addresses change. Before launch, we check the migrated content, forms, links, and key visitor journeys. Search visibility can fluctuate during a move, so monitoring and a recovery plan are part of the work.

Sanity stores content separately from the website that displays it. We use its API and GROQ queries to retrieve the fields each page needs, then render rich text through Portable Text components. Publishing can trigger a rebuild, refresh cached pages, or supply fresh content on a request. We choose the approach for the project and configure visual preview when it is part of the agreed scope.

In Sanity, an edit stays a draft until someone publishes it. Our website reads published content only, so a visitor never sees a draft. Our own Studio runs two tools: Structure, where editors create and edit records, and Vision, where developers test GROQ queries against the dataset. Blog and case-study pages are generated when the site builds, and a published change appears after the next build. A client project can be set up differently. When a team needs to see drafts inside its own page layout before publishing, we scope visual preview for that website and confirm which content types and layouts it covers.

The ComCreate blog uses Sanity to manage articles, authors, categories, and search descriptions, while each article's cover is drawn by the site's own code from the article's title, categories, and publication order rather than taken from an uploaded image. Our website templates turn those records into the pages you read here. An article's title and cover appear on the blog listing, while its author record supplies the byline and profile link. This site's article pages are generated during a build, so updating a published page includes rebuilding the site.

Each article is one record in our Studio, split into two tabs. Content holds the title, a URL slug the editor can generate from the title, an author chosen from the author records, categories, a publication date, a short excerpt, and the body. SEO & keywords holds an optional search title of up to 60 characters, a meta description of up to 160, target keywords, and optional questions with answers. An empty search title falls back to the article title plus the blog name, and an empty description falls back to the excerpt. Keywords go into the article's BlogPosting structured data. Answers appear under Frequently asked questions on the article and are published as FAQPage structured data. Articles that share a category fill the Read next list, up to three, newest first. Each author with a published article gets a profile page that lists their articles.

Images placed inside an article carry four extra fields: an image description for screen readers, a visible caption, a source URL, and a screenshot capture date. The Studio asks editors to describe the information a reader needs from the image and to leave out keywords and the article title. When an image has no description, the Studio shows a warning unless the editor marks the image decorative. A warning does not block publishing, so older articles stay editable while their images are filled in. Under each image, the page shows the caption, a View source link, and the capture date when those fields are set. Sanity's image service supplies each image in several widths, and the browser picks the one that fits the screen.

The case studies on this site are also Sanity records. Their fields are grouped into Identity, Hero, Editorial, Metrics, and Brand & SEO. The editorial body is a list of sections the editor can reorder. Each section has a label, an optional subhead, body copy, and an optional screenshot with alt text, shown bare or inside a browser or phone frame at a chosen aspect ratio. Metrics holds the stat rows, before-and-after tables, charts, testimonials, and press mentions. Brand colours are stored as plain CSS values and set the page's accent and the colour zones it moves through as you scroll.

A local business that wants a new website with published package pricing can start with small business web design.