[{"data":1,"prerenderedAt":517},["ShallowReactive",2],{"project-\u002Fprojects\u002Fcourt-websites":3,"surround-\u002Fprojects\u002Fcourt-websites":511},{"id":4,"title":5,"body":6,"caseStudy":23,"client":492,"cover":493,"description":494,"extension":495,"featured":496,"meta":497,"navigation":498,"order":499,"path":500,"publishedAt":501,"role":32,"seo":502,"stem":503,"tags":504,"url":508,"year":509,"__hash__":510},"projects\u002Fprojects\u002Fcourt-websites.md","Supreme Court & District Court Website",{"type":7,"value":8,"toc":18},"minimark",[9,14],[10,11,13],"h2",{"id":12},"overview","Overview",[15,16,17],"p",{},"Redesigning the Idaho Supreme Court and District Court websites — modernizing a\nlarge public-information ecosystem with a clearer information architecture and a\nmore accessible experience across desktop and mobile.",{"title":19,"searchDepth":20,"depth":20,"links":21},"",2,[22],{"id":12,"depth":20,"text":13},{"meta":24,"hero":41,"sections":48},[25,29,33,37],{"icon":26,"label":27,"value":28},"material-symbols:event-available-outline-rounded","Timeline","Ongoing",{"icon":30,"label":31,"value":32},"material-symbols:face-4-outline","Role","UI\u002FUX Designer & Front-End Developer",{"icon":34,"label":35,"value":36},"material-symbols:sdk-outline-rounded","Tools","Figma, Nuxt.js",{"icon":38,"label":39,"value":40},"material-symbols:tactic-rounded","Project Type","Website Design & Development",{"frame":42,"columns":43,"items":44},"plain",1,[45],{"src":46,"alt":47},"\u002Fimages\u002Fprojects\u002Fcourt-sites\u002Fcourt-thumbnail.jpg","Internal CMS platform login screen",[49,72,147,199,348,390,411,438,461,481,486],{"title":50,"body":51,"list":56,"outro":70},"Project Summary",[52,53,54,55],"The Supreme Court website served as a central public resource for court services, legal information, announcements, forms, and official documents. Over the years, the platform had expanded significantly, resulting in increasingly complex navigation, fragmented information structures, and inconsistent user experiences across devices.","The goal of the redesign was not only to modernize the visual experience, but more importantly, to improve how users discover, understand, and navigate large volumes of court-related information.","In addition to redesigning the Supreme Court website, I was also responsible for designing the District Court websites that existed within the same ecosystem while helping maintain consistency across the broader platform experience.","This project focused heavily on:",{"items":57},[58,60,62,64,66,68],{"text":59},"Information architecture",{"text":61},"Navigation restructuring",{"text":63},"Content discoverability",{"text":65},"Responsive usability",{"text":67},"Accessibility-minded design",{"text":69},"Scalable front-end implementation",[71],"Rather than designing purely for aesthetics, the outcome aimed to create a more intentional experience for the different types of users interacting with the platform.",{"title":73,"body":74,"subsections":76,"figures":140},"The Problem",[75],"The existing website had evolved over many years without a unified UX strategy, resulting in a platform that felt difficult to navigate and overwhelming for users unfamiliar with court systems.",[77,98,135],{"title":78,"blocks":79},"Navigation Complexity",[80,82,96],{"text":81},"The navigation structure had become increasingly difficult to use due to:",{"list":83},{"icon":84,"items":85},"material-symbols:asterisk-rounded",[86,88,90,92,94],{"text":87},"Crowded menu systems",{"text":89},"Overlapping categories",{"text":91},"Inconsistent hierarchy",{"text":93},"Too many competing entry points",{"text":95},"Difficult-to-find resources",{"text":97},"Users often needed to navigate through several pages before locating important information or documents.",{"title":99,"blocks":100},"Content Discovery Challenges",[101,103,116,118,133],{"text":102},"Court websites naturally contain large amounts of content intended for a wide range of audiences, including:",{"list":104},{"icon":84,"items":105},[106,108,110,112,114],{"text":107},"Legal professionals",{"text":109},"Government employees",{"text":111},"Citizens",{"text":113},"First-time visitors",{"text":115},"Users unfamiliar with legal terminology",{"text":117},"One of the biggest usability concerns was helping users quickly locate:",{"list":119},{"icon":84,"items":120},[121,123,125,127,129,131],{"text":122},"Documents",{"text":124},"Court information",{"text":126},"Forms",{"text":128},"Contacts",{"text":130},"Services",{"text":132},"Court-related resources",{"text":134},"The redesign aimed to simplify how users searched, browsed, and understood information throughout the ecosystem.",{"title":136,"blocks":137},"Outdated Experience",[138],{"text":139},"The existing experience also reflected older design standards and was not fully optimized across modern devices, leading to inconsistencies between desktop and mobile experiences.",[141],{"frame":42,"columns":43,"caption":142,"items":143},"Planning the website navigation stracture",[144],{"src":145,"alt":146},"\u002Fimages\u002Fprojects\u002Fcourt-sites\u002Fplanning.jpg","navigation planning",{"title":148,"body":149,"subsections":151},"Constraints",[150],"This project involved several real-world constraints that significantly influenced design decisions.",[152,172,194],{"title":153,"blocks":154},"Content-Heavy Environment",[155,157,159,161],{"text":156},"Because the platform contained large amounts of text-based information, the design needed to prioritize readability, clarity, and structure over heavy visual styling.",{"text":158},"I intentionally avoided overly graphic-heavy layouts and instead focused on creating interfaces that helped users process information more efficiently.",{"text":160},"The challenge was finding the right balance between:",{"list":162},{"items":163},[164,166,168,170],{"text":165},"Visual modernization",{"text":167},"Content clarity",{"text":169},"Accessibility",{"text":171},"Usability",{"title":173,"blocks":174},"Frequent Content Changes",[175,177,179,181,183],{"text":176},"Court-related information changes frequently, requiring the website to remain flexible and maintainable over time.",{"text":178},"To support this, I designed reusable and scalable components that could easily adapt to content updates without requiring major redesign efforts.",{"text":180},"This was especially important because revision timelines and implementation windows were often limited.",{"text":182},"The goal was to ensure that:",{"list":184},{"items":185},[186,188,190,192],{"text":187},"Future updates remained efficient",{"text":189},"Components stayed consistent",{"text":191},"Design revisions were not cumbersome",{"text":193},"The system could scale across multiple court websites",{"title":195,"blocks":196},"Balancing Consistency and Flexibility",[197],{"text":198},"Since the project included both Supreme Court and District Court websites, I needed to create a system that felt unified while still allowing each site to maintain its own structure and identity.",{"title":200,"subsections":201,"figures":341},"Process & Approach",[202,228,252,283,305,321],{"title":203,"blocks":204},"Website Audit & Analysis",[205,207,209,226],{"text":206},"Before proposing solutions, I conducted a comprehensive review of the existing experience.",{"text":208},"I analyzed:",{"list":210},{"items":211},[212,214,216,218,220,222,224],{"text":213},"Navigation structures",{"text":215},"Content organization",{"text":217},"User pathways",{"text":219},"Existing page hierarchy",{"text":221},"Searchability of information",{"text":223},"Mobile responsiveness",{"text":225},"Common usability pain points",{"text":227},"This helped identify where users were likely experiencing friction and confusion.",{"title":229,"blocks":230},"Information Architecture Strategy",[231,233,235,237,250],{"text":232},"One of the most significant parts of the project was restructuring how information was organized.",{"text":234},"Rather than immediately redesigning pages visually, I focused first on improving the underlying structure of the platform.",{"text":236},"Key objectives included:",{"list":238},{"items":239},[240,242,244,246,248],{"text":241},"Simplifying navigation",{"text":243},"Reducing cognitive load",{"text":245},"Improving discoverability",{"text":247},"Creating clearer content relationships",{"text":249},"Supporting both expert and non-expert users",{"text":251},"The goal was to design information around how users naturally search for resources rather than how the organization internally categorized them.",{"title":253,"blocks":254},"Wireframes & User Flows",[255,257,259,270,272],{"text":256},"Because navigation restructuring represented a major shift from the existing experience, wireframes became an important communication and validation tool.",{"text":258},"Wireframes helped:",{"list":260},{"items":261},[262,264,266,268],{"text":263},"Explore structural concepts quickly",{"text":265},"Compare navigation approaches",{"text":267},"Validate user journeys",{"text":269},"Align stakeholders around proposed changes",{"text":271},"Key flows focused on:",{"list":273},{"items":274},[275,277,279,281],{"text":276},"Document discovery",{"text":278},"Court resource navigation",{"text":280},"Public information access",{"text":282},"Search experiences",{"title":284,"blocks":285},"Iterative Design & Prototyping",[286,288,290,303],{"text":287},"The project involved multiple rounds of iteration and refinement.",{"text":289},"Interactive prototypes were used to evaluate:",{"list":291},{"items":292},[293,295,297,299,301],{"text":294},"Navigation hierarchy",{"text":296},"Page layouts",{"text":298},"Information prioritization",{"text":300},"Responsive behavior",{"text":302},"Content presentation",{"text":304},"This iterative process allowed the experience to evolve while balancing user needs, technical constraints, and stakeholder feedback.",{"title":306,"blocks":307},"Responsive Design",[308,310,319],{"text":309},"The redesigned experience was built to support:",{"list":311},{"items":312},[313,315,317],{"text":314},"Desktop",{"text":316},"Tablet",{"text":318},"Mobile devices",{"text":320},"Special attention was given to maintaining readability, navigation clarity, and accessibility regardless of screen size.",{"title":322,"blocks":323},"Front-End Development",[324,326,328,339],{"text":325},"In addition to design responsibilities, I also implemented front-end pages using Nuxt.js.",{"text":327},"This included:",{"list":329},{"items":330},[331,333,335,337],{"text":332},"Translating designs into production-ready interfaces",{"text":334},"Building responsive layouts",{"text":336},"Maintaining consistency across pages",{"text":338},"Supporting reusable implementation patterns",{"text":340},"Working across both design and development allowed me to ensure the final implementation closely aligned with the intended user experience.",[342],{"frame":42,"columns":43,"caption":343,"items":344},"Website Wireframe",[345],{"src":346,"alt":347},"\u002Fimages\u002Fprojects\u002Fcourt-sites\u002Fwireframe.jpg","Wireframe",{"title":349,"subsections":350},"Design Improvements",[351,358,374,381],{"title":352,"blocks":353},"Improved Navigation Structure",[354,356],{"text":355},"The redesigned navigation introduced a clearer hierarchy that made it easier for users to understand where information existed within the platform.",{"text":357},"Content was reorganized into more meaningful categories, reducing the effort required to locate resources.",{"title":359,"blocks":360},"Better Content Organization",[361,363,365],{"text":362},"Pages and resources were grouped more intentionally based on user needs and content relationships.",{"text":364},"This helped improve:",{"list":366},{"items":367},[368,370,372],{"text":369},"Information discoverability",{"text":371},"Scanability",{"text":373},"Overall usability",{"title":375,"blocks":376},"Enhanced Search Experience",[377,379],{"text":378},"One of the most impactful improvements was enhancing how users locate important documents, people, and court-related information.",{"text":380},"The redesign addressed previous usability concerns around search and discovery, making critical resources easier to access without excessive navigation.",{"title":382,"blocks":383},"More Accessible Experience",[384,386,388],{"text":385},"Legal terminology and court systems can feel intimidating for many users.",{"text":387},"Where appropriate, content structures and interface labels were designed to feel more approachable and easier to understand for non-legal audiences.",{"text":389},"The goal was to create a platform that felt accessible and welcoming to a broader range of users.",{"title":391,"body":392,"list":395,"outro":407},"Challenges & Tradeoffs",[393,394],"One of the biggest challenges was designing within a highly content-driven environment while avoiding interfaces that felt visually overwhelming.","Instead of relying heavily on graphics or decorative elements, I focused on:",{"items":396},[397,399,401,403,405],{"text":398},"Information clarity",{"text":400},"Layout structure",{"text":402},"Typography hierarchy",{"text":404},"Navigation simplicity",{"text":406},"Content readability",[408,409,410],"Another important tradeoff involved balancing scalability with customization.","The design system needed to remain flexible enough to support future updates and multiple court websites while still maintaining a cohesive ecosystem experience.","I also had to consider development efficiency by designing reusable components that minimized implementation overhead and simplified future revisions.",{"title":412,"list":413},"My Contributions",{"icon":414,"items":415},"material-symbols:workspace-premium-outline-rounded",[416,418,420,422,424,426,428,430,432,434,436],{"text":417},"Led the redesign of the Supreme Court website",{"text":419},"Designed the District Court website ecosystem",{"text":421},"Conducted UX audits and usability analysis",{"text":423},"Restructured information architecture",{"text":425},"Redesigned navigation systems and user flows",{"text":427},"Created wireframes and prototypes",{"text":429},"Designed responsive experiences across devices",{"text":431},"Improved document and information discoverability",{"text":433},"Enhanced search experiences",{"text":435},"Developed front-end pages using Nuxt.js",{"text":437},"Created reusable and scalable UI patterns",{"title":439,"body":440,"list":443,"outro":459},"Outcomes",[441,442],"Although formal metrics cannot be publicly shared, the redesign successfully addressed several long-standing usability concerns across the platform.","Key improvements included:",{"items":444},[445,447,449,451,453,455,457],{"text":446},"Simplified navigation",{"text":448},"Improved information organization",{"text":450},"Easier discovery of important documents and resources",{"text":452},"Clearer user pathways",{"text":454},"Better accessibility for non-legal audiences",{"text":456},"More consistent responsive experiences",{"text":458},"Improved search and browsing workflows",[460],"The outcome was not simply a more modern-looking website, but a more intentional experience designed around the needs of different user groups interacting with court-related information.",{"title":462,"body":463,"list":469,"outro":479},"Reflection & Learnings",[464,465,466,467,468],"This project reinforced the importance of designing for clarity, accessibility, and usability within complex information ecosystems.","Unlike many consumer-facing products, court websites serve users with very different levels of expertise and familiarity with legal systems. Designing for this audience required a strong focus on predictability, comprehension, and confidence.","One of the biggest lessons from this project was understanding how impactful information architecture can be on the overall user experience.","Improving how information is structured and discovered often creates more value than visual redesign alone.","The project also strengthened my ability to:",{"items":470},[471,473,475,477],{"text":472},"Design scalable systems",{"text":474},"Balance stakeholder and technical constraints",{"text":476},"Maintain consistency across large website ecosystems",{"text":478},"Build reusable patterns that support long-term maintainability",[480],"Most importantly, it reinforced that successful UX is not always about creating something visually bold. Sometimes the best solution is one that feels calm, intuitive, and effortless to navigate.",{"title":482,"body":483},"Conclusion",[484,485],"This project demonstrates my ability to lead large-scale UX initiatives that extend beyond interface design into information architecture, navigation strategy, content organization, responsive usability, and front-end implementation.","By redesigning both the Supreme Court and District Court websites, I helped transform a complex public information platform into a more accessible and user-centered experience while maintaining the clarity and reliability expected from government services.",{"title":487,"body":488},"Ongoing Involvement",[489,490,491],"I am currently continuing work within the District Court website ecosystem.","One ongoing challenge is maintaining a cohesive experience that still feels connected to the Supreme Court platform while allowing individual District Court websites to support their own unique content structures and operational needs.","This ongoing involvement continues to strengthen the scalability of the overall design system and reinforces the importance of consistency across large digital ecosystems.","Idaho Courts","\u002Fimages\u002Fprojects\u002Fcourt-sites\u002Fthumbnail.mp4","Transforming a complex public information ecosystem into a more accessible digital experience","md",false,{},true,3,"\u002Fprojects\u002Fcourt-websites","2025-01-01",{"title":5,"description":494},"projects\u002Fcourt-websites",[505,506,507],"Website","Prototype","Front-End",null,"2025 - Present","H8SdXpSnOax9mrLj0t1dWyElHqhI6QQK2fJZ257YFAU",[508,512],{"title":513,"path":514,"stem":515,"description":516,"children":-1},"Idaho Lottery Mobile App","\u002Fprojects\u002Fidaho-lottery-mobile-app","projects\u002Fidaho-lottery-mobile-app","Modernizing a live lottery application while establishing a scalable design foundation",1781719491197]