8c37de49b0
IMPLEMENTATION: Added react-i18next translations to InventoryWizard
following the pattern from ItemTypeSelector
CHANGES IMPLEMENTED:
- Added useTranslation('wizards') hook
- Translated header section (title + description)
- Translated required fields:
* Name field with placeholder
* Product Type dropdown (all 4 options)
* Unit of Measure dropdown (all 8 units)
- Translated Basic Information section:
* SKU field with tooltip
* Barcode field
- Used common translations (optional, etc.)
TRANSLATIONS USED:
- inventory.inventoryDetails → "Inventory Item Details"
- inventory.fillRequiredInfo → Localized descriptions
- inventory.fields.name → "Name"
- inventory.fields.namePlaceholder → "E.g., All-Purpose Flour..."
- inventory.productTypes.* → All product types
- inventory.units.* → All units (kg, g, l, ml, units, dozen, lb, oz)
- inventory.fields.sku → "SKU"
- inventory.fields.skuTooltip → Full tooltip text
- common.optional → "Optional"
BENEFITS:
✅ Core inventory fields now multilingual
✅ Works in EN/ES/EU languages
✅ Auto-updates when language changes
✅ User-facing strings now translatable
TESTING:
1. Open Add Inventory wizard
2. Switch language (EN → ES → EU)
3. See header, labels, placeholders, and dropdowns translate
4. Examples:
- EN: "Name", "Product Type", "Unit of Measure"
- ES: "Nombre", "Tipo de Producto", "Unidad de Medida"
- EU: "Izena", "Produktu Mota", "Neurri Unitatea"
This demonstrates i18n working in the actual wizard forms!
Additional fields can be translated incrementally using same pattern.
🍞 Bakery IA - Multi-Service Architecture
Welcome to Bakery IA, an advanced AI-powered platform for bakery management and optimization. This project implements a microservices architecture with multiple interconnected services to provide comprehensive bakery management solutions.
🚀 Quick Start
Prerequisites
- Docker Desktop with Kubernetes enabled
- Docker Compose
- Node.js (for frontend development)
Running the Application
-
Clone the repository:
git clone <repository-url> cd bakery-ia -
Set up environment variables:
cp .env.example .env # Edit .env with your specific configuration -
Run with Docker Compose:
docker-compose up --build -
Or run with Kubernetes (Docker Desktop):
# Enable Kubernetes in Docker Desktop # Run the setup script ./scripts/setup-kubernetes-dev.sh
🏗️ Architecture Overview
The project follows a microservices architecture with the following main components:
- Frontend: React-based dashboard for user interaction
- Gateway: API gateway handling authentication and routing
- Services: Multiple microservices handling different business domains
- Infrastructure: Redis, RabbitMQ, PostgreSQL databases
🐳 Kubernetes Infrastructure
🛠️ Services
The project includes multiple services:
- Auth Service: Authentication and authorization
- Tenant Service: Multi-tenancy management
- Sales Service: Sales processing
- External Service: Integration with external systems
- Training Service: AI model training
- Forecasting Service: Demand forecasting
- Notification Service: Notifications and alerts
- Inventory Service: Inventory management
- Recipes Service: Recipe management
- Suppliers Service: Supplier management
- POS Service: Point of sale
- Orders Service: Order management
- Production Service: Production planning
- Alert Processor: Background alert processing
📊 Monitoring
The system includes comprehensive monitoring with:
- Prometheus for metrics collection
- Grafana for visualization
- ELK stack for logging (planned)
🚀 Production Deployment
For production deployment on clouding.io with Kubernetes:
- Set up your clouding.io Kubernetes cluster
- Update image references to your container registry
- Configure production-specific values
- Deploy using the production kustomization:
kubectl apply -k infrastructure/kubernetes/environments/production/
🤝 Contributing
- Fork the repository
- Create a feature branch
- Make your changes
- Submit a pull request
📄 License
This project is licensed under the MIT License.