Credibility through product
The site itself is proof: localized content, API, back-office, realtime, SEO and coherent documentation.
Public documentation
What Bz Info proves as a product system.
An editorial view of the portfolio architecture: multilingual frontend, NestJS backend, realtime chat, first-party analytics, admin and quality discipline.
Respectful by design
Interactions stay useful, measured and privacy-first, without aggressive tracking or intrusive UI.
Maintainable structure
Content, routes, components and contracts are separated so the platform can evolve cleanly.
Reading map
The sections follow the real path from public system to operations.
01
Frontend
Pages remain orchestrators. Public copy lives in localized modules, slugs are centralized and the sitemap exposes alternates.
02
Backend
The backend handles contact, availability, chat, chatbot, leads, notifications, audit logs and first-party analytics.
03
Admin
The admin covers requests, leads, conversations, availability, monitoring, logs and useful statistics.
04
Quality
Quality targets risk: typecheck, lint, build, module tests, smoke flows and environment documentation.
Useful documentation links site, API, admin, quality and decisions.
Documentation connects what the public site says, what the API guarantees, what admin workflows operate and what quality reports make decidable.
01
Public site
Messages, SEO pages and visible proof.
02
API contracts
Routes, forms, validation and expected errors.
03
Admin workflows
Operational reading of requests and content.
04
Quality reports
Build, typecheck, URL audit and weak signals.
05
Decisions
Product priorities, risk and production readiness.
Frontend
Next.js, typed content and multilingual SEO
Pages remain orchestrators. Public copy lives in localized modules, slugs are centralized and the sitemap exposes alternates.
fr/en/ar/es/de/nl routes with stable logical mapping.
Arabic RTL at document level with compatible layout treatment.
Page-level metadata, canonical, hreflang and Open Graph.
Backend
NestJS API for conversion and operations
The backend handles contact, availability, chat, chatbot, leads, notifications, audit logs and first-party analytics.
Validated DTOs and Swagger documentation.
Socket.IO realtime for visitors and admins.
No AI key or sensitive secret exposed to the frontend.
Admin
Product back-office for system supervision
The admin covers requests, leads, conversations, availability, monitoring, logs and useful statistics.
Dedicated admin authentication.
Realtime support conversations.
Decision-oriented analytics instead of vanity counters.
Quality
Pragmatic validation with production awareness
Quality targets risk: typecheck, lint, build, module tests, smoke flows and environment documentation.
Real validation scripts from the monorepo.
Existing API contracts preserved.
Internal docs kept separate from public documentation.
Living architecture
This public documentation shows engineering discipline without exposing secrets.
For an audit, backend mission or complete product platform, the contact page is ready for context.