PC Guru: a bilingual website for a repair workshop
A bilingual website for a computer repair workshop in Covasna. Customers find the repair they need in Romanian or Hungarian and send a request straight to the bench.
- Romanian and Hungarian, each page at its own address
- RO · HU
- repair services, each explained on its own page
- 7
- PC Guru's Google rating, shown live on the site
- 5.0
A workshop customers search for in two languages.
PC Guru repairs PCs, laptops, tablets and consoles from a workshop on Strada Gheorghe Doja in Covasna. The county is bilingual, so people look for a repair shop in Romanian and in Hungarian — and the business also runs a separate online shop. The site had to serve both languages equally and turn a search into a repair request.
- Romanian and Hungarian, each with its own addresses
- Every repair explained on a page of its own
- One clear way to send a repair request
Everything the workshop does, on one site.
Built with the same tools as this site: Next.js on the front end and Payload CMS behind it, so the PC Guru team can edit every page themselves.
Two languages, two sets of addresses
Every page exists in Romanian and in Hungarian, each with a translated address of its own, rather than one language bolted onto the other.
Seven service pages
Repairs, board-level work, component replacement, cleaning, data recovery, IT maintenance and diagnostics: one page each, not a bullet list.
A request form that reaches the workshop
Device, service and a description of the fault, so the first reply can already be a useful one.
Their Google reviews, live
Read from their own Google listing and shown on the page, rather than retyped into it by hand.
Address, opening hours and a map
The workshop on Strada Gheorghe Doja, its opening hours and directions, shown where people look for them.
Consent handled properly
A cookie banner that genuinely controls what loads, and a privacy policy that describes what the site actually does.
Every repair explained on its own page.
Someone searching for data recovery lands on the data recovery page, not on a general list. Each page says what is fixed, how it works and how to ask for it, in both languages.
- Written the way customers search
- A clear next step on every page
- Built to read well on a phone
After launch, we keep it running.
The build was the start of the work, not the end. The site is on the same care plan as every site we look after.
- Monthly CMS, dependency and security updates, tested before they go live
- Daily off-site backups, kept away from the server they came from
- Uptime and security monitoring, so a problem is ours to notice, not theirs
- A short monthly report in plain language