Leviro Brand Website

This is the website of Leviro, Abdelrhman Diab's software brand. Visitors can read about the brand, browse its product pages, and send a contact request. Arabic and English pages have their own routes. The site presents product information from content files.

The problem

A brand site must explain several products without mixing their status or audience. It also needs Arabic layouts, language-aware search metadata, and a contact path that works when browser scripting is unavailable. Leviro's site uses a shared content structure for product details and serves both language versions from a static build.

Key features

• Locale-prefixed home, product, about, contact, legal, and error pages serve Arabic and English readers.
• Product pages are generated from content entries with status, audience, features, workflow, FAQs, and calls to action.
• A root visit redirects according to the browser's Accept-Language preference, with Arabic as the fallback.
• Canonical, hreflang, sitemap, and structured-data output support page discovery.
• The contact form validates fields in the browser and on the server.
• The form also submits without JavaScript and redirects to localized success or error pages.
• Contact requests are forwarded to Telegram after validation.
• A local audit checks generated pages and source styles for SEO, resource, and RTL issues.

Technical architecture

Astro builds the localized pages from Markdown, MDX, and YAML content collections. TypeScript components and Tailwind CSS build the interface. Express serves the generated files, negotiates the root language, and handles the contact API. The contact route validates input, checks the request origin and a honeypot field, applies an in-memory per-IP rate limit, then forwards accepted messages to Telegram. A shared alternates helper supplies both page metadata and sitemap links.

Engineering highlights

• The content collection schema rejects malformed product and page data during the build.
• Content Security Policy and other response headers are set by the Express server.
• The proxy-trust parser avoids unsafe forwarded-IP settings that would undermine rate limiting.
• A source lint and generated-site audit check RTL and language metadata.