Chalarangelo/30-seconds-of-interviews

Plans for the second version

Open

#171 opened on Aug 23, 2019

View on GitHubContributor guide
 (11 comments) (4 reactions) (3 assignees)JavaScript (964 forks)github user discovery
help wantedopinions needed

Repository metrics

Stars
 (12,132 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Hello everyone 👋

It's been over a year since this project was released. The feedback so far was phenomenal and it' seems that some people really find this project useful despite my initial thoughts.

I'd like to make the second version of it and I need your opinions on it. The idea is to introduce a completely new structure similar to the 30-seconds-starter kit.

Things I would like to include in the second version:

  • Make the project 100% accessible, and add accessibility category
  • Introduce visually pleasing dark mode
  • At least one new category (e.g. Computer Science)
  • Make it with Gatsby (so many things out of the box)
  • Add the ability to share questions
  • Individual pages for each question (better SEO I guess)
  • Remove expertise tags, at least visually (so many people complain about it)
  • Add about page
  • A form to submit new questions without GitHub account
  • Host the project on Netlify
  • A random interview simulation

What do you think about proposed changes? Would you like to see something else? What current parts of the projects do you like the most?

Contributor guide

Research direction
Review the current project structure and the 30 seconds starter kit to understand the proposed changes. Then evaluate each item in the list for feasibility and prioritization.
Tech stack
javascriptreact
Domain
frontendaccessibility
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptReactGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30