You're More Amazing Than You Think!

YMATYT is a project started by Wren Turkal to remind people how amazing and important they are. The goal of the project is to build confidence in folks around the world, especially those who find it confidence difficult to come by.

The code for this site is based on the GatsbyJS project.

🚀 Quick start

1. Clone the repo

   Use the Git CLI to clone the site code.

   git clone git@github.com:ymatyt/ymatyt_site.git

2. Install NPM and Gatsby CLI

   Install npm via their instructions..

   Install Gatsby CLI:

   npm install --global gatsby-cli

3. Start developing.

   Navigate into your new site’s directory and start it up:

   cd ymatyt_site_code/
   gatsby develop

4. Open the source code and start editing!

   Your site is now running at http://localhost:8000!

   Note: You'll also see a second link: http://localhost:8000/___graphql. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the Gatsby tutorial.

   Open the ymatyt_site_code directory in your code editor of choice. The home page code is in src/pages/index.js. Save your changes and the browser will update in real time!

🧐 What's inside?

A quick look at the top-level files and directories you'll see in a this projectdirectory.

.
├── node_modules
├── src
├── .gitignore
├── .prettierrc
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── gatsby-ssr.js
├── CODE_OF_CONDUCT.md
├── LICENSE
├── LICENSE.deps
├── package-lock.json
├── package.json
└── README.md

1. /node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed. These are not checked into the repo.

2. /src: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser) such as your site header or a page template. src is a convention for “source code”.

3. .gitignore: This file tells git which files it should not track / not maintain a version history for.

4. .prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.

5. gatsby-browser.js: This file is where Gatsby expects to find any usage of the Gatsby browser APIs (if any). These allow customization/extension of default Gatsby settings affecting the browser.

6. gatsby-config.js: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you’d like to include, etc. (Check out the config docs for more detail).

7. gatsby-node.js: This file is where Gatsby expects to find any usage of the Gatsby Node APIs (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process.

8. gatsby-ssr.js: This file is where Gatsby expects to find any usage of the Gatsby server-side rendering APIs (if any). These allow customization of default Gatsby settings affecting server-side rendering.

9. CODE_OF_CONDUCT.md: This is the code of conduct for this project.

10. LICENSE: This project is licensed under the Apache 2 license.

11. LICENSE.deps: This is the license of dependencies used in this project.

12. package-lock.json (See package.json below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. (You won’t change this file directly).

13. package.json: A manifest file for Node.js projects, which includes things like metadata (the project’s name, author, etc). This manifest is how npm knows which packages to install for your project.

14. README.md: A text file containing useful reference information about your project.

💫 Deploy