Earlier public Angular implementation

With.in

An earlier Angular implementation with routed content, reusable components, responsive layouts, and prototype form validation.

My role: Sole developer
Context: Independent web project
Period: 2025–2026
Status: Earlier implementation · source available

View earlier implementation on GitHub

Later delivered With.in homepage showing its responsive navigation and hero section — Later delivered version. This version is no longer publicly hosted.

01 · Overview

Project overview

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.

02 · My role

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.

Project scope

Project-wide capabilities

Service and practitioner profiles, testimonials, contact content, legal pages, and appointment calls to action.
Reusable Angular components backed by structured JSON content.
Responsive navigation, modal interactions, prototype client-side validation, and external booking links.
Search-engine metadata and production build configuration.

03 · Decisions

Project decisions

How the project structured its systems, interactions, and delivery constraints.

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.

04 · Problem solving

Challenges and responses

Concrete constraints are paired with the implementation or design response used in the project.

Challenge

Keeping content-dense service and team pages usable on narrow screens.

Response

Applied responsive component layouts and shared spacing rules so navigation, profiles, forms, and calls to action adapt together.

Challenge

Supporting enquiries without a custom backend.

Response

Kept public booking calls to action on external Google Forms. The repository form remains a client-side prototype.

05 · Iteration

Testing and iteration

The Angular production configuration enforces bundle budgets during builds.
The public repository contains no automated component test files. Adding them remains a future improvement.

What I learned

What the project changed

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.

Future pass

What I would improve

Document the differences between the earlier public implementation and the later delivered version.
Add automated accessibility and component tests to the production checks.

Related work

LusoHealth

Five-person team project · shared Git workflowCompleted academic project · source available

A five-person academic digital-health platform for appointments, user workflows, communication, and clinical-support features.

Role: Frontend and backend contributor
Built: Built patient agenda and consultation-history interfaces, completed chat and reports frontend work, and contributed appointment and moderation backend functionality.

View LusoHealth case study View source on GitHub