How maxepunk/alntool works
Project type and purpose
• This is a full-stack web application (“StoryForge”) that reads narrative data from Notion, exposes it via a Node/Express backend API, and visualizes it in a React frontend.
• The sample data under SampleNotionData (characters, elements, puzzles, timelines CSV/MD files) confirm that the system’s domain is “story world-building” based on Notion databases.
File structure
• Top-level
• package.json + node_modules – possibly a root workspace orchestrator or placeholder.
• SampleNotionData/… – local CSV/MD exports for development or testing.
• storyforge/ – contains the actual monorepo.
• storyforge/backend
• .env / .env.example / .env.test – environment variables for Notion API credentials, test database or mocks.
• src/controllers/notionController.js – HTTP handlers.
• src/services/notionService.js – Notion API client logic.
• src/utils/notionPropertyMapper.js – maps Notion’s property schemas to the app’s domain model.
• src/routes/notion.js – routes for characters, elements, puzzles, timelines.
• tests/… – Jest unit, integration, and utils tests with coverage artifacts.
• storyforge/frontend
• index.html + dist/… – compiled React app assets.
• src (inferred) – though not shown, tests indicate pure functions, hooks, and components are under test.
• babel.config.cjs, jest.config.cjs – transpilation and test setup.
README for additional insights
• The provided README focuses on frontend testing configuration: colocated tests, transforming ES modules, testing hooks/components, running npm test.
Final recommendations
• Be very detailed: show the controller→service→utils chain within the backend.
• Both development and production modes (i.e., sample data vs. real Notion).
• Do not over-compartmentalize; separate into these logical components and highlight their interactions.