Skip to content

tyler-morales/visit-national-parks

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

Parkwayโ€“ Visit National Parks

Parkway is the Goodreads for National Parks across America. Discover parks, save parks to you list of visited and want to visit places, and learn more about events near you.

A full-stack web that helps outdoors enthusiasts discover and save their favorite National Parks across America, Parkway is the one stop shop to tracking and planning trips across the US. Leveraging the National Parks Service API in combination with Amazon Web Services, users are presented with beautifully displayed data from all 463 parks! Through Google social sign-in and email sign in, users can save the parks theyโ€™ve visited and want to visit. Built from a love of the outdoors and having struggled to find accurate and unbiased information from sponsored blogs or articles, I decided to build a solution to finding every National Park in the US. Think of Parkway as the Goodreads for National Parks!



๐Ÿ“– Background

I love road tripping. On countless trips with friends and family it has been difficult to search for official parks sanctioned by the National Parks Service. Many of the websites I found were sponsored blogs that promoted already popular National Parks. What I and those around me wanted was a place to find the lesser traveled places.

This is where Parkway was born. After a proof of concept MVP at Columbia college that myself and three of my classmates built, I took a break, but couldn't get this idea out of my mind. It wasn't until December of 2021, about six months after we pushed the first version when I started to rebuild the entire project from scratch.

Fast forward to the last day of Februray 2022 and I've released a stable version of Parkway! More improvements are soon to follow, so be sure to come along me with this version.

๐Ÿ† Goals

The two main goals of this project are to:

  1. Build my technical knowledge on Next.js
  2. Create a production website that REAL people can interact with and utilize

๐Ÿ›  Features

  • ๐Ÿ— Discover every sansctioned National Park including National Seashores, Trails, Mounuments and more...
  • ๐Ÿ’พ Save all the parks you've visited or want to visit

Think of Parkway as the Goodreads for parks in America. View information for a park, and if it interests you, save it to your "Want to Visit" list or your "Visited List"

๐Ÿ’ป Tech Stack

Front End Backend Packages
React/ Next js AWS Amplify (Hosting & CI/CD) Formik (Forms)
Tailwind css AWS Cognito (User Authentication) Mapbox
AWS Dynamo DB (Database) Splitbee (Analytics)
GraphQL (API)

๐Ÿ”ฎ Future Features

  1. Social Users I would like to add the ability to allow users to search for their friends and family to see where they have visited. They could also add them to trips and plan group trips together

  2. Guides Currently, through the many blogs, there aren't unbiased accounts of what to do at National Parks. I think it would be great to have unbiased or park rangers give their advice to what to do at parks.

๐Ÿ‘ฅ Contributing

I'm glad you are considering contributing to this project. I've poured a ton of hours into this and I would love to see any of your additions. Please read the following to make contributing easier for both you and me.

Note: If you need to access AWS credentials reach out to me and I can get you setup with that.

Step 1: Creating a branch

If you see an issue that sparks your interest or if you would like to contribute something else please follow this guide:

Branch Structure

  • Branches should follow this format
    • feature/name-of-branch (a new feature that is being made)
    • update/name-of-branch (an update to an existing feature)
    • bug/name-of-branch (a bug fix)

Step 2: Create a PR

Once you are happy with your branch, submit a PR with comments and a descripting documenting what you changed.

When I get the notification that you submitted a PR, I will review the PR and if there are no errors, merge it into main. If however, there are errors, I will provide you with what errors exist so you can fix them.