How ericgichuri/worklane works
Worklane is an in-development business workflow platform. The visible user path is initial setup or sign-in, session-aware navigation, and access to the dashboard and user/role administration; the backend provides authentication, password reset, and user/role APIs backed by SQLAlchemy models. The README and model definitions also identify customer requests, tasks, approvals, workflow stages, documents, activity logs, and automation as product capabilities, though their runtime flows are not shown. Those capabilities are represented without asserting unsampled execution paths.
Main entry points: App.jsx Page routing · auth.py Authentication API · users.py User and role API · AuthContext.jsx Auth context
Components 20
Web client
- App bootstrap
frontend/src/main.jsx - Page routing
frontend/src/App.jsx - Auth context
frontend/src/context/AuthContext.jsx - Session and setup
frontend/src/hooks/useAuthAndSetup.js - Login and setup
frontend/src/pages/Login.jsx - Home page
frontend/src/pages/Home.jsx - Dashboard
frontend/src/pages/Dashboard.jsx - User administration
frontend/src/pages/Users.jsx - Navigation
frontend/src/components/Navbar.jsx - Sidebar
frontend/src/components/Sidebar.jsx
Identity and access
- Authentication API
backend/routes/auth.py - User and role API
backend/routes/users.py - Reset email
backend/utils/email_password.py - API responses
backend/utils/response.py
Workflow domain
- Workflow domain models
backend/models/models.py
Backend and persistence
- Flask application
backend/app.py - ORM and login extensions
backend/extensions.py - Backend configuration
backend/config.py - SQLite database
Other components
- Business user
Connections 29
- Business user → App bootstrap: uses
frontend/src/main.jsx - App bootstrap → Page routing: renders
frontend/src/main.jsx - App bootstrap → Auth context: provides auth
frontend/src/main.jsx - Page routing → Auth context: reads session
frontend/src/App.jsx - Page routing → Login and setup: routes to
frontend/src/App.jsx - Page routing → Home page: routes to
frontend/src/App.jsx - Page routing → Dashboard: routes to
frontend/src/App.jsx - Page routing → User administration: routes to
frontend/src/App.jsx - Page routing → Navigation: renders
frontend/src/App.jsx - Page routing → Sidebar: renders
frontend/src/App.jsx - Auth context → Session and setup: uses
frontend/src/context/AuthContext.jsx - Session and setup → Authentication API: calls API
frontend/src/hooks/useAuthAndSetup.js - Login and setup → Auth context: uses auth
frontend/src/pages/Login.jsx - Navigation → Auth context: uses auth
frontend/src/components/Navbar.jsx - Navigation → Authentication API: requests profile
frontend/src/components/Navbar.jsx - User administration → User and role API: calls API
frontend/src/pages/Users.jsx - Flask application → Backend configuration: loads config
backend/app.py - Flask application → ORM and login extensions: initializes
backend/app.py - Flask application → Authentication API: registers routes
backend/app.py - Flask application → User and role API: registers routes
backend/app.py - Authentication API → Workflow domain models: queries and updates
backend/routes/auth.py - Authentication API → ORM and login extensions: commits changes
backend/routes/auth.py - Authentication API → API responses: formats replies
backend/routes/auth.py - Authentication API → Reset email: sends reset link
backend/routes/auth.py - User and role API → Workflow domain models: queries and updates
backend/routes/users.py - User and role API → ORM and login extensions: commits changes
backend/routes/users.py - User and role API → API responses: formats replies
backend/routes/users.py - Workflow domain models → ORM and login extensions: uses ORM
backend/models/models.py - Backend configuration → SQLite database: configures store