Effibotics
The alt text
All articles
n8nAutomations

Our first article

6 min read

This is iour excerpt

This is our content and all the items we need to have and the full article

Configure SanityHow then will the published article onm the local version go to the online version? 3:41 PM

In Sanity, the content does not live inside your local Studio. The local Studio is just the editor UI.

When you create or publish a Post locally at:

http://localhost:3333

…it saves directly to the Sanity cloud project:

  • Project ID: zwnb228p
  • Dataset: production

So the flow is:

  1. You run the Studio locally with npm run dev.
  2. You create or edit a Post.
  3. You click Publish.
  4. Sanity saves that document to the online production dataset.
  5. Any deployed/online Studio or website connected to zwnb228p / production sees the same published content.

The only thing you deploy with:

npm run deploy

is the Studio app itself, meaning the editor interface. Your articles are already online once published, because they are stored in Sanity’s cloud dataset.

Web previewWebsiteOpen in3:41 PM Deploying to sanity.studio Success! Studio deployed to https://effibotics.sanity.studio/ Add appId: 'o3wjn84svzupsw856c6u7802' to the deployment section in sanity.cli.js or sanity.cli.ts to avoid prompting for application id on next deploy. Example: export default defineCliConfig({ //… deployment: { appId: 'o3wjn84svzupsw856c6u7802', }, //… }) zachariakimotho@192 ef 3:43 PMWorked for 15s

Added the deployed Studio appId to sanity.cli.ts, inside the existing deployment section:

appId: 'o3wjn84svzupsw856c6u7802'

Verified with npm run check: lint, format, TypeScript, and Sanity build all pass. The old “No appId configured” warning is gone now.

Edited sanity.cli.ts+1-0UndoReviewDetails3:43 PMHow does this now conenct to our application on https://github.com/Imperol3/operational-flow/tree/claude/intelligent-babbage-Q0Mp8 so it gets the articles and posts from this? 2. Will this sanity be running on my lcoal pc? 3:45 PMWorked for 3m 6s

Yes, that app is already mostly wired for Sanity.

I inspected the GitHub branch you linked. It already has:

  • @sanity/client
  • @sanity/image-url
  • blog routes at /blog and /blog/$slug
  • a Sanity client in src/lib/sanity.ts
  • .env.example with:SANITY_PROJECT_ID= SANITY_DATASET=production

To connect it to the Studio you just deployed, set the app’s environment variables to:

SANITY_PROJECT_ID=zwnb228p SANITY_DATASET=production

Then the app will query Sanity’s cloud Content Lake for documents where _type == "post". When you publish a post in https://effibotics.sanity.studio/, the app’s /blog page can fetch it from the same production dataset.

One important mismatch: the application expects fields like excerpt, coverImage, tags, and seo, but the simple postType.ts we just added only has title, slug, publishedAt, image, and body. So articles may load partially, or cards may look empty, until we either expand your Studio schema to match the app’s richer schema or simplify the app’s queries/components. Best path: update the Studio schema to match the app’s existing sanity/schemas/post.ts.

For your second question: no, Sanity does not need to run on your local PC for the online app to show articles.

There are three separate things:

  • Local Studio: http://localhost:3333, only for editing from your machine.
  • Deployed Studio: https://effibotics.sanity.studio/, online editor.
  • Sanity Content Lake: the cloud database where published posts actually live.

Your live application talks to the cloud Content Lake, not your local PC. Your local Studio is optional once the deployed Studio exists.

Sources: inspected your GitHub branch files and Sanity’s official client docs: @sanity/client setup, Sanity CDN config.

Web previewWebsiteOpen in3:48 PMhttps://operationsystems.lovable.app/blog This the page we have with the new article we just created We need to make sure the content types are working for an actual CMS where we have the tags, titlem SEO, items and all. Also the featured image and such 3:52 PMWorked for 4m 11s

Done. I upgraded the Sanity Post content type into a real CMS schema and deployed it to:

https://effibotics.sanity.studio/

Updated postType.ts now supports:

  • title
  • slug
  • excerpt
  • coverImage with required alt text
  • publishedAt
  • tags
  • rich body
  • inline images
  • video embeds
  • callouts
  • seo.title
  • seo.description
  • seo.ogImage

I also tightened validation so future posts require the important website fields: excerpt, featured image, alt text, tags, and body.

Verified:

  • npm run check passes
  • Studio redeployed successfully
  • Sanity deployed 1/1 schemas

Important: the article currently showing on https://operationsystems.lovable.app/blog was created with the old schema. I checked the dataset and it has image, but the website expects coverImage; it also has excerpt, tags, and seo as empty. Open that post in Sanity Studio, fill the new fields, set the featured image under Cover image, then publish again. The blog card should then show properly.

Edited postType.ts+179-5UndoReviewDetails3:58 PM


Custom5.5MediumOutputslocalhost:3333README.mdSourcesGitHubWeb search

Back to all articles