Project case study
PixelTool
How a bookmarks folder grew into a catalog of free tools
Technology stack
- Typescript
- Next.js
- shadcn/ui
- Tailwind CSS
- Vitest
A password generator, a unit converter, a QR code for a link. Small things like these come up every day, and bookmarks to them soon overflow the browser toolbar. PixelTool started as a single page where these tools were collected as needed. Over time the set grew into a full catalog.
Everything at hand
The first tools were written for internal use. Once there were a few dozen, the site opened to everyone with a simple rule: each widget solves one task and starts working as soon as the page opens.
New tools appear for one of two reasons: a task that came up at work, or a query that surfaced in search statistics.
The catalog and the tools
Tools are grouped by topic: development, text, images and PDF, finance, health, construction, cars, and even esoterics. The right one is a search or a category click away.
Each tool returns a result right away. The QR code redraws while you type the link. A new password takes one click, and right next to it is an estimate of how long it would take to guess by brute force. It shows at once that the longer the password, the stronger it is.
Images are compressed right in the browser, and the file stays on the user’s computer. A quality slider and a live size comparison show how many kilobytes were saved.
One registry for all the tools
The stack is Next.js, TypeScript, Tailwind CSS, and shadcn/ui. Every tool is described in a single registry, which automatically builds the catalog, categories, navigation, the list of pages for search engines, and related-tool blocks. A new widget shows up in all of them on its own.
A new tool is built from a ready template: a script creates the page skeleton, and only the calculation itself remains to be written. Before release, the code is checked for type errors, vulnerabilities, accessibility, and speed. The AI assistants Claude and Codex take part in both the code and the copy.
Search
Almost all traffic comes from search, so every tool has its own page with a clear URL and an explanation of the task. Queries with small and medium demand are grouped, and page impressions and clicks are regularly checked against demand.
The blog answers the questions that come up after a calculation, such as how compound interest works or why 0.1 turns into an endless fraction in binary.
Outcome
From a folder of bookmarks, PixelTool grew into a catalog that fills up with little effort. A new tool goes into the single registry, and the site shows it in the catalog, in the navigation, and in the list of pages for search engines on its own. The template and the checks before release let pages ship quickly and with the same quality.
In three months the site gathered several thousand visitors, and almost all of them came from search engines. People find a tool for their task by a specific query, and the blog answers the questions that come up after a calculation.
The result is a service where every page solves one task and finds its own reader through search. The scheme scales simply: the more tools there are, the wider the range of queries it covers.
Have a similar task?
Tell us about it and we will find the solution together, from the idea and design to launch and support.
Or write directly