Skip to content

weka/weka-dot-io

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

73 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Weka – Sanity Studio + Next.js Frontend

Monorepo with Sanity Studio (content CMS) and Next.js frontend (from next-vercel-shadcn).

Structure

  • studio/ – Sanity Studio (schema, structure, components). Content for weka.io blog and related types.
  • frontend/ – Next.js app (Shadcn, Tailwind). Consumes the same Sanity project/dataset for the blog and optional embedded Studio.

Prerequisites

  • Node.js 20+ (or 22+)
  • Same Sanity project for both apps: ult5g8gw, dataset production (or set in env)

Setup

  1. Install root dependency (for running both apps together):

    npm install
  2. Studio (already has its own node_modules if you moved it; otherwise):

    cd studio && npm install && cd ..
  3. Frontend (already ran once; if needed):

    cd frontend && npm install && cd ..
  4. Environment

    • frontend/.env.local is set with NEXT_PUBLIC_SANITY_PROJECT_ID=ult5g8gw and NEXT_PUBLIC_SANITY_DATASET=production. Adjust if you use another dataset.
    • Optional: SANITY_STUDIO_PREVIEW_URL (e.g. http://localhost:3000) so Studio’s Presentation tool points at your local frontend.

Run

From repo root:

Build

  • npm run build – build frontend only (used by Vercel; avoids building Studio)
  • npm run build:frontend – build Next.js
  • npm run build:studio – build Studio
  • npm run build:all – build both studio and frontend (for local)

Deploy

  • Studio: from studio/, run npm run deploy (or your host’s Sanity deploy).
  • Frontend (Vercel)
    So only the Next.js app is built (Studio is a separate app and not deployed to Vercel):
    1. In the Vercel project: Settings → General → Root Directory → set to frontend and Save.
    2. Redeploy. Vercel will run npm install and npm run build inside frontend/; no Studio build runs.
    3. In Settings → Environment Variables, set NEXT_PUBLIC_SANITY_PROJECT_ID, NEXT_PUBLIC_SANITY_DATASET, and optionally SANITY_API_READ_TOKEN.
  • Frontend (other hosts): build from the frontend/ directory and set the same env vars.

About

This repository contains the source code and configuration for managing and maintaining the Weka website.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors