Case study · Web development

I rebuilt a messaging company's main website on my own, and I still run it

Sole designer and developer on ritorica.com: Figma file, Django CMS build, launch, server and everything since. First commit June 2026, in production ever since. It is now the company's single main site, and it carries the Arabic and Bengali versions.

  • Role: the only designer and developer, from the Figma file to the production server
  • Stack: Figma, Django CMS, PostgreSQL, HTML/CSS/JS, Gemini API, GitHub Actions, Linux, key-only SSH
  • Timeline: first commit June 2026, maintained since
  • Live: ritorica.com
The ritorica.com home page on desktop.
The home page today. The source code is private: it belongs to the company.
What this proves: I can own a company's public website end to end on my own. Design, build, launch, security, and the unglamorous fixes afterwards.
June 2026first commit, and in production ever since
8 weeksSEO and GEO checklist, tracked in Search Console
1 per countrypages in the coverage catalogue
3 languagesEnglish, Arabic and Bengali versions, on one site

The job

Ritorica sells business messaging: SMS, WhatsApp, Viber, Telegram and push. The website has to explain that to buyers, let the team edit pages without a developer, and turn visitors into leads.

What I built

  • Design in Figma, then turned into HTML, CSS and JavaScript templates.
  • Content management on Django CMS, so pages can be edited in the browser. PostgreSQL in production.
  • Lead capture: contact forms, demo requests and newsletter sign-up.
  • An AI chatbot on the Google Gemini API that answers visitors' questions.
  • A coverage catalogue with one page per country, at /messaging/.

I build with Claude Code as a pair programmer. I make the decisions, review every change and own what ships.

After launch

  • It is now the company's single main site, and it carries the Arabic and Bengali versions.
  • I audited the UX of my own live site and scored it 6.4 out of 10. Then I fixed what the score exposed: dead buttons, leftover placeholder text, and statistics that contradicted each other between pages.
  • The site was close to invisible in AI search, so I wrote an SEO and GEO strategy with an eight-week checklist and reported progress through Search Console.
  • I added an events section covering the company's past events.

Shipping and running it

  • Deployed to a Linux server. Changes go live automatically through GitHub Actions, with a systemd timer as a second route.
  • The server only accepts SSH keys, and deploys use their own key.
  • I wrote the production runbook: what is configured, how to deploy, how to check it worked.
  • I worked with the company's system administrator on server access and DNS.

The bug that taught me the most

For almost three weeks the deploy pipeline showed a green tick on every run. Nothing was actually deploying.

The deploy script didn't stop on errors, so each failing step was skipped quietly and the run still reported success. Underneath, the deploy key was broken, an old firewall step timed out for GitHub's servers, and the restart command couldn't run without a password.

I found it by comparing the commit running on the server with the last one I had pushed. Then I replaced the key, removed the step that timed out, gave the deploy user only the permissions it needs, and made the script fail loudly.

Lesson: a green pipeline is a claim, not proof. Check what is actually live.

What I'd do differently

Add a check at the end of every deploy that compares the live commit with the pushed one, from day one. It's a few lines, and it would have caught the silent failures on the first run.

The ritorica.com home page on a phone.
The same page on a phone.

← All work