We build fast, server-rendered websites on Next.js and SvelteKit, connected to Prismic so your team publishes in English and Arabic without waiting on a developer.
What is included in Next.js and SvelteKit development?
Next.js and SvelteKit development covers planning, building and launching a server-rendered website connected to a headless CMS. At Cairo Studio that means a content audit, Prismic slice modelling, design and build in TypeScript, bilingual routing for Arabic and English, an SEO and performance pass, and a handover where you own the code and accounts.
Frameworks
Next.js with React and TypeScript
SvelteKit with TypeScript
Server rendering and static generation
API routes and form handling
Tailwind CSS component systems
GSAP and Three.js motion
+
Headless CMS
Prismic slice modelling
Custom page types and relationships
Draft previews
Content migration from old sites
Editor training
+
Bilingual and SEO
Arabic and English locales
Right-to-left layouts
hreflang and per-language sitemaps
Structured data
Redirects from old URLs
+
Hosting and handover
Deployment from Git
Managed hosting or your own server
Domain and environment setup
Code and CMS documentation
Ongoing maintenance
=Next.js and SvelteKit Development
Overview
Next.js and SvelteKit websites with a headless CMS
Next.js and SvelteKit development is how we build most client websites at Cairo Studio. Both frameworks render pages on the server, send lean code to the browser and pair cleanly with a headless CMS. The result is a site that loads quickly, reads well to search engines and stays easy to change after launch.
This approach suits companies that have outgrown a page builder or a heavy WordPress theme, marketing teams that publish often and are tired of filing a ticket for every edit, and businesses in Egypt and the Gulf that need Arabic and English as equal languages rather than a translation plugin added later. If your site is a few static pages that rarely change, a simpler setup may serve you better, and we will say so.
01 / 04
What Next.js and SvelteKit development involves
We write the reasoning down with the code.
Both frameworks are mature and both support server rendering, static generation and server-side API routes. Next.js is built on React, so it fits teams that already work in React or plan to hire for it, and it has the larger ecosystem of libraries. SvelteKit compiles components into plain JavaScript, which keeps bundles small and the code short, and it is our usual choice for content-led sites with a lot of motion.
We choose based on your team, your integrations and who will maintain the code after handover, and we write the reasoning down. 32 Real Estate, a bilingual property platform for a Saudi developer with an interactive map, runs on Next.js. MASAR, a Cairo business law firm with Arabic and English as equal locales, runs on SvelteKit.
02 / 04
A headless CMS website your team actually runs
Built so pages load fast on any connection.
We pair the front end with Prismic. Content lives in Prismic, code lives in your Git repository, and the two meet through an API. Editors build pages from slices we design around your brand, such as heroes, case studies, team grids and FAQs. They can reorder sections, preview drafts and publish without touching code or breaking the layout.
Slices modelled on your real content, not a generic template
Separate English and Arabic locales, each with its own URLs
Preview links so drafts are reviewed before they go live
SEO titles, descriptions and share images editable per page
03 / 04
Server rendering, SEO and bilingual routing
You own the code and the hosting.
Every page is rendered on the server, so search engines and link previews receive complete HTML with titles, descriptions and structured data already in place. We set up clean locale routes such as /en and /ar, hreflang tags, a sitemap for each language, and right-to-left layouts that mirror properly instead of only flipping the text direction.
Arabic gets its own typography and spacing decisions. Lines that mix Arabic with English names, numbers and product terms are handled so they read correctly in both directions.
04 / 04
Hosting, handover and ownership
We write the reasoning down with the code.
We deploy to a managed platform or to a server you control, depending on traffic, budget and where your data needs to live. Builds run from your repository, so every change is tracked and can be rolled back. At handover you receive the code, the Prismic repository, hosting access and notes on every slice. You own all of it. We can stay on for maintenance, or your developers can take over a clean TypeScript and Tailwind CSS codebase.
Here is what goes into a Next.js or SvelteKit build with Prismic, and the order we do it in.
A→B
How we work
01
Content and stack audit
We map every page type, every content field and who edits what. We review your current site, your integrations and your team's skills, then recommend Next.js or SvelteKit with the reasons written down. You see the trade-offs, including hosting and maintenance, before any code is written.
A→B
02
Content modelling
We design the Prismic structure: page types, slices, shared fields such as navigation and footer, and how English and Arabic versions relate to each other. Good modelling is what stops editors from breaking layouts later, so we test it against your real content, not placeholder text.
03
Design and build
Pages are built as components that match the slices one to one. We set up server rendering, locale routing, right-to-left layouts and GSAP animation where it serves the content. Each slice is built and reviewed in both languages, with real copy, before we mark it done.
04
SEO and performance pass
Before launch we check titles, descriptions, hreflang, sitemaps, structured data and redirects from old URLs. We run Lighthouse on the key templates, size images correctly, review font loading and trim scripts, so the site starts fast and stays crawlable in both languages.
05
Launch and handover
We deploy, connect the domain and watch the first days of traffic and indexing. Your team gets a Prismic training session and written notes for each slice. You receive the repository and every account, and we agree on maintenance or hand over cleanly to your own developers.
Selected work0123/ 03
Web Development, UI/UX Design, BrandingUI/UX Design, Web Development, Creative DirectionWeb Development, UI/UX Design, E-commerce
It depends on the number of page types, the slices your editors need, how many languages you publish in, and integrations such as forms, CRMs or a shop. Custom animation and 3D add time. A content site with a handful of templates costs less than a platform with accounts and APIs. We quote after scoping your content model.
141516---
1718
#
If your team already writes React or depends on React libraries, Next.js is the safer choice. If you want smaller bundles and less code for a content-led site, SvelteKit fits well. Both perform and rank well when built properly. We recommend one after looking at who will maintain the site after launch.
192021---
2223
#
A headless CMS separates content from code. Editors get a clean interface built around your own sections, developers get a modern codebase, and the site is not weighed down by themes and plugins. Prismic also handles locales, previews and image delivery. WordPress still suits some teams, and we will tell you if you are one of them.
242526---
2728
#
Yes, that is the point of the build. Editors add pages, reorder slices, swap images and publish in English and Arabic from Prismic. What they cannot do is break the design, because each slice controls its own layout. New kinds of sections still need a developer, and we add them as you grow.
293031---
32
#
It depends on the number of templates, how ready your content is and how quickly feedback comes back. Content is often the deciding factor: projects stall waiting for copy and photography more often than for code. We set a schedule after the content audit and share progress on a live preview link throughout.
333435---
3637
#
Fully. Arabic is set up as its own locale with its own URLs, metadata and sitemap, and layouts are built to mirror for right-to-left reading. We choose Arabic typefaces deliberately and handle mixed Arabic and English text so names and numbers read correctly. MASAR, for example, runs Arabic and English as equal locales.