Custom Integrations

How to load dynamic content into your next.js project

To dynamically load your instance's content into your Next.js project, you will need three files and zesty env values in your next.config.js file. You can see a working example of this in our nextjs starter The starter is a great place to launch your nextjs app with everything for already configured.

If you plan to integrate into your project, this document will break down how the integration works in the starter project.

Files Needed

  1. [...slug].js in the root of your pages/ directory.

  2. fetchPage.js a function that resolves dynamic content into [...slug].js

  3. ZestyView a dynamic component that resolves views/zesty/ content model components

ENV Setup - next.config.js


// Some code
const { fetchZestyRedirects } = require('./lib/zesty/fetchRedirects');

// generated by lib/sync.js
module.exports = {
  trailingSlash: true,
  eslint: {
    ignoreDuringBuilds: true
  async redirects() {
    return await fetchZestyRedirects()
  env: {
      zesty: {
          instance_zuid: "", // zesty unique id of content instance
          stage: "", // e.g. the preview url from zesty
          production: "", // e.g. the live url
          stage_password: "",
          src_dir: "", // where the next project has pages, components, etc folders
          options: {
            skip_config_overwrite: false, // for setups with custom config files, after initial setup of the env.zesty object, set to true
            model_ignore_list: [
              '6-xyz-xyz' // an array of models ZUIDS to ignore when creating component files in views/zesty


Working with Zesty View Components

The configuration for next.js will look for a component name after the content model in views/zesty directory in your next.js project. A content model named articles will look for a component views/zesty/Article.js Note the slight name change, as the naming convention is a PascalCase without pluralization, therefore articles becomes Article. We call this the alternate name, you can find the automated alternate name by look at the ?toJSON response of any content item through WebEngine.

Content models that start with a number will need N prepended to the name, e.g. 3slides will be named N3slides.js. The sync script will automatically do this..

Instead of manually creating component, provide a script from downloading and creating components for each content model in your instance. Next.js Sync

The zesty sync is already built into the nextjs-starter, but if you would like to implement a custom sync file, you may download or reference this file

Once sync is in your project, add this line to your package.json file "sync": "node lib/zesty/sync.js", under "scripts" once that is in place you can run npm run sync from your terminal to automatically pull down files.

After a npm run sync a view component is created for each Zesty Content Model in the views/zesty directory. Zesty Content Items that have URL will automatically resolve to the component in that views directory that is associated with the content models name.

// Example Component

import React  from 'react';

function Article({ content }) {
    return (
            {/* Output Example and accessible JSON object for this component. Delete or comment out when needed.  */}
            <h1 dangerouslySetInnerHTML={{__html:content.meta.web.seo_meta_title}}></h1>
            {/* End of output example */}

export default Article;

Each Component loads with a {content} object, this object is a direct feed of that URLs ?toJSON response. Read about toJSON

Last updated