How ohjelmistokehitys/merge-exercise works
Project type and purpose
• This is a single-page application (SPA) frontend project: a React/TypeScript-based countdown timer scaffolded with Vite.
• There is no separate backend service or database; it’s purely a client-side app that can be served statically or via a simple containerized HTTP server.
• The purpose is to teach Git merging via feature branches while exercising core React/TypeScript/Vite workflows.
File structure
• Top-level configuration: Dockerfile, docker-compose.yml, Git ignore/config files, ESLint, tsconfig, vite.config.ts.
• Public assets: index.html and public/.gitkeep hold the static HTML shell and any static assets.
• Source code: src/main.tsx (entry point), src/App.tsx (app shell), src/Timer.tsx (countdown logic/UI).
• Package.json lists dependencies (React, Vite, Pico CSS, dev tooling).
• Screenshots directory contains sample UI states (documentation purposes).
README for additional insights
• The README focuses on Git branch merging rather than feature complexity.
• It shows the minimal tech stack: Node.js/NPM, React, Vite, Docker, GitHub Actions (in feature/workflows).
• No backend API or external services are mentioned. Styling relies on the Pico CSS framework.
Detailed breakdown of components to capture
• Source Control: branches (main, feature/*), merge conflicts resolution (manual).
• CI/CD: GitHub Actions workflows from feature/workflows branch.
• Local dev: Vite dev server (hot module reload).
• Production build: Vite build → dist folder.
• Containerization: Dockerfile instructions → nginx or static server layer (if present).
• Client runtime: index.html → main.tsx → App.tsx → Timer.tsx.
• Styling: Pico CSS included via HTML head or import.
• NPM scripts: “dev”, “build”, “serve” (if any).