pronoy656/hircon-website

1. This repository is a single Next.js application built with the App Router and TypeScript. The architecture is almost entirely frontend/UI-driven: src/app defines routes and layouts, while src/components holds reusable presentation and feature components.

2. The top-level route structure is split into three broad areas:

- public/authentication flows under src/app/auth/*

- the main authenticated dashboard under src/app/dashboard/*

- a few standalone pages such as /jobs, /network, and /support

This makes the route tree itself the primary architectural map.

3. The dashboard is the core shell of the app. src/app/dashboard/layout.tsx wraps the authenticated experience, and shared navigation elements live in src/components/layout (Navbar, NavbarWrapper, Topbar). This suggests a persistent shell with nested feature pages rendered inside it.

4. Feature domains are organized by business capability rather than technical layer. The biggest ones are:

- shipping: export domestic, import, pallet, quick ship, ship manager, spot rate, saved shipments

- tracking: tracking history, watch shipment, spot-rate history

- quoting: quick quote, saved quotation

- management: contacts, CSV mapping, preferences, dashboard preferences, printing/profile/roles/users tabs

- products: product and packaging editing

- printing/invoicing/integration: separate dashboard sections

Each route page is thin and delegates most UI/workflow logic to a feature component.

5. The src/components/features tree is the main application layer. It contains composite modules such as QuickShipForm, ExportDomesticForm, ShipManager, TrackingHistoryList, ContactTable, and QuickQuoteForm. These components likely own form state, modal workflows, tables, and multi-step interactions for each business area.

6. Shared UI primitives live in src/components/ui. These are generic controls used across features: inputs, selects, text areas, tables, tabs, pagination, confirmation/delete/success modals, and buttons. This layer acts as the design-system boundary between business-specific features and low-level UI.

7. There is a clear modal-and-table interaction pattern across the app. Many workflows are centered on list management plus dialogs: contacts, shipment details, address books, product editing, commercial invoices, sold-to addresses, schedule collection, and success/confirmation states. That indicates the app is designed around CRUD-like operations and guided user flows rather than freeform pages.

8. Shared data and helper logic is minimal and centralized in src/lib. Notable files are countries.ts, savedQuotes.ts, and utils.ts. This implies some app data is local/static or client-managed, with reusable utility functions rather than a large server-side domain layer in this repo.

9. Styling is global plus component-scoped. src/app/globals.css provides the base app styling, while src/styles/custom-shapes.css adds extra visual primitives. The presence of components.json and small UI primitives suggests a component-driven styling system, likely with a strong focus on consistent reusable controls.

10. There is little evidence of a backend service boundary in this repository. No API layer, database client, or server module tree is visible, so the architectural diagram should treat this as a client-heavy Next.js frontend that assembles route pages from reusable feature modules and shared UI, with any persistence/integration likely abstracted away or mocked in local state/data files.