How andrescamiloocampo/get-hired-frontend works
Project type and purpose
• This is a front-end Angular Universal (SSR) application called “GetHired.”
• It uses Angular CLI v19, Angular Universal for server-side rendering (server.ts, main.server.ts), and a traditional client bootstrap (main.ts).
• Purpose: render a job-matching UI with styling, components (atoms → organisms → sections), routing, authentication guards, and data fetched via service calls.
File structure
• Top level:
• server.ts, main.server.ts → Express SSR entrypoints
• main.ts → client bootstrap
• angular.json, tsconfig*.json → build config
• package.json, bun.lock, package-lock.json → dependencies
• src/app:
• app.config.ts/.server.ts, app.routes.ts/.server.ts → environment-aware routing & configuration
• components (atoms, organisms, sections) → atomic-design UI hierarchy
• layouts, pages, guards, models, datasources, services → logical separation (presentation, routing, state, API layer)
• public/assets, environments → static content & environment flags
README for additional insights
• Standard Angular CLI setup, no built-in backend; SSR is provided by an Express server defined in server.ts.
Detail
• Environment configuration feeding into SSR vs. client build
• Static asset serving (public folder) as part of SSR server responsibilities