Agh, I don't know what to do. Let's create a list.
this list is not specific to the frontend at the moment, it's just all the things I can think of

• #54 (backend placeholder ticket)
• Click on Following to show everyone the user is currently following
• Create a table to associate followers
• Create a follow button
• Make all the fields in the database editable through a mutation call
• Make a CDN so that images can be uploaded.
• Clicking on an item in the tick-list should take you to that adventure
• Have a list itemizing the history of activities (this is the user's resume of sorts to show other user's their capability).
• Have a contact user button
• Have a contributions tab

• #62
• #58
• #59
• #60
• #61

Login Flow

• Add a forgot password button
• Add a return to create user button
• Clean up header text
• Clean up input fields
• Show text in password field
• Implement forgot password button
• Implement return to create user button
• Add an overlay behind <DisplayCard />
• Position correctly on screen

Create User Flow

• Clean up input fields
• Add a return to login button
• Create a spot for legal notices

Add Forgot Password Flow

• Add send email field and button
• Do the whole 'send an email' thing

• Username
• Bio
• Activity List

Receive edits to an adventure from the clients and save them to the db

Finished Tasks

• Click add adventure
• Double click the map
• Pulls up edit adventure pane
• Fill out required fields
• Add an error field to edit adventure
  I'm not sure I'm gonna do this because most of the fields aren't required
  Actually, although they aren't required, many of the fields have specific values so I can enforce that
• Send request to backend
• Close window

Unfinished Tasks

• #47
• #48
• #49
• #50
• #51

Just a placeholder so far

Edit all applicable fields of an adventure and save them to the backend

Platform Learning

• Create an environment locally
• Add a database
• Add users
• Add a table
  • Add columns to the table
  • Add rows to the table
  • Select rows
  • Change rows
  • Delete rows

Set up for backyard friends

• Create a byFriends database
• Create a users table
• Create a lines table
• Create a ticks table
• Create an activities table

Contents

• Followers
• Following
• Activities done
• Image
• Activities to do
• Location
• Gallery

• Make Create a User and Login buttons for when a user isn't currently logged in
• Make a Create a User flow
• Make a Login flow
• Login should select from available users

Refer to Adobe XD board

gear_required and season are saved as arrays of the possible choices to choose from. In the static view, it would be nice to save those fields with some kind of interesting UI element to them so it's easy to visualize.

Routing Layers

User Layer

• /user
  • /login POST - login user
  • /add POST - add user
  • /other GET - get another user's data
  • /edit PUT - edit user
  • / DELETE - delete user

Lines Layer

• /line
  • / POST - get all lines for an area
  • /add POST - add a line
  • /detail GET - get a line's full details
  • /edit PUT - edit a line
  • / DELETE - delete a line

Ticks Layer

• /tick
  • /add POST - add a new tick
  • /line GET - get all ticks for a line
  • /user GET - get all ticks for a user

Activities Layer

• /activity
  • /add POST - add a new activity
  • /line GET - get all ticks for a line
  • /user GET - get all ticks for a user

💡 Note: I'm not using routes except for external APIs which I haven't developed yet. I'm converting all the routes to GQL schemas.

• Create a Tick List of lines you want to ski, climbs you wants to send or trails you want to hit. See who else shares your ambitions and go do it.
• Enter your accomplishments for others to wow at what you've been able to do this season
• Check in on other's accomplishments to see if they match up with what you want to do
• Give beta on lines to share with those aspiring to get to where you are

Use MapBox free tier. This should help me render everything I need to.

https://www.youtube.com/watch?v=IJA0Nu_gMJY&list=PL_cUvD4qzbkxZZyyuXa1xkWFhRB_NoQwl

Express-Apollo Template
https://github.com/aichbauer/express-graphql-boilerplate/blob/master/api/api.js

Everything has been migrated back to Express, no more GQL.

Flow 1 - User sign in:

• route /api/users/login

Flow 2 - Page load:

• GET /initial

Flow 3 - Tick added:

• POST, (adventure_id, user_id)
  • route /tick/create

Flow 4 - Activity added:

• Same as above, but activities table
  • route /activity/create

Flow 7 - Add a new adventure:

• POST, (adventure object)
  • route /adventures/create

Flow 8 - Add a new user:

• POST, (user object)
  • route /api/user/signup

Flow 9 - View other user:

• GET, (new_user_id)
  • route /user/other

Flow 10 - View detailed line view:

• GET (line_id)
  • route /line/detail

Flow 11 - Edit user:

• PUT request (user object)
  • route /user/edit

Flow 12 - Delete user:

• DELETE request (user_id)
  • route /user
• Remove all ticks for that user
• Remove all activities for that user

Flow 13 - Edit line:

• PUT request (line obj)
  • route /line/edit

Flow 14 - Delete line:

• DELETE request (line_id)
  • route /line
• Remove all ticks for that line
• Remove all activities for that line

First create a table of all searchable entities
Then search that table