dbeattie / nag-me Goto Github PK

If you simply change the navbar/appbar to ="fixed", it will cut off the content below it. Need to give it the appropriate padding on the bottom to push the other content down so it doesn't overlap and cut things off at the very top.

Set up seeds for API so that we have something to connect to on the front end.

To accept new users, goals, nags routing.

Fatima suggested it as a nice dynamic component (for notifications mostly).

Toastify Documentation Here
Toastify Code Samples Here

Mailgun, Mandrill, or SendGrid Integration (my[Darren] vote is probably Mailgun)

Ideally set the drawer up:

• Right Align
• Hide existing buttons in the nav bar in the drawer

BONUS:

• Make it mobile responsive. If we're planning to do a mobile view in our presentation though, that might not matter much...

To show how consistently a person has stuck to their nag completions.

Basically a percentage of nags recorded completely compared to how many nags a person has received from the current date.

API isn't rendering out the JSON tables to the /api/:id routes properly when in development mode (local machine).

Trying to get 3 tables to render properly as JSON objects on the API server so we can push the server to Heroku and then start connecting the front end on a feature to feature basis.

Edit and Delete will be separate things to do, for simplicity.

• Needs to query the DB for end_dates
• Then if end_date is still in the future, create a new nag with a 'false' boolean
• That false boolean is what the user will mark true if they practice that day
• If they don't, then the Twilio Cron will text message friends saying 'the didn't 'run 30 minutes today' or whatever they are doing to try and keep themselves accountable.

Return basic JSON object from the Nags Table so we can check the front end.

Look at Material Ui Sign In Example for sign in and look at Material UI Sign Up Form.

Examples are taken from:

Currently, the SignUp component does not render underneath the navbar when at the /register route.

React router logic needs to be fixed to display the new SignUp component underneath.

Table that lists the day in one column and a checkbox in the other for now...

User clicks the checkbox to indicate they completed it.

Database gets updated with truthy values on save or something, so will need save unless we can figure out how to do it real-time. Web Sockets might enable such functionality?

Just a different way to show off the table, in more of a calendar format. Check off the days you complete either in the box or something that simply shows you what days you completed your nags and what days you didn't.

Some insights into this can be found here

Currently, the login component does not render underneath the navbar when at the /login route.

React router logic needs to be fixed to display the new Login component underneath.

Create basic users route to return a JSON object from the users table.

Used existing scheduler API as boilerplate with mild modifications, need to rework for our needs.

Nag.me API

The GET request we currently have is getting all of the SQL date component.

Create a helper function to trim this information before it goes into the Table.

Will need to go to the create form that is populated? Or will it need to be a new form?

Let's break this longer form down a bit

H2 Tags for:

• '/'
• '/login'
• '/register'
• '/goals'
• '/nags'

Just adding this for fun, it was a stretch Martin gave me for my mid-term and we never got there.

Currently no way to delete cookies from the front end.

I'm a big fan of the first middle option

It's a mobile modal that opens up and fits our mobile-first approach.

When you click things on the navbar it's not going to the correct URL.

Will need to make a post/delete request on the back end to the DB.

Create a navbar component

• Will show login/register if user not logged in
• Will show goals page and nag tracker page options
• See Here

Form element in the create goal form to get frequency of the nag.

Look Into Chips

For a phone, I'm looking for 7 circle components that have S, M, T, W, T, F, S and then highlight on when day selected or highlight off.

I was trying to do some research on this and came up empty other than chips...

Select All * query to render table from db to /goals as JSON object.

Need to auto-populate the nags page with data from the database.

Either using Bcrypt and Cookies on the back end OR something like AuthO.

Gif of Will Smith from Fresh Prince of Belair
OR a safer image...

Little blurb, 2-3 features with an image or something, pretty standard, low priority but somewhat needed for MVP.

Set up Twilio API and get text messaging working.

• Will need to set up Cron jobs appropriately to query the database at specific times.

Get cookies from the API server to the front end.

Add nag section to create goal form/page.

Submit Button

Maybe clean up the form so that it's one component not two as it currently is. Then you have one solid form outputting when the submit button is clicked.

• GoalsIndex is currently hardcoded
• Should be dynamically rendered based on the user logged in.

Need to style the create goal page '/goals/new'

Create a React Button Component

Check this out

Getting an error within the tables when trying to persist the data.

i.e. trying to save a new goal, or trying to edit a goal or trying to delete a goal

Add Date Selector to goal form.

Pusher Is probably the most well-known API for this
OneSignal is another option

There are others...

Perhaps asking a mentor will be useful here to see if anyone has experience with any API's and which one might be the fastest to get set up (Pusher looks like a good option)

I believe we'll also need to enable PWA functionality in React for this but Vasily did that in like < 20 minutes in a lecture so I don't think that will be too difficult, it's just manipulating a few things within React.

New NavBar conflicts with old routes in App.js

A way to trigger each nag for the same time on the day they are triggered/fired.

Create an Axios put request that inserts new goal creation into the database.