Namayandegi Yab
-1920x1080.webp&w=1920&q=100)
Technologies
services
Client
SEO partner
(directory product)
About this project
Namayandegi Yab is a directory: listings, filters, profiles — in this case, clinics. The client is a former SEO colleague. We proposed the product, then had to prove we could learn Payload and still hit a two-week deadline.
The CMS is the actual asset. Relationships are modeled so the same skeleton can become another kind of directory without a rewrite, and so the later phase (practitioners publishing, visitors registering, booking, comments) does not require throwing the schema away. For now it is a directory. It is allowed to become a marketplace.
Omid learned Figma in order to wireframe from the conversations, get approval, then design the UI before code — because Amin was on the frontend and a client was waiting. After first assembly, components were refactored so they could be reused. Code from week one was not precious; structure at week two was.
Honest status: performance and SEO were not taken to the same standard as Bscenius. The site stayed an MVP because content never landed. We will not dress that up as a growth story. What you can judge is the data model, the two-week path from conversation to a running Payload app, and whether that is how you want a first version of a directory built.
Case study · related service: Custom CMS
Results
Delivered a working directory CMS and UI on a two-week deadline while learning Payload and Figma in parallel. Content is not public yet — this is an architecture and delivery piece, not a traffic case.
we did this here jus so you know that you are the b
so don't tell me we're not grinding enough
1// features/services/types.ts2// طبق Core فایل ۰۳: RichTextData برای فیلدهای با لینک/فرمت؛ @field برای string مبهم3
4import type { DocumentMeta, FaqItem, ImageData, RichTextData, SeoFields } from '@/types/shared'5
6export type ServiceFeatureItem = {7 title: string // @field: text8 description?: string // @field: text9}10
11export type ServiceProcessStep = {12 number: number | string // @field: text13 title: string // @field: text14 description?: string // @field: textarea15}16
17export type ServicePricingPlan = {18 name: string // @field: text19 price: string // @field: text20 period?: string // @field: text21 description?: string // @field: textarea22 features: string[] // @field: text[]23 highlighted?: boolean // @field: checkbox24 ctaLabel?: string // @field: text25 ctaHref?: string // @field: text26}what ever you did doesn't matter
if that's true I have nothing to say to you exept bye