Multiple page templates for the same node type in Gatsby  📄 1️⃣

How can you achieve different page layouts for content with the same content node type but varying content types?

A typical example is sourcing both posts and projects content from markdown. Both posts and projects are added to the Gatsby Content Layer as MarkdownRemark Nodes. But are "logically" different content types.

This week we'll look at three different approaches!

First up is using multiple page templates. Tomorrow's email looks at multiple page components, and then we'll round it off with my current favorite: parrot pages.

Multiple Page Templates

For the multiple page templates approach, we'll use the createPages extension point to create a page for each markdown file.

Something you probably have done before, but we'll extend on it a little and make sure it selects the correct page template for the content type:

// gatsby-node.js
const path = require(`path`);

exports.createPages = async (gatsbyUtils) => {
  const { actions, graphql, reporter } = gatsbyUtils;
  const { createPage } = actions;

  const { data } = await graphql(`
    {
      allMarkdownRemark {
        nodes {
          id
          fields {
            slug
          }
          parent {
            ... on File {
              sourceInstanceName
            }
          }
        }
      }
    }
  `);

  const templates = {
    post: path.resolve(`src/templates/post-template.js`),
    project: path.resolve(`src/templates/project-template.js`),
  };

  data.allMarkdownRemark.nodes.forEach((node) => {
    const contentType = node.parent.sourceInstanceName;
    createPage({
      path: contentType + node.fields.slug,
      component: templates[contentType],
      context: {
        id: node.id,
      },
    });

    reporter.info(
      `Created page for slug ${node.fields.slug} with type ${contentType}`
    );
  });
};

The sourceInstanceName used comes from configuring your gatsby-source-filesystem with the name option.

// gatsby-config.js
module.exports = {
  plugins: [
    {
      resolve: `gatsby-source-filesystem`,
      options: {
        path: `${__dirname}/content/posts`,
        name: "post",
      },
    },
    {
      resolve: `gatsby-source-filesystem`,
      options: {
        path: `${__dirname}/content/projects`,
        name: "project",
      },
    },
  ],
};

And the slug is created using the onCreateNode extention point.

// gatsby-node.js
const { createFilePath } = require("gatsby-source-filesystem");

exports.onCreateNode = (gatsbyUtils) => {
  const { actions, node, getNode, reporter } = gatsbyUtils;
  const { createNodeField } = actions;

  if (node.internal.type === "MarkdownRemark") {
    const slug = createFilePath({ node, getNode });

    createNodeField({
      name: "slug",
      node,
      value: slug,
    });

    reporter.info(`Create slug ${slug}`);
  }
};

How do you solve different page layouts for content with the same content node type but varying content types?

 
All the best,
Queen Raae

Stuck on a reef in the sharky waters around the Gatsby islands?

Book a 1-on-1 Gatsby Call with Queen Raae. Friendly advice you can put into action immediately, guaranteed!

Serious about Gatsby? Sign up for emails sent every weekday to help you get the most out of Gatsby!