2025-11-16 22:13:52 +01:00
|
|
|
import React from 'react';
|
2025-11-18 07:17:17 +01:00
|
|
|
import { useTranslation } from 'react-i18next';
|
2025-11-09 08:52:10 +00:00
|
|
|
import { WizardStep, WizardStepProps } from '../../../ui/WizardModal/WizardModal';
|
2025-11-16 22:13:52 +01:00
|
|
|
import { Wrench } from 'lucide-react';
|
feat: Add JTBD-driven Unified Add Wizard system
Implemented a comprehensive unified wizard system to consolidate all "add new content"
actions into a single, intuitive, step-by-step guided experience based on Jobs To Be Done
(JTBD) methodology.
## What's New
### Core Components
- **UnifiedAddWizard**: Main orchestrator component that routes to specific wizards
- **ItemTypeSelector**: Beautiful visual card-based selection for 9 content types
- **9 Individual Wizards**: Step-by-step flows for each content type
### Priority Implementations (P0)
1. **SalesEntryWizard** ⭐ (MOST CRITICAL)
- Manual entry with dynamic product lists and auto-calculated totals
- File upload placeholder for CSV/Excel bulk import
- Critical for small bakeries without POS systems
2. **InventoryWizard**
- Type selection (ingredient vs finished product)
- Context-aware forms based on inventory type
- Optional initial lot entry
### Placeholder Wizards (P1/P2)
- Customer Order, Supplier, Recipe, Customer, Quality Template, Equipment, Team Member
- Proper structure in place for incremental enhancement
### Dashboard Integration
- Added prominent "Agregar" button in dashboard header
- Opens wizard modal with visual type selection
- Auto-refreshes dashboard after wizard completion
### Design Highlights
- Mobile-first responsive design (full-screen on mobile, modal on desktop)
- Touch-friendly with 44px+ touch targets
- Follows existing color system and design tokens
- Progressive disclosure to reduce cognitive load
- Accessibility-compliant (WCAG AA)
## Documentation
Created comprehensive documentation:
- `JTBD_UNIFIED_ADD_WIZARD.md` - Full JTBD analysis and research
- `WIZARD_ARCHITECTURE_DESIGN.md` - Technical design and specifications
- `UNIFIED_WIZARD_IMPLEMENTATION_SUMMARY.md` - Implementation guide
## Files Changed
- New: `frontend/src/components/domain/unified-wizard/` (15 new files)
- Modified: `frontend/src/pages/app/DashboardPage.tsx` (added wizard integration)
## Next Steps
- [ ] Connect wizards to real API endpoints (currently mock/placeholder)
- [ ] Implement full CSV upload for sales entry
- [ ] Add comprehensive form validation
- [ ] Enhance P1 priority wizards based on user feedback
## JTBD Alignment
Main Job: "When I need to expand or update my bakery operations, I want to quickly add
new resources to my management system, so I can keep my business running smoothly."
Key insights applied:
- Prioritized sales entry (most bakeries lack POS)
- Mobile-first (bakery owners are on their feet)
- Progressive disclosure (reduce overwhelm)
- Forgiving interactions (can go back, save drafts)
2025-11-09 08:40:01 +00:00
|
|
|
|
2025-11-16 22:13:52 +01:00
|
|
|
const EquipmentDetailsStep: React.FC<WizardStepProps> = ({ dataRef, onDataChange }) => {
|
2025-11-18 07:17:17 +01:00
|
|
|
const { t } = useTranslation('wizards');
|
2025-11-16 22:13:52 +01:00
|
|
|
const data = dataRef?.current || {};
|
2025-11-09 08:52:10 +00:00
|
|
|
|
2025-11-16 22:13:52 +01:00
|
|
|
const handleFieldChange = (field: string, value: any) => {
|
|
|
|
|
onDataChange?.({ ...data, [field]: value });
|
2025-11-09 09:01:18 +00:00
|
|
|
};
|
2025-11-09 08:52:10 +00:00
|
|
|
|
|
|
|
|
return (
|
|
|
|
|
<div className="space-y-6">
|
|
|
|
|
<div className="text-center pb-4 border-b border-[var(--border-primary)]">
|
|
|
|
|
<Wrench className="w-12 h-12 mx-auto mb-3 text-[var(--color-primary)]" />
|
2025-11-18 07:17:17 +01:00
|
|
|
<h3 className="text-lg font-semibold text-[var(--text-primary)] mb-2">{t('equipment.equipmentDetails')}</h3>
|
feat: Add JTBD-driven Unified Add Wizard system
Implemented a comprehensive unified wizard system to consolidate all "add new content"
actions into a single, intuitive, step-by-step guided experience based on Jobs To Be Done
(JTBD) methodology.
## What's New
### Core Components
- **UnifiedAddWizard**: Main orchestrator component that routes to specific wizards
- **ItemTypeSelector**: Beautiful visual card-based selection for 9 content types
- **9 Individual Wizards**: Step-by-step flows for each content type
### Priority Implementations (P0)
1. **SalesEntryWizard** ⭐ (MOST CRITICAL)
- Manual entry with dynamic product lists and auto-calculated totals
- File upload placeholder for CSV/Excel bulk import
- Critical for small bakeries without POS systems
2. **InventoryWizard**
- Type selection (ingredient vs finished product)
- Context-aware forms based on inventory type
- Optional initial lot entry
### Placeholder Wizards (P1/P2)
- Customer Order, Supplier, Recipe, Customer, Quality Template, Equipment, Team Member
- Proper structure in place for incremental enhancement
### Dashboard Integration
- Added prominent "Agregar" button in dashboard header
- Opens wizard modal with visual type selection
- Auto-refreshes dashboard after wizard completion
### Design Highlights
- Mobile-first responsive design (full-screen on mobile, modal on desktop)
- Touch-friendly with 44px+ touch targets
- Follows existing color system and design tokens
- Progressive disclosure to reduce cognitive load
- Accessibility-compliant (WCAG AA)
## Documentation
Created comprehensive documentation:
- `JTBD_UNIFIED_ADD_WIZARD.md` - Full JTBD analysis and research
- `WIZARD_ARCHITECTURE_DESIGN.md` - Technical design and specifications
- `UNIFIED_WIZARD_IMPLEMENTATION_SUMMARY.md` - Implementation guide
## Files Changed
- New: `frontend/src/components/domain/unified-wizard/` (15 new files)
- Modified: `frontend/src/pages/app/DashboardPage.tsx` (added wizard integration)
## Next Steps
- [ ] Connect wizards to real API endpoints (currently mock/placeholder)
- [ ] Implement full CSV upload for sales entry
- [ ] Add comprehensive form validation
- [ ] Enhance P1 priority wizards based on user feedback
## JTBD Alignment
Main Job: "When I need to expand or update my bakery operations, I want to quickly add
new resources to my management system, so I can keep my business running smoothly."
Key insights applied:
- Prioritized sales entry (most bakeries lack POS)
- Mobile-first (bakery owners are on their feet)
- Progressive disclosure (reduce overwhelm)
- Forgiving interactions (can go back, save drafts)
2025-11-09 08:40:01 +00:00
|
|
|
</div>
|
2025-11-09 09:01:18 +00:00
|
|
|
|
2025-11-09 08:52:10 +00:00
|
|
|
<div className="grid grid-cols-1 md:grid-cols-2 gap-4">
|
|
|
|
|
<div>
|
2025-11-18 07:17:17 +01:00
|
|
|
<label className="block text-sm font-medium text-[var(--text-secondary)] mb-2">{t('equipment.fields.type')} *</label>
|
2025-11-09 09:01:18 +00:00
|
|
|
<select
|
2025-11-16 22:13:52 +01:00
|
|
|
value={data.type || 'oven'}
|
|
|
|
|
onChange={(e) => handleFieldChange('type', e.target.value)}
|
2025-11-09 21:25:36 +00:00
|
|
|
className="w-full px-3 py-2 border border-[var(--border-secondary)] rounded-lg focus:outline-none focus:ring-2 focus:ring-[var(--color-primary)] bg-[var(--bg-primary)] text-[var(--text-primary)]"
|
2025-11-09 09:01:18 +00:00
|
|
|
>
|
2025-11-18 07:17:17 +01:00
|
|
|
<option value="oven">{t('equipment.types.oven')}</option>
|
|
|
|
|
<option value="mixer">{t('equipment.types.mixer')}</option>
|
|
|
|
|
<option value="proofer">{t('equipment.types.proofer')}</option>
|
|
|
|
|
<option value="refrigerator">{t('equipment.types.refrigerator')}</option>
|
|
|
|
|
<option value="other">{t('equipment.types.other')}</option>
|
2025-11-09 08:52:10 +00:00
|
|
|
</select>
|
|
|
|
|
</div>
|
|
|
|
|
<div>
|
2025-11-18 07:17:17 +01:00
|
|
|
<label className="block text-sm font-medium text-[var(--text-secondary)] mb-2">{t('equipment.fields.brand')}</label>
|
2025-11-09 09:01:18 +00:00
|
|
|
<input
|
|
|
|
|
type="text"
|
2025-11-16 22:13:52 +01:00
|
|
|
value={data.brand || ''}
|
|
|
|
|
onChange={(e) => handleFieldChange('brand', e.target.value)}
|
2025-11-18 07:17:17 +01:00
|
|
|
placeholder={t('equipment.fields.brandPlaceholder')}
|
2025-11-09 21:25:36 +00:00
|
|
|
className="w-full px-3 py-2 border border-[var(--border-secondary)] rounded-lg focus:outline-none focus:ring-2 focus:ring-[var(--color-primary)] bg-[var(--bg-primary)] text-[var(--text-primary)]"
|
2025-11-09 09:01:18 +00:00
|
|
|
/>
|
2025-11-09 08:52:10 +00:00
|
|
|
</div>
|
|
|
|
|
<div>
|
2025-11-18 07:17:17 +01:00
|
|
|
<label className="block text-sm font-medium text-[var(--text-secondary)] mb-2">{t('equipment.fields.location')}</label>
|
2025-11-09 09:01:18 +00:00
|
|
|
<input
|
|
|
|
|
type="text"
|
2025-11-16 22:13:52 +01:00
|
|
|
value={data.location || ''}
|
|
|
|
|
onChange={(e) => handleFieldChange('location', e.target.value)}
|
2025-11-18 07:17:17 +01:00
|
|
|
placeholder={t('equipment.fields.locationPlaceholder')}
|
2025-11-09 21:25:36 +00:00
|
|
|
className="w-full px-3 py-2 border border-[var(--border-secondary)] rounded-lg focus:outline-none focus:ring-2 focus:ring-[var(--color-primary)] bg-[var(--bg-primary)] text-[var(--text-primary)]"
|
2025-11-09 09:01:18 +00:00
|
|
|
/>
|
2025-11-09 08:52:10 +00:00
|
|
|
</div>
|
|
|
|
|
<div>
|
2025-11-18 07:17:17 +01:00
|
|
|
<label className="block text-sm font-medium text-[var(--text-secondary)] mb-2">{t('equipment.fields.purchaseDate')}</label>
|
2025-11-09 09:01:18 +00:00
|
|
|
<input
|
|
|
|
|
type="date"
|
2025-11-16 22:13:52 +01:00
|
|
|
value={data.purchaseDate || ''}
|
|
|
|
|
onChange={(e) => handleFieldChange('purchaseDate', e.target.value)}
|
2025-11-09 21:25:36 +00:00
|
|
|
className="w-full px-3 py-2 border border-[var(--border-secondary)] rounded-lg focus:outline-none focus:ring-2 focus:ring-[var(--color-primary)] bg-[var(--bg-primary)] text-[var(--text-primary)]"
|
2025-11-09 09:01:18 +00:00
|
|
|
/>
|
2025-11-09 08:52:10 +00:00
|
|
|
</div>
|
feat: Add JTBD-driven Unified Add Wizard system
Implemented a comprehensive unified wizard system to consolidate all "add new content"
actions into a single, intuitive, step-by-step guided experience based on Jobs To Be Done
(JTBD) methodology.
## What's New
### Core Components
- **UnifiedAddWizard**: Main orchestrator component that routes to specific wizards
- **ItemTypeSelector**: Beautiful visual card-based selection for 9 content types
- **9 Individual Wizards**: Step-by-step flows for each content type
### Priority Implementations (P0)
1. **SalesEntryWizard** ⭐ (MOST CRITICAL)
- Manual entry with dynamic product lists and auto-calculated totals
- File upload placeholder for CSV/Excel bulk import
- Critical for small bakeries without POS systems
2. **InventoryWizard**
- Type selection (ingredient vs finished product)
- Context-aware forms based on inventory type
- Optional initial lot entry
### Placeholder Wizards (P1/P2)
- Customer Order, Supplier, Recipe, Customer, Quality Template, Equipment, Team Member
- Proper structure in place for incremental enhancement
### Dashboard Integration
- Added prominent "Agregar" button in dashboard header
- Opens wizard modal with visual type selection
- Auto-refreshes dashboard after wizard completion
### Design Highlights
- Mobile-first responsive design (full-screen on mobile, modal on desktop)
- Touch-friendly with 44px+ touch targets
- Follows existing color system and design tokens
- Progressive disclosure to reduce cognitive load
- Accessibility-compliant (WCAG AA)
## Documentation
Created comprehensive documentation:
- `JTBD_UNIFIED_ADD_WIZARD.md` - Full JTBD analysis and research
- `WIZARD_ARCHITECTURE_DESIGN.md` - Technical design and specifications
- `UNIFIED_WIZARD_IMPLEMENTATION_SUMMARY.md` - Implementation guide
## Files Changed
- New: `frontend/src/components/domain/unified-wizard/` (15 new files)
- Modified: `frontend/src/pages/app/DashboardPage.tsx` (added wizard integration)
## Next Steps
- [ ] Connect wizards to real API endpoints (currently mock/placeholder)
- [ ] Implement full CSV upload for sales entry
- [ ] Add comprehensive form validation
- [ ] Enhance P1 priority wizards based on user feedback
## JTBD Alignment
Main Job: "When I need to expand or update my bakery operations, I want to quickly add
new resources to my management system, so I can keep my business running smoothly."
Key insights applied:
- Prioritized sales entry (most bakeries lack POS)
- Mobile-first (bakery owners are on their feet)
- Progressive disclosure (reduce overwhelm)
- Forgiving interactions (can go back, save drafts)
2025-11-09 08:40:01 +00:00
|
|
|
</div>
|
2025-11-09 08:52:10 +00:00
|
|
|
</div>
|
|
|
|
|
);
|
|
|
|
|
};
|
|
|
|
|
|
2025-11-16 22:13:52 +01:00
|
|
|
export const EquipmentWizardSteps = (dataRef: React.MutableRefObject<Record<string, any>>, setData: (data: Record<string, any>) => void): WizardStep[] => {
|
|
|
|
|
// New architecture: return direct component references instead of arrow functions
|
|
|
|
|
// dataRef and onDataChange are now passed through WizardModal props
|
|
|
|
|
return [
|
|
|
|
|
{
|
|
|
|
|
id: 'equipment-details',
|
2025-11-18 07:17:17 +01:00
|
|
|
title: 'wizards:equipment.steps.equipmentDetails',
|
|
|
|
|
description: 'wizards:equipment.steps.equipmentDetailsDescription',
|
2025-11-16 22:13:52 +01:00
|
|
|
component: EquipmentDetailsStep,
|
|
|
|
|
validate: async () => {
|
|
|
|
|
const { useTenant } = await import('../../../../stores/tenant.store');
|
|
|
|
|
const { equipmentService } = await import('../../../../api/services/equipment');
|
|
|
|
|
const { showToast } = await import('../../../../utils/toast');
|
2025-11-18 07:17:17 +01:00
|
|
|
const i18next = (await import('i18next')).default;
|
2025-11-16 22:13:52 +01:00
|
|
|
|
|
|
|
|
const data = dataRef.current;
|
|
|
|
|
const { currentTenant } = useTenant.getState();
|
|
|
|
|
|
|
|
|
|
if (!currentTenant?.id) {
|
2025-11-18 07:17:17 +01:00
|
|
|
showToast.error(i18next.t('wizards:equipment.messages.errorGettingTenant'));
|
2025-11-16 22:13:52 +01:00
|
|
|
return false;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
try {
|
|
|
|
|
const equipmentCreateData: any = {
|
2025-11-18 07:17:17 +01:00
|
|
|
name: `${data.type || 'oven'} - ${data.brand || i18next.t('wizards:equipment.messages.noBrand')}`,
|
2025-11-16 22:13:52 +01:00
|
|
|
type: data.type || 'oven',
|
|
|
|
|
model: data.brand || '',
|
|
|
|
|
serialNumber: data.model || '',
|
|
|
|
|
location: data.location || '',
|
|
|
|
|
status: data.status || 'active',
|
|
|
|
|
installDate: data.purchaseDate || new Date().toISOString().split('T')[0],
|
|
|
|
|
lastMaintenance: new Date().toISOString().split('T')[0],
|
|
|
|
|
nextMaintenance: new Date(Date.now() + 30 * 24 * 60 * 60 * 1000).toISOString().split('T')[0],
|
|
|
|
|
maintenanceInterval: 30,
|
|
|
|
|
is_active: true
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
await equipmentService.createEquipment(currentTenant.id, equipmentCreateData);
|
2025-11-18 07:17:17 +01:00
|
|
|
showToast.success(i18next.t('wizards:equipment.messages.successCreate'));
|
2025-11-16 22:13:52 +01:00
|
|
|
return true;
|
|
|
|
|
} catch (err: any) {
|
|
|
|
|
console.error('Error creating equipment:', err);
|
2025-11-18 07:17:17 +01:00
|
|
|
const errorMessage = err.response?.data?.detail || i18next.t('wizards:equipment.messages.errorCreate');
|
2025-11-16 22:13:52 +01:00
|
|
|
showToast.error(errorMessage);
|
|
|
|
|
return false;
|
|
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
},
|
|
|
|
|
];
|
|
|
|
|
};
|