DrZerafati.ir

A Persian-first health and performance platform spanning appointment scheduling, athlete intake, accounts, training and nutrition plans, progress, evidence-led content, and commerce.

drzerafati.ir
Health and performance homepage · Live website capture
Year
2026
Role
Product / Full-stack development
Scope
PHP · SQLite · Bilingual
Status
Live

The project, in context

For DrZerafati.ir, I connected a personal performance brand, athlete intake, training delivery, evidence-oriented reading, and store infrastructure in a Persian-first platform. The project spans a public website and private working tools, with a clear distinction between implemented capabilities and services that still require operational activation.

The service continues after the visit

An athlete's relationship with a coach does not fit inside an introduction page. Intake, training instructions, nutrition, feedback, and follow-up all belong to the same service. Keeping them in separate messages and files makes it harder to know which programme is current and what the next action is.

The platform also carries a special editorial responsibility: educational material must remain distinguishable from a personal plan, and an available form must not imply that booking or commerce is operationally ready. The interface therefore needed to make status, context, and access boundaries visible.

A public front, a working core

The public experience explains the brand, service approach, and collaboration process. A staged athlete registration flow gathers the initial context, while the account provides a personal place for programmes and interaction. The administrator's programme studio uses day and session structure rather than treating a plan as an unstructured text file.

The same visual language extends to the supplement guide, magazine, food guide, and store. These public sections can be explored independently. Booking and sales have explicit activation conditions, while private tools are described as product capabilities rather than illustrated with real athlete records.

What I built

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

  1. A Persian-first public experience

    The site introduces the service approach, professional background, and collaboration steps in Persian, with an English route. Local fonts, right-to-left layout, responsive navigation, and reduced-motion support keep reading and navigation practical across phone and desktop screens.

  2. Intake with relevant context

    A three-step intake supports beginner, professional, and competition-oriented questionnaires. Health answers are encrypted in storage and reviewed through the authorized administration path. The flow is designed to gather context for the team, not to produce an automatic medical conclusion.

  3. Programme design by day and session

    The programme studio supports session duplication, exercise ordering, sets, repetitions, rest, load, RPE, RIR, tempo, and training systems. A mobile preview helps the editor see how the athlete will receive the plan before publishing it.

  4. Exercise media and a growing library

    Exercises can be searched and edited by approved muscle categories. The administration flow supports motion video, animation, and image uploads. Licensed starter media and target-muscle maps give the library a usable starting point, while staff can extend it through the panel.

  5. Nutrition and the athlete account

    Nutrition is structured around meals, calories, and macronutrients; supplement plans have timing fields. Programme versions can be cloned. The athlete account gives personal plans and communication a dedicated interface, separate from public educational articles and the store.

  6. Reading with sources

    The magazine offers archive, search, categories, and a dedicated scientific article layout. Articles include reading structure and sources, while the supplement and food guides form separate browsing paths. Generated pages carry metadata and article structured data without exposing private service information.

  7. Booking and store, with explicit readiness

    Booking logic includes temporary slot holding and payment verification. Store infrastructure covers variants, stock, cart, orders, and private receipt handling. Operational activation depends on real schedules, tariffs, merchant configuration, product information, and sales permissions; the interface must respect that state.

From structure to release

  1. Separate the service paths

    Introduction, education, intake, personal coaching, and commerce have different purposes and are given distinct routes.

  2. Structure the working information

    Days, sessions, exercises, meal entries, and timing turn programme information into something that can be edited and presented consistently.

  3. Design the phone experience

    Responsive forms, calendar controls, compact navigation, and programme previews support the screens athletes are likely to use during their routine.

Delivery and current scope

  • Persian-first public website with an English version and independent reading sections.
  • Athlete intake, account interface, administration, and programme-building tools.
  • Exercise library, media upload, nutrition structure, and mobile preview.
  • Booking and store infrastructure with configuration-dependent activation.

Questions about this project

Is this only a personal website?

The public brand website is one part. The implementation also includes athlete intake, personal account screens, administration, training and nutrition tools, content publishing, and store and booking infrastructure.

Are all booking and sales functions active?

Implementation and service activation are separate. Booking requires a real schedule, tariffs, and merchant settings; commerce requires product and operational readiness. The availability shown by the live service is the reference for its current state.

How are training programmes built?

The programme studio organizes days and sessions, then assigns exercises, their order, sets, repetitions, rest, load, and execution notes. Session duplication and a mobile preview let the coach edit the plan and review the athlete's view before publishing.

Have a similar project in mind?

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

Next projectFamaLing.ir