This is a Pokédex built with Gatsby. It uses my own GraphQL server, which uses the PokéAPI SQLite3 database for the data source. Since the data is from an external source, some data is still incomplete (i.e. Let's Go Pikachu, Let's Go Eevee, Sword, and Shield). I periodically pull from PokèAPI to update the database to keep the app up to date, but at the end of the day, I'm at the mercy of PokéAPI.

In Progress

• Desktop design and implementation

Using this repo

1. Clone this repo and install the dependencies

   npm install

2. Spin up the development server

   gatsby develop

3. Open the source code in your code editor and start editing!

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

   _Note: To play with the GraphQL queries, navigate to http://localhost:8000/___graphql

🧐 What's inside?

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

.
├── node_modules
├── src
├── .gitignore
├── .prettierrc
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── gatsby-ssr.js
├── LICENSE
├── 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.

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 the 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. 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).

10. 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.

11. README.md: A text file containing useful reference information about this project.

🎓 Learning Gatsby

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

• For most developers, it is recommended starting with the in-depth tutorial for creating a site with Gatsby. It starts with zero assumptions about your level of ability and walks through every step of the process.

• To dive straight into code samples, head to the documentation. In particular, check out the Guides, API Reference, and Advanced Tutorials sections in the sidebar.

💫 Deploy