Added spacing to the ClientHomePage widget column and updated icon and background colors in ActionsWidget to use theme constants. Adjusted padding and removed boxShadow from _ActionCard for a cleaner appearance.
Standardized navigation route paths for client home, hubs, and settings to use '/client-home', '/client-hubs', and '/client-settings'. Added missing module imports and exports in main.dart and krow_data_connect.dart, including business_repository_mock.
Updated Makefile, mobile.mk, and melos.yaml to centralize mobile app build, start, and code generation commands using Melos scripts. Added info and install-melos commands for easier onboarding and workspace setup. Documentation updated to reflect staff app naming and new command structure.
Relocated all app directories (client, design_system_viewer, staff) and their contents under the new 'apps/mobile' path. This change improves project organization and prepares for future platform-specific structuring.
This commit adds a new hash to the allowed-hashes.json file.
This commit adds a new user to the iap-users.txt file.
The new hash is for a new version of the launchpad.
The new user is a new IAP user.
This commit introduces a comprehensive document outlining the
KROW Workforce Platform project, covering vision, architecture,
domain logic, feature gap analysis, and development strategy.
The document serves as a central source of truth for team
onboarding and sprint planning, ensuring alignment and
consistency across the project. It details the migration from
a legacy system to a new GCP-based architecture using Firebase
Data Connect, Cloud Functions, and Cloud SQL.
Key aspects covered include:
- Project vision and business value proposition
- System architecture and technology stack comparison
- Core domain logic and entity definitions
- Feature gap analysis between legacy and prototype apps
- Data Connect schema evolution and development strategy
- Definition of Done (DoD) for features and sprints
The document also includes appendices with entity relationship
summaries, status enum references, and key file locations.