NBA Feed
Your teams' news and games, with scores hidden until you reveal them.
Frontend web application for the Berliz fitness and combat sports platform
Sports & fitnessTypeScript · HTMLGitHub @blessedtaselaOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
Angular single-page application for Berliz, a fitness and combat sports platform connecting trainers, gyms, and clients through profiles, bookings, and content.
See docs/TECH_STACK.md for a full breakdown of every library in use and why it's here, and docs/ARCHITECTURE.md for how the app is structured.
• Node.js 18+
• Angular CLI (npm install -g @angular/cli)Read the full README ↗Angular single-page application for Berliz, a fitness and combat sports platform connecting trainers, gyms, and clients through profiles, bookings, and content.
Live: berliz.fitness
Angular 16 · TypeScript · NgRx · Tailwind CSS · RxJS
See docs/TECH_STACK.md for a full breakdown of every library in use and why it's here, and docs/ARCHITECTURE.md for how the app is structured.
npm install -g @angular/cli)git clone https://github.com/blessedtasela/berliz.git
cd berliz
npm install
Configuration lives in src/environments/environment.ts (development) and environment.prod.ts (production, swapped in automatically by angular.json's fileReplacements on a production build) — not a .env file. Copy the shape of environment.ts if you need to point at a different backend locally.
ng serve
Opens at http://localhost:4200, proxying API calls to whatever environment.api points at (defaults to a local backend at http://localhost:8080).
ng build # development build
ng build --configuration=production # production build, used by Netlify
Output goes to dist/berliz/.
ng test
Netlify builds and deploys automatically on every push to master (see netlify.toml). Cloudflare sits in front of the custom domain for DNS and SSL. Full details in docs/DEPLOYMENT.md.
src/
app/
admin/ # Admin-only management screens (users, centers, trainers, content, etc.)
services/ # HTTP services, auth interceptor, shared business logic
state/ # NgRx: actions, reducers, effects, selectors
shared/ # Reusable components, pipes, directives
models/ # TypeScript interfaces for API data shapes
utils/ # Framework-agnostic helper functions
... # Feature areas (trainers/, centers/, categories/, etc.), each
# typically paired with an admin/<feature> counterpart
environments/ # environment.ts / environment.prod.ts — build-time config
legacy/ # Pre-NgRx state services, kept for reference during migration
angular.json # Angular CLI / build configuration
netlify.toml # Netlify build & deploy configuration
docs/ # Architecture, setup, deployment, roadmap, API, tech stack docs
docs/ARCHITECTURE.md — how the pieces fit togetherdocs/SETUP.md — detailed local setupdocs/DEPLOYMENT.md — how production deploys workdocs/API.md — backend API reference from the frontend's perspectivedocs/ROADMAP.md — what's built and what's planneddocs/TECH_STACK.md — every technology in use, and why