UI Design | MHR Home Dealer Improvements
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Within BC, Manufactured Home Dealers not only act as sellers of new homes, but will also perform activities to assist the re-sale of older homes as well. As such, they are needing to be able to have less restrictions on what was previously designed for them in the modern MHR application:
- Request Transport Permits for homes not on their lots
- Conduct Bill of Sale Ownership Changes (Sale and Gift)
- Add home dealer lot information to QS HD Access flow
- Add a toast notification to inform the HDealer of newly granted access and prompt them to complete the required information.?
In order to ensure the safeguards of the data in the registry, we will require dealers to indicate that they understand the documentation requirements that go along with these transfers.
### [Figma Design: Home Dealer Access](https://www.figma.com/design/0sD17BVTK7OwTqPRsAoreu/MHR-Account-User-Flow?node-id=2557-1482)
### [Figma Design: Home Dealer Application](https://www.figma.com/design/0sD17BVTK7OwTqPRsAoreu/MHR-Account-User-Flow?node-id=2487-1642)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked Figma designs for Home Dealer Access and Home Dealer Application, then trace the existing MHR dealer flows for transport permits, ownership changes, lot information, and access granting. Done means the listed dealer capabilities, required documentation acknowledgement, and new-access toast match the designs and work together.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100