Case studies.

The interesting part is that this is a migration, not a greenfield build. The original explorer is a 46-file PHP application still serving live traffic, and the new app has to take over route by route without a flag day. The nginx layer routes new app paths to Node and leaves the legacy tree on php-fpm, so both run side by side while the migration completes.

Every new block triggers a city pulse: building lights ripple, vehicles move, particles spawn near validator nodes. Synchronising that with a live 3D scene without dropping frames meant batching DOM updates and pre-allocating vehicle pools rather than allocating per frame.

Used as the public face of the mainnet launch.

The knowledge base is tourism office leaflets, county pages, restaurant menus and festival programmes, refreshed weekly by a cron job pulling RSS plus manual uploads. The retrieval layer was written rather than bought, so the answers stay inside the county's own material instead of drifting into the model's general knowledge.

The tourism office uses it as a first-line FAQ.

A stock WooCommerce theme collapses at this catalogue size. Variant rendering was rebuilt with batched AJAX, a pre-warmed product cache and a chunked search index.

The client's admins now run the whole catalogue from the WordPress dashboard, without a developer in the loop.

Public-sector work has a particular constraint: a county homepage is read by people using screen readers, older browsers and cheap phones on rural connections, and none of them are optional. Calendar cells that fall outside the month render as blank, disabled, non-focusable cells rather than as decorative noise a keyboard user has to walk through.

The v2 homepage is built and reviewed and is going through client sign-off. It carries placeholder dates in the calendar which must be confirmed before they reach production - recorded in the handoff rather than left to be discovered.

The hard part of a Web3 shop is not the wallet - it is making a wallet checkout sit beside an ordinary card checkout without the ordinary customer noticing anything unusual, and without the crypto path becoming a second, unmaintained storefront.

The page template builds its own sticky table of contents from the H2 headings in the body, so an editor writing a long page gets working in-page navigation without touching a plugin or a shortcode.

Every Customizer field ships with the design's exact Croatian default text, which means the site is complete and correct on the day it is handed over rather than a set of empty boxes for the client to fill.

Fashion retail is where stock themes usually show: a look book, a size guide and a variant picker each want a layout the theme did not anticipate, and the usual answer is a page builder that adds weight to every page on the site. This one is built from the design instead.