How aseempsri/bhavishyat-journal-app works
Project type and purpose
• This is a full-stack Angular application with server-side rendering (SSR) and prerendering capabilities.
• Purpose: A journal app built with Angular CLI (v19.2.6) that can serve both server-rendered pages (for SEO and fast first-paint) and prerendered static pages (in docs/), plus a client bundle for dynamic interactions.
File structure
Top-level:
• src/ – Angular application source (components, routes, styles).
• server/ – Node.js code and manifests for SSR (Angular Universal).
• browser/ – Client bundle output for CSR.
• docs/ – Prerendered static site artifacts for hosting (e.g., GitHub Pages).
• public/ – Any publicly served static assets (favicon, robots.txt, etc.).
• .github/workflows/ – CI/CD pipeline (deploy.yml).
• angular.json, tsconfig*.json – Build and compiler config.
Patterns:
• Angular CLI → separate client and server build targets.
• “assets-chunks” folder → chunked module loading for CSR and SSR.
• prerendered-routes.json → routes to prerender.
README for additional insights
• Standard Angular CLI commands for serve, build, test, e2e.
• No explicit external API or database—likely a purely front-end data layer or static content.
• Github Actions deploy on commit using a GH_TOKEN.
Final advice
• Be very detailed: include each build artifact and its purpose.
• Both dynamic SSR flow and static prerender flow.