A static site for goinvo.com built using GatsbyJS.
NOTE: To work in this project, it is assumed you have basic familiarity with using the command line and Git/GitHub. If you are not comfortable with these tools, please reach out to a coworker for some help.
MORE NOTE: When copy/pasting the examples, do not include the $. This is used to represent your command line prompt, showing individual commands on new lines.
MANY NOTE: You may be required to install additional dependencies like XCode command line tools on Mac.
Homebrew is an easy way to install the system packages you'll need for this project on Mac. (Don't copy the $ :))
$ /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"Before you can use the brew command, you may have to add it to your path. If you are using a MacBook with an M1 or M2 chipset, try
$ echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> ~/.bash_profile"This project uses NodeJS at its core.
$ brew update
$ brew install nodeYou may also find it helpful to use a tool to manage your Node installations. nvm is a good one. Follow the instructions there to install nvm. The command that looks like curl -o- <url> | bash
Alternatively, brew can install nvm with $ brew install nvm
Then you can check your Node versions with:
$ nvm lsOpen a new terminal, and install the Node version the project wants by running:
$ nvm use
Check for warnings or errors. If you don't have the right version installed, it will give you a command to run, such as:
$ nvm install lts/*
Node comes with a package manager, NPM, by default. However, this project chooses to use Yarn instead, namely because it's faster and more secure.
$ brew install yarnUse the command line or your GitHub app to clone this project repository to your machine. When using the command line, make sure you're already in the folder you want the project downloaded to.
$ git clone https://github.com/goinvo/goinvo.com.git$ cd goinvo.com
$ yarn$ yarn developGive it a few seconds and you should see:
You can now view goinvo.com in the browser.
http://localhost:8000/Head over to http://localhost:8000/ and you should see the website.
There are many editors to choose from, but most of the time you won't need elaborate features for testing or debugging with this project. The main things you'll use are syntax highlighting and some maybe some additional packages to help with code completion and formatting. Some editors to consider if you don't already have a preferred favorite:
A thorough examination of best practices, tips, and resources related to coding at GoInvo can be found in our Styling Guidelines.
This project uses prettier to format code. This formatting will be triggered automatically on any staged files when you make a commit, so don't be surprised if your code changes slightly. You can also manually run yarn format to run code formatting across the project.
You may also wish to make things easier by installing and using EditorConfig, which will apply many of the same rules from prettier directly in your code editor. This helps keep things like indentation in check as you code. If you use Atom, there is an Atom EditorConfig package available.
Do not add or commit images directly to this project!
Content images are managed with Dropbox and should not be added here. But now that that's clear, there are a few exceptions. The only images found in this project are small images like icons and logos, many of which can often be included inline or as data URI's. When in doubt about where you should add an image, always ask for guidance!
TODO: Sharon to add details on picking proper images for the site.
Export your image (Photoshop example steps):
- Ensure the image is 2000px wide.
- Select 'File' > 'Save As'.
- Name the image appropriately using all lowercase letters, numbers, and dashes (that means don't use uppercase or underscores, etc).
- Use the 'JPEG' format (or 'PNG' if alpha channels are required), and click 'Save'.
- Set the Quality to Maximum (12), or slightly lower if the file size will be too large. We aim for a file size around 1.2M or below, but this can be higher for more complex images. Use your best judgment here, but avoid massive file sizes.
- Use 'Progressive' Format option with 3 scans.
- Click 'OK' and your image will be saved.
All the beautiful images you see throughout this site of our work, products, studio, and studioites are managed on our Dropbox account. Naturally you'll need access to our Dropbox account to work with these. Images for the website are stored in the Graphics/goinvo.com/ folder.
When adding an image, think about where it best belongs. The folders on Dropbox generally correspond with routes on the website. For instance, all photos for the 'About' page are in Graphics/goinvo.com/images/about/. In some cases, your image may be used in multiple spots throughout the site, but aim to place it where it feels most proper. For instance, if you have a hero image for the 'Vision' page, but it's also used in a card on the homepage, place it in the vision/ folder. Do not add the same image file in two different locations, this is unnecessary and creates a slower loading experience for our visitors. When creating new folders, use the same naming conventions as we use for images (lowercase letters, numbers, and dashes only).
IMPORTANT: You should not replace or remove images on Dropbox, and they cannot be replaced on S3 (it is possible to remove/replace on S3 but you must have the power). If you want to change an image somewhere on the site, simply name the file something new (i.e. rather than trying to replace an image called eric-beard.jpg, instead add a new image in the same folder called eric-beard-2.jpg, or whatever. Keep in mind that you'll now have to update any reference of eric-beard.jpg in the codebase to eric-beard-2.jpg).
Again, remember that folders and file names should have no spaces or funky characters. Just stick with lowercase letters, numbers, and dashes. Use dashes where you might normally use a space.
After moving your image(s) to Dropbox, you'll need to sync with S3. To do this, you need an Invo AWS account. If you don't have one, and you really want one, just say "Nickelodeon Magazine, PLEASE!". You can also get a coworker who already has AWS access to help you sync the images.
To sync to S3, you'll need to add your AWS credentials to ~/.aws/credentials. You can follow the instructions for that here].
Once those are in place, open up your command line and navigate to your Graphics/goinvo.com Dropbox folder, then run:
$ yarn uploadThat's it! You should see lots of messages like Already exists: <file>. Make sure your files were uploaded by scanning for the message Successfully uploaded: <your-file>. If so, your images are ready to use on the site. Note that the upload will fail if any of your images are not exported at exactly 2000px wide.
If you're looking to use an image in a case study, please skip to the next section. Otherwise...
The project has an <Image /> component which takes care of most of the image rendering process for you. Simply include the component with the path to your image (which corresponds to the Dropbox path) like so:
<Image src="/images/about/bowling.jpg" />By default, the image assumes it will always render at the full width of the screen. You can make better use of the responsive image technique by passing in some sizes, of which there are some presets in the config file:
import config from '../../config'
...
<Image src="/images/about/bowling.jpg" sizes={config.sizes.fullToHalfAtLargeInsideMaxWidth} />Or with custom sizes:
<Image
src="/images/about/bowling.jpg"
sizes={['(min-width: 20em) 100px', '100vw']}
/>Learn more about the sizes attribute in a nice article from Eric Portis.
To add images to your case study content, simply use the default markdown syntax. Use the path that corresponds with the directory structure in Dropbox. Be sure to include that meaningful alt text!
Sometimes, images are so small in file size, or in a format we don't need to process with the image service (like SVG), that we can include them directly in the project. Images less than 10kb will be rendered with data URIs by Gatsby, which is beneficial because it removes the request the browser would have to make to fetch the image. So in general, if the image is less than 10kb, or an SVG file, it can be included in the project directly. If uncertain if an image meets these criteria, ask for guidance. Be confident your image should be housed in the project before committing it in git. These types of images can be added at an appropriate location inside src/assets/images/. In general, following our styling guidelines, image file names in the project are prefixed by their type or purpose, like icon-email.svg or logo-npr.png.
Since these images will not run through the image service, we can use regular img tags to include them (instead of the <Image /> React component). To use an image from the project, you can import it in your JavaScript file then use it as the img source:
import logoNpr from '../assets/images/publication-logos/logo-npr.png'
...
<img src={logoNpr} alt="Logo for National Public Radio" />SVG's can be used in a similar manner to above, but also can be included inline using a special syntax. This is similar to using SVG's from a sprite sheet in that it allows for adding classes and control of the SVG through CSS. The key here is to add .inline to your filename before .svg, like icon-hamburger.inline.svg. Then capitalize your import variable name, as you would with importing a JavaScript class or component, like so:
import Hamburger from '../assets/images/icon-hamburger.inline.svg'
...
<Hamburger className="icon icon-hamburger" />Now we can use CSS to style icon and icon-hamburger, like controlling the size or fill color of the icon, etc.
Videos are also managed through Dropbox and work similarly to images. The project makes use of a <Video /> component. However, videos have a few extra requirements that images do not. First, videos need two sources, one as .mp4 filetype and one as .webm filetype. This is to make sure there is a video format that supports every browser's needs. Check the syntax below for how to include these formats in JavaScript. Also, videos should have a poster image (displayed before video plays, while the video is loading), and a fallback image (used if the video element is not supported by the browser). Use the component with the sources of your video (which corresponds to the Dropbox path), the poster image, and the fallback image, like so:
import Video from '../components/video'
const heroVideoSources = [
{src: "/videos/homepage/sdoh-hero.mp4", format: "mp4"},
{src: "/videos/homepage/sdoh-hero.webm", format: "webm"}
]
...
<Video sources={heroVideoSources} poster="/images/homepage/doh-hero-poster.jpg" fallback="/images/homepage/doh-hero-fallback.jpg" />First and foremost, remember to make a new branch in Git. It is reasonable to name it something like case-study-<name>.
Once you're set up on a new branch, make a new Markdown file in the src/case-studies folder. Name the file with all lower-case letters and hyphens, with the .md extension. The convention is to list the client name then project name (e.g. mitre-shr.md, fastercures-health-data-basics.md). It's fine if the name is a bit long, but also probably best to not go crazy on it. Some clients have sensible abbreviations, like jnj for Johnson and Johnson. Invo projects can omit the client name portion of the file (e.g. paintrackr.md, hgraph.md).
Inside the file, the first thing to do is add the frontmatter at the very top of the file. This is meta data associated with the case study, used throughout the rest of the website. It must be at the top and include the --- syntax, as shown below:
---
title: 'Health Data Basics'
image: '/images/case-studies/fastercures/health-data-basics/hero.jpg'
client: 'FasterCures'
caption: 'Engaging patients to understand health.'
categories:
- 'public-health-and-policy'
- 'open-source'
results:
- stat: '97%'
description: 'Recall of educational concepts'
- stat: '90%'
description: 'Engagement with knowledge retention quiz'
- stat: '8,760'
description: 'Yearly views of new health data definition'
upNext:
- 'code-ryte'
- 'acme'
- 'mitre-shr'
hidden: false
---You can also look at other existing case studies as examples.
Let's break down the fields:
title(required) This is the title that will be shown on cards throughout the rest of the site, not necessarily the title shown on the case study page (you'll make than with an h1 or#in Markdown).image(required) The path to the image on Dropbox to be used as the hero and the card image on other pages.client(required) The client we worked with on the project. For Invo projects you can use an empty string ("").caption(required) A one-liner describing the project.categories(required) A YAML array of ID's for the categories (or 'tags') associated with the project. These must be selected from a predefined list, located insrc/data/categories.json. The exact ID string must be used or it won't work. See the example above.resultsA YAML array of objects including astatanddescriptionfor that stat. See the example above. Currently, the results only support text. In the future we'll work to add an option for including buttons/links.upNext(required) A YAML array of ID's associated with other case studies to link to at the bottom of the page. The ID is simply the filename of the case study you'd like to link to without the extension. See the example above.hiddenControls whether the case study should show up as a page and be included in lists of case studies throughout the site. Set totrueif this case study is a work in progress. Keep in mind that even though it will be hidden from the site, this content is still publicly accessible on GitHub, so never include any content that we don't have client approval on.metaDescription(not required, but you should really include this) A concise summary of the case study, usually only a sentence or two long, used for search engines and link details. For more information, read how to create the right meta description.
NOTE: If you don't include required frontmatter fields, the app may crash.
When you add a new markdown file, it is necessary to restart your development server. Use ctrl + c to kill your process then start it up again with yarn develop. This will add your new markdown file in the list of case studies. The case study you're working on will become accessible through the 'Work' page, or at http://localhost:8000/work/<filename> (filename without .md file extension).
For the most part, just write plain old Markdown. If you're unfamiliar with Markdown, it's a very basic programming language, designed to make writing content a breeze. Read up on the syntax here.
Each page should have exactly one h1 title, written with markdown using # (e.g. # This is the title). Subsequent sections can get h2 (##), h3 (###), and so on.
All Markdown pages in this project make use of a wonderful plugin for Gatsby called gatsby-mdx. This allows us to use React components inside our Markdown, inserting more complicated markup and code where we otherwise wouldn't be able to insert it. Though you can use virtually any component in the markdown, the ones used most frequently in case studies are Dividers and Quotes. To use these, you need to import them near the top of the file, underneath the frontmatter section:
---
... frontmatter stuff
---
import Divider from 'components/divider'
import Quote from 'components/quote'Then use them anywhere you like in your content:
Here is some markdown paragraph content.
<Divider />
## Hey a new section!
With some more content. And I sense a quote coming...
<Quote quotee="Merkin Muffley" quoteeSub="President of the United States">
Gentlemen, you can’t fight in here. This is the war room.
</Quote>
Wow I was right. A quote.Make commits to your branch adding content to your case study as you go, and make sure to push your branch to the GitHub repo. When finished, seek assistance getting your case study code reviewed and merged into the production website.
First and foremost, remember to make a new branch in Git. It is reasonable to name it something like feature-<name>. This section is mainly for adding simple features that follow the same general layout and styles as the rest of the GoInvo website.
As stated above, to review changes as you make them, just open a terminal and run yarn develop. Then you can view your work live at http://localhost:8000/
Once in your new branch, create your feature directory in src/pages/vision/your-feature-url. Create a new file in this folder called index.js and get started.
As you go, you may make several commits to your branch and push them up to Github. If you want to share your feature with folks to review before going live, you may locate your branch in the list of branches, and create a new pull request. If you're not ready to go live yet, you can add a tag for don't merge yet and that'll indicate to reviewers not to approve and merge just yet. After automatic checks have passed, a netlify url will be generated for your branch and you can use this to check that your feature works and looks how it should, and it can be shared to others to review your work before it goes live. After that, you can continue to work and push as normal. When you're ready to go live, just remove the don't merge yet tag and let a reviewer know that you're ready for their review.
import React, { Component } from 'react'
import Layout from '../../../components/layouts/layout'
import Hero from '../../../components/hero'
import Image from '../../../components/image'
import Divider from '../../../components/divider'
import References from '../../../components/references'
import Author from '../../../components/author'
import { mediaUrl } from '../../../helpers'
import config from '../../../../config'
const frontmatter = {
metaTitle: 'Your Feature Title',
metaDescription:
'Brief feature description.',
heroImage: '/images/features/your-feature-url/your-feature-hero.jpg',
}
You can also look at other existing features as examples.
Let's break down the fields:
React(required) Allows React to work its magic.Layout(required) More magic here. Layout magic.Hero(required) Displays the hero standard to the rest of the GoInvo site.ImageAny good feature has an image. We'll go over how to add images below.DividerIf you want to use the<Divider />graphic consistent with the rest of the GoInvo site.ReferencesAny good feature also has references. We'll go over how to add images below.AuthorA nifty component for easily adding team members as authors to the feature!mediaURLHandles access to media items. For example, if we have a poster we want readers to be able to download, we store those in a media folder (covered below) and set up a download link or button.configNeeded when you have images. This helps with resizing images for different browser widths or mobile views.metaTitleThis is the title of your feature. You want to make this somewhat short, ideally <30 characters. Should match the title feature infeatures.json(We'll cover this in a bit too)metaDescriptionA brief description about your feature. With the title, date, and tags, this should fit comfortably in a small card on the Vision page. Should match the description infeatures.jsonheroImageLink to the hero image for your feature. We'll cover adding this with images.
class YourFeatureName extends Component {
render() {
return (
<Layout frontmatter={frontmatter}>
<Hero image={frontmatter.heroImage} />
<div className="{your-feature-name}">
<div className="pad-vertical--double">
<div className="max-width max-width--md content-padding">
// start coding your feature
</div>
</div>
</div>
</Layout>
)
}
}
export default YourFeatureName
Hero(required) Grabs the URL we defined in the frontmatter to display the Hero based on the Layout componentyour-feature-name(required) Lets you create styles specifically for this feature without overwriting styles elsewhere on the GoInvo site or in other features.pad-vertical--doubleandmax-width max-width--md content-paddingAnything inside of these divs will be constrained to the max width of content consistent with the rest of the site. If you want to set a style or image to bleed all the way to the edge, you'll want to close this and place it outside.export(required) Actually exports your feature, should match the feature name inclass YourFeatureName extends Component
Writing up a feature is a little different from a case study, because instead of markdown, we're using straight-up html.
In general, unless your feature needs specific styling, most of the website styles and utility classes should work for your feature. If you need specific styling, in src/styles/vision, add a new file _your-feature-name.scss. At the bottom of the main.scss add this stylesheet as @import 'vision/your-feature-name';. Start off the styles in your .scss file with .your-feature-name { }, consistent with the className you used at the beginning of your feature html, and add your feature's specific styles inside of the brackets.
We use classes to impart header styles defined in the GoInvo style guide. The typical breakdown is as follows:
h1 className="header--xl"Adobe Jenson Pro, font-size: 2.25rem;h2 className="header--lg"Adobe Jenson Pro, font-size: 1.5rem;h3 className="header-md"Open Sans, font-size: 15px;, font-weight: 600;, text-transform: uppercase;,h4 className="header-sm"Open Sans, font-size: 16px;, font-weight: 600;
Try to use one <h1> at the beginning of your feature to showcase the title. For following titles that you want to appear the same size, you can use an <h2> with the header-xl class. To center text, add text--center.
Try to use header-md only for categories. For descriptive titles, use header-sm.
Adding buttons is as straightforward as adding a button and button-primary classes to a link, but there's a button-group class to contain multiple buttons at once or centers a single button.
<div className="button-group">
<a
href={mediaUrl(
'/pdf/vision/your-feature-url/your-feature.pdf'
)}
className="button button--secondary margin-top--double margin-bottom--double"
>
Download
</a>
</div>
Pretty much the same as adding images for case studies. We'll just restate some of the basics. When exporting your images, you want them to be 2000px wide, progressive jpg, and ideally 72dpi (more px per inch will increase the filesize). Save them into our dropbox folder at Graphics/goinvo.com/images/features/your-feature-url/[your-feature-image.jpg using lowercase and dash separation. Add your hero image here too.
You'll need AWS permissions to do this, so if you don't have what you need, check with Craig, Eric, or Jen. To upload your images, open a terminal in the goinvo.com dropbox folder and run
$ yarn upload
When adding the image to your feature, it will look like this:
<Image
src="/images/features/your-feature-url/your-feature-poster.jpg"
className="image--max-width"
sizes={config.sizes.fullInsideMediumMaxWidth}
/>
Captioning your image is simple, with
<p className="text--caption">Caption away</p>
When linking away from the site, we generally want to open up a new tab to not disturb the reader's current position, so add target="_blank". When linking externally, or whenever using target="_blank", add rel="noopener noreferrer".
<a
href="https://github.com/goinvo/HealthDeterminants/"
target="_blank"
rel="noopener noreferrer"
>
GitHub
</a>
So far, media has included pdf downloads of posters or reports associated with the feature. Unlike when adding images, these are not relegated to 2000px width and jpg format. Instead, these would typically be printable pdf quality. You would save these out similarly to Dropbox, in Graphics/goinvo.com/pdf/your-feature-url/your-feature-file.pdf. These get uploaded with the yarn upload command as well.
When adding a link to the media in your feature, use the following:
<a href={mediaUrl(
'/pdf/vision/your-feature-url/your-feature-preview.pdf'
)}
target="_blank"
rel="noopener noreferrer"
>Download</a>
Thanks to the 'Authors' component we added earlier, adding authors is easier than ever. For active team members, all you need is their name to access their photo and bio. Optionally, you can include company and name on an author card.
<h3 className="header--md">Authors</h3>
<Author name="Jen Patel" />
<Author name="Juhan Sonin" company="GoInvo, MIT" />
For external contributors or authors, since we don't keep a photo and bio on hand for them, we have to write out the author card, which looks like this:
<Author
name="Vanessa Li"
company="University of Washington"
image="/images/features/your-feature/headshot-vanessa-li.jpg"
>
Vanessa specializes in health systems and public health
modeling, with an emphasis in substance abuse and disease
prevention research. She graduated from the University of
Southern California with a B.S. in Public Policy and a double
minor in Business Economics and Global Health. Vanessa is
working towards a graduate degree in biostatistics at the
University of Washington.
</Author>
To add linkable references in your text that, when clicked, will scroll down to the references section.
<sup>
<a href="#references">8,18</a>
</sup>
You would list your references at the bottom of your feature, just after the Authors section, and preferably with a <Divider /> separating the two. When rendered, references will be listed in an ordered list format. For links, you need only add the url, such as https://github.com and the references component will take care of the rest. It is also helpful and good citation practice to indicate when the reference was last accessed during research for the feature.
<Divider />
<div id="references">
<References
references={[
{
title: '[citation]',
link: '[url if there is one]'
},
{
title: '[citation]'
}
]}
/>
</div>
Open up src/data/features.json and add your feature to the top as the following. Your title doesn't necessarily have to match the url, but they should be similar enough for readers to find it on the world wide web.
{
"id": "your-feature-url",
"title": "Your Feature Title",
"date": "Feb.2019",
"client": "Feature",
"categories": ["open-source", "public-health-and-policy"],
"caption": "Brief feature description.",
"image": "/images/features/your-feature-url/your-feature-hero-2.jpg",
"link": "/vision/your-feature-url/"
},
When a new teammate starts, we ask them for a bio and photo. Once we have an approved bio and photo, we’re ready to get them on the website.
Original photos should be uploaded resources > photos-people > Headshots > [name] Photos for the team page should be resized to 2000px width, saved as optimized jpg, and uploaded to Dropbox: Graphics > goinvo.com > images > about Someone with AWS credentials (Craig, Eric, or Jen) should run yarn upload and the image should be ready to use.
In the data/team.json file, add a team member using the following: { "name": " ", "title": " ", "bio": " ", "social": { "email": "name@goinvo.com", "twitter": " ", "linkedin": " " }, "image": "/images/about/headshot-first-lastname.jpg" }
When your feature is ready to go live, make sure to push up any final changes to the branch. Then, on Github, you may locate your branch in the list of branches, and create a new pull request and let a reviewer know that you're ready for their review. Once approved, the final reviewer will merge it into master.