guildcrafts / interview-app Goto Github PK

Add Menu button to approval page.

When user submits options on intro page, they will be redirected to the path based on selected game mode.

Add link in menu called "Approve Questions".

Create Go - init script for new contributors to easily setup their environment.

Write a script to initialize project
Write a script to setup database
Write a script to setup environment
Write a script to create testing scripts to create and drop database

After go file is complete, edit readme doc for goal.

*Get advice from pro-player for how to make go file if you're unsure.

• Profile page should include the following user information:

  • Name
  • Experience
  • Interviews completed
  • Interviews assisted
  • Number of questions completed
  • Join date
  • Date of last interview completed
  • Notes from previous interviews
  • Number of questions user has submitted

Configure webpack so it will have hot reloader.

Below the questions section, Interviewer can see the answer to question (or multiple answers, depending on the question).

In game page, create prompt button which displays a prompt/hint for the interviewer to use.

Work on front end design to make user interface more enjoyable and intuitive.

Create Database Schema

Approvers will see a badge number within the menu side-bar with the number of pending-review questions. Approvers should be able to approve, deny, or edit questions.

Build CRUD (Create, Read, Update, Delete) functionality for users.
Build CRUD (Create, Read, Update, Delete) functionality for questions.
Build testing for all CRUD functions.

For users, find by github handle
For questions, find by id
etc.

In question section, build a time tracker to track how long it takes to complete a question.

When the "create a question" button is clicked, a modal appears with the submission form.

https://getuikit.com/v2/docs/modal.html

Within the menu, add "create a question" link

Interviewer will have a list of process provoking prompts/hints located under the questions section which can be used to help candidates if they get stuck.

These may take a while to populate (they will be more specific according to the questions), but here are a few open ended ones:

• How would this be used?
• What is the smallest next step you can take?
• Describe what you're trying to do.

Create a new questions table in database for Whiteboard questions (Mimics Speaking Questions)

Approver column in user table will be boolean and allow user to access approval page.

"Approve Questions" link navigates to the approval page.

Create a table for prompts which connects IDs from the question table.

(Prompts are hints that the interviewer can give when the candidate is stuck)

Work on design of approval page.

Create a speaking questions table with the following columns:

• question
• difficulty_level
• topic
• point_value
• time_limit

Create knex.js
create confi.js
create db.js
create migration scripts within package.jsonn
run migration
populate migration with knex.schema.createtable

Install appropriate npm modules required

*Create a new questions table per game mode.
*Pro-players will (eventually) populate the questions table, or provide values for you to enter.

Add approved boolean column to questions.

Write bash scripts for setup in a Go file.
Include help section and various go init scripts.

Build user login (based off of GitHub login account) so that both the interviewer and the candidate can have their stats recorded.

See previous Learner's Guild OSS projects for examples of files.

IDM setup:

• Create .env.development file
• Add within README the steps for authenticating yourself to IDM
• Install npm module for "dotenv"
• Create config/auth.js
• Setup config folder
• Add @learnersguild/idm-jwt-auth to package.json
• Test with team mates who haven't set up IDM yet.

Interviewer will ask questions, then mark "correct", "incorrect" or "pass".
"Correct":
Provides experience points to candidate

"Incorrect":

"Pass":
Skips question

Connect functionality to all links and buttons

When the new question form is populated and submitted, it creates a question within the database. The "Approved" column for all new questions is default to false, until the question has been approved within the approval page.

Author of questions - When new question is submitted, the author is recorded within the question database.

• All input fields need to be assigned to db columns that they will effect.
• Routes need to be connected to submit, edit, delete buttons or form, and submit button of finished interview (will send data to user table and interview table).
• Link pages to the menu bar (approval page, profile page)

BUTTONS:
pages/landing:
"Start Interview" button: Needs to fetch appropriate questions

pages/game-options:
All option fields need to be hooked up to database

pages/approval:
When question is selected, form modal appears with populated data (GET)
Form submitted = PUT
Delete button = DELETE

Other Things:
pages/approval: filter should work

Create menu button in header (separate from stats bar)

For each topic and level in the matrix, there will be a link to the interview app intro page which autofills the topic and level categories.

Ideally, write a script that automates the process of pre-filling the topic and level categories so this does not have to be done manually.

When user levels up, an encouraging and beautiful alert message appears.

On questions page, display header which includes the following stats:

• username
• game mode
• difficulty level
• experience
• topic
• profile link

Create a candidate table with the following columns:

• roles (interviewer vs candidate)
• experience
• level
• average_time_per_question
• notes

Create knex.js
create confi.js
create db.js
create migration scripts within package.jsonn
run migration
populate migration with knex.schema.createtable

Install appropriate npm modules required

Questions increase in difficulty either when all questions of that level have been correctly answered.
Level 1.0
Level 1.1
Level 1.2
Level 1.3
Level 2.0
Level 2.1
Level 2.2
Level 2.3
Level 3.0
etc.

src/config/config

When interviewer submits Feedback, they become available to candidate and are recorded in the candidate's profile to be viewed later.

Feedback is a column located in the interview table.
When notes are submitted, the user can see the difficulty and topic of the interview they were given.

Intro page should have the following options for the user to select from:

• Priority level
• Username
• Questions Difficulty Level (Beginner, Intermediate, Advanced, Jedi)
• Topic (Requirements, Testing, Technical Design, Object Oriented Programming, Functional Programming, Problem Decomposition, Data Structures, Algorithms, Regular Expressions, Systems Programming, etc.)
• *Game Modes (Speaking, Whiteboard, Coding, Debugging, Solo)

*These modes will be built out later down the line. For now we are focusing on Speaking Mode only.

Setup ESLint

In the header, experience will increase as candidate answers questions correctly.

see also issue #70

Create knex file

Add more questions to the database. Ask learners and pro players to create questions.

Add react router as a dependency to the project
Add react router to front end routes

When the new question form is populated and submitted, it creates a question within the database. The "Approved" column for all new questions is default to false, until the question has been approved within the approval page.

Author of questions - When new question is submitted, the author is recorded within the question database.

Go to Istanbul.js.org and setup Istanbul NYC for test coverage

*note: for Istanbul testing, include "nyc" before mocha test script.

Create a space for interviewer to write notes during the mock interview, and submit afterwards. (These notes will become available for the candidate to see after session is complete. See issue #7)

When you finish all the questions in an interview, the "Finish Interview and Submit Notes" button will:

• Return you to the landing page using React Router.
  -Submit the notes into the interview table as Feedback.

Form will include most/all columns within the questions table, and include a area to submit prompts.

Approval page will display a list of pending question.
Approval page will have buttons for approve, delete, and edit.

When the approve button is clicked, it will be marked "true" in the approved column of the questions table.
When the delete button is clicked, the question is removed from the database.
When the edit button is clicked, the question becomes editable within the questions modal form.

Menu button will open OffCanvas.

https://getuikit.com/v2/docs/offcanvas.html

Does environment have proper dev dependencies? nodemon? etc.

In the header, experience counter will increase as candidate gains enough experience points.