Step 4: Navigation Reorganization
- Add new 'CRM & 세무관리' nav group (BusinessCenter icon)
- Organize 5 CRM pages: TaxProfiles, TaxFilingSchedules, Contracts, ConsultingActivities, RevenueTrackings
- Reorder nav groups: Dashboard → CRM (default expanded) → Customer → Website → Inquiries → Settings
- Update 'Customer' group label and icons for clarity
- Set expandedCRMGroup=true for immediate visibility
Navigation Structure (Post-change):
`
대시보드
├─ CRM & 세무관리 [EXPANDED]
│ ├─ 세무 프로필 (Assignment icon)
│ ├─ 신고 일정 (CalendarMonth icon)
│ ├─ 계약 관리 (Description icon)
│ ├─ 상담 활동 (ChatBubble icon)
│ └─ 수익 추적 (Receipt icon)
├─ 고객 관리
│ ├─ 고객 카드
│ └─ 세무신고
├─ 홈페이지
│ ├─ 공지사항
│ ├─ FAQ 관리
│ ├─ 블로그 관리
│ └─ 시즌 시뮬레이터
├─ 문의 관리
└─ 설정
`
Design Rationale:
- CRM group positioned first (after dashboard) for workflow priority
- Default expanded = immediate page discovery
- Icons from Material Design Filled set for consistency
- Grouped by business domain, not by data type
Build Status: 0 errors, 3 warnings (existing)
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Phase 7-4 추가:
- 5개 CRM/세무관리 Blazor 페이지 (TaxProfile, TaxFilingSchedule, Contract, ConsultingActivity, RevenueTracking)
- 5개 API Controller + Browser Client (API-First 패턴)
- MudDataGrid Douzone ERP 수준 UX (32px 행, 데이터 밀도)
- MudDialog 모달, ConfirmDialog 삭제 확인
- Status/Risk Level 컬러 칩, D-day 추적, MRR 계산
현재 상태:
- Phase 1-7 모두 완료 (2026-06-28)
- 16개 Blazor 페이지 API-First 마이그레이션 완료
- 모든 SOLID 원칙 적용
- 빌드: 0 errors
다음 우선순위:
1. Nav 그룹 추가 (CRM/세무관리 섹션)
2. E2E 테스트 (Playwright)
3. 모바일 앱 (React Native/Flutter)
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Admin Grid UX Enhancements (Section 8.6):
- High-density data display (32px row height, 5-7 column layout)
- Responsive design: PC(6) → Tablet(4) → Mobile(2) columns
- Pad-optimized (24px cells, 36px buttons for touch)
- Advanced interactions: inline editing, multi-select, context menu
- MudDataGrid implementation pattern with virtualization
- Status-based coloring (normal/warning/danger/success)
- Performance optimization (virtualization, lazy loading, caching)
Deployment User Experience Protection (Section 11.1):
- No forced refresh during deployment ❌
- Users receive notifications with manual refresh option ✅
- SignalR-based deployment notification (not server-sent events)
- Auto-save form data to sessionStorage
- Recovery options after refresh
- Deployment status API endpoint
- Admin-only deployment notification API
Core Principles:
- 사용자 작업 중 배포 시 강제 새로고침 금지
- 알림 + 수동 새로고침 옵션 제공
- 폼 데이터 자동 보존 및 복구 기능
Architecture:
- Create companies table with company_code as unique identifier
- Add company_id foreign key to admin_users for multi-tenant support
- Implement backward compatibility with DEFAULT company for existing users
Core Components:
- Company entity with full CRUD operations
- ICompanyRepository interface following Repository pattern
- CompanyRepository with Dapper implementation
- CompanyService with business logic and validation
- CompanyController with REST API endpoints
Admin UI:
- CompanyForm reusable component (Create/Edit pattern)
- CompanyList.razor with pagination and company overview
- CompanyCreate.razor for registering new companies
- CompanyEdit.razor for managing existing companies with delete
- All pages follow admin-page-hero pattern for consistency
SOLID Principles:
- Single Responsibility: Each component has one reason to change
- Open/Closed: Extensible without modifying existing code
- Interface Segregation: Clean repository and service contracts
- Dependency Inversion: All layers depend on abstractions
Database Migration (V014):
- Creates companies table with active/inactive status
- Assigns existing admin users to DEFAULT company
- Provides foundation for role-based access control
Future Enhancement:
- Admin users can belong to specific companies
- Data filtering based on company_id (multi-tenant isolation)
- Company-based permission model
Core Components:
- Create reusable InquiryForm.razor component following SOLID principles
- Implement InquiryCreate.razor for registering new inquiries (offline, phone)
- Implement InquiryEdit.razor for modifying existing inquiries with delete
- Add DeleteAsync method to InquiryRepository and InquiryService
- Update InquiryList with 'Create' button and Edit link in table
Architecture:
- InquiryForm: Encapsulates form logic, can be reused for create/edit
- Service Layer: All operations go through InquiryService for cache invalidation
- Repository Pattern: Database operations isolated in InquiryRepository
- UI Consistency: Both pages follow admin-page-hero pattern
Features:
- Admin can create inquiries from phone/offline consultations
- Admin can modify inquiry details (name, phone, email, message, status, memo)
- Admin can delete inquiries with confirmation dialog
- All operations update dashboard cache
- Status validation and error handling throughout
Testing:
- Updated FakeInquiryRepository in tests to implement DeleteAsync
- Add 'Remember ID' checkbox for improved UX
- Store username in localStorage when checked
- Restore saved username on login page load
- Remove saved username when checkbox unchecked
- Follow security best practice: save username only, not password
- Create BlogEdit.razor for editing existing posts
- Add admin-page-hero section for consistent navigation
- Implement delete functionality with confirmation dialog
- Add GetByIdAsync method to BlogService to support entity retrieval by ID
- Follow SOLID principles: single responsibility for each component
- Move deployment completion alert to background Task
- Prevent blocking app startup waiting for Telegram API
- Fixes 'service not responding' errors during health check
- Add error handling for Telegram send failures
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Set MaxRequestBodySize to 100MB for large file uploads
- Resolves 'Request Header Or Cookie Too Large' errors
- Applies to Kestrel server in both development and production
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Enhanced topbar with better button styling and tooltips
- Added system information to drawer footer (server, update status)
- Improved visual hierarchy and spacing
- Better responsive design for mobile screens
- Replaced meaningless message with useful admin context
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
InquiryDetail and ClientDetail pages were missing the admin-page-hero
section, causing the loading overlay to remain stuck on navigation.
The loading indicator (admin-session.js) detects page.admin-page-hero
to know when to hide the overlay.
Now all detail pages show smooth loading indicators on navigation.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Apply same EnsureAuthHeader pattern for consistency across all API
clients. Dashboard summary numbers now load correctly with proper JWT
authentication in Blazor Server environment.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Blazor Server components cannot access client-side localStorage, so
InquiryBrowserClient needs to get the access token from server-side
ITokenStore and manually add the Authorization header to requests.
This fixes 401 Unauthorized errors when InquiryList loads inquiry data.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Move MudTabs inside MudPaper always visible structure
- Only render MudTabs content (with data) after isLoading becomes false
- Add null/empty check in InquiryTable.OnParametersSet()
- Add error handling in InquiryList data loading
Previously, MudTabs would render before data loaded, causing child
InquiryTable components to mount with empty Inquiries list. After
data loaded, child components weren't re-rendered because Blazor
didn't detect parameter changes in that scenario.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
kjh2064