Android-Piepaint / sites

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Gatsby

Gatsby Starter Drupal Homepage

Create a homepage using Gatsby and Drupal. This starter demonstrates how to use Drupal to build a homepage and can be customized to match your own visual branding.

View the Demo

Note: This version of the Drupal homepage starter is written in JavaScript. If you want to use Drupal but TypeScript is more your style, there is also a TypeScript version maintained on GitHub.

Quick start

You will need a new or existing Drupal website to use this starter and will be asked for your baseUrl and the username and password for your Drupal during installation.

  1. Create a Gatsby site

    Use the Gatsby CLI to get started locally:

    npx gatsby new my-homepage https://github.com/gatsbyjs/gatsby-starter-drupal-homepage
  2. Import content to your Drupal instance

    For this implementation we used Pantheon as our host. So some configurations may be specific to that platform. Before importing the sql dump file we recommend extracting and adding the files located in data/files.zip to your drupal site under sites/default/ or wherever your files folder is located on your instance. Afterwards you may use the sql dump file provided in the same data directory called homepage-starter-dump.sql.gz. Depending on the setup, you may have to extract the sql file before trying to import the data.

    Hosting on Pantheon

    1. Go to Pantheon.io, register and log in

    2. Create a new blank project and provide a name for the project

    3. Select Drupal with Composer and then following the instructions to complete the installation

    4. On the Dashboard there will be three (3) environments (Dev, Test and Live) and for our purposes we will use Dev. Select Database/Files then Wipe. Click Wipe the Development Environment and follow the instructions to start with an empty site.

    5. Go to Import. Here under MySQL Database select File and use the homepage-starter-dump.sql.gz provided in the data directory to upload the database. Make sure Run update.php after the database import finishes is selected before uploading the file. Click Import.

    6. Under Archive of site files select File and use the files.zip also provided in the data directory to upload the files. Click Import.

    7. Clear Caches and test out your site by clicking either Visit Development Site or Site Admin.

    8. The credentials for logging in are: sh username: admin password: DrupalGatsby123 It is highly recommended that you change the password to your Drupal site afterwards to something that only you know.

      Now, our site is up but we still need to install the Gatsby Module. To do that on Pantheon we need to pull down the site locally and install the module using composer. To streamline this process we will use a free, open source, cross-platform tool called Lando which you can Download Here (At the time v3.6.0 was the latest stable version).

Lando & Pantheon Integration

For a video guided step-by-step tutorial see the links below:

Local dev for Pantheon sites with Lando by Jantcu

  1. Install Lando and Docker

  2. A Machine Token is needed by Pantheon in order to push and pull the Database, Files and Code. To generate a Machine Token follow these instructions. Remember that the Machine Key will only be visible once so keep it handy.

  3. # Create a new directory for your Drupal site
    mkdir homepage-starter
    cd homepage-starter
    
    # Initialize Lando and when prompted select Pantheon and paste in the Machine Key generated earlier. Continue following the prompts provided to pull donw your site.
    lando init
    
    # Start server
    lando start
    
    # Pull down Database, Files and Code. We are working on the dev server so be sure to select "dev" when prompted
    lando pull
    
    # Clear caches
    lando drush cr
  4. # Manually install modules
    lando composer config repositories.2 '{"type": "package", "package": { "name": "ionaru/easy-markdown-editor", "version": "2.15.0", "type": "drupal-library", "dist": { "url": "https://registry.npmjs.org/easymde/-/easymde-2.15.0.tgz", "type": "tar" } } }'
    lando composer require 'drupal/gatsby:^1.0@RC'
    lando composer require 'drupal/markdown:^3.0@RC'
    lando composer require 'league/commonmark:^1.0'
    lando composer require 'drupal/simplemde:^1.0@alpha'
    
    # Optional but makes navigation easier
    lando composer require 'drupal/admin_toolbar'
    
    # Clear caches again
    lando drush cr
    
    # Push up Database, Files and Code. We are working on the dev server so be sure to select "dev" when prompted
    lando push

