Emlak

To reduce future technical debt, please keep the following conventions in mind: Data-driven content – Most public-facing text lives in src/data/*.json (see testimonials.json), not hard‑coded in components. Utility functions to read/write are in src/lib/cms.ts. Typed models – All data shapes (Property, Testimonial, etc.) are defined and exported from the CMS module so that consumers can import the interfaces. Reusable UI pieces – Common markup (e.g. section headers) lives in small components like SectionHeader.tsx; duplicate layouts increase maintenance burden. Server/Client separation – Only federate to client components when interactivity/animation is required; keep pages async to allow future async data fetching. Documentation comments – Public helpers in cms.ts are documented; continue the habit when adding new APIs. Translations – Use the messages JSONs only for words that must be localized. Remove keys when switching to a CMS source. Following these patterns will make it easier to add new features, switch storage backends, or refactor design without accumulating hidden work.