Skip to content
YMP
← All work

Product system · AI generation, visual builder, CMS integrations

Public demo

Yappaflow

A platform concept for web agencies. A client conversation becomes a structured brief, real reference sites are researched, and the site is generated as a canonical JSON project that can be refined in an in-house visual builder and exported toward Shopify, WordPress, Webflow or IKAS. The product decision that shapes everything else: the AI fills a strict schema instead of writing free-form pages, so what it produces can be edited, validated and exported. The live link is the public landing page, in English and Turkish.

  • TypeScript
  • Next.js
  • Express / GraphQL
  • MongoDB
  • Playwright
  • Model Context Protocol
  • Zustand
Landing page scroll recording · 30 seconds · no sound
The Yappaflow builder: a page and section list on the left, a generated studio site in the centre with the feature section selected, and that section’s editable fields on the right.
Builder, running locally on sample content
Yappaflow landing page hero: the headline “From conversation to code” in white and orange over a wireframe sphere on a dark starfield, with a short description of the platform at the bottom left.
Landing page: hero
Yappaflow landing page platform section: a statement describing an AI-powered agency platform above a grid of integration tiles for WhatsApp, Instagram, Shopify, WordPress, Webflow, IKAS, Namecheap and Hostinger.
Landing page: platform and integrations
Yappaflow landing page closing section: the headline “Ready to automate your agency?” above start-free-trial and book-a-demo buttons.
Landing page: closing call to action

My part

Primary developer — nearly all commits in the repositories are mine: the API server with its CMS connectors, the reference-research pipeline, the section library, the builder interface and the monorepo structure.

Scope

  • The platform repositories are private; the only public surface is the landing page.
  • The schema-first approach describes how the system is designed; this showcase does not demonstrate every generation path.
  • The builder is shown running locally on bundled sample content. In the repository it is marked as still in progress, and CMS export is further along for some platforms than others.
  • The conversation window on the landing page is a scripted illustration, not a working application.
  • Marketing wording on the landing page, such as customer and free-trial lines, is page copy, not a claim about users or availability.
  • The recording and screenshots are of the public landing page. The conversation, code and deploy window in the recording is a scripted illustration.
  • The integration tiles name platforms the repositories have connectors or references for; I have not verified each one end to end.
  • The builder screenshot is the local editor running on sample content; it is not part of the public site.

09 — Work with me

Have somethingyou needbuilt?

A new product, an internal tool, or the system behind an interface that already exists. If the problem isn’t pinned down yet, I can help shape the product and the architecture before anything is written. Tell me what it is, who it is for and when you need it. I answer with what I would build, in what order, and what I would decide first — and I say so when what I learn along the way contradicts the plan, including mine.