The Pixel Insider — From tools to a system

JULY 2026 — Edition #6

the

pixel

insider

by WEB DESIGN TEAM

INTRODUCTION

July moves the team into a more strategic phase. After building several internal tools, the focus is now on making them easier to scale, share and connect to real publishing workflows. From PDP enrichment to shared repositories and newsletter automation, the goal is to reduce manual work while keeping quality and consistency under control.

WHAT WE BUILT

PDP enrichment flow

KNOW MORE +

PDP AI HTML Content Enrichment Images

Problem

Enriching product detail pages can require several manual steps, from product research and content structure to image creation and final HTML implementation.

Solution

We planned a SKU-based flow that gathers product information, builds the enrichment HTML and prepares supporting visuals for the PDP.

Impact

This can make enriched product content faster to create, more consistent and easier to scale across selected products and brands.

Shared code repositories

KNOW MORE +

GitHub Design System Components Collaboration

Problem

Several internal apps now share similar needs, but reusable code still needs to be separated from private project code.

Solution

We planned shared repositories for common parts such as the Design System, image editor logic, components, icons and utilities.

Impact

This allows developers to reuse proven parts without exposing unrelated project code, improving collaboration and reducing duplicated work.

Newsletter backoffice automation

KNOW MORE +

Automation Backoffice Internal Communication Workflow

Problem

Updating the team newsletter manually takes time, especially when several months of projects, images and modal content need to be recovered.

Solution

We structured the newsletter content so it can be imported into the database with titles, summaries, modals, tags and image notes prepared in advance.

Impact

This reduces backoffice work, keeps team communication more consistent and makes it easier to recover updates that were left behind.

Banner guidelines become a website

KNOW MORE +

Guidelines Banners Figma Sites

Problem

Even with clearer rules, banner guidelines lived in a document that people outside Design rarely opened before sending files.

Solution

Bruno Biscaia turned the guidelines into a website: pick the format, follow the essential rules, download the template and check the file before delivery.

Impact

                                            7
                                            formats in one place
                                        

Anyone who briefs or produces banners now has one link with every format and rule, checked before the file is made instead of after.

TEAM ACHIEVEMENTS

Duarte Almada

Team roadmap and tooling

Defined the next step for the internal tooling ecosystem, connecting PDP enrichment, shared repositories, newsletter automation and the webdesignteam.pt hub into a more scalable direction.

Francisco Ferreira

Internal app updates

Continued contributing technical updates and app progress that helped document the evolution of tools such as Wizard Services Pages, FAQ workflows and service-related implementations.

Vítor Cardoso

Steady campaign delivery

Closed more tasks than anyone in the team in June (226) and kept the pace in July (212), keeping the GW campaigns and the weekly board moving through the summer.

OPERATIONAL SNAPSHOT

Team Activity

KNOW MORE +

July focused on turning accumulated work into a more scalable system. Instead of treating each app, component or newsletter as a separate task, the team started organising shared foundations, publishing workflows and documentation so future work can move faster with less repeated setup.

                                        599
                                        tasks delivered in July
                                    

A quieter month with summer holidays: 424 owned and 175 assisted, the highest assisted share of the summer, with a peak of 184 tasks in the week of 13 July. The weekly board, Acquisition requests and the search banner fixes led the work.

LEARNINGS

Documentation must be close

The best way to keep work visible is to document it while it is being built.

Automation needs structure

A backoffice can only be automated well when the content is prepared consistently.

Shared code needs boundaries

Reusable repositories work best when they separate common logic from private project code.

Strategy is operational

Big improvements often start by removing small repeated steps from daily work.

WHAT'S NEXT

🛒

PDP

Connecting PDP enrichment to production

The next step is to keep developing the SKU-to-PDP flow, including image generation, icon usage, HTML output and future CMS or Metis integration.

📚

Shared Libraries

Making reusable code available

We will continue separating shared parts of the internal apps into documented repositories that other developers can import, test and improve.

📰

Newsletter

Keeping The Pixel Insider updated

The newsletter process should become easier to maintain, with structured content prepared in advance and less time spent filling the backoffice manually.