UNPKG

ng-hub-ui-board

Version:

An Angular-based Kanban board component with Trello-like drag-and-drop, customizable columns, and straightforward event handling.

540 lines (396 loc) 18.2 kB
# ng-hub-ui-board [![npm version](https://badge.fury.io/js/ng-hub-ui-board.svg)](https://badge.fury.io/js/ng-hub-ui-board) ## Part of ng-hub-ui Family This component is part of the ng-hub-ui ecosystem, which includes: - [ng-hub-ui-table](https://www.npmjs.com/package/ng-hub-ui-table) - [ng-hub-ui-modal](https://www.npmjs.com/package/ng-hub-ui-modal) - [ng-hub-ui-stepper](https://www.npmjs.com/package/ng-hub-ui-stepper) - [ng-hub-ui-breadcrumbs](https://www.npmjs.com/package/ng-hub-ui-breadcrumbs) - [ng-hub-ui-portal](https://www.npmjs.com/package/ng-hub-ui-portal) - [ng-hub-ui-avatar](https://www.npmjs.com/package/ng-hub-ui-avatar) - [ng-hub-ui-accordion](https://www.npmjs.com/package/ng-hub-ui-accordion) ## Description A flexible and powerful board component for Angular applications, perfect for implementing Kanban-style boards, task management systems, or any drag-and-drop card-based interface. Similar to Trello boards, this component allows you to create interactive columns with draggable cards. ## Features - 🎯 **Standalone component** - Modern Angular approach with minimal setup - 🔄 **Drag and drop support** - Full drag-and-drop for both cards and columns using Angular CDK - 📱 **Responsive design** - Works seamlessly across desktop, tablet, and mobile devices - 🎨 **Highly customizable** - Custom templates for cards, headers, and footers - 🔧 **Bootstrap compatible** - Integrates perfectly with Bootstrap 5 design system -**Virtual scrolling** - Supports infinite scroll with end-detection for performance - 🎭 **Custom styling** - CSS custom properties for easy theming and customization - 🔒 **Granular control** - Enable/disable functionality at board, column, or card level - 🏷️ **TypeScript support** - Full type safety with generic interfaces -**Accessibility ready** - Follows WAI-ARIA best practices for drag-and-drop ## Installation ```bash # Install the component npm install ng-hub-ui-board # Install required peer dependency npm install @angular/cdk ``` Or using yarn: ```bash yarn add ng-hub-ui-board yarn add @angular/cdk ``` ## Quick Start Here’s a quick example to get you started with `ng-hub-ui-board` using the standalone component approach. ### 1. Setup your board model ```ts import { signal } from '@angular/core'; import { Board } from 'ng-hub-ui-board'; export const board = signal<Board>({ title: 'Project Sprint', columns: [ { title: 'To Do', cards: [ { title: 'Login page', description: 'Build login form with validation' }, { title: 'Landing hero', description: 'Implement hero section' } ] }, { title: 'In Progress', cards: [{ title: 'Set up CI/CD', description: 'Add GitHub Actions' }] }, { title: 'Done', cards: [{ title: 'Project scaffold', description: 'Initial Angular setup' }] } ] }); ``` ### 2. Create your component ```ts import { Component } from '@angular/core'; import { HubBoardComponent, CardTemplateDirective, BoardColumnHeaderDirective, BoardColumnFooterDirective, BoardCard } from 'ng-hub-ui-board'; @Component({ selector: 'board-demo', standalone: true, imports: [HubBoardComponent, CardTemplateDirective, BoardColumnHeaderDirective, BoardColumnFooterDirective], templateUrl: './board-demo.component.html' }) export class BoardDemoComponent { board = board; handleCardClick(card: BoardCard) { console.log('Card clicked:', card); } handleCardMoved(event: any) { console.log('Card moved:', event); } } ``` ### 3. Use in your template ```html <hub-board [board]="board()" (onCardClick)="handleCardClick($event)" (onCardMoved)="handleCardMoved($event)"> <ng-template cardTpt let-card="item"> <strong>{{ card.title }}</strong> <p>{{ card.description }}</p> </ng-template> </hub-board> ``` This code block provides a minimal and functional example for both beginners and intermediate users. ## Usage The component can be used in two ways: ### 1. Standalone Component Import (Recommended) ```typescript import { Component } from '@angular/core'; import { HubBoardComponent, CardTemplateDirective, BoardColumnHeaderDirective, BoardColumnFooterDirective } from 'ng-hub-ui-board'; @Component({ selector: 'app-my-component', standalone: true, imports: [HubBoardComponent, CardTemplateDirective, BoardColumnHeaderDirective, BoardColumnFooterDirective], template: ` <hub-board [board]="board" (onCardClick)="handleCardClick($event)" (onCardMoved)="handleCardMoved($event)"> <!-- Templates go here --> </hub-board> ` }) export class MyComponent { // ... component logic } ``` ### 2. Module Import (Legacy) ```typescript import { NgModule } from '@angular/core'; import { BoardModule } from 'ng-hub-ui-board'; @NgModule({ imports: [BoardModule] // ... rest of the module configuration }) export class AppModule {} ``` ## Templates The component uses three different templates for customization. If you're using the standalone approach, remember to import the corresponding directives for each template you plan to use. ### Card Template (CardTemplateDirective) Used to customize how each card is rendered within the columns. This template gives you complete control over the card's appearance and structure. ```html <ng-template cardTpt let-card="card"> <div class="custom-card"> <h3>{{ card.title }}</h3> <p>{{ card.description }}</p> <div class="card-metadata"> <span class="priority">{{ card.data?.priority }}</span> <span class="due-date">{{ card.data?.dueDate | date }}</span> </div> </div> </ng-template> ``` ### Column Header Template (BoardColumnHeaderDirective) Used to customize the header of each column. Perfect for adding column-specific actions, showing card counts, or adding filtering options. ```html <ng-template columnHeaderTpt let-column="column"> <div class="custom-header"> <h2>{{ column.title }}</h2> <span class="card-count">{{ column.cards.length }} items</span> <div class="column-actions"> <button (click)="addCard(column)">Add Card</button> <button (click)="filterColumn(column)">Filter</button> </div> </div> </ng-template> ``` ### Column Footer Template (BoardColumnFooterDirective) Used to add a footer to each column. Useful for summary information, quick actions, or column-specific controls. ```html <ng-template columnFooterTpt let-column="column"> <div class="custom-footer"> <div class="column-summary"> <span>Total: {{ column.cards.length }}</span> <span>Priority Items: {{ getPriorityItems(column) }}</span> </div> <button (click)="quickAddCard(column)">Quick Add</button> </div> </ng-template> ``` ## Events The `HubBoardComponent` emits several events to help you interact with user actions such as clicking cards, moving items, or reaching scroll limits. ### onCardClick Emitted when a card is clicked. ```html <hub-board [board]="board" (onCardClick)="handleCardClick($event)"> </hub-board> ``` **Type:** `EventEmitter<BoardCard>` **Example:** ```ts handleCardClick(card: BoardCard) { console.log('Card clicked:', card.title); } ``` --- ### onCardMoved Emitted when a card is moved either within the same column or between columns. ```html <hub-board [board]="board" (onCardMoved)="handleCardMoved($event)"> </hub-board> ``` **Type:** `EventEmitter<CdkDragDrop<BoardColumn, BoardColumn, BoardCard>>` **Example:** ```ts handleCardMoved(event: CdkDragDrop<BoardColumn, BoardColumn, BoardCard>) { const card = event.item.data; const from = event.previousContainer.data; const to = event.container.data; console.log(`Moved "${card.title}" from "${from.title}" to "${to.title}"`); } ``` --- ### onColumnMoved Emitted when a column is reordered via drag and drop. ```html <hub-board [board]="board" (onColumnMoved)="handleColumnMoved($event)"> </hub-board> ``` **Type:** `EventEmitter<CdkDragDrop<BoardColumn[]>>` **Example:** ```ts handleColumnMoved(event: CdkDragDrop<BoardColumn[]>) { console.log(`Column moved from ${event.previousIndex} to ${event.currentIndex}`); } ``` --- ### reachedEnd Emitted when a user scrolls to the end of a column. Useful for triggering lazy-loading of additional cards. ```html <hub-board [board]="board" (reachedEnd)="handleReachedEnd($event)" style="max-height: 600px;"> </hub-board> ``` **Type:** `EventEmitter<ReachedEndEvent>` **Example:** ```ts handleReachedEnd(event: ReachedEndEvent) { console.log('Reached end of column:', event.data.title); this.loadMoreCards(event.index); } ``` > ℹ️ To enable scroll detection, set a `max-height` on the `hub-board` container. ## Inputs The following inputs are available on the `HubBoardComponent`: | Input | Type | Description | Default | |------------------------|-------------------------------|---------------------------------------------------------------------|-------------| | `board` | `Signal<Board>` | The board object containing columns and cards | `undefined` | | `columnSortingDisabled`| `boolean` | Disables drag-and-drop sorting of columns | `false` | ## Outputs These outputs are emitted by the component during user interaction: | Output | Type | Description | |-----------------|-----------------------------------------------------------|-----------------------------------------------------------------------------| | `onCardClick` | `EventEmitter<BoardCard>` | Triggered when a card is clicked | | `onCardMoved` | `EventEmitter<CdkDragDrop<BoardColumn, BoardColumn, BoardCard>>` | Emitted when a card is moved (within or across columns) | | `onColumnMoved` | `EventEmitter<CdkDragDrop<BoardColumn[]>>` | Emitted when a column is reordered via drag and drop | | `reachedEnd` | `EventEmitter<ReachedEndEvent>` | Triggered when the user scrolls to the bottom of a column (for lazy load) | ## Interfaces ### Board Main container interface that represents the entire board structure. Used to define the overall board configuration including its columns and general styling. ```typescript interface Board<T = any> { id?: number; title: string; description?: string; columns?: BoardColumn<T>[]; classlist?: string[]; style?: { [key: string]: any }; } ``` ### BoardColumn Represents a single column in the board. Used to configure individual columns, their cards, and column-specific behavior like drag-and-drop rules. ```typescript interface BoardColumn<T = any> { id?: number; boardId?: number; title: string; description?: string; cards: BoardCard<T>[]; style?: { [key: string]: any }; classlist?: string[] | string; disabled?: boolean; cardSortingDisabled?: boolean; predicate?: (item?: CdkDrag<T>) => boolean; } ``` ### BoardCard Represents individual cards within columns. Used to define card content and behavior, including custom data and styling. ```typescript interface BoardCard<T = any> { id?: number; columnId?: number; title: string; description?: string; data?: T; classlist?: string[]; style?: { [key: string]: any }; disabled?: boolean; } ``` ## 🧩 Styling The `ng-hub-ui-board` library is fully style-configurable through **CSS custom properties (CSS variables)**, defined with a consistent naming convention and designed to be easily overridden in consuming applications. It is built with flexibility in mind and integrates seamlessly with **Bootstrap** or any design system that supports custom properties. ### 🌱 Base styles and integration The base styles for the board component are located in the `base.scss` file within the library: ```scss // projects/board/src/lib/styles/base.scss $boardPrefix: hub- !default; // Example CSS custom properties defined in .hub-board__column .hub-board__column { --#{$boardPrefix}column-border-color: rgba(0, 0, 0, 0.175); --#{$boardPrefix}column-border-radius: 0.375rem; --#{$boardPrefix}column-bg: #fff; ... } ``` These styles follow the naming convention `--hub-<element>-<property>`, making it simple to identify and override individual variables. ### 🔗 How to include the styles in your application To use the styles from `ng-hub-ui-board`, you need to import the base SCSS file from the compiled library into your main application’s `styles.scss` (or wherever you define your global styles). Example `styles.scss` in the consuming application: ```scss @use 'bootstrap'; // Optional but recommended @use '../dist/board/src/lib/styles/base.scss' as boardBase; ``` > ✅ **Tip**: Using `@use` instead of `@import` ensures proper scoping and avoids global leakage. ### 🎛 Customizing styles via CSS variables Once the styles are imported, you can customize any of the exposed CSS variables using your own class selectors, CSS scopes, or directly at the root level. Example: Overriding the column border width and background color ```scss .hub-board__column { --hub-column-border-width: 0; --hub-column-bg: #f8f9fa; } ``` This approach allows for theme-level overrides without needing to fork or modify the library source code. ### ⚙️ Seamless Bootstrap integration Because the board components are designed to align visually and structurally with **Bootstrap 5**, you can: - Use spacing (`gap`, `padding`) and color schemes consistent with Bootstrap. - Integrate the board layout into Bootstrap grids or utilities. - Customize the variables with Bootstrap's own SCSS variables if needed. Example override using Bootstrap color variables: ```scss .hub-board__column { --hub-column-cap-bg: var(--bs-light); --hub-column-border-color: var(--bs-border-color); } ``` ### 🎨 Theming and scalability You can define different visual themes by grouping variable overrides under custom CSS classes or even media queries. Example of dark mode support: ```scss .dark-theme .hub-board__column { --hub-column-bg: #1e1e1e; --hub-column-color: #f1f1f1; --hub-column-border-color: #333; } ``` This makes `ng-hub-ui-board` a great fit for design systems that need scalable and adaptable UI building blocks. ## Real-world Use Cases The `ng-hub-ui-board` component is versatile and has been used in a variety of real-world applications, such as: - **Project Management Tools** – Visualize task progress across stages (To Do, In Progress, Done). - **Support Ticket Boards** – Organize support tickets by urgency, team, or status. - **Recruitment Pipelines** – Track candidates through different phases of hiring. - **CRM Systems** – Manage leads and customers in pipeline-style workflows. - **Editorial Calendars** – Schedule and organize content by publication status. Each case benefits from customizable columns, card templates, and event outputs to integrate with your app logic. ## Troubleshooting Here are some common issues and how to resolve them: ### 🔄 Drag and drop not working - **Check dependencies**: Ensure `@angular/cdk` is installed and imported - **Reactive data**: Verify your board data is reactive (using `signal()`, `Observable`, or proper change detection) - **Browser compatibility**: Ensure your target browsers support the HTML5 Drag and Drop API ### 📏 Scroll detection not triggering `reachedEnd` - **Height constraints**: The `<hub-board>` element or its parent must have a `max-height` or fixed height - **Overflow setting**: Ensure `overflow: auto` or `overflow-y: scroll` is applied to enable scrolling - **Content length**: Make sure there's enough content to actually trigger scrolling ### 🎨 Styles not applying - **Import path**: Confirm you've imported the SCSS base styles in your global `styles.scss`: ```scss @use '../dist/board/src/lib/styles/base.scss' as boardBase; ``` - **CSS custom properties**: Check that your custom CSS variables follow the `--hub-*` naming convention - **Style specificity**: Ensure your custom styles have sufficient specificity to override defaults ### 🧩 Templates not rendering - **Import directives**: When using standalone components, import the template directives: ```typescript imports: [HubBoardComponent, CardTemplateDirective, BoardColumnHeaderDirective] ``` - **Template syntax**: Verify you're using the correct template selectors (`cardTpt`, `columnHeaderTpt`, `columnFooterTpt`) ### 🛠️ Runtime errors - **"Cannot read property 'cards' of undefined"**: Initialize your board signal properly: ```typescript board = signal<Board>({ title: 'My Board', columns: [] }); ``` - **Type errors**: Ensure your data matches the `Board`, `BoardColumn`, and `BoardCard` interfaces - **Signal updates**: Use `.set()` or `.update()` methods to modify signal values ### 🎯 Performance issues - **Large datasets**: Consider implementing virtual scrolling for columns with many cards - **Memory leaks**: Ensure proper cleanup of event listeners and subscriptions - **Change detection**: Use `OnPush` change detection strategy when possible If problems persist, open an issue at: https://github.com/carlos-morcillo/ng-hub-ui-board/issues ## Contributing Contributions are welcome! Here's how you can help: 1. Fork the repository 2. Create your feature branch: `git checkout -b feature/my-new-feature` 3. Commit your changes: `git commit -am 'Add some feature'` 4. Push to the branch: `git push origin feature/my-new-feature` 5. Submit a pull request ## Support the Project If you find this project helpful and would like to support its development, you can buy me a coffee: [!["Buy Me A Coffee"](https://www.buymeacoffee.com/assets/img/custom_images/orange_img.png)](https://www.buymeacoffee.com/carlosmorcillo) Your support is greatly appreciated and helps maintain and improve this project! ## License This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details. --- Made with ❤️ by [Carlos Morcillo Fernández](https://www.carlosmorcillo.com/)