Tiago FélixGameplay Programmer & Technical Game Designer

Earlier public Angular implementation

With.in

I built the Angular service and practitioner pages so visitors could read them on a phone and go straight to booking. The public links went to Google Forms, and I built a separate validation prototype in Angular. The repository shows that earlier version. The later client site is offline.

Role
Sole developer
Context
  • Client web project
  • earlier public implementation
Period
2025–2026
Status
  • Earlier implementation
  • client site no longer hosted in this version
  • source available
  • Angular 20
  • TypeScript
  • SCSS
  • Reactive Forms
  • GitHub Actions
Later delivered With.in homepage showing its responsive navigation and hero section
Later client-delivered With.in homepage. The public repository is an earlier implementation, and this later version is no longer hosted.

My role

The public repository contains an earlier implementation. A later version was delivered for the client but is no longer publicly hosted.

The earlier implementation is an Angular single-page application with responsive layouts, reusable content components, routes, client-side validation, crawler files, and an automated build workflow.

My contribution

  • Built reusable Angular components and routed service, team and information pages.
  • Adapted layouts and navigation for narrow screens using shared SCSS rules.
  • Created a Reactive Forms validation prototype while public enquiry links used external Google Forms.
  • Added canonical metadata, crawler files, production budgets and an automated build workflow.

Design decisions

Component-led content structure
Services, practitioners, testimonials, contact content, and legal information were split into reusable, focused components.
Prototype form validation
A standalone Angular Reactive Forms component models client-side validation without implying a repository-backed enquiry service.
Static search support
Canonical tags, a sitemap, robots directives, and verification files were included alongside the production build.

What was hard

Keeping content-dense service and team pages usable on narrow screens.
Applied responsive component layouts and shared spacing rules so navigation, profiles, forms, and calls to action adapt together.
Supporting enquiries without a custom backend.
Kept public booking calls to action on external Google Forms. The repository form remains a client-side prototype.

Outcome and evidence

The public repository preserves my earlier implementation. A later client version was delivered but is no longer publicly hosted.

  • The source contains responsive layouts, routes, Reactive Forms validation and build configuration. External Google Forms handles public enquiries. The prototype form does not provide a custom enquiry backend.

What I learned

Shared components kept content changes consistent across pages. I also learned to make the boundary between browser validation and external form processing clear.

View GitHub