Official Website & Magazine Display/Purchase Platform

Context

As an intern at a Milan-based startup, I owned the official website and the magazine platform — both the display side and the purchase flow — for a fashion-magazine and event-marketing service.

Two things were true when I started. The site was static HTML, so every new page meant copying markup around. And the domain and hosting account sat in a freelance contractor's personal name. It was the company's website, but the company did not own it.

The site is viewable at common-mag.com.

What I did

1. Rebuilt static HTML on Vue.js/Vuetify

I broke the repeated markup into Vue.js components and rebuilt the official website and the magazine display and purchase pages on top of the Vuetify component library. The mobile, tablet, and desktop breakpoints went in during the rebuild — far cheaper than retrofitting responsive behaviour onto static HTML later, when the component structure was being redrawn anyway.

2. Moved the domain and hosting into company accounts

Both the domain and the hosting lived in the personal accounts of the contractor who had built the site before. If that person became unreachable, the company had no way to touch its own site.

I opened shared hosting on Hostinger under a company account and transferred the domain to the company. Not technically hard, but rebuilding a frontend while the company does not own the place it runs only solves half the problem, so it went in the same piece of work.

3. Improved the portfolio navigation

I reworked the navigation flow of the portfolio pages so that visitors arriving from social media could review the studio's work and follow through to a business inquiry.

4. Worked with a multinational team

I collaborated with the on-site Milan team, turning the fashion-magazine and event-marketing service's requirements into agreed screens and then into implementation.

Results

It was the first project where I owned the full frontend arc — screen planning through implementation and delivery. What actually lasted is that the company ended up owning its domain and hosting, not just the code.