Have feedback for the Replo team?

Share how Replo can make their product better for you and your team.

Read-only API access to Classic pages, product templates, sections, and components

Our Shopify site depends on approximately 50 published pages, product templates, and sections built in Replo Classic. Replo support explained that the current public API and Claude/ChatGPT connector only support Agent projects and cannot access our existing Classic content. Please expose Classic content through a read-only API, ideally accessible through the connectors as well. At a minimum, we need to: List all Classic pages, product templates, sections, and reusable components in a project. Retrieve their structured content, layout, styling, responsive settings, and asset references. Read interactions, Shopify data bindings, custom code, and component dependencies where available. Identify each item’s published URL and Shopify template or section association, where applicable. This would let Replo Agent or an external coding agent inspect our existing implementation and use it as the source for rebuilding editable equivalents in Agent projects. Read-only access would already be valuable as a first release. It would substantially reduce the manual work required to migrate while a full bulk importer is being developed.

Joseph J. Lam about 13 hours ago

💬 Replo

One-click bulk import from Replo Classic into Replo Agent

Our Shopify site depends on approximately 50 published pages, product templates, and sections built in Replo’s Classic editor. We want to adopt Replo Agent, but manually rebuilding all of that would be a substantial project and a major barrier to adoption. Please provide a one-click bulk import that brings an entire Classic project—or selected items—into the new Agent experience as editable content. The import should: Include pages, product templates, sections, and the reusable components they depend on. Preserve content, assets, responsive layouts, styling, interactions, and Shopify data connections wherever supported. Clearly flag anything that cannot be migrated, including custom code or unsupported functionality. Create drafts we can preview and validate before changing the live site. Preserve existing URLs and SEO metadata where possible, with clear guidance for any required changes. Product templates and theme sections are essential to this request. Please explain how those map into the new experience and identify any compatibility gaps before migration begins. We have a significant investment in Replo already. A bulk migration path would let us carry that work forward and start using Agent without rebuilding our site from scratch.

Joseph J. Lam about 13 hours ago

💬 Replo

Bulk update / API support for asset references across Replo pages

We are migrating away from Contentful and need to update hundreds of image and video references across Replo pages, templates, sections, and components. Currently, it appears these references need to be updated manually in the Replo editor. It would be very helpful to have a way to perform bulk updates, ideally through one or more of the following: Project-wide search and replace for URLs Import/export of Replo page data in a structured format An API for reading and updating Replo page/template content A bulk asset migration tool that accepts an old URL → new URL mapping Our specific use case is replacing Contentful asset URLs with Shopify CDN URLs, but this would also be useful for any CDN migration or large-scale asset reorganization. Ideally, the replacement would update the underlying Replo source so that future edits and republishes preserve the new asset references.

Gregory Campbell 1 day ago

💬 Replo

Responsive Typography for Text Styles (Desktop / Tablet / Mobile)

Currently, Shop / Brand Library Text Styles are not breakpoint-aware. Each style (H1, H2, Body, etc.) applies the same font size and line height across all devices. To create responsive typography, users must duplicate styles (e.g. H1 Desktop + H1 Mobile) and manually apply them per breakpoint. Problem Typography often doesn’t translate well from desktop to mobile Requires duplicating every semantic style per breakpoint Updates become time-consuming and error-prone Reduces the value of having a centralized style system Request Allow a single Text Style to define responsive values per breakpoint (Desktop / Tablet / Mobile). Example: H1: 48px (desktop) / 40px (tablet) / 32px (mobile) This would keep styles semantic while automatically adapting typography across devices. Why it matters This would significantly improve: Design system scalability Mobile readability Consistency across pages Workflow efficiency (less duplication and manual overrides)

An Anonymous User 2 months ago

💬 Replo

Reviewed

Global Optimization for Replo-Injected Google Fonts

We are requesting the ability to append the &display=swap parameter and implement tags for all Google Fonts (specifically Noto Serif JP and Inter) injected via Replo. Currently, these fonts are loading in a render-blocking manner, causing significant delays, up to 2,010ms in recent audits, which negatively impacts First Contentful Paint (FCP) and Largest Contentful Paint (LCP) scores. Since these tags are injected by Replo rather than the Shopify theme, users cannot manually optimize them. Enabling "font-display: swap" by default would allow pages to render immediate fallback text, improving the perceived performance and SEO scores for all AI Builder and Replo-hosted landing pages.

An Anonymous User 5 months ago

1

💬 Replo