Tiago FélixGameplay Programmer & Technical Game Designer

Earlier public Angular implementation

With.in

With.in is an earlier Angular implementation with routed content, reusable components, responsive layouts, and prototype form validation.

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 delivered version. This version is no longer publicly hosted.

Earlier implementation

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.

What I built

  • Built the Angular application and its reusable header, service, team, testimonial, contact, and legal-content components.
  • Implemented routed pages and responsive SCSS layouts for mobile and desktop use.
  • Implemented a standalone Reactive Forms prototype with client-side validation. Public booking calls to action use external Google Forms.
  • Added canonical metadata, Search Console verification, sitemap.xml, robots.txt, production budgets, and an automated deployment 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.

Public version

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

What I took from it

  • How content architecture, responsive behaviour, validation, and SEO files combine in a client-facing site.
  • How to make the boundary between client-side validation and external form processing explicit.
View GitHub