All work

Project 04Agency website · CMS · Live

Leqta

Leqta is a content marketing and film production agency in Algiers. They needed a site that looks as polished as their videos and that their own team can update. I built the website and its CMS, and I run the server it lives on, along with the team's 12 mailboxes.

Client
Leqta, Algiers
What I delivered
Website, CMS, hosting, email
Languages
English, French, Arabic
Stack
Next.js, Strapi 5, MariaDB
leqta.com
leqta.com home page
Home page, desktop and phone.
leqta.com on a phone
[01] // WALKTHROUGH

45 s walkthrough · pages, three languages, the phone layout and the stack behind it · made with HyperFrames

[02] // WHAT_I_BUILT

A showcase the team keeps up to date

Services that sell

Each offer, from content marketing to ad production, has its own clear section and call to action.

Edited in Strapi

Pages, services, partners and blog posts come from the CMS, in all three languages.

Fast by default

A standalone Next.js build served behind nginx, with HTTPS forced everywhere.

Consent the law asks for

Analytics and ad pixels wait for the visitor's consent, as Algerian Law 18-07 requires.

[03] // THE_CMS_BEHIND_IT

18 content types, one admin, three languages

The whole site is driven by a Strapi 5 backend I designed for the team. Every page, offer and post is an entry they can edit, translate and publish without a developer.

marketingServices & offersServices (with gradients, icons and video), pricing plans with sections, projects, partners, testimonials, missions, FAQ
contentBlogPosts with header and inline images, authors, categories and tags
leadsInboundNewsletter subscribers and partner requests, saved with consent and a status to follow up
site-wideSettingsContact details and social links, privacy policy, cookie consent texts, tracking pixels
REST API · 31 custom endpoints · EN / FR / AR
cms.leqta.comStrapi 5
i18n · drafts & publishing · media library · OpenAPI docs
MariaDBin production, on the HestiaCP server
PostgreSQLfor local development, same schema
Next.js front endreads the API; a revalidation endpoint refreshes it on publish
[04] // WHAT_THE_CMS_DOES

More than a content store

Changes show up instantly

Lifecycle hooks tell the Next.js site to refresh exactly what changed, so updated settings, consent texts or pixels go live without a rebuild.

One entry, three languages

15 of the 18 content types are translated inside the same entry, so English, French and Arabic never drift apart.

Marketing owns its pixels

Google Analytics, Meta and TikTok IDs are switched on and off from one settings screen, and only load after consent.

Leads land in the admin

Newsletter sign-ups and unsubscribes (re-joining reactivates the address) and partnership requests, each with a follow-up status.

Clean URLs by default

Service slugs are generated from their titles, so the team never has to think about URLs.

Rebuildable and monitored

13 seeders recreate a complete site for testing, and a health endpoint reports database latency for monitoring.

[05] // INSIDE_THE_ADMIN

What the team sees when they log in

The real Strapi admin, run locally with the project's own seed content and clearly fictional demo values.

Strapi Content Manager listing the services, each available in Arabic, English and French
Content ManagerEvery service, in three languagesServices with their colours, order and publishing state; each one exists in English, French and Arabic.
A service edited in its Arabic version
LocalisationSwitch the entry to ArabicThe same service, edited in Arabic from the locale switcher, with its own title, description and content.
Service editor with icon and featured images and two colour pickers
EditorBrand colours without codeIcons, images and the card gradient are picked in the editor, so the team restyles a service on its own.
Tracking Pixels settings with IDs and on/off toggles
Single typePixels switched on and offGoogle Analytics, Meta and TikTok IDs with a toggle each (demo IDs shown).
Content-Type Builder showing the fields of the Service type
Content-Type BuilderA content model built for themEach of the 18 types is designed around what the team needs to publish, field by field.
Swagger API documentation listing the service endpoints
API docsDocumented APIOpenAPI documentation generated from the schema, so the front end and any future app share one contract.
[05] // HOSTING_AND_MAIL

The site, the CMS and the team's email, all looked after

Leqta's website, CMS and 12 mailboxes moved to a new HestiaCP server in October 2026 with every email accounted for. The team manages its own corner from its own panel.

  • leqta.comNext.js website
  • cms.leqta.comStrapi 5 + MariaDB
  • webmail12 mailboxes, Roundcube
  • panel.leqta.comTeam's own HestiaCP login
Next project · 05Stage Color Cosmetics