How plastikaweb/plastikspace works
Project type and purpose
• This is an Nx-based monorepo hosting multiple Angular front-end applications (nasa-images, experimental, llecoop, plastikaweb, etc.), end-to-end test apps (Cypress), Firebase backends (hosting + Firestore, Cloud Functions triggers), and a large suite of reusable libraries (core and shared domains).
• Purpose: provide a playground for experiments and production-grade apps in Angular, TailwindCSS, Redux (NgRx), Firebase, GraphQL, with CI/CD via GitHub Actions.
File structure
• Top-level “apps” directory:
• Angular SPAs under apps/ (each with its own environment, routing, components, assets, styles).
• E2E test runners under apps/*-e2e (Cypress configurations).
• Firebase hosting under apps/llecoop-firebase (public folder, firestore rules).
• Cloud Functions under apps/llecoop-triggers (TypeScript functions for Firestore triggers).
• Top-level “libs” directory:
• “core” scoped libraries for layout, guards, NgRx data-access, routing, styles, utilities.
• “shared” scoped libraries for Authentication, Forms, Buttons, Tables, Notification, Storage, Signal-State, reusable UI, and utilities.
• Domain-specific libs under libs/llecoop, libs/nasa-images, libs/plastikaweb, etc.
• Tools and config: nx.json, tsconfig.base.json, GitHub workflows, Lerna/Yarn Workspaces, husky, ESLint, Prettier, Verdaccio (private NPM registry).
README for additional insights
• Architectural guidelines in documentation/nx-architecture.md.
• Emphasis on Nx generators, affected graph, dependency graph.
• CI/CD pipelines defined in .github/workflows for build, test, deploy (staging/production).