redacademy / beta-summer-2017 Goto Github PK

TBD.

The login screen asks for the user's:

• First Name
• Last Name
• Email
• Password

Plan the score reducer to gather the stats needed to populate the graph on the dashboard page.
This will require an understanding of:

• what form the survey data will be in on submit.
• read into transactions with Firebase

Have basic structure laid out.

For the surveys, the same style/component is used, but the questions and answers will change (logic in container).

Create the reusable outline button viewable on the login/sign up screen.

There are several pop-ups during and after answering the Survey Questions. These pop-ups will be used with the Solid Yellow Survey Buttons.

Implement navigation between screens starting with the landing page.

Basic navigation from scene to scene.

Create a google developer's account for association with the Firebase SDK. Account will be shared among teammates.

The Signup fields will be reused for the Edit Profile Scene as well. Once the user finishes signing up with their first name, last name, email and password, they will be redirected to the Edit Profile scene where they can also fill out their "Bio", "Things I'm Working On", Twitter, LinkedIn and Facebook links.

Fields for SignUp & Profile Scene:

• First Name
• Last Name
• Email
• Password

Add a routes file that provide routing to all possible scenes within the app.

The landing page shows the Beta Talks logo, the Login button and a signup link.

Received fonts and images from design team.

Set up nav structure

Research implementing firebase db into app.

Build on the presentational components Charlie created for the survey scene and make it work functionally so that a form is submitted at the end of the scene pipeline.

The My Speaker Dashboard scene shows the user's speaker skills over time per talk, which they can click each bar to see the skill graph.

The home screen shows the "Next Event" including the date, time, attendees and location of the talk.

Create JSON data to populate FireBase databases with.

This single event scene lists the speakers for the event including the topic and speaker.

This scene will also contain the "Attend Event" button.

Added missing # to a few of the preset colors.

Changes to be made:

• Create login scene
• Signup Page w/full name & profile changes
• Attending Event - Entering code when attempting to give feedback prior to the date of the talk.
• Implement button for users to attend events as none currently exists.
• Removed tags from survey and reduced number of survey pages (no additional comments field)
• Verify how speaker goals are to be determined (we suggest adding them to edit profile)
• No blog page/resources as they do not currently exist on the website.

To access the survey one must enter an event code. These are hardcoded into the db for each event. We need a method to match the user-input to the code in the db and if they match, allow access to the survey for that event.

Create the custom loader using the lightbulb from the main-screen. Assigning Sonia because she has experience with custom loaders from Lunch Buddies.

The Events scene will list all of the upcoming Events with the following filtering options:

• Past
• Upcoming
• Attended
• My Talks

Based on current needs for tabnav, we are likely going to have to migrate to React Navigation from ExNavigation for their support of tabnavbar pop-ups. This will require further investigation.

This scene shows the information for an individual speaker of an event.

This page contains the "Give Feedback" button which will prompt the user to enter in the event code for access to the survey questions.

Themes config should include default settings for

• colours
• fonts
  in a similar manner as it was implemented in R10.

Decide Schema

Basic implementation of all scenes with routing and tabnav where needed. Styling and wiring to follow.

Get all files by Thursday.

These navigation arrows will be used for the Survey Questions scene, My Talks and Dashboard.

This is the welcome pop-up that appears after the user has successfully signed up to use the app.

Implement Auth so we could proceed with db helper functions

Create an eslint config file with custom rules to define standarized code across all teammates.

Added button component to landing page to allow for navigation between LandingPage and Login

Implement routing using exNavigator to push and pop between each scene. This is not necessarily complex, just time consuming.

Dependant on Eric and Sonia providing me some boilerplate.

• Fonts
• Images

Remove the default README content and add our own.

Implement the score reducer to parse form data and pass back into individual speaker to update stats.

Update that README again!