cityofaustin / cityofaustin/techstack
Joplin UI: Edit Service Page
- Dominant language
- No language data
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
"As a city author, I need the authoring experience to have a logical visual hierarchy so that I am better able to understand the **Edit Service Page** interface." - A City Author
This is a broken out section of the Joplin UI re-design.
#### Acceptance Criteria
- [ ] Matches styles from XD Design 👇
- https://xd.adobe.com/view/c533a077-9314-46a6-5db4-d4a7f8601e8f-b302/screen/53026787-cb85-40fe-a20e-180c8639c775/Joplin-3-Phase-1-enhancements-Edit-service-page
- [ ] Matches CSS for Themes and Colors from Google doc 👇 "Phase 1 acceptance criteria"
- See Edit service page section: https://docs.google.com/document/d/1SdAro51Ppdi3Hirn1XkVviJ6nu89dDXtvvFKIX4T8t8/edit#heading=h.m158dr7viuc
#### Technical Acceptance Criteria
- [ ] Matches any new structural patterns implemented into the new Joplin UI
- [ ] Checks for and removes any dead-css no longer being used.
Contributor guide
No contributing guide indexed for this repository
Research direction
Begin by reviewing the linked XD design and the Google document's Edit service page section to identify the required visual hierarchy, themes, and colors. Then inspect the existing Edit Service Page and its CSS against those references and the newer Joplin UI structural patterns. Done means the page matches the designs and unused CSS has been removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100