How dragonman225/jade works
Project type and purpose
• Jade is a client-side, canvas-based note-taking application shipped as both a web app and an Electron desktop app.
• Core purpose: allow users to create and connect “blocks” of content on a canvas, supporting rich text, embed tools, and conceptual relations.
• Plugin-first architecture: features (tools like text editor, image embed, search) are implemented as self-contained “factories.”
File structure
• Top‐level config: eslint, prettier, tsconfig, Webpack configs for web dev/prod and Electron.
• src/
• factories – Plug-ins (tools) that render various block types (ProseMirror text, Slate text, image, embeds, status bar, etc.) and implement their own styles, hooks, and utilities.
• platforms – Abstractions over persistence and runtime differences: web uses localStorage, Electron uses IPC+SQLite (better-sqlite3). Also startup scripts per platform.
• assets, initial-content, theme, env – static assets and initial data.
• No separate backend server: data is stored in the browser or local SQLite via Electron IPC.
Key points from README
• The app is experimental, focused on UX research around canvas interactions and plugin-first architecture.
• Two targets: web (demo) and Electron (desktop) – both share the same core code.
• Emphasis on exploring canvas APIs, rich text, and extensibility.