How mrtaz77/career-studio-frontend works
Project type and purpose
• From the README (“career-studio-frontend: Frontend of Career Studio”) and the file tree (no backend or “src” directory shown, only CI/CD and config files), we know this is purely a frontend application. Its role is to serve the user interface for the Career Studio product, fetching data and sending user actions to downstream services (a backend API, authentication provider, analytics, etc.).
File structure
• Top-level only shows configuration and CI/CD artifacts:
• .github/workflows/build.yml → GitHub Actions build/test pipeline
• sonar-project.properties → SonarQube code quality scan
• .gitignore, LICENSE, README.md
Keep it detailed but focused
• Essential elements (UI, hosting, pipeline, APIs, auth, analytics).
• Don’t clutter with trivial files—focus on runtime components and deployment workflow.