Yext Sites for Developers

Summary

A revised version of the Yext legacy Pages offering intended to open our existing site generation tools to a developer focused audience.

View interactive demo

Static Site Generation

The existing static site generation landscape is comprised of offerings that combine a complex intersection of CMS tools, development frameworks, and deployment orchestration tools.

Static sites have a number of advantages over dynamic sites for customers who have large numbers of pages built from a single template. The pages are rebuilt every time content updates are made and hosted on a CDN in advance of user request cutting load times to a fraction of those of dynamic sites, while abstracting CMS content editing completely from web development.

View industry examples

Site Deployment Overview

The overview screen uses a deploy card treatment similar to the layout used by comparable industry platforms (Netlify, Heroku, Gatsby), coupled with a deploy details screen for debugging and troubleshooting errors.

The three states of deployment progress represented in each card are "initial build","site generation", and "data updates". Because each state of the process is independent of the next, each has a unique status creating a large number of possible variations. Only the first two are necessary for a successful deployment, but the third is still an important indicator of content accuracy.

Yext Sites

The legacy Pages offering used a simple visual editor to allow users to generate Sites using basic templates. Our new Sites offering is intended to offer the Site Generation features of that product coupled with the CMS capabilites of our data set called Knowledge Graph.

This allows us to support the deployment management capabilities and external repository integration that a developer would expect, and allows them to continue working in their existing external workflows while Yext automates the deployment process and rebuilds site content on each commit.

Sites v2 with Visual Editor

The next phase of the project involves layering in the existing features of the legacy product intended for non-developers in order to reach parity and deprecate the old system.

The visual editor features should work in harmony with the in-platform code editor, such that the user can make the same edits using either version of the UI as well as be able to toggle seamlessly between the two.

View visual editor analysis