Mohammadreza Talebi

Fargah.ir

A bilingual Laravel platform for architectural stone—connecting executed work, ready projects, material knowledge, editorial content, and qualified inquiry.

View live siteExplore the project

By Mohammadreza Talebi · 6 min read

fargah.ir
Architecture and material-led homepage · Live website capture
Year
2026
Role
Design / Laravel development
Scope
Bilingual · Content · CRM
Status
Live

The project, in context

I designed and developed Fargah.ir as a specialist architectural-stone website: a place to examine built work, explore facade references, read material information and begin a useful conversation with the team. The Laravel platform brings bilingual presentation, an editorial library and structured enquiries together, while retaining the routes and content inherited from the earlier website.

Helping an architectural decision take shape

The audience arrives with different questions. A homeowner may need a starting point for a villa facade; an architect may be looking for dimensions, component families or a comparable executed project. A gallery alone cannot serve both. I needed to organise those questions into clear routes without turning a visually expressive brand into a dense technical directory.

The earlier WordPress site also carried an existing archive of projects, articles, media and incoming URLs. A redesign had to make that material readable again while avoiding broken journeys. Another important boundary was evidence: photographs demonstrate appearance, whereas laboratory reports and certificates have their own limited scope. The website needed to preserve those distinctions in its wording and navigation.

A clear path from reference to enquiry

I shaped the public experience around three starting points: executed projects, the stone catalogue and bespoke facade design. Large images establish the architectural character, while concise descriptions explain what each route offers. The cream, dark and gold palette stays consistent across pages, with Persian reading direction and mobile spacing treated as part of the layout rather than a translation applied afterwards.

The design enquiry records context such as city, project type, style, approximate area and chosen references. The request is stored as a lead and enters the team's follow-up workflow. Alongside that path, I organised legacy content, canonical URLs, language alternates and sitemap generation, and built editorial pages that let visitors inspect the relevant report or document before making contact.

What I built

The parts that make this project useful in day-to-day work.

  1. Executed-work library

    A dedicated archive presents completed facades with project pages, photographs and video sections. It gives a visitor a visual reference before the design conversation and keeps project material separate from general brand imagery.

  2. References for a new design

    Ready-project browsing and reference selection offer a starting point for a new facade. The chosen reference can travel with the enquiry, so the team receives the visitor's intended direction rather than a vague request for a similar-looking building.

  3. Catalogue and useful documents

    The catalogue experience brings component information and downloadable material closer to the project journey. Dedicated laboratory-report and certificate pages provide context for the original documents instead of leaving visitors to interpret an isolated badge or image.

  4. Structured design enquiry

    The enquiry form captures contact details and project context, including location, project type, style and selected references. Validation and clear confirmation states support the handoff to the team without requiring the visitor to write a complete technical brief unaided.

  5. An editorial knowledge layer

    Articles and practical guides cover topics such as choosing modular facade stone, preparing a villa-design brief and reading evidence. This content connects the visual catalogue to the questions people actually ask before ordering or consulting.

  6. Language and search foundations

    Persian and English routes use language-aware navigation and page metadata. Canonicals, alternate-language links, structured data, sitemaps and legacy URL resolution support a readable content structure without claiming guaranteed rankings.

From structure to release

  1. Map the decision

    I separated inspiration, material research and bespoke-design intent, then organised the navigation around those needs. Each page needed a useful next step, not simply another block of photographs.

  2. Build presentation and continuity

    I implemented the Blade layouts, bilingual patterns and enquiry flow alongside the content migration and legacy route handling. The visual system and the operational handoff were developed as related parts of the same site.

  3. Refine real reading conditions

    I refined title hierarchy, card descriptions, image framing and light-theme readability across layouts. Public documents and editorial copy were reviewed for scope so the presentation remains understandable as the content grows.

Delivery and current scope

  • A Laravel and Blade website with Persian and English public journeys.
  • Executed projects, ready-project references, catalogue pages and a structured design enquiry.
  • Editorial guides, document pages and a search-readable content structure.
  • Legacy URL handling and a connection from public enquiries to the internal CRM.

Questions about this project

Is Fargah.ir a complete online shop?

The main journey is consultation, catalogue exploration and design enquiry. Product-catalogue and showroom code exist, but their public availability is controlled separately. I do not present those retained modules as active checkout features.

What did you handle in this project?

My work covered interface design, responsive and bilingual layout, Laravel development, content organisation, legacy URL handling and enquiry integration. Architectural designs, product documents and the underlying project photographs belong to Fargah's work and are presented as its material.

How does the content support search and answer engines?

Clear page topics, direct answers, original document links and consistent metadata make the content easier to interpret. These are foundations for discovery and accurate citation, not a promise of a specific search position or AI recommendation.

Have a similar project in mind?

Tell me what you need to build and where the current experience falls short.

Start a conversation+989304330645
Next projectSaeedFargah.ir