Goal

The goal of this project is to have a widget that:

• fetches questions from a server
• shows them in a widget that can easily be added to any page
• makes it convenient for users to answer questions and convenient for site owner to access answers.

TODO

This project is very much in progress. Main parts missing are:

• fetching questions from server (later on, fetch more questions as we go)
• sending back answers to server
• adding cookie to recognize users (later on, integrate with SSO)
• design
• back button - come back to previous question.

This project was bootstrapped with Create React App. See their docs for more details on available features.

This is my first project using redux, so feedback is welcome.

Install

You need npm and git.

git clone git@github.com:SheCanCodeHQ/question-queue.git
cd question-queue
npm install
npm start

Open your browser to http://localhost:3000/

Folder Structure

Following a folder structure described in react-redux tutorial:

  README.md
  node_modules/
  package.json
  public/
    index.html <-- Do not rename
    favicon.ico
  src/
    actions/ <-- all states changes are sent through actions
    components/  <-- components describe how things look
    containers/  <-- wrap components in smartness and handle state changes (as far as I understand)
    reducers/  <-- implement state changes sent by actions
    index.css
    index.js <-- main entrypoint - Do not rename

Available Scripts (From the Create React App doc)

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Supported Language Features and Polyfills (From the Create React App doc)

This project supports a superset of the latest JavaScript standard.
In addition to ES6 syntax features, it also supports:

• Exponentiation Operator (ES2016).
• Async/await (ES2017).
• Object Rest/Spread Properties (stage 3 proposal).
• Dynamic import() (stage 3 proposal)
• Class Fields and Static Properties (stage 2 proposal).
• JSX and Flow syntax.

Learn more about different proposal stages.

While we recommend to use experimental proposals with some caution, Facebook heavily uses these features in the product code, so we intend to provide codemods if any of these proposals change in the future.

Note that the project only includes a few ES6 polyfills:

• Object.assign() via object-assign.
• Promise via promise.
• fetch() via whatwg-fetch.

If you use any other ES6+ features that need runtime support (such as Array.from() or Symbol), make sure you are including the appropriate polyfills manually, or that the browsers you are targeting already support them.