UI - Transition Application Form
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
This was started by a previous team. We need to integrate that code into the layers infrastructure.
- add into the project into 'corps' project (will also host other corps filings like the dod)
- all form components should be using layer components where possible / new ones should be created where necessary (i.e. offices / share structure)
- init / submission / routing / etc. should be updated to follow the new common flows
- UX:
- regular: https://www.figma.com/design/9Lp6kpwm6JyfQmBqvRdVJF/Transition-Application?node-id=13492-50081&t=z1NjEjVw8PP93juM-0
- staff: https://www.figma.com/design/9Lp6kpwm6JyfQmBqvRdVJF/Transition-Application?node-id=13493-63118&t=DisZZpdtneS1Ytpz-0
Outstanding Questions:
- In the COLIN filing they do not let you edit the offices. Should we keep this rule? We will need the edit offices component later anyways so if its desirable then it is probably good to add it in to this filing
- note from julie: we are allowed to edit the offices within the filing (does not need new ledger item, but may need an extra fee added)
- In the COLIN filing they only let you alter the director if it is a 'typing or spelling mistake'. Should we keep this rule?
- if not, then do we need to allow them to specify appointment / cessation dates? What would be the min dates they can select -> potentially follow same logic as director change?
- note from julie: we are allowed to edit the directors within the filing (does not need new ledger item, but might not have full functionality)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.