Skip to content
ES
All projects

unPisPas

Responsive build of a cloud POS marketing website, from a Figma design.

Mobile screenshot of the unPisPas website.

Summary

unPisPas is a cloud POS and QR ordering system for bars, cafés and restaurants. My part was the frontend: I built the website from a Figma file designed by Julia Carrión.

What I did

I built the website in plain HTML, CSS and JavaScript: responsive, with reusable components, dropdown navigation and a language selector.

I left the website ready for six languages, with each one’s content injected from JSON. I also prepared a scaffold: when you run it, it generates a new language with the same pages and imports its content from JSON, so adding languages doesn’t require rebuilding the layout.

During development, from January to March 2026, I was in contact with the client and the designer. Most of what I asked the designer to change was about accessibility. Otherwise I stuck to the Figma design; the client asked for the home page copy changes.

The unPisPas home page in Figma: dark header, a photo of a waiter with a tablet, a headline, a button reading Prueba 1 mes gratis and six circular icons below.

The same home page on the live website, with a shorter headline, a button reading Pide una demo and the same six icons below.

The home page in Figma and the same page on the live website, both in Spanish.

For example, the yellow text on the highlighted button didn’t pass contrast on the white background: it came to 1.53:1. I talked to the designer about the accessibility problem: she suggested changing the text to black, and the client confirmed it.

Row of circular buttons from the Figma design, with the TPV en la nube (cloud POS) button marked in yellow and its text also in yellow on a white background.

Contrast checker with yellow FFCA0A on white FFFFFF: a ratio of 1.53 to 1, which fails WCAG AA and AAA for normal and large text.

The highlighted button in the design and its contrast check: 1.53:1, short of WCAG AA.

Where my work ended

My part ended with sending the repository, the test URL, a full accessibility audit and the documentation for modifying and running the scaffold. The client published the website in October 2026.