Initial Homepage
- Dominant language
- JavaScript
- Stars
- 42
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] Add specific benefits to the homepage
- [ ] Easy for developers of all skill levels to understand
- [ ] Remove boilerplate (no .setState)
- [ ] Less Time Rendering (.shouldComponentUpdate)
- [ ] Add benefits overview to the hompage
- Option 1: Within the initial example white area, add:
 with links to the benefit sections below.
- Option 2: Create a benefits section right below, which links to individual benefits below.
- [x] Improve "If you know React, you already know ylem.". It doesn't really state what it does. Indirect on why you should use it.
- "The simplest state management for react"
- [x] React with Ylem => "If you know React, you already know ylem".
- [ ] Add Get started in JSBin / JSFiddle / CodePen
- [x] Calculate the size of ylem. #132
- [x] Figure out the size of our competitors. #132
- [x] Improve highlighting of differences
- [ ] Change "Bitovi" link to double dot dropdown.
- [ ] Create `.md` files for "Is easy to debug", "Creates unit-testable ViewModel types", etc and link to them.
- [ ] Hovering over Ylem logo should show OS tools dropdown.
- [ ] `state and lifecycle guide` link is almost invisible.
Contributor guide
Research direction
Start by locating the homepage implementation and its current React example, then review the unchecked items and linked design image. Break the work into specific homepage changes, benefits content, examples, links, and navigation details; done means the selected homepage improvements are implemented and each checklist item is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- content, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100