QnA App

This project aims to develop a question-and-answer web app where users can solve the questions posted by other users or the system. They will also have the ability to post their questions. The app will allow users to bookmark or group questions and challenge others.

Donald Knuth

Requirements

FR - Functional Requirement,

NFR - Non Functional Requirement

ER - Extended Requirement

SR - System Requirement

ID	Description	Status
FR1	User must be able to login via email and password, gmail, and others supported by `Supabase`	DONE
FR2	User must be able to view list of questions	INPROGRESS
FR3	User must be able to view and attempt a specific question	TODO
FR4	User must be able to add new question	TODO
FR5	User must be able to delete his question	TODO
FR6	User must be able to Group existing questions that further can be shared as challenge to others	TODO
FR7	User must be able to see his score and activity history	TODO
FR8	Add support for google and facebook OAuth provider	TODO
FR9	Add validation for email signup	TODO
FR10	Send to profile update page on first login	TODO
SR1	System must handle realtime notification	TODO
SR2	System should allow new question ingestion	TODO

Questions

User Interface

Flow

Small, Medium, and Large Device

Mobile Device

Deployments

Demo

demo-4.webm

demo-3.webm

output.mp4

demo.mp4

Home

Implemented backend logic to verify answer

Type to answer - ui update

Updated Question details ui

Implemented Question click handler

Fixed scroll issue

Question list rendering

Question List from backend

Small, Medium, and Large Device

Mobile Device

Post Question

Login

Signup

Technical Debt

Improve Login page
Improve Signup page
Implement loading page for page transitions

System APIs

TODO

Database Design

Users

Name	Type	Description
id	uuid	system generated user id
email	string	user email id
phone	string	user phone number
provider	string	oAuth provider
created	datetime	user creation date
last_sign_in	datetime	last sign in date

Profiles

Name	Type	Description
id	uuid	system generated user id
updated_at	datetime	last profile update date
username	string	username
full_name	string	user full name
avatar_url	url	user profile pic
website	url	user website

Questions

Name	Type	Description
id	uuid	question id
created_by	uuid	creators user id
created_at	datetime	creation time
category	string	question category
type	string	question type - text, url, image, draw, and latex
question	string	question description
answer	string	single or multi-word answer

Above is the response presented to the browser. Answer field is removed in backend.

History

Name	Type	Description
user_id	uuid	id of user trying to attempt the question
question_id	uuid	question id the user is trying to answer
created_at	datetime	datetime for first attempt
updated_at	datetime	datetime for later attempt till its solved
failed_attempt	number	count for failed attempts
status	enum	status for user attempts

System Design

TODO

Purging or DB Cleanup

TODO

Security and Permissions

TODO

Technology Stack

Fullstack Framework - Next.js
Database - Supabase
Authentication - Supabase Auth, Youtube Tutorial, Example
Client State Management - Zustand
Client Data Fetching - Swr
Server Data Fetching - fetch
CSS framework - Tailwindcss
Tailwindcss Forms Plugin - Tailwindcss Forms
Tailwindcss Prettier Plugin - Prettier Plugin
Form Validation - zod
Drag and Drop - dndkit
Icons - heroicons
Version Control - GitHub
Deployment - Vercel

Tools

Editor - VS Code
Wireframe - Figma or Draw.io

Getting Started

First, run the development server:

Run command nvm use to use node version configured in .nvmrc

npm run dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in pages/api/hello.ts.

The pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.

This project uses next/font to automatically optimize and load Inter, a custom Google Font.

New Feature Add Process

Switch to main branch and pull

> git checkout main
> git pull

Create feature branch

All feature work should be done on a branch. The branch should start with word "feature/". Dash (-) should be used as separator the branch name.

> git checkout -b feature/<name-of-feature>

Example branch name could be "feature/update-docs-for-new-feature"

This should create branch and change to it.

Make changes and add to local git

Work on the feature. You may have to add new files or update existing ones. Add to local git after testing the changes

# cd to the top of the project tree
> git add .

Commit the changes to local git

Git commit messages should follow the convention from coding guideline. A feature comment should start with word feature:. A documentation only change should start with docs:

> git commit -m 'feature: <feature desciption>'

All the words that could be at the begining of the commit message can be found at commitlint.config.js

This commit would trigger some checks. Fix any failures.

Push changes to github

> git push --set-upstream origin <feature-branch-for-github-which-could-be-same-as-local-feature-branch>

Feature branch should follow same naming convention as local feature branch where branch name starts with "feature/feature-name". Git push will trigger push check as defined in husky setup. Fix any failures

Create github pull request

Click on 'Pull Request' tab in github. Click on [New pull request] button. Under "Compare changes", make change to go from feature branch to main

main <- 'feature-branch'

Select a reviewer in the right. Submit pull request.

Resolve reviewer concerns

