How serhatblb/angular-one-page-project works
Project type and purpose
• This is a full-stack demo application built around an Angular single-page application (“OnePage”) that consumes data from two kinds of back-ends:
• A mock JSON-server (_1_jsonserver/blog.json) for quickly serving blog entries.
• A Node.js/Express/MongoDB API (_2_nodejs/…) for a more realistic persistence layer.
• The Angular front-end implements a one-page blog site with components for header, main content, blog listing, login/register, navbar, footer, pipes and services.
File structure
Top-level:
• _1_jsonserver/ – JSON file and instructions for spinning up json-server.
• _2_nodejs/ – Node.js Express REST API code, environment config, MongoDB integration.
• src/app/ – Angular components, services, pipes, routing and configuration.
• angular.json, package.json, tsconfig.* – Angular CLI and TypeScript build/config.
• proxy.conf.json – Proxy rules for routing API calls in development.
README for additional insights
• Describes Angular CLI workflow, JSON-server usage (json-server --watch blog.json), Node.js commands (npm run nodemon), ports (Angular:4200 or custom, JSON-server:2222, NodeJS:1111).
• Lists tech stack: Angular (TypeScript, RxJS), Express, Mongoose, json-server, Bootstrap, jQuery, Alertify.js.
• Explains the component-service-module architecture in Angular (MVC-like).
Elements
• UI Components → Services → HTTP Requests → Back-end
• Back-end → Services → UI Components (responses)
• Express API → MongoDB (CRUD operations)
• Rectangles (blue) for front-end layers
• Rectangles (orange) for back-end services