←All projects

ThriveDX

August 2021 - June 2022 · Desktop

A no-code system for building, testing, and publishing marketing pages.

MARMANA no-code marketing asset builder

Overview

MARMANA was not meant to give marketers a blank canvas. It was built to remove the handoffs behind repeatable landing-page work: organize the assets, assemble the page, test it, keep it on brand, and publish. My role covered product design, product ownership, and the no-code ecosystem structure. After launch, more than 360 websites were published through the tool, more than 10 design systems shipped on top of it, and time to production fell 83%.

Role
Product Design Lead
My focus
Product ownership, no-code builder UX, and the ecosystem design-system direction.
Evidence
  • Research into user goals, pain points, and confusing areas of the existing production workflow.
  • Existing marketing-production workflow mapped across design, development, and campaign teams.

Process and solution

Animated MARMANA product identity
MARMANA ecosystem user-experience model

Build the workflow, not just the editor

Mapping the workflow showed that drag-and-drop editing solved only one step. Users also needed asset organization, testing, publishing, and brand rules to work as one process.

Reusable patterns reduced the knowledge required to produce a working page without pushing every design and development decision onto non-specialist users.

That made the product a production ecosystem rather than a page editor: users could move from source assets to a live marketing page with fewer handoffs.

MARMANA no-code builder and production workflow

Guardrails were the product

Shared rules for typography, imagery, layout, and reusable structures limited arbitrary output. Users gave up some freedom in exchange for safer publishing and more consistent pages.

The brand system was treated as part of the product, not a layer applied after the fact. That kept the ecosystem cohesive across the builder, assets, published pages, and supporting materials.

MARMANA brand system applied across product touchpoints

Key decision

Use guarded no-code templates instead of offering unrestricted page-building flexibility.

Specialist production preserved flexibility but kept the bottleneck. An unrestricted builder increased quality and brand risk. Guarded patterns gave more users a reliable path to publishing.

Alternative considered: Preserve maximum creative control and continue routing production through designers and developers. / Offer an unrestricted builder to non-specialist users.

Outcome

0+

Websites published

-0%

Time to production

0+

Design systems shipped

Looking ahead

Measure publishing errors and the cases that still require specialist intervention, alongside the production-time gains.

Continue exploring