How inkandswitch/potluck works
Project type and purpose
• This is a front-end-only, single-page application research prototype (“Potluck”) built with React, TypeScript, Vite, and Tailwind CSS.
• Its goal is to let users turn plain text documents into “live” interactive tools: run searches over text, author formulas, and display dynamic annotations in the document.
File structure
• Top-level:
• index.html: main app shell
• embedded.html/embedded-test.html: stripped-down shells for embedding the editor in other pages
• package.json, tsconfig.json, vite.config.ts, tailwind.config.js: toolchain / build config
• src/: all source code—React components, utility modules, data, assets, and a small “refactor” script folder.
• src/main.tsx: app entry point
• src/App.tsx + components (Editor.tsx, DocumentSidebar.tsx, HighlightHoverCard.tsx, etc.) form the UI layer
• src/compute.ts, src/formulas.tsx, src/highlight.ts, src/markdown.ts, src/patterns.ts: core logic for query, computation, and text processing
• src/persistence.tsx: layer handling document state saving/loading
• src/data + sample-data/: static JSON, CSV, and text fixtures for demos
• No backend folder: it’s a static web app, everything runs in the browser.
README for additional insights
• Emphasizes “gradual enrichment from docs to apps”
• Features: live searches, formulas, dynamic annotations
• Research prototype, not a production service
Detail
• Sequence: user event → UI component → computation → UI update → persistence