Bug: I shouldn't own the DOM fixtures website
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 251k
- Forks
- 51.4k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 53
Description
Some folks at Google are helping us to think through some ideas to help our input code be more sane, and we discovered that our DOM Text Fixtures site (http://react-dom-fixtures.surge.sh) was both:
- Very out of date
- Owned by me
Both seem fixable. However I think a good first start is to figure out a way to publicly host the fixtures where I am not a bottleneck.
What do you think? Could we setup a deploy process - maybe with netlify - to deploy the fixtures automatically?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the DOM Text Fixtures site at http://react-dom-fixtures.surge.sh and determine how the current fixtures are hosted. Investigate a public automated deployment process, possibly using Netlify, with ownership independent of the reporter. Done means the fixtures are publicly hosted and can be deployed without making the reporter a bottleneck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devops, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100