[FEAT- Roadmap]: Adapt Stormsim into the App
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This ticket will serve as a hub for info regarding everything related to creating the FEAT input pages for StormSim.
At the moment of creating this ticket we have to:
- flesh out what inputs are needed for StormSim (StormTrack, Hazard Curves, CHS data)
- Create Wireframes
- Create UI
- Create DB tables
- Create API endpoints
- much more
Contributor guide
No contributing guide indexed for this repository
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 with the StormSim input requirements listed in the issue: StormTrack, Hazard Curves, and CHS data. The scope first needs to be narrowed into defined inputs and separate tasks for wireframes, UI, database tables, and API endpoints; done is not yet specified beyond completing this broad roadmap.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, database, design, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100