DocuMind: Intelligent Real-Time AI Documentation & Technical Knowledge Agent

Problem Statement

In modern engineering teams, documentation fragmentation is a chronic drain on developer velocity. Architectural decisions, API schemas, installation walkthroughs, and troubleshooting guides end up scattered across static Markdown files, external developer blogging platforms (like DEV.to), and disconnected internal wikis. When developers encounter roadblocks, they waste hours manually hunting through multiple articles or asking generic AI models that frequently hallucinate out-of-date answers.

Solution Overview

DocuMind solves this by unifying static technical publications into a dynamic, conversational AI documentation partner. Powered by Next.js 15, Sanity CMS Content Lake, and Google Gemini AI, DocuMind allows engineers to query complex architectures, code implementations, and technical topics using natural language.

Key Features

• Grounded AI Reasoning (RAG Without Hallucinations): Instead of relying on general model weights, DocuMind retrieves exact Portable Text blocks from Sanity via structured GROQ queries. Google Gemini is constrained to answer strictly using the retrieved documents.
• Verifiable Source Attribution: Every response includes clickable Source Cards linking directly to the full Sanity-backed article reader, allowing users to cross-check claims with the original text.
• Automated DEV.to Synchronization: DocuMind isn't a one-off import. It includes:
  • Real-time Webhook Receiver: Ingests newly published DEV.to Markdown and converts it into structured Sanity Portable Text blocks automatically.
  • On-Demand Sync Button: Triggers real-time content reconciliation directly from the UI.
  • Automated GitHub Action: Scheduled background synchronization running every 6 hours.
• Interactive Documentation Browser: A dedicated /browse portal allowing developers to explore articles by tags and categories with full syntax highlighting.
• Modern Glassmorphic UI: Built with dark-mode aesthetic design tokens, smooth micro-interactions, and streaming responses for sub-second perceived latency.

Demo & Access

• Live Web App: https://documind.inusha.me
• Live Sanity Studio: https://documind.inusha.me/studio
• GitHub Repository: https://github.com/inusha-thathsara/documind
• Sanity Public Query: https://j5tvnuy8.api.sanity.io/v2024-01-01/data/query/production?query=*[_type=="doc"]

Architecture

┌─────────────────────────┐
│   User Interface        │
│   (Next.js 15 App Router)│
└───────────┬─────────────┘
            │
            ▼
┌─────────────────────────┐
│  Natural Query          │
│  Streaming Response     │
└───────────┬─────────────┘
            │
            ▼
┌─────────────────────────┐
│  GROQ Context Query     │
│  Grounded Context       │
└───────────┬─────────────┘
            │
            ▼
┌─────────────────────────┐
│   Sanity CMS            │
│   (Content Lake)        │
│   (Google Gemini)       │
└─────────────────────────┘

Implementation Details

Structured Content Modeling (Sanity Studio v3)

A specialized document schema was designed in Sanity Studio (studio/schemas/doc.js) with the following fields:

export default {
  name: 'doc',
  title: 'Documentation Article',
  type: 'document',
  fields: [
    {
      name: 'title',
      title: 'Title',
      type: 'string',
      validation: (Rule) => Rule.required()
    },
    {
      name: 'slug',
      title: 'Slug',
      type: 'slug',
      options: { source: 'title', maxLength: 96 }
    },
    {
      name: 'category',
      title: 'Category',
      type: 'string',
      options: {
        list: [
          'Architecture',
          'Guides',
          'DevOps & Cloud',
          'Web3 & Blockchain',
          'AI & Machine Learning'
        ]
      }
    },
    {
      name: 'description',
      title: 'Description / Summary',
      type: 'text',
      rows: 3
    },
    {
      name: 'tags',
      title: 'Tags',
      type: 'array',
      of: [{ type: 'string' }]
    },
    {
      name: 'body',
      title: 'Body Content',
      type: 'array',
      of: [
        { type: 'block' },
        { type: 'code' }
      ]
    },
    {
      name: 'publishedAt',
      title: 'Published At',
      type: 'datetime'
    }
  ],
}

Populating with Real, High-Value Content

For Path 1, authentic data is essential. The author pointed DocuMind at 25 real technical engineering articles from their published library on DEV.to (@inushathathsara), spanning:

• Large-scale Cloud & GKE infrastructure
• Next.js 15 & React Server Components
• Web3 architectural paradigms
• ML model optimization & data pipelines

A custom Markdown-to-PortableText engine (web/scripts/import-devto.mjs) was written to parse markdown headings, paragraphs, lists, links, and code blocks into valid Sanity Portable Text blocks with syntax attributes.

Grounded Retrieval via GROQ

When a user submits a query in the chat interface, the server performs these steps:

1. Extracts high-signal semantic tokens from the user's prompt.

2. Executes a GROQ query against the Sanity Content Lake:

   *[_type == "doc" && (
     title match $keyword ||
     description match $keyword ||
     tags[] match $keyword
   )][0...4]{
     _id,
     title,
     "slug": slug.current,
     category,
     description,
     tags,
     "plainText": pt::text(body)
   }
   

3. Passes the retrieved plain-text context to Google Gemini with a strict grounding prompt instructing the model to act as a technical documentation partner and only formulate answers based on the provided Sanity articles. If a concept is not present in the Knowledge Base, the model explicitly acknowledges that the docs do not contain this information rather than hallucinating.

4. Returns the response streamed back with structured citation cards containing the document's title, category, and slug.

Codebase Structure

The entire codebase is open-source and structured as a monorepo containing both the Next.js 15 frontend application and the Sanity Studio v3 workspace:

• GitHub Repository: https://github.com/inusha-thathsara/documind

Author & Acknowledgements

Built by Malawige Inusha Thathsara Gunasekara

• DEV.to Profile: @inushathathsara
• GitHub: @inusha-thathsara
• LinkedIn: inusha-gunasekara

Special thanks to the DEV.to and Sanity.io teams for hosting this challenge.