Lisbon's Tram 28 reimagined as a dark tourism route — dictatorship, colonialism, and collective memory.
Things I've built at this desk.
Where the best cities share a desk.
I build web things that make you feel something. Pixel art, vanilla code, and AI-assisted workflows.
See the work LinkedInTry clicking the desk — the objects work.
Hold a title bar to move a window.
Projects
This portfolio — a pixel-art Y2K where Rio de Janeiro and Lisbon share a desk.
An open-source agent skill that answers one tax question Portuguese freelancers keep getting wrong.
A review-reply assistant for local businesses: paste the review, pick a tone, get three replies in ten seconds.
Kawaii e-commerce brand built and run solo — store, payments, inventory, and identity.
WordPress rebrand for a Lisbon optical clinic — from dated site to a storefront the owner can run.
A watchman for the law an app depends on: it reads the official pages on a schedule and opens an issue when the text moves.
An invite-only marketplace for women, designed down to the last token — and stopped at the go/no-go, because the validation turned out not to exist.
A hundred invitations across two channels, a shared cost and a kitchen to fill — run as a pipeline instead of a group chat.
Some of it you can play.
Not everything I build is a case study. A few are small machines that just run in a browser, and they live in here.
Enter the arcade
The desk has a story.
I'm Aline — a creative technologist built at the intersection of two cities. Brazil shaped how I see colour, texture, and warmth. Portugal taught me resilience, history, and how to start again and keep building. The desk you're looking at holds both.
I work where creativity, product and code meet: I design things, build them, and use AI to bring them to life faster — illustration, brands, interfaces and the front-end behind them. On the web my default is HTML, CSS and vanilla JavaScript — not because I don't know frameworks (I do), but because starting from fundamentals means every abstraction I add is earned, not assumed.
This site is the work. The attention to detail you find here — the objects you can click, the day and night palettes, the two skylines outside the window — is the same attention I bring to everything I build.
Open to creative tech, product/UI design, front-end and AI content work — based in Lisbon (WET/CET), hybrid or remote, Portuguese and EU citizen, working in Portuguese and English. Freelance or employed. geral@bylx.dev
Credentials
- BSc Software Engineering · GPA 9.80/10 · in progress
- Google Data Analytics Certificate · Google / Coursera · 2024 ↗
- CET Cultural Tourism & Heritage · EHTL Lisboa · EQF 5 · internship pending
Verified badges · Cisco IT Support track
Currently fluent in
Dark28 — Case Study
- Next.js
- TypeScript
- React
- Tailwind CSS
The question
Lisbon's Tram 28 passes through layers of history that most tourist guides ignore. I kept finding apps that told the same polished story and skipped the uncomfortable parts — the dictatorship, the colonial memory, the religious weight embedded in the architecture. What if a route helped you understand a city instead of just photograph it?
What I built
An editorial web app that transforms the Tram 28 into a self-guided dark tourism experience. Users discover landmarks filtered by historical theme, read narrative context for each stop, and build a personal plan of places to visit and track.
- Editorial homepage with thematic framing
- Landmark discovery by theme (dictatorship, colonialism, religion, death)
- Detail pages with narrative context per stop
- Save landmarks and track visited places
- Route direction toggle and dark/light theme
- Fully responsive, mobile-first
Technical decisions
Next.js (App Router) — editorial content needs good SEO and fast initial load. Server components simplified data fetching and nested layouts.
TypeScript throughout — enforced clear data contracts between components and caught two broken data shapes before they hit the UI.
Tailwind CSS — rapid iteration on a content-heavy interface without fighting specificity. Consistent spacing without thinking about it.
localStorage + custom hooks — one useLocalStorage hook persisted all user state across four features with no backend required.
What I learned
Designing content-first changes the UI. The narrative weight of each stop shaped the information hierarchy — generic card components didn't work because the content resisted being genericised. TypeScript caught real bugs, not theoretical ones. App Router's server/client boundary required rethinking where state lives.
bylx.dev — Case Study
- HTML
- CSS
- Vanilla JS
- PHP
The question
Developer portfolios all look the same: hero, grid, footer. Mine had to prove something instead of claiming it. Could a pixel-art desk — where Rio de Janeiro and Lisbon share a window — carry an entire portfolio, built with nothing but the fundamentals?
What I built
An interactive scene where every object does what it looks like it should: the camera opens the gallery, the phone opens the contact form, the MP3 player opens a working player, the cocktail tells the story of the two cities, and the sushi tray explains how the desk was drawn.
- Canvas pixel-art scene on a 640×390 grid, always drawn at a whole-number scale
- Every sprite drawn once in greyscale and recoloured into a day (AM) and a night (PM) palette, plus a 3-bit grey mode
- Sections as program windows you can minimise, maximise, close and drag
- Custom pixel cursor with sakura-petal trail
- Working MP3 player with a 17-track lo-fi playlist
- PHP contact form with honeypot and graceful non-JS fallback
- Keyboard-accessible case-study modals
Technical decisions
Vanilla ES modules — scene, windows, theme, cursor, audio, modals and forms are isolated modules with a single init each. There is nothing to hydrate, so a framework would only add weight.
Greyscale in, palettes out — a small build script maps each grey level of every sprite to one of seven colours per theme, so a new palette is a JSON change, not a redraw. Clickable objects are real buttons laid over the canvas, so the scene stays keyboard- and screen-reader-accessible.
Seven colours per mode — the whole site, not just the scene, uses only the seven colours of the active palette, through role tokens in :root.
Pixel-crisp motion — the opening moves layers in whole-pixel steps, and it is skipped entirely when the system asks for reduced motion.
What I learned
Constraints are a design system. Refusing frameworks forced clean module boundaries; refusing smooth easing forced intentional animation. And accessibility inside a fully custom scene — focus states, aria labels, a form that works without JS — is where the real engineering happened.
irs-pt — Case Study
- Agent Skill
- Python (stdlib only)
- Markdown
- MIT
The question
Every freelancer in Portugal asks the same thing in March: is it worth assigning this invoice to my activity? I could not find an answer that started with the arithmetic instead of the portal. Under the regime simplificado the answer is close to binary — expenses only matter once 15% of gross service income passes the automatic deduction — and almost nobody is told that before they start classifying receipts one by one.
What I built
An open-source assistant packaged as an agent skill: it runs inside Claude and any agent that reads the agentskills format, asks two or three questions, and does the threshold maths before it mentions invoices at all. It explains, calculates and recommends — it never submits anything to the Portal das Finanças.
- Works out the year's threshold first and says, in one sentence, whether invoices change anything
- Handles mixed activity (sales, services, other services) and income on top of a salaried job
- Reads the e-Fatura CSV export locally and proposes a classification invoice by invoice
- Shows a preview and asks for confirmation before listing what to click in the portal
- Ends with one next action and the year's deadlines
Technical decisions
The maths before the portal — the whole point is the question nobody answers first. Getting the order right is the product; the parser is the easy half.
Python with no dependencies — parse_efatura.py is stdlib only and reads the CSV on your own machine. Tax data does not leave the computer, and there is nothing to install or trust.
Volatile values in one file — IAS, thresholds and deadlines live in references/valores-anuais.md, apart from the structural rules that do not change every year. Updating for a new tax year is one file, not a hunt.
The human clicks — it is not tax advice, and it does not act. The line between "explains" and "submits" is the safety property; it is written into the skill's inviolable rules, not just the README.
What I learned
Writing software for a rule someone else wrote means reading the primary source: the CIRS articles, not the blog posts about them. And shipping something in public with "tested by one person — her own return" on the label is a different kind of honesty than a portfolio demo, because strangers rely on it.
respondaja.click — Case Study
- PHP 7.4
- Anthropic API
- Stripe
- HMAC
The question
A one-star review lands on a Sunday night. The right reply is not hard to write — thank them, acknowledge the problem briefly, invite them to continue in private, stay under eighty words, never admit liability. It is just that it takes twenty minutes, it comes out the same every time, and the person who runs a restaurant is not a copywriter. So why twenty minutes?
What I built
Paste the review — Google, iFood, TripAdvisor, anywhere — choose one of three tones, and get three replies in about ten seconds. Edit and publish wherever it came from. Five a month for free with no account at all; unlimited on a Pro tier at R$ 29 a month through Stripe. Portuguese and English. The market is Brazil.
- Three options rather than one, because the useful part is choosing
- The rules of the trade live in the prompt: thank, acknowledge, take it offline, under eighty words, never admit liability, never offer compensation the review did not ask for
- The free tier runs in the browser with no signup screen anywhere
- Pro cancels from Stripe’s own portal — no cancellation flow to build, and none to make deliberately hard
Technical decisions
No account on the free tier — what kills a tool like this is the signup screen, not the price. The free path never asks for an email, so the distance between pasting a review and having three replies is one click.
The key never reaches the browser — generation happens server-side. That is also the only reason a quota can exist at all: anything counted in the browser is a suggestion, not a limit.
Pro is a signed token, not a user table — after checkout the server verifies the session with Stripe and issues an HMAC-signed licence with an expiry. No accounts, no passwords, no personal data to protect, nothing to leak. The signature is compared with hash_equals, so a wrong one takes exactly as long to reject as a right one takes to accept.
The free count is client-side on purpose, and the code says so — an abused free call costs about a tenth of a cent, so per-IP hardening was priced and postponed rather than pretended. That reasoning is a comment in the repository, not a secret.
What I learned
It is finished. The payment path runs end to end — checkout, verification, licence, renewal — and it has never taken a single payment, because I never told anyone it existed. Building was the easy half, and it is the half I am good at. The lesson is not about code: from the outside, a product nobody has heard of and a product that does not work look exactly the same.
konochan.pt — Case Study
- E-commerce
- Stripe
- MB Way
- Hostinger
The question
Could I take a brand from zero to real orders — not a portfolio mockup, but a shop with actual customers, payments, and parcels that have to arrive?
What I built
A kawaii and handmade-resin e-commerce brand, built and operated solo: visual identity, product catalogue, checkout, and everything that happens after someone pays.
- Full store setup on Hostinger, from DNS to checkout
- Stripe and MB Way payment integration for the Portuguese market
- WhatsApp integration for order support and customer contact
- Brand identity, product photography, and packaging design
- Inventory, pricing, and customer support operations
Technical decisions
Platform over custom code — the goal was a working shop, not a stack demo. Hostinger shipped the store in weeks instead of months.
Local payment rails — MB Way is how Portugal actually pays online. Supporting it mattered more than any feature.
WhatsApp as CRM — customers already live there; meeting them in their channel beat building one.
What I learned
E-commerce is UX plus logistics — the interface is the easy half. Running the store taught me what "done" means when customers are real. The shop is open again since October 2026, now with pieces made to order and an Etsy store alongside it.
luparoad.com — Case Study
- WordPress
- UX
- Branding
The question
A Lisbon optical clinic had a website that undersold the business — dated, hard to navigate, and impossible for the owner to update. How do you rebuild trust online for a business whose whole trade is precision?
What I built
A full WordPress rebrand: new visual identity applied to a restructured site, designed so the owner can maintain it without calling a developer.
- Theme customisation aligned with the new brand
- Restructured content and navigation around what customers ask first
- Plugin selection and configuration kept deliberately minimal
- Responsive layout and performance cleanup
- Handover so the client edits content independently
Technical decisions
WordPress, on purpose — the client needs to edit content themselves. The right stack is the one the business can maintain after you leave.
Fewer plugins, fewer problems — every plugin is a future update, a security surface, and a support call. The build stayed lean.
What I learned
Client work is a different discipline: listening before building, designing within the client's capacity, and writing handover docs as carefully as code. The best compliment was silence — the site just works.
Two cities
Look out of the window behind the monitor. Cristo Redentor and Pão de Açúcar stand on one side of it; the Ponte 25 de Abril and the Torre de Belém on the other. That is not a mixed metaphor that got away from me — it is the whole point of the desk.
What Rio gave me
Colour, texture, warmth, and the nerve to use all three at once. I studied Design & Visual Communication at UFRJ's Escola de Belas Artes, in a city where nothing is beige. The palette on this site — the cyan, the pink, the purple that has no business working next to either — is a Rio palette. So is the instinct that a portfolio should be somewhere you want to stay, not a document you scroll.
What Lisbon taught me
Resilience — how to start again in a new country and keep building. I took a CET in Cultural Tourism & Heritage here, which is a formal way of saying I learned to read a place. dark28.pt came out of that — a dark-tourism route along Tram 28, written for people standing at the stop. konochan.pt is run from a flat in Greater Lisbon, and my five years at Accenture happened here too.
How this desk was drawn
Every object on this desk was drawn by hand in shades of grey, laid out in a Photoshop file, and coloured by code. This is how.
Drawn in grey
Each sprite is drawn once, in seven levels of grey. Light and shadow are decided before colour exists, so a drawing never has to be redone when the palette changes. The 3BIT button in the settings shows you the desk exactly as it was drawn.
Coloured by code
A small build script maps every grey to one of seven colours per mode: PM runs from deep purple to pink, AM from navy to mint. In AM the walls, the hills, the bridge, the Sugarloaf and the Belém tower flip their scale, so daylight reads as daylight. The rest of the site uses the same seven colours, so the page and the desk never disagree.
Placed by hand
The scene is a 640×390 grid, and every position is copied from the Photoshop file where the desk was arranged. It is drawn on a canvas at whole-number scale only — 2×, 3×, 4× — so one pixel of the art is always a clean square on your screen, never a blur. On a phone you see the same desk, cropped around the monitor.
The rules
Motion moves in whole pixels: the desk assembles itself once when the page opens, and the monitor's power light blinks slowly, because a real one would. Both stop when your system or the settings ask for reduced motion. The objects you can click are real buttons laid over the drawing, so the desk works with a keyboard and a screen reader, not just a mouse.
The parts
Twenty-nine sprites, two seven-colour palettes, seventeen lo-fi tracks the mp3 player genuinely streams, and a single dependency in the whole project — which only runs the tests. No framework; the only build step turns the grey sprites into palettes. The windows you can drag around are plain HTML with a two-pixel border.
sentinela — Case Study
The question
irs-pt answers a tax question using numbers that Parliament changes every December. A tool built on a law has a quiet failure mode that a tool built on an API does not: nothing breaks. No test goes red, no request 500s. The skill keeps answering, confidently, with last year's thresholds. So who tells you the ground moved?
What I built
A watchman that runs on a schedule, reads the official pages the skill is built on — CIRS, CIVA, Social Security, e-Fatura — and opens a GitHub issue with the diff when the text changes. It never edits the skill. Deciding what a changed article means is the human's job; the watchman's only job is to make sure nobody finds out by accident.
- Runs on the 1st of each month, plus 15 January and 10 July — the dates the law actually moves
- Opens one issue per run, carrying the diff of every source that changed
- Watches PDFs (the practical guides) by hash of their bytes
- A source that stops responding also opens an issue — a dead URL means the portal was rebuilt
- First run writes the baseline and stays quiet
Technical decisions
Alert first, baseline second — the run compares, then publishes the issue, and only then commits the new snapshots. If publishing fails, the baseline is not updated and the next run catches the same change again. A change is never absorbed in silence, which is the one outcome that would make the whole thing worse than nothing.
Every source carries a marker — a string that has to be present for the page to count as read. A page that answers 200 with a cookie banner and a menu is a failure, not an all-clear. Pages on the tax portal are cropped from "Artigo N" onwards, so a SharePoint redesign doesn't register as the law changing.
Scheduled, not real-time — the law moves on predictable dates: the budget in December and January, the IAS in December, rarely mid-year. Reading the source on a timer and having a person confirm it beats scraping on every request, which breaks without telling you.
Adding a source is one line — sources live in a JSON file, so watching something new is a data change, not a code change.
Where it went
A watchman that files issues is useful to one developer. The same engine, pointed at the people the law actually lands on, is a product — so it became one. Sentinela Fiscal watches the same official pages and sends a short email instead: what changed, whether it affects your tax regime, and what it is worth in euros for your case. The November 2026 one reads “IRS brackets up 3.88%” and, for fifteen thousand euros of taxable income, “about ninety-five euros a year less”.
Taking money changes what you have to build. There is a sole trader behind it with a tax number on the page, card payments through Stripe, invoices issued through the tax portal, fourteen days to cancel with no reason given, and a full refund if the service does not launch by 15 January 2027. The privacy notice names the controller, the legal basis and the fact that card details never reach me. None of that is code, and all of it had to exist before the first euro.
One decision shaped the rest: a person reads every alert before it is sent. The repetitive part — fetching, diffing, drafting — is software. The part where someone could act on a wrong number is not. That is slower and it does not scale, and it is the only version I was willing to charge for.
What I learned
Most monitoring tells you a system is down. The interesting kind tells you a system is now wrong — still up, still fast, still answering, just no longer true. Building the second kind meant deciding, in advance, what evidence counts as "I really did read the page", and then being strict enough to call a 200 a failure. The ordering of three steps turned out to matter more than the diffing itself.
The second lesson came later: the gap between a tool and a product is almost never the code. It was the refund policy, the invoice, the sentence explaining who is liable if the number is wrong. Writing those took longer than the watchman did.
Rapariga Social Club — Case Study
The question
Starting over costs money at the worst possible moment. Someone leaving a house has to furnish another one in a week, on whatever is left. The idea was an invite-only club where women pass on the furniture, the clothes and the things a restart needs — a marketplace where the community, not the catalogue, is the product.
What I built
An MVP of eight pages, a design system at v1.2, and a finished brand: a chrome tulip, "grow together, glow together", a deep purple that clears AA, copy in European Portuguese. The plan was deliberately staged — design and build, then a beta with five testers, then fifteen to twenty members, and only then money, trademark and a permanent domain. Product first, spend last.
- Eight pages plus a standalone flow, built against a documented token set
- Brand, emblem and voice closed before a line of marketing
- Payments, moderation and reporting obligations mapped before building any of them
- A written go/no-go date, set months in advance
Technical decisions
The riskiest part was never the code — it was holding other people's money. Taking payment between members means identity checks on every seller, invoicing the fee, and a legal shape for the whole arrangement. The plan was to run the first transactions by hand, with me as the clearing house, before writing a single line against a payments API.
Points that never leave the club — a closed, non-transferable balance keeps the thing from becoming something I am not licensed to run. That constraint came from reading the rules first, not from a feature meeting.
Moderation is a liability decision — a wall where members post reduces what I am responsible for in the transaction and increases what I am responsible for in the content. Those are different problems and they wanted different answers.
What I learned
At the go/no-go I went back to the file that said validation was complete — twenty contacts, around eighty-five per cent positive. It wasn't true. The twenty were twenty posts I had read, not twenty people I had spoken to. The three things I had genuinely verified were the brand, the domain and the handle: availability, not desire. The figure was even labelled "estimate" in my own notes, and the file meant to hold the feedback was empty.
Written down plainly: I was treating as validated what I had never tested, and as tested what I had only checked. The honest move was to stop, and the cost of stopping was one summer of design instead of a year of build. Everything I made — the system, the brand, the regulatory map — still exists and still works. What was missing was five real conversations, and that is a gap no amount of design closes.
What I did about it
So I went and got the conversations. raparigas.club is live and recruiting twenty beta testers — not a launch, a validation page. It asks for one thing, an application, and it says so at the top of the screen.
Building it forced the product to get specific, which the design system never had. Trust is a plant two members grow together, not a five-star average: a rating can be farmed in an afternoon, a plant takes two people and time. Entry is by a member's invite or a questionnaire read by hand. Handovers happen at public meeting points, so nobody has to give a stranger their address. And listings marked Recomeço — starting over — get priority and fair prices, because the person furnishing a flat in a week on whatever is left is the person this was for in the first place.
Those four rules are answers to the question I had skipped: what, concretely, makes this safer than the marketplace that already exists? None of them came out of the design system. They came out of writing a page that had to convince someone to apply.
Guest ops — Case Study
The question
A hundred-odd people, two messaging channels, a venue that had to be paid for up front, and a kitchen somebody had to fill. Run in a group chat, this is a week of answering the same four questions. The brief I set myself: know, at any moment and without asking anyone, who is coming, who has paid, and what is still missing from the table.
What I built
A guest pipeline in a spreadsheet — one row per person, one column per state they can be in — replacing the thread everyone scrolls. It is a small CRM wearing a party hat, and the design problems are the ones any outreach pipeline has: two channels with different delivery evidence, a funnel that only moves in one direction, and a money column that has to be reconciled against something real.
- One row per guest, with the channel the invitation went out on
- Delivery state kept separate from reply state — sent, delivered, read
- A reply column and a decision column, because "answered" and "coming" are not the same event
- A contribution column for the shared cost, and a column for what each person is bringing
- A free-text note per row for the reason — which is the only part a number cannot hold
Technical decisions
Delivered is not read, and read is not an answer — three separate states, because collapsing them is how you end up chasing someone who never got the message and ignoring someone who did. The channel with no read receipts gets its own state, rather than being guessed at.
One row per person, never per message — a guest invited on two channels is still one guest. The duplicate is a note on the row, not a second row, so the headcount can be trusted.
Decline with a reason — a no that records "away that weekend" or "working" is worth keeping; a blank cell is not. The reasons are what told me the real constraint was the date, not the plan.
Money is tracked, never assumed — the contribution column holds what actually arrived, so the budget is reconciled against transfers instead of intentions.
What I learned
The useful output was not the headcount, it was the funnel: how many invitations converted at each step, which channel answered, and which day of the week a reply arrives on. The same pipeline, relabelled, is the one I use for job applications — and the one any small team uses for leads.
The other lesson was about people: a tracker with real names, numbers and reasons in it is a privacy problem the moment it leaves your hands. This write-up describes the system and none of the guests, and the file itself never went anywhere it did not need to go.
Gallery
Twelve years of making things look like something. Pick a project.
pixel
ink and paint
identity
tourism and events
Pixel art · 2026 · the site you are on
bylx
The desk started as a loose scribble and ended up an interface. Three versions, from the first line to a scene of twenty-nine sprites that answer the mouse.
v0.1 · the sketch
Loose line over a purple and pink base. It fixes what never changed after: the CRT at the centre, the 日本 poster, the sushi boat, the glass of ice and the camera on the right.
v0.5 · first pixel comp
Translated into pixel art and dithering. Christ the Redeemer and the 25 de Abril bridge arrive in the window, along with the pink phone and the XP wallpaper. The bylx tag still took up the whole wall.
v1.0 · the room you can touch
The wall goes quiet and the brand becomes a watermark. In come the MP3 player, Pão de Açúcar, the Belém tower and the mascot on the CRT. Every object is its own sprite, recoloured at runtime for the day or the night palette.
Graphite · 2013 · SENAC
Smokers
Three graphite portraits from the drawing and illustration course at SENAC. The smoke is the exercise: it is the only part with no outline.
i
The smoke crosses the whole sheet, which forces you to work the white of the paper as if it were paint.
ii
High contrast, almost no midtones: the form resolves through solid black and clean paper.
iii
The opposite of the one before — all midtones, with black held back for the holder and the earrings.
Illustration · 2026 · in progress
Orixás
Sixteen orixás drawn from scratch for a mural of panels, each with its own iconographic research. Two are finished.
research
Before the line comes deciding what is correct to draw. The disc behind the figure is built from the vocabulary of the Yoruba beaded crown, not from a halo; the head follows the ere ibeji canon, one fifth and a half of the figure, because it reads better from ten paces and it is culturally right. References: the adé crowns, Rubem Valentim's Afro-Atlantic constructivism, Carybé's panels at the MAFRO, and the Oshogbo school.
Oxalá
The elder beneath the alá, with the greeting repeating behind him. The opaxorô belongs to Oxalufã alone; the adé with a fringe over the face is the royal convention, and it avoids the documented error of painting the skin white — the white is cloth, chalk and bead.
Oxóssi and Ogum
Bahia turquoise, not Umbanda green — the right question is which nation the house belongs to. The ofá is a metal bow and arrow, the eruquerê an ox tail in a leather sheath. Honey stays out of every panel: it is the central interdiction and has an itan of its own.
Poster · 2017 · UFRJ
SOS EBA
A campaign poster after the fire at the School of Fine Arts. I drew a modular typeface after the Bauhaus, where the composition lets you read SOS several ways at once.
the poster
The same blocks spell SOS and EBA depending on where the eye enters. I played with the spaces inside the word itself, and with focus: what is urgent is solid, the rest is outlined. Black and red because the subject is fire and ash — there was never a third colour to argue about.
Cover · 2017 · UFRJ
The Catcher in the Rye
A cover redesign on the same principle as SOS EBA: the front is type alone, the illustration lives on the back.
front and back
The front is white with heavy black letters and no image. The illustration sits behind: the protagonist in profile, with the blurb set inside his head, showing a young man who thinks too much. The red is his rebellion, and it is the only colour allowed in.
Logo and motion · 2017
Fire in Rio
A logo for a startup gamifying fire safety training. The blue is Rio's, from the state flag — not the green and yellow you expect.
the logo
Every letter carries something of the city: the red extinguisher leans into the F, Christ the Redeemer opens his arms inside the R, and the O is the Copacabana pavement seen from above. The yellow flame closes it on top. The blue comes from the state flag.
the animation
The promo builds the logo piece by piece, then walks through the game's isometric sets — offices, classrooms, auditoriums — until the fire. The game art is not mine; the brand and the opening are.
Social · three clients
Social media · 2016–17
Thirteen pieces for three clients in Londrina: a Korean restaurant, an aesthetics clinic and an imaging clinic. Square format, one idea per piece.
Hanguk House
The restaurant changed its name from Korean House to Hanguk House partway through, so the announcement had to work as a handover, not a launch. The rest alternates between explaining — what soju is, what bibimbap is — and converting, with the check-in discount.
AestheticDerm
An aesthetics clinic, in a calmer register: light type, a lot of air, and skin photography. The pet-friendly mall piece is the only one out of key, and that was on purpose.
Foco Imagem
An imaging clinic. The job here was explaining scans to people who are afraid of them, so the language is a manual's, not an advert's.
Email · 2014 and 2024–25
Internal newsletters
Four internal newsletters, ten years apart. All of them were made to be read in a work inbox, which is the hardest place to design for: no fonts you chose, images off by default, and a reader who opened it between two meetings.
the monthly letter · 2024–25
Two issues of the same monthly letter, eight weeks apart and unrecognisable from each other. December is flat vector, primary red and green, hard-edged banners. February is watercolour, washes, hand lettering. The structure underneath is identical — editorial, achievements, then the same four standing sections — and that is the point: the skeleton holds while the skin changes with the month, so the thing never feels like a template even though it is one.
The content is the ordinary stuff of a company letter — professional development, culture, wellness, a Portugal section, the team — and the job was to make people read it anyway. The names and the logo are painted out in these copies.
Click Rank · 2014
A weekly team ranking, ten years earlier. Trophies for the top three, then a table by criterion — effectiveness, planning, deadline, cooperation, punctuality — and a prize at the end. The hierarchy had to read on a small screen with images switched off, which is why the ranking is type and colour blocks rather than a graphic.
Collection concept · 2014
Predictions of the Future
A collection concept from the fashion production course: theme, audience, palette, materials, and the pieces, from basic to conceptual.
the theme
Predictions of the Future: divination, cards, crystal balls, palmistry. The board gathers the imagery of the oracle before a single piece is drawn.
the audience
An audience board for women, summer 2015 — where that person eats, where she travels, what she watches.
palette and materials
Eleven named colours, and the list of fabrics, trims and finishes: cool knit, chiffon, crystal organza, lace; digital print, sublimation, silk-screen.
the pieces
Four plates, each carrying the four tiers of the collection: day-by-day, basic, fashion and one-off. The conceptual one closes with the crystal-ball dress and the gold appliqué.
Brand and production · 2026
GiraZuka
A channel built end to end: brand, a rigged mascot, an illustration library, scene templates, thumbnails, an ident and the edit.
the brand
The wordmark is one continuous ribbon weaving Portugal's red and green into Brazil's yellow and blue — the channel's premise in a single drawing. The system fixes six named colours and two typefaces: Fraunces 900 for titles, Inter for everything else.
the mascot
Mini Aline, with a rig in five versions and fifteen drawn, labelled expressions. Each expression has its own animation, exported as mp4 with a background and webm with alpha.
the video system
Four categories, each with its colour and its thumbnail. Plus eight scene templates, the ident and six chapter transitions.
the illustrations
Around sixty vector illustrations, for everything there is no photograph of: the Lisbon waterfront after 1755, a baptism at a stone font, maps, ships, a family tree.
Teaching · Lisbon
Illustration workshops
Illustration workshops with materials bought in primaries only: cyan, magenta, yellow, black and white. Everyone mixes the rest.
the exercise
The twelve-step colour wheel is the first exercise and it settles half the questions of the day: once you have made one with your hands, nobody asks how to reach a tone.
the table
Materials laid out before anyone arrives, one palette per person. Outdoors whenever the weather allows.
Event production · 2018
Notice Me Senparty
Producing a party, run jointly with one of the DJs. The pixel art in the scene came from elsewhere; the flyers, the promo and the event itself are mine.
the square flyer
A neon street at night with the party's name in a speech bubble. The square cut is the one that went out as a post.
the vertical flyer
The story format carries what the square one could not fit: date, time, venue, and the discount code for buying early.
the promo
Fifteen seconds that travel down the street while the speech bubbles arrive one at a time — today, at eleven, the name, the address. The information lands in the order someone actually needs it, instead of all at once.
Feedback
Five quick questions and one box. No account, no email needed — it takes about a minute and it genuinely changes what I build next.