A reviewer might approve changes. In that case, pull request can be merged to main by cliking the MERGE button. In case reviwer, doesn't approve, you will have to make changes to satify the reviewer by making changes and notifying the reviewer through the pull request on github.

Fixes should be committed with commit message with prefix "fix: "

Development Setup

Create Project

Create GitHub repository
Create NextJs project on laptop
- npx create-next-app@latest --experimental-app
Execute the following steps. Final step will push changes to GitHub repository.

Engine Locking

Create .nvmrc in root directory to specify which node version to be used in this project i.e. lts/hydrogen - v18.15.0
Create .npmrc in root directory to indicate which package manager is to be used strictly.

NextJs use Node v16.8.0 or later. If node version used is lower than v16.8.0, then change it using nvm by doing following.

nvm ls will show what node version is currently set to.

nvm install v18.15.0 to install v18.15.0 or anyother you want.

nvm use if .nvmrc is specified with node version or nvm use v18.15.0

Update package.json to indicate node and npm version.

"engines": {
    "node": ">=18.15.0",
    "yarn": "please-use-npm",
    "npm": ">=9.5.0"
  },

Linting

Create .eslintrc.json file in root directory with following content

{
  "extends": ["next", "next/core-web-vitals", "eslint:recommended"],
  "globals": {
    "React": "readonly"
  }
}

Run npm run lint

Formatting

Install prettier as dev dependency. Run npm add -D prettier

"devDependencies": {
    "prettier": "^2.8.4"
}

Create .prettierrc file in root directory with the following content.

{
  "trailingComma": "es5",
  "tabWidth": 2,
  "semi": true,
  "singleQuote": true
}

Create .prettierignore file in root directory with the following content.

.yarn
.next
dist
node_modules

Update package.json

"scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint",
    "prettier": "prettier --write ."
  }

Run npm run prettier

Git

Install Husky
- Run npm add -D husky
- Run npx husky install. It creates .husky folder

"devDependencies": {
    "husky": "^8.0.3",
    "prettier": "^2.8.4"
}

Update package.json in the scripts section "prepare": "husky install" so that Husky gets installed automatically when other developers run the project.

"scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint",
    "prettier": "prettier --write .",
    "prepare": "husky install"
}

Create following hooks
- Run npx husky add .husky/pre-commit "npm run lint"
- Run npx husky add .husky/pre-push "npm run build"

$ > npx husky add .husky/pre-commit "npm run lint"
husky - created .husky/pre-commit
$ > ls  .husky
_          pre-commit

$ > cat .husky/pre-commit
#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"

npm run lint

$ > npx husky add .husky/pre-push "npm run build"
husky - created .husky/pre-push
$ > ls  .husky
_          pre-commit pre-push

$ > cat .husky/pre-push
#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"

npm run build

Install commitlint package as dev dependency
- Run npm add -D @commitlint/config-conventional @commitlint/cli

"devDependencies": {
    "@commitlint/cli": "^17.4.4",
    "@commitlint/config-conventional": "^17.4.4",
    "husky": "^8.0.3",
    "prettier": "^2.8.4"
}

Create commitlint.config.js in root directory
Enable commitlint with Husky
- Run npx husky add .husky/commit-msg 'npx --no -- commitlint --edit "$1"'

$ > npx husky add .husky/commit-msg 'npx --no -- commitlint --edit "$1"'
husky - created .husky/commit-msg

$ > ls  .husky
_          commit-msg pre-commit pre-push

$ > cat .husky/commit-msg
#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"

npx --no -- commitlint --edit "$1"

VS Code

Create .vscode/settings.json file with following content

{
  "typescript.tsdk": "node_modules/typescript/lib",
  "typescript.enablePromptUseWorkspaceTsdk": true,
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.formatOnSave": true,
  "editor.codeActionsOnSave": {
    "source.fixAll": true,
    "source.organizeImports": true
  }
}

Debugging with VS Code

Create .vscode/launch.json file with following content.

https://nextjs.org/docs/advanced-features/debugging

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Next.js: debug server-side",
      "type": "node-terminal",
      "request": "launch",
      "command": "npm run dev"
    },
    {
      "name": "Next.js: debug client-side",
      "type": "chrome",
      "request": "launch",
      "url": "http://localhost:3000"
    },
    {
      "name": "Next.js: debug full stack",
      "type": "node-terminal",
      "request": "launch",
      "command": "npm run dev",
      "serverReadyAction": {
        "pattern": "started server on .+, url: (https?://.+)",
        "uriFormat": "%s",
        "action": "debugWithChrome"
      }
    }
  ]
}

Install cross-env as dev dependency.
- Run npm add -D cross-env

"devDependencies": {
    "@commitlint/cli": "^17.4.4",
    "@commitlint/config-conventional": "^17.4.4",
    "cross-env": "^7.0.3",
    "husky": "^8.0.3",
    "prettier": "^2.8.4"
}

Update package.json

