How devwithjay/boardify works
Main Components
• User Interface (Presentation Layer):
• index.html: The main HTML entry point that serves as the container for the application.
• css/style.css (or Tailwind CSS integration): Handles styling and responsive design.
• assets folder: Contains images and other static resources (e.g., the tech-stack image, board screenshots, etc.).
• JavaScript Functionality (Application/Business Logic Layer):
• js/script.js and js/broadify.js: Main entry and integration scripts for initializing and controlling application flow.
• js/modules folder: Contains distinct modules each handling different functionalities:
▸ board-manager.js: Organizes the overall board structure.
▸ task-manager.js: Manages creating, editing, and deleting tasks.
▸ drag-drop-manager.js: Provides functionality for drag-and-drop task reordering.
▸ search-manager.js: Handles task searching and filtering.
▸ theme-manager.js: Controls dark/light theme switching.
▸ ui-manager.js: Manages the dynamic update of the user interface.
▸ constants.js: Provides shared constants across modules.
• Project Configuration and Build Tools:
• package.json, vite.config.js, and related configuration files (e.g., .prettierrc, .editorconfig): Define project dependencies, code style, and bundler settings.
• pnpm-lock.yaml: Indicates the use of pnpm for package management.
• Deployment:
• Public folder (if applicable) and deployment files that indicate hosting on Vercel.
Relationships and Interactions
• The index.html ties together the CSS and JavaScript components.
• The main JavaScript files (script.js and broadify.js) act as the glue that imports the various modules.
• Modules work together in a loosely coupled manner:
• The board-manager orchestrates board-level events and delegates specific tasks to task-manager, ui-manager, and drag-drop-manager.
• User interactions (e.g., dragging tasks, clicking to edit, toggling themes) trigger events managed by their respective modules.
• The constants.js module supplies invariant values to ensure consistency across the modules.
• All updates to the UI and business logic communicate soundly with the browser’s local storage for persistence.
• Vite config and package files define build transformations and bundling processes for development and production.
Architectural Patterns and Technologies
• Modular Architecture: The separation into multiple modules (UI, board, task, theme, search, drag-and-drop) promotes maintainability.
• Separation of Concerns: Distinct responsibilities are assigned to presentation (HTML/CSS), logic (JavaScript modules), and configuration (Vite, package.json).
• Local Storage Persistence: The application stores task data and user preferences locally.
• Build and Deployment: Utilizes Vite for a streamlined development workflow and Vercel for hosting.
• Tools: HTML5, Tailwind CSS, and JavaScript form the core tech stack, supported by Git for version control.