How lander-hatsune/vecnote works
Main Components
a) Frontend Layer:
• Templates (Bulma-based UI)
• Static assets
• Document rendering components (Pandoc integration)
b) Backend Layer (Django):
• Document Management System
• Vector Embedding System
• GTD (Getting Things Done) System
• Search & Filter System
c) Database Layer:
• PostgreSQL with pgvector extension
• Document storage
• Vector embeddings storage
d) External Services:
• ZhipuAI API (for embeddings generation)
• Pandoc (for document conversion)
• [Frontend] → [Backend Services] → [Database & Storage]
• ↕
• [External Services]
Detailed Component Breakdown
Frontend Layer:
• Document views (create, edit, delete, restore)
• Todo management interface
• Search interface
• Document list/detail views
• Pin/Unpin functionality
Backend Services:
• Document Controller
• CRUD operations
• Document parsing (org/latex/typst)
• Vector Embedding Service
• Embedding generation
• Similarity search
• Todo Management Service
• Todo extraction
• Task scheduling
• Date management
• Search Service
• Vector-based search
• Filtering system
Database Layer:
• Document Store
• Vector Embeddings
• Todo Items
• Tags/Categories
Key Interactions to Highlight
• Document Flow:
• [User Input] → [Django View] → [Document Controller] → [Vector Embedding Service] → [Database]
• Search Flow:
• [Search Query] → [Search Service] → [Vector DB Query] → [Results]
• Todo Management Flow:
• [Document] → [Todo Extraction] → [Todo Storage] → [Todo View]
Important Architectural Notes
• Vector embedding pipeline
• Integration points with external services
• Document processing flow
• Demonstrate the GTD system integration
Technical Details
• Django MVT (Model-View-Template) pattern
• PostgreSQL with pgvector extension
• External API integrations
• Document conversion pipeline