Skip to content

Conversation

@Lukecsharpwalker
Copy link
Owner

This pull request introduces a major refactor to support a multi-project Angular workspace architecture, including new configuration files, project separation, and updated build/deployment workflows. The changes enable modular development with distinct apps for admin, web, code samples micro-frontend, and shared libraries, aligning with modern Angular best practices and deployment targets.

Workspace & Project Structure

  • Migrated from a monolithic app to a multi-project workspace in angular.json, defining separate projects for admin, web, code-samples-mfe, and shared, each with their own build, serve, test, and lint configurations. This enables modular development and easier maintenance. [1] [2]

Build & Deployment Configuration

  • Added a production-ready Dockerfile for SSR deployment of the blog app on Google Cloud Run, using a multi-stage build process and supporting both pnpm and npm for dependency installation.
  • Updated CI workflow in .github/workflows/google-cloudrun-docker.yml to use new build and test commands (npm run test:all, npm run build web --configuration production) for compatibility with the new workspace structure. [1] [2]

Development & Formatting Standards

  • Added a comprehensive .prettierrc file to standardize code formatting across the workspace, including overrides for HTML, SCSS, and Markdown files.

Hosting & Environment Configuration

  • Introduced .firebaserc to define Firebase Hosting targets for admin and samples sites, supporting multi-app deployment.

Documentation & Guidelines

  • Added CLAUDE.md with detailed guidance for LLM-assisted development, outlining project architecture, coding standards, migration status, and authoritative context files for future refactoring and code changes.

…abel' to 'web-label' and 'app-post-card' to 'web-post-card'
…nd consistency, add login component and styles, and update routing logic
…ate styles for consistency, and improve responsiveness
…or tag selection, search functionality, and dropdown menu
…rity, adjust router links, and implement new layout component
…ve spacing, and update component structure for better layout consistency
…or consistency and clarity across components
…e generation from Supabase posts and adjust Angular SSR configuration
…egister components for consistency, adjust template syntax, and improve import paths
…ling, and improve button positioning for better responsiveness
…e module allowance rules for improved structure and clarity
…m shared module for consistency and clarity across components
…rom shared module and enhance public API structure for improved clarity and maintainability
…nhance rules for clarity and safety, and utilize optional chaining for better null handling
…lement DestroyRef cleanup for event listeners and MutationObserver, convert @input to signal inputs, and standardize error handling for improved clarity and maintainability
…es to provide more context and ensure type safety for error handling
…kup and enhance structure for better maintainability
…component creation and enhance code structure for better maintainability
…ns and specify file patterns for improved code quality
…nvironment.ts to ensure correct file structure in CI workflow
…d actions to v4 for improved performance and compatibility
@Lukecsharpwalker Lukecsharpwalker merged commit 9e95cb1 into main Aug 24, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants