Personal portfolio of Pulkit Saraf (@PsudoKit).

npm run dev

Content — blog posts and OSS contributions — is managed via Sanity. The static data in src/data/ is the permanent baseline; Sanity adds new entries on top. Both sources are merged at request time.

1. Fill in .env.local (copy from .env.example, add your project ID + tokens).
2. npm run dev — then visit http://localhost:3000/studio.
3. Log in with GitHub (must be added as a member of the Sanity project at sanity.io/manage).

1. Open Studio (/studio locally or the deployed URL).
2. Click Blog Post → Create.
3. Fill in: Title → hit "Generate" on Slug → Published At → Excerpt (≤200 chars) → Body.
4. Mark Featured if it should appear on the homepage.
5. Publish. The page auto-revalidates within 60 s (or immediately via the webhook).

1. Studio → OSS Contribution → Create.
2. Fill in: Title, Repo (owner/name), Repo URL, PR URL, Status, Category.
3. Set Merged At for correct ordering.
4. Publish.

Hit the revalidate endpoint directly:

curl -X POST https://psudokit.in/api/revalidate \
  -H "sanity-webhook-signature: <sig>" \
  -H "Content-Type: application/json" \
  -d '{"_type":"blog","slug":{"current":"your-slug"}}'

Or just wait — pages revalidate automatically every 60 s.

1. Go to sanity.io/manage → your project → API → Webhooks → Create.
2. URL: https://psudokit.in/api/revalidate
3. Dataset: production
4. Trigger on: Create, Update, Delete
5. Filter (optional): _type in ["blog", "ossContribution"]
6. HTTP method: POST
7. Secret: paste the value of SANITY_REVALIDATE_SECRET from your .env.local
8. Save and enable.

You can test any of these in Sanity Studio's Vision tab.