How readr-media/sachiel works
Main components
• Monorepo Root: Represent core configuration files (.dockerignore, Dockerfile, lerna.json, package.json) and tools that govern the entire repo (husky, yarn workspaces, lerna).
• Shared configurations and utilities: Show common pieces—like ESLint configuration files, tailwind.config.js, and global styles—that are referenced across multiple packages.
• Infrastructure & Integration Tools: Include husky (for commit hooks), lerna (for package management), and yarn workspaces (for dependency resolution).
Directory structure for architectural patterns
• Each sub-package (for example, packages/mesh) has a highly granular directory structure, splitting features by pages, components, hooks, contexts, utilities, GraphQL queries/mutations, and shared assets.
• Multiple “api”, “graphql”, “components”, and “pages” directories indicate that each project is a full-fledged Next.js application with its own routing, data fetching (via GraphQL and Apollo), and UI components.
• The numerous nested folders for variations (e.g., different mobile, tablet, and desktop components) suggest a separation of concerns based on device-specific or feature-specific UI components.