"scripts": {
    "dev": "cross-env NODE_OPTIONS='--inspect' next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint",
    "prettier": "prettier --write .",
    "prepare": "husky install"
}

Environment Variables

Create .env.local in root directory

.env.local always overrides the defaults set.

Note: .env, .env.development, and .env.production files should be included in your repository as they define defaults. .env*.local should be added to .gitignore, as those files are intended to be ignored. .env.local is where secrets can be stored.

Reference - NextJs Environment Variables

Zustand

Inatall Zustand package
- npm install zustand

Tailwindcss

Tailwindcss configuration for NextJS

npm install -D tailwindcss postcss autoprefixer
npx tailwindcss init -p
Update tailwind.config.js

/** @type {import('tailwindcss').Config} */
module.exports = {
  content: ['./src/**/*.{js,ts,jsx,tsx}'],
  theme: {
    extend: {},
  },
  plugins: [],
};

Update globals.css in src/app folder

@tailwind base;
@tailwind components;
@tailwind utilities;

Update src/app/page.tsx to test if tailwind is configured correctly.

export default function Home() {
  return <h1 className="text-3xl font-bold underline">Hello world!</h1>;
}

Run npm run dev to test

Tailwindcss Forms Plugin

Install @tailwindcss/forms package
- npm install -D @tailwindcss/forms
Update tailwind.config.js

// tailwind.config.js
module.exports = {
  theme: {
    // ...
  },
  plugins: [
    require('@tailwindcss/forms'),
    // ...
  ],
};

Reference: @tailwindcss/forms

Tailwindcss Prettier Plugin

Install prettier-plugin-tailwindcss
- npm install -D prettier prettier-plugin-tailwindcss
Update prettier.config.js

// prettier.config.js
module.exports = {
  plugins: [require('prettier-plugin-tailwindcss')],
};

Reference: prettier-plugin-tailwindcss

Zod

Install zod package
- npm install zod

Dndkit

Install dndkit package
- npm install @dnd-kit/core

Supabase Cleint

Install supabase-js package
- npm install @supabase/supabase-js

Icons

Install heroicons package
- npm install @heroicons/react

Commit and Push Changes to GitHub

git add .
git commit -m "ci: configure development environment"
git remote add origin https://github.com/groupsvkg/qna.git
git push -u origin main

Errors

Encoding

./node_modules/node-fetch/lib/index.js Module not found: Can't resolve 'encoding' in '/Users/vishalgupta/work/personal/programming/project/qna/qna/node_modules/node-fetch/lib'

Solution - Github

Delete .next folder

npm install -D encoding

Learn More

To learn more about Next.js, take a look at the following resources:

Next.js Documentation - learn about Next.js features and API.
Learn Next.js - an interactive Next.js tutorial.

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

Install vercel cli
- npm install -g vercel
Execute vercel command from root to deploy(non-production deployment)
Add environment variables - executed once
- vercel env add NEXT_PUBLIC_SUPABASE_URL
- vercel env add NEXT_PUBLIC_SUPABASE_ANON_KEY
- vercel env add SUPABASE_SERVICE_KEY

Reference

Name		Name	Last commit message	Last commit date
Latest commit History 85 Commits
.husky		.husky
.vscode		.vscode
cypress		cypress
design		design
public		public
src		src
.eslintrc.json		.eslintrc.json
.gitignore		.gitignore
.npmrc		.npmrc
.nvmrc		.nvmrc
.prettierignore		.prettierignore
.prettierrc		.prettierrc
README.md		README.md
commitlint.config.js		commitlint.config.js
cypress.config.ts		cypress.config.ts
jest.config.mjs		jest.config.mjs
jest.setup.js		jest.setup.js
next.config.js		next.config.js
package-lock.json		package-lock.json
package.json		package.json
postcss.config.js		postcss.config.js
prettier.config.js		prettier.config.js
tailwind.config.js		tailwind.config.js
tsconfig.json		tsconfig.json

groupsvkg/qna

Folders and files

Latest commit

History

Repository files navigation

QnA App

Requirements

Questions

User Interface

Flow

Deployments

Demo

Home

Post Question

Login

Signup

Technical Debt

System APIs

Database Design

Users

Profiles

Questions

History

System Design

Purging or DB Cleanup

Security and Permissions

Technology Stack

Tools

Getting Started

New Feature Add Process

Switch to main branch and pull

Create feature branch

Make changes and add to local git

Commit the changes to local git

Push changes to github

Create github pull request

Resolve reviewer concerns

Development Setup

Create Project

Engine Locking

Linting

Formatting

Git

VS Code

Debugging with VS Code

Environment Variables

Zustand

Tailwindcss

Tailwindcss Forms Plugin

Tailwindcss Prettier Plugin

Zod

Dndkit

Supabase Cleint

Icons

Commit and Push Changes to GitHub

Errors

Encoding

Learn More

Deploy on Vercel

About

Resources

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Contributors 2

Uh oh!

Languages

Packages