Riverscapes / riverscapes-gatsby-theme

The theme for all Gatsby Riverscapes sites
https://riverscapes.github.io/riverscapes-gatsby-theme/
1 stars 1 forks source link

Same favicon used for all sites #18

Closed philipbaileynar closed 4 months ago

philipbaileynar commented 4 months ago

Is it possible to have a custom favicon for each site?

MattReimer commented 4 months ago
  1. put icon (16x16 pixels in png format) in the static folder
  2. add iconUrl to your config file like so:
import { GatsbyConfig } from 'gatsby'

module.exports = {
  // You need pathPrefix if you're hosting GitHub Pages at a Project Pages or if your
  // site will live at a subdirectory like https://example.com/mypathprefix/.
  // pathPrefix: '/mypathprefix',
  flags: {
    // DEV_SSR fixes a problem where `gatsby develop` is overwhelming the system memory
    // It's related to this issue: https://github.com/gatsbyjs/gatsby/issues/36899
    // More about DEV_SSR: https://www.gatsbyjs.com/docs/debugging-html-builds/#ssr-during-gatsby-develop
    // Eventually this needs to go away but likely not until the Gatsby webpack version is updated
    DEV_SSR: false,
  },
  pathPrefix: '/riverscapes-gatsby-theme',
  siteMetadata: {
    title: `Riverscapes Developer Site`,
    author: {
      name: `North Arrow Research`,
    },
    // Just leave this empty ('') if you don't want a help widget in the footer
    helpWidgetId: '153000000178',
    description: ``,
    siteUrl: `https://riverscapes.github.io/riverscapes-gatsby-theme/`,
    social: {
      twitter: `RiverscapesC`,
    },
    menuLinks: [
      {
        title: 'About us',
        url: '/contentPages',
        items: [
          {
            title: 'What is a riverscape',
            url: '/contentPages/contentSubFolder',
            items: [
              {
                title: 'Level 2 A',
                url: '/contentPages/contentSubFolder',
              },
              {
                title: 'Level 2 B',
                url: '/contentPages/contentSubFolder',
              },
            ],
          },
          {
            title: 'FAIR principles',
            url: '/contentPages/contentSubFolder',
          },
        ],
      },
      {
        title: 'Our work',
        url: '/contentPages',
        items: [
          {
            title: 'Riverscapes Consortium Data Exchange',
            url: '/contentPages/contentSubFolder',
          },
          {
            title: 'Riverscapes Consortium Applications',
            url: '/contentPages/contentSubFolder',
          },
          {
            title: 'Riverscapes Consortium Models',
            url: '/contentPages/contentSubFolder',
          },
          {
            title: 'Data Standards and Compliance',
            url: '/contentPages/contentSubFolder',
          },
        ],
      },
      {
        title: 'Impact stories',
        url: '/',
      },
      {
        title: 'Workshops & events',
        url: '/contentPages',
      },
      {
        title: 'Get involved',
        url: '/contentPages',
      },
      {
        title: 'Contact',
        url: '/contentPages',
      },
      {
        title: 'Search',
        url: '/contentPages',
      },
    ],
  },
  plugins: [
    {
      resolve: '@riverscapes/gatsby-theme',
      options: {
        contentPath: `${__dirname}/content/page`,
        manifest: {
          name: `Riverscapes Developer Site`,
          short_name: `RiverscapesDEV`,
          start_url: `/riverscapes-gatsby-theme`,
          // ADD THIS LINE
          iconUrl: `./static/custom_favicon.png`,
        },
      },
    },
  ],
} as GatsbyConfig
philipbaileynar commented 3 months ago

I just implemented this on the Viewer web site. Worked.