Menu
Services
Projects
Mekishico®BrandingWebsitesSocial mediaContent Lab
Conversations Blog Let's talk ESEN
ESENLet's talk
Web projects

Web App · AI Agent

Web Editor Agent with AI

Your next change starts with a conversation.

A private application to update the Veromadrig site with natural language instructions, contribute images and review a preview before deciding what to publish.

I want an editor for my site
AI Web Editor Agent home interface with conversation on the left and site preview on the right
AI Web Editor Agent on a desktop screen and tablet
VEROMADRIG · 01 / 03
01 · Conversation and context

Your content. Your site. One conversation.

The initial interface screenshot shows the central idea of ​​the product: keeping close what is requested and what changes. The panel evolves with use, maintaining one rule: review first and publish later.

01Own content and images
Files are contributed from the panel and the agent receives instructions on where to place them. Image optimization is part of the upload flow.
02Visual continuity
New pages should reuse navigation, header, footer, and site styles. The location on the menu is defined before adding them.
03Editorial control
Requests have visible statuses and changes are reviewed before publishing is approved. Errors require resolution, they are not interpreted as a successful delivery.
AI Web Editor Agent on a Phone with Image Upload
VEROMADRIG · 02 / 03
02 · Adaptable to every screen

An experience that goes with you.

Editorial decisions are also reviewed where most people work: on the phone. The mobile mockup shows how to add an image and review a page without losing the hierarchy or tone of the brand.

DeskTabletMobile
Visual map of the editorial flow of the Web Editor Agent with AI
VEROMADRIG · 03 / 03
03 · How the agent works

Request. Review. Approve.

The logic behind the agent can be explained without turning the case into technical documentation: receive context, prepare the change, review the preview, and approve the release. Each step retains a human checkpoint.

01Receive
The person writes the request, contributes content and attaches the necessary assets.
02Build
The agent interprets the intent within the component system and prepares a proposal.
03Review
The preview allows you to compare the result on desktop, tablet and mobile.
04Approve
Only after confirmation does the publishing process begin.

The project

Period
2026 · Product in evolution
Scope
Conversational editing · Assets · Preview · Publication
01

A site that can keep up with its creator.

After publishing a site, the editorial work continues: new projects, articles, images and message changes. The Vero editor was created to bring these tasks closer to those who know the content, without forcing them to go through code files for each update. The conversation becomes the entry point; The existing design remains the reference.

02

Ask, provide context and review.

Vero describes what you want to change and on which page. You can attach your images and give the content of a new section. When information is missing, the agent asks before continuing. The scope includes editorial changes and new pages that reuse the site's identity, components and structure, not automated, directionless redesigns.

03

The preview is part of the decision.

The application brings together the chat and the page in the same space. Desktop, tablet, and mobile views help you review the proposal before approving it. Pending changes are distinguished from the public site: an agent response is not equivalent to a publication. The person retains the final decision on which version should be released.

04

Automation with clear limits.

The agent works on the connected project and prepares changes that go through technical checks and a publishing process. Access is private and credentials remain server-side. New integrations, infrastructure changes, and out-of-system design decisions require technical review; the editor does not replace that specialized work.

05

A custom tool, not another generic builder.

The dashboard uses Next.js, React and TypeScript. Netlify hosts the application and coordinates agent execution and deployments; GitHub maintains site versions. Images are optimized to WebP with Sharp and stored in Netlify Blobs. This separation allows us to take care of the editorial experience without turning the public site into an administration panel.

The system behind

An experience ready to grow.

The visual direction coexists with a technical base designed to keep the content current, facilitate operation and take care of each point of contact.

01

Discuss

Instructions and content provided by the person who knows your brand.

02

Review

Preview and pending changes before touching the public version.

03

Post

Explicit approval and monitoring of the publication result.

System map

From an instruction
to a publication.

Automation helps prepare work; The editorial decision always remains on the person's side.

  1. 01

    Receive

    Request, context, content and assets.

  2. 02

    Interpret

    The agent identifies page, scope, and reusable components.

  3. 03

    Prepare

    A proposal is generated within the existing visual system.

  4. 04

    Review

    The preview allows you to check desktop, tablet and mobile.

  5. 05

    Approve

    Publishing only starts after confirmation.

Let's start with a conversation

Let's talk about
your project.

We explore your idea, your objectives and the challenges you face to define the next step.

$638 MXNExploration session

45 min · Online · VAT included

You will receive a list of next steps and recommended tasks.

Schedule your session