regen-network / regen-web Goto Github PK

Same as #44 and #46

I like the idea of starting the filename with either the page it's in, or shared...so the marketplace section could be:
home-marketplace-section.tsx

Also theres a question of whether or not include the word section at the end of them, maybe not necessary since they're all in a section folder.

Additionally, we could go camelcase or dashes..

Including confirmation email and redirect to "For Buyers" page with notification at the top.

Would speed up development to not have to cmd + r after every change.

For example, on jared/home-climate-change the positioning of the dialogue boxes / text / image need to be pretty different on mobile vs on desktop.

It seems like absolute positioning could work, but would feel a bit brittle. Flexbox maybe with order property..

In looking at this section, I'm wondering how I might draw those connecting lines best? It seems like an SVG might be a good bet, but we'd need the locations of the image and the dialogue box in order to best fit the ends. Do you have any suggestions @blushi ?

same as #38

Needs some fixing up.

• mobile version
• fix layout (due to absolute position)

I am pulling RegenThemeProvider into layout.tsx

/**
 * Layout component that queries for data
 * with Gatsby's useStaticQuery component
 *
 * See: https://www.gatsbyjs.org/docs/use-static-query/
 */

import React from 'react';
import PropTypes, { string } from 'prop-types';
import { useStaticQuery, graphql } from 'gatsby';
import Header from 'web-components/lib/components/header';
import { useTheme } from '@material-ui/core/styles';
import './layout.css';
import ThemeProvider from 'web-components/lib/theme/RegenThemeProvider';

let logo = 'images/logo.png';
interface propTypes {
  children: Array<React.ReactElement>;
  color: string;
}

const Layout = ({ children, color }: propTypes): JSX.Element => {
  const data = useStaticQuery(graphql`
    query SiteTitleQuery {
      site {
        siteMetadata {
          title
        }
      }
    }
  `);

  //   const theme = useTheme();

  //   const url = typeof window !== 'undefined' ? window.location.href : '';

  //   let color = theme.palette.primary.contrastText;
  //   console.log(`url: ${url}`);
  //   if (url.includes('page')) {
  //     color = theme.palette.primary.main;
  //   }

  const menuItems = [
    { title: 'Buyers', href: '/buyers' },
    { title: 'Land Steward', href: '/landsteward' },
    {
      title: 'Learn More',
      dropdownItems: [
        { title: 'Case Studies', href: '/casestudies' },
        { title: 'FAQ', href: '/faq' },
        { title: 'Team', href: '/team' },
      ],
    },
  ];

  return (
    <>
      <ThemeProvider injectFonts>
        <Header menuItems={menuItems} absolute transparent color={color ? color : null}></Header>
        <div
          style={{
            margin: `0 auto`,
          }}
        >
          <main>{children}</main>
          <footer>
            © {new Date().getFullYear()}, Built with
            {` `}
            <a href="https://www.gatsbyjs.org">Gatsby</a>
          </footer>
        </div>
      </ThemeProvider>
    </>
  );
};

Layout.propTypes = {
  children: PropTypes.node.isRequired,
};

export default Layout;

So it should be a parent of the component call makes the call. Which I am thinking is why I can't make the call from this same component. Because it's not a parent. In researching the best ways to do this, this person, suggests using gatsby-plugin-layout to avoid issues with FOUC. So I'm giving this a go on jared/home-fold-section to fix the header color.

https://www.figma.com/file/4bF2ANkIkCIdSJYBOy4H1L/New-Buyer-Flow-Integrated-into-regen.network-%2F-Site-Map?node-id=8%3A5011

Now that the layout is being set in a plugin, we no longer are able to send in different color parameters to the header from different pages. We could go back to using the http_location string in combination with a list of pages to change the color to in the layout file...but maybe one of you has a better solution? @blushi @clevinson

same as #33 but different background.

same as #38

Currently, we're using https://apply.workable.com/regen-network/
Should we pull data from it? In that case, we would need to filter dev only posts.
Or should we just replace this section with a link to workable for now?
Or have it editable from the cms so that it shows the featured job post? Then that means that the person who deals with that should make edits in both workable and the cms.

via gatsbyjs/gatsby#15601

Seems like they're trying to fix it, and there might be a couple hacky work arounds. But depending on what other libraries we use, it could be something we have to deal with down the road.

Embed airtable form for now (without email notification).