האתר שלךהאתרשלךבאמת שלך.באמתשלך.

In my existing Next.js project, set up Sanity:
1. Install next-sanity, @sanity/vision and sanity.
2. Run: npx sanity@latest init --env — create a new Sanity project,
   and save the resulting projectId and dataset in .env.local as
   NEXT_PUBLIC_SANITY_PROJECT_ID and NEXT_PUBLIC_SANITY_DATASET.
Do not create any schema yet — that is the next step.

Create sanity/env.ts that centralizes the Sanity env vars:
- Export apiVersion (default "2024-10-01"), dataset and projectId
  from NEXT_PUBLIC_SANITY_API_VERSION / _DATASET / _PROJECT_ID.
- dataset and projectId are required: write an assertValue helper
  that throws a clear "Missing env: ..." error when one is missing.

Create a Sanity schema for a product in sanity/schemaTypes/product.ts
(defineType, name "product", Hebrew title "מוצר") with these fields:
1. title — string, title "שם המוצר", required with a Hebrew error.
2. description — text, title "תיאור", 4 rows.
3. price — number, title "מחיר (בשקלים)", minimum 0.
4. status — string radio: available ("זמין") / sold ("נמכר") /
   archived ("בארכיון"). Default available, required.
5. img — image with hotspot, title "תמונה ראשית", required.
6. slug — required, sourced from title. Important: titles are in
   Hebrew, so write a slugify that outputs lowercase Latin letters,
   digits and hyphens only, with a "product-" + timestamp fallback
   when nothing remains.
All field titles must be in Hebrew — they become the editing form
in the Studio.

Wire Sanity Studio into the site, three files:
1. sanity.config.ts — defineConfig with basePath "/studio",
   structureTool (using the structure below), visionTool, and the
   product schema.
2. sanity/structure.ts — a content list with three folders filtered
   by status: "זמינים" (available) / "נמכרו" (sold) /
   "בארכיון" (archived).
3. sanity/actions/productActions.ts — a document action labeled
   "סמן כנמכר" (tone: caution) that only appears on products not yet
   sold: on click it sets status to "sold", publishes, and completes.
   Register it in the config for product documents only.

Build the content-fetching layer from Sanity:
1. sanity/lib/client.ts — createClient with useCdn: true and
   perspective: "published", so only published content reaches
   the site.
2. sanity/lib/queries.ts — two GROQ queries with defineQuery:
   all products that are not archived (newest first), and a single
   product by slug. Also project "imageUrl": img.asset->url.
3. sanity/lib/fetch.ts — getAllProducts() and getProductBySlug(slug)
   using next: { revalidate: 60, tags: ["product"] } so every publish
   reaches the site within a minute (ISR).

Connect the content to the pages:
1. app/products/page.tsx — a Server Component with revalidate = 60
   that calls getAllProducts() and renders the products; a sold
   product shows a "נמכר" label instead of its price.
2. app/studio/[[...tool]]/page.tsx — mount the Studio with NextStudio
   from next-sanity/studio, with dynamic = "force-static".

Prepare the project for production on Vercel:
1. Make sure NEXT_PUBLIC_SANITY_PROJECT_ID and
   NEXT_PUBLIC_SANITY_DATASET are set in Vercel (Production +
   Preview).
2. Push to git and let Vercel build.
3. Add the site domain to the CORS origins in the Sanity project
   settings (otherwise the Studio will not load in production).
4. Verify that /studio loads and that publishing a product shows up
   on the site within a minute.