React.js Best Practices for 2016 (ClickBait / React Zeitgeist)

Open
#17 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
react
Domain
frontend

Research direction

Start by reading the two linked articles and comparing their 2016 React guidance with the learn-react material. The issue names no files, tests, entry points, specific change, or completion criteria, so its intended scope needs to be established before implementation.

Written by the indexing model from the issue text.

Description

enhancement

https://blog.risingstack.com/react-js-best-practices-for-2016

... also: https://medium.com/@wob/the-sad-state-of-web-development-1603a861d29f 😉

Dominant language
HTML
Stars
107
Forks
21
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dwyl/learn-react

All issues in dwyl/learn-react

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.