Rebuilding the Frontend for a Large Corporate Website

TIM Group
tim.it desktop website
The TIM.it desktop website brand page. Image credit: TIM S.p.A.
m.tim.it mobile website
Mobile user interfaces to be implemented on the frontend. Image credit: TIM S.p.A.
tim.it menu screenshot
The TIM.it desktop mega menu. Image credit: TIM S.p.A.

As Frontend Developer contracted through Nexse at TIM Group from 2015 to 2016, I contributed to the rebuild of TIM’s corporate web platform (tim.it and m.tim.it), delivering modular, high-performance UI components used across hundreds of templates.

The Challenge

TIM needed a scalable frontend foundation for one of Italy’s largest corporate websites: hundreds of templates, a dedicated mobile site at m.tim.it, and compatibility across desktop, mobile, and legacy browsers, with distributed design, backend, and QA teams working in Agile sprints.

My Role

As Frontend Developer, I worked on the rebuild of tim.it and m.tim.it: turning design handoffs into modular UI components reused across hundreds of corporate templates.

Scope covered desktop and dedicated mobile templates, with delivery in Agile sprints alongside design, backend, and QA, including cross-browser checks down to legacy Internet Explorer.

What I Did

  • Converted Sketch and PSD handoffs into reusable components with pixel accuracy and consistent rendering across devices.
  • Built those components in modular SCSS and semantic HTML, following BEM and internal design-system rules.
  • Delivered tailored mobile templates for m.tim.it to improve loading times and cut responsive overhead on the main site.
  • Worked on Bootstrap with custom UI utilities in HTML5, CSS3, JavaScript, and jQuery.
  • Automated builds with Gulp and tracked delivery in Git and Jira.
  • Tested with BrowserSync and physical devices, including legacy browsers such as Internet Explorer.
  • Used BrowserStack for cross-browser coverage and regression checks on mobile and desktop templates.
Banner of the Bootstrap HTML/CSS/JS library
Bootstrap as the primary UI framework. Image credit: getbootstrap.com.
Debugging the UI on multiple physical mobile devices
Debugging UI across mobile devices using BrowserSync.

Results

  • The components held up across hundreds of templates on tim.it and m.tim.it, serving millions of users.
  • Mobile visitors got purpose-built templates instead of desktop markup bent to fit.
  • Regressions stayed out of the rollout across desktop, mobile, and legacy browsers.

What I Learned

At this scale, a separate mobile site plus modular BEM components beat one responsive codebase trying to cover every template. Disciplined QA across BrowserSync, devices, and BrowserStack kept regressions out of a hundreds-of-templates rollout.

Get in touch

Rebuilding a large corporate site? Let's discuss your project.