All the modules should now be installed and activated. To ensure that they are all installed correctly:

  1. Go to your local Drupal site and login.

  2. Select Extend in the toolbar.

  3. Find the Gatsby Section and check Gatsby, Gatsby Fast Builds, Gatsby JSON:API Instant Preview and Incremental Builds. All other dependent modules will automatically be installed.

  4. Find the Web Services Section and ensure that HTTP Basic Authentication is checked.

  5. Head to the bottom on the page and click the Install button.

  6. Now you're done in your Drupal site! But we have one more step remaining to connect to your Gatsby homepage site.

  7. Run the setup script

After setting up the Drupal site, navigate back to your Gatsby site's root directory and run:

yarn setup

This will run a script to create .env.development and .env.production files for you populated with your Drupal site environment variables.


Local Drupal Development

The composer.json file as well as exported configurations found in the config folder are also included. If you decide to import and install these configurations, please do so before executing the sql script and be sure not to clean the existing database.

# import configurations
drush cim

# initial install
composer update

# installing from composer.lock
composer install

Drush

For more information on how to use drush commands and how to install the command line shell visit Drush Documentation Site.

# If you wish to start from a clean site
drush sql-drop
drush sql-cli < ~/path/to/homepage-starter-dump.sql

An admin user already exists in the application. You will have to reset the password if you decide to start from a clean site.

# Drush 9
drush user:password admin "new_password"

# Drush 8 & earlier
drush user-password admin --password="new_password"

Lando

A free, open source, cross-platform, local development environment and DevOps tool built on Docker container technology and developed by Tandem. See the docs.

# This will destroy the database and import the data.
# If you wish to keep you existing data add the --no-wipe flag.
lando db-import ~/path/to/homepage-starter-dump.sql
  1. Start developing

    In your site directory, start the development server:

    yarn start

    Your site should now be running at http://localhost:8000

  2. Open the source code and start editing

Deploy your site

Once your content is available in Drupal, deploy your site to Gatsby Cloud:

  1. Push your local site to a new repo in either GitHub, GitLab, or Bitbucket
  2. Log into your Gatsby Cloud Dashboard and click on Add a site
  3. Use the Import from a Git repository option to find your site
  4. Add the environment variables from your .env.production file to Gatsby Cloud during setup
  5. Click Build site and your site should start building

For a more detailed walkthrough, see the tutorial on how to build your site with Gatsby Cloud.

Deploy without using the CLI

Alternatively, you can deploy this starter directly to Gatsby Cloud.

Note that you will need to set up your content in Drupal manually.

Deploy to Gatsby

Setting up Gatsby Cloud Preview

To enable Gatsby Preview with this site, see the documentation for:

Configuring for Live Preview

Installing Gatsby Module for Drupal

Drupal FastBuilds

What's included?

├── README.md
├── gatsby-config.js
├── gatsby-node.js
├── src
│   ├── components
│   ├── pages
│   ├── colors.css.ts
│   ├── styles.css.ts
│   └── theme.css.ts
└── .env.EXAMPLE
  1. gatsby-config.js: Gatsby config file that includes plugins required for this starter.
  2. gatsby-node.js: Gatsby Node config file that creates an abstract data model for the homepage content.
  3. src/: The source directory for the starter, including pages, components, and Vanilla Extract files for styling.

How to

Update the color theme

To update the colors used in this starter, edit the src/colors.css.ts file.

// src/colors.css.ts
export const colors = {
  background: "#eff6ff",
  text: "#004ca3",
  primary: "#004ca3",
  muted: "#e6f1ff",
  active: "#001d3d",
  black: "#000",
}

If you'd like to add additional colors, add additional keys to this object. This file is imported into src/theme.css.ts and creates CSS custom properties, that can be imported and used in other .css.ts files.

The UI components file src/components/ui.js imports styles from src/components/ui.css.ts. You can see how the theme and color values are being used in this file.

Add your logo

Logo

Replace the src/components/brand-logo.js component with your own brand logo. If you have an SVG version, it can be rendered inline as a React component, following the example in this file. Note that SVG attributes will need to be camel cased for JSX.

Using an inline SVG for the logo allows it to pick up the colors used in CSS, which is how the logo colors are inverted for the mobile menu.

If you prefer to use an image, use the StaticImage component from gatsby-plugin-image in place of the SVG in this file.

Customize headings, buttons, and other styles

Headings & Buttons

To further customize the look and feel of the homepage, edit the UI components in src/components/ui.js and styles in src/components/ui.css.ts.

Customize section components

To customize any of the sections of the homepage, edit the relevant component in src/components. Most of the styles for these components are handled with shared UI components in src/components/ui.js.

Create custom section components

To create a new type of section in your homepage, you'll want to create a new section component, using the existing components as an example. For this example, we'll create a new "Banner" component.

  1. First, update your content model in Drupal

    1. In your Drupal website, create a new content type and call it "Homepage Banner".

      Step 1
    2. For this example, change the Title field's name to Heading in when creating your new content type. Remove any fields that are added dy default and create a new field called text this should be of Text (plain, long) data type or use an existing field with the same type and field name.

      Step 2 Step 3
    3. Find the content type for Homepage click Manage fields and edit the settings for the content field. Under Reference Type -> Content Type, ensure that the new Homepage Banner type is checked to make it available as a content type on the Homepage.

      Step 4 Step 5
    4. Create a new Homepage Banner entry then navigate back to the Content page to edit the Homepage entry and insert a section with this new Homepage Banner by appending it to the list.

      Step 6
  2. Update gatsby-node.js

    Edit your site's gatsby-node.js file, adding an interface for HomepageBanner that matches your content model in Drupal. This allows the homepage to query the abstract HomepageBanner type.

    // in gatsby-node.js
    exports.createSchemaCustomization = async ({ actions }) => {
      // ...
      actions.createTypes(`
        interface HomepageBanner implements Node & HomepageBlock {
          id: ID!
          blocktype: String
          heading: String
          text: String
        }
      `)
      // ...
      actions.createTypes(`
        type node__homepage_banner implements Node & HomepageBanner & HomepageBlock @dontInfer {
          id: ID!
          blocktype: String @blocktype
          heading: String
          text: String
        }
      `)
      // ...
    }
  3. Next, create the Banner component:

    // src/components/banner.js
    import * as React from "react"
    import { graphql } from "gatsby"
    import { Section, Container, Heading, Text } from "./ui"
    
    export default function Banner(props) {
      return (
        <Section>
          <Container>
            <Heading>{props.heading}</Heading>
            <Text>{props.text}</Text>
          </Container>
        </Section>
      )
    }
    
    export const query = graphql`
      fragment HomepageBannerContent on HomepageBanner {
        id
        heading
        text
      }
    `
  4. Export the component from src/components/sections.js

    // src/components/sections.js
    export { default as HomepageHero } from "./hero"
    export { default as HomepageFeature } from "./feature"
    export { default as HomepageFeatureList } from "./feature-list"
    export { default as HomepageLogoList } from "./logo-list"
    export { default as HomepageBenefitList } from "./benefit-list"
    export { default as HomepageTestimonialList } from "./testimonial-list"
    export { default as HomepageStatList } from "./stat-list"
    export { default as HomepageCta } from "./cta"
    export { default as HomepageProductList } from "./product-list"
    
    // add export for new component
    export { default as HomepageBanner } from "./banner"
  5. Add the GraphQL query fragment to the query in src/pages/index.js

    // in src/pages/index.js
    export const query = graphql`
      {
        homepage {
          id
          title
          description
          image {
            id
            url
          }
          blocks: content {
            id
            blocktype
            ...HomepageHeroContent
            ...HomepageFeatureContent
            ...HomepageFeatureListContent
            ...HomepageCtaContent
            ...HomepageLogoListContent
            ...HomepageTestimonialListContent
            ...HomepageBenefitListContent
            ...HomepageStatListContent
            ...HomepageProductListContent
            # New component fragment
            ...HomepageBannerContent
          }
        }
      }
    `

Troubleshooting

Errors after making changes to the schema

If you've made changes to the gatsby-node.js file or changes to the Drupal data model, clear the Gatsby cache before running the develop server:

yarn clean && yarn start

🎓 Learning Gatsby

Looking for more guidance? Full documentation for Gatsby lives on the website. Here are some places to start:

💫 Deploy

Build, Deploy, and Host On The Only Cloud Built For Gatsby

Gatsby Cloud is an end-to-end cloud platform specifically built for the Gatsby framework that combines a modern developer experience with an optimized, global edge network.

About

License:BSD Zero Clause License


Languages

Language:JavaScript 73.8%Language:TypeScript 26.2%