Bit-Er Devs Agency Site (past engagement)

The brief

A past engagement, not a current employer: I worked with Bit-Er Devs from June 2024 to July 2025, first as a UI/UX designer and then as a web developer. This is the marketing and services site we published at biterdevs.com, with service pages, a technical blog and case studies wired to programmatic schema and generated sitemaps.

Problem

The team was selling web work with a website that could not publish its own content. Every new case study or blog post needed a developer, so the marketing side of the agency ran slower than the delivery side. The site also had to be findable, which meant real technical SEO rather than a plugin.

My role

I joined Bit-Er Devs in June 2024 as a UI/UX designer and moved into web development on the same team, ending in July 2025. I owned interface design and front-end delivery: the service pages, the case-study and blog templates, the responsive component library and the on-page SEO setup. Bit-Er Devs is a past engagement, not a company I run or work for today.

Process

• Started from the content model: what a service page, a case study and a post each needed to carry
• Built a reusable component library and design tokens so three page types looked intentional without three separate layouts
• Wired structured data, generated sitemaps and canonical URLs into the templates instead of adding them page by page
• Agreed a load budget with the team before launch and treated anything that broke it as a bug
• Ran a design-to-development handoff process so the next person could ship a page without me

Result

A published agency site where a non-developer can add a case study or a post and get the full template: structured data, canonical tag, sitemap entry and social image. The outcome I can stand behind is process, not a metric: the content pipeline worked, the design system held across page types, and the SEO scaffolding came from the templates instead of being retrofitted later. The engagement ended in July 2025. Two years on, the parts I would still defend are the structured data helpers and the shared component library, because both outlived the launch: the schema work kept the site eligible for rich results, and the tokens meant a new service page was a content job rather than a design job.

What it had to do

• Blog and case-study publishing pipeline for the team
• Programmatic schema plus high-contrast responsive UI
• Core Web Vitals budget agreed with the team before launch

Stack

• Next.js
• React
• TypeScript
• Tailwind CSS
• Technical SEO