NanoPrint

The project
nanoPrint makes custom t-shirts, company swag, storefront signage and vehicle decals. The business serves a region where customers speak Romanian or Hungarian, and it had no brand and no web presence: no logo, no photos, no site. The goal was a single page that shows the work and moves visitors to one action, requesting a quote.

Brand
I started with the constraints of the trade. The logo would be plotter-cut in vinyl, embroidered on hats and screen-printed. So it had to work in a single solid color, with no gradients or hairline details. I explored four directions and chose a monogram: a bold "n" in a rounded tile with a single square "pixel". In the one-color version, the "n" and the pixel are real cut-outs, and I spaced the pixel so the cut vinyl never leaves a strip too thin to weed.

For color, I paired ink black with process magenta, the "M" in CMYK. It signals printing to anyone in the trade and stands apart from local competitors. I also avoided color combinations that echo either national flag. The type is Oswald for headings and IBM Plex Sans for body text, and every accent color was checked against WCAG contrast.

Website
The site is a single page: hero, services, a four-step process, portfolio, testimonials and a quote form. It runs fully in Romanian and Hungarian. Each language has its own URL (/ro/ and /hu/), with hreflang tags so both are indexed, and all copy lives in translation files rather than in the code.

• Stack: Astro (static output), plain CSS built on design tokens, and almost no JavaScript.
• Privacy: fonts are self-hosted, and there are no cookies or third-party scripts, so the site needs no cookie banner.
• Quote form: it posts to a small serverless backend (API Gateway, then Lambda, then Amazon SES), defined in AWS CDK. It has server-side validation, a honeypot field against spam, and CORS limited to the site's own domain.
• Hosting: AWS Amplify, deploying automatically from Git.

How I built it
I used AI tools throughout, with me setting direction and making the decisions. I designed the brand, the layout and the copy with Claude, iterating on a shared design canvas. It also produced the vector logo package, the social media assets and the bilingual privacy policy.

For the code I used Kiro's spec-driven workflow. I wrote "steering" files that fixed the brand rules, stack, folder structure and language rules. Then I ran two specs, one for the frontend and one for the backend and deployment. In each I reviewed the requirements, design and task list before Kiro wrote anything, and checked each task's output as it went.