|
| 1 | +Project Detail Page Redesign Documentation |
| 2 | + |
| 3 | +Overview |
| 4 | + |
| 5 | +This redesign improves the Project Detail page for both crowdfunding projects and hackathon submissions. |
| 6 | +The objective is to create a simpler, clearer, and more professional experience by improving layout structure, visual hierarchy, and interaction flow. The redesign focuses on clarity of primary actions (Vote / Back), improved content readability, and consistent behavior across desktop and mobile. |
| 7 | + |
| 8 | +--- |
| 9 | + |
| 10 | +Design Principles |
| 11 | +* Clear primary action above the fold |
| 12 | +* Strong visual hierarchy |
| 13 | +* Reduced visual noise |
| 14 | +* Consistent spacing and typography |
| 15 | +* Intentional use of the green accent |
| 16 | +* Professional and trustworthy product feel |
| 17 | + |
| 18 | +--- |
| 19 | + |
| 20 | +Layout Structure |
| 21 | + |
| 22 | +Desktop |
| 23 | +Left: Sticky summary sidebar |
| 24 | +* Project logo |
| 25 | +* Title |
| 26 | +* Status and short description |
| 27 | +* Progress (votes/funding where applicable) |
| 28 | +* Primary CTA (Vote or Back) |
| 29 | +* Secondary actions (Share) |
| 30 | +* Creator info and external links |
| 31 | + |
| 32 | +Right: Main content area |
| 33 | +* Horizontal tab navigation |
| 34 | +* Dynamic tab content |
| 35 | +* Optimized reading width for long-form content |
| 36 | + |
| 37 | +> The sidebar remains visible while scrolling to maintain action visibility and improve engagement. |
| 38 | +
|
| 39 | +Mobile |
| 40 | +* Sidebar collapses into a condensed header block |
| 41 | +* Horizontal scrollable tab navigation |
| 42 | +* Single-column content layout |
| 43 | +* Primary CTA positioned prominently without overwhelming the interface |
| 44 | + |
| 45 | +> No feature loss between desktop and mobile. |
| 46 | +
|
| 47 | +--- |
| 48 | + |
| 49 | +Component Redesign |
| 50 | +1. Loading State |
| 51 | +A simplified skeleton layout that mirrors final structure: |
| 52 | +* Sidebar placeholder block |
| 53 | +* Tab row skeleton |
| 54 | +* Content block placeholders |
| 55 | +* Reduced visual motion for a clean, professional feel |
| 56 | + |
| 57 | +> The loading state communicates layout structure without clutter. |
| 58 | +
|
| 59 | +--- |
| 60 | + |
| 61 | +2. Sidebar (Desktop) / Header Block (Mobile) |
| 62 | +Improvements: |
| 63 | +* Strong title hierarchy |
| 64 | +* Short description positioned clearly under title |
| 65 | +* Simplified progress visualization |
| 66 | +* One clearly emphasized primary action |
| 67 | +* Secondary actions styled with lower visual weight |
| 68 | +* Creator avatar and name placed below primary CTA |
| 69 | +* External links grouped and visually subtle |
| 70 | + |
| 71 | +> The goal is clarity and action focus. |
| 72 | +
|
| 73 | +--- |
| 74 | + |
| 75 | +3. Tab Bar |
| 76 | +Tabs: Details, Team, Milestones, Voters (optional), Backers (optional), Comments |
| 77 | +Improvements: |
| 78 | +* Clear selected state |
| 79 | +* Subtle hover state |
| 80 | +* Consistent spacing and typography |
| 81 | +* Scrollable on mobile |
| 82 | +* Optional tabs hidden gracefully when not applicable |
| 83 | + |
| 84 | +> The tab system is visually lightweight but structurally strong. |
| 85 | +
|
| 86 | +--- |
| 87 | + |
| 88 | +Tab-Level Redesign |
| 89 | +Details Tab |
| 90 | +* Controlled reading width for markdown content |
| 91 | +* Clear heading hierarchy |
| 92 | +* Improved paragraph spacing |
| 93 | +* Links styled consistently |
| 94 | +* Optional media block positioned after introduction |
| 95 | +* Improved vertical rhythm |
| 96 | + |
| 97 | +> Focus: readability and professional presentation. |
| 98 | +
|
| 99 | +Team Tab |
| 100 | +* Grid layout on desktop |
| 101 | +* Vertical list on mobile |
| 102 | +* Avatar, name, and role hierarchy clearly defined |
| 103 | +* Clean spacing between members |
| 104 | + |
| 105 | +Empty State Example: |
| 106 | +> No team members yet. This project is currently solo. |
| 107 | +
|
| 108 | +Milestones Tab |
| 109 | +* Vertical timeline layout |
| 110 | +* Status indicators (Upcoming, Active, Completed) |
| 111 | +* Clean separation between stages |
| 112 | +* Optional filter alignment |
| 113 | + |
| 114 | +Empty State Example: |
| 115 | +> No milestones have been added yet. |
| 116 | +
|
| 117 | +Voters Tab |
| 118 | +* Clean list layout |
| 119 | +* Vote indicators clearly distinguished |
| 120 | +* Sorting control aligned with header |
| 121 | + |
| 122 | +Empty State Example: |
| 123 | +> No votes yet. Be the first to support this project. |
| 124 | +
|
| 125 | +Backers Tab |
| 126 | +* Supporter card or structured list layout |
| 127 | +* Clear contribution display |
| 128 | +* Encouraging but subtle empty state |
| 129 | + |
| 130 | +Empty State Example: |
| 131 | +> Be the first to back this project. |
| 132 | +
|
| 133 | +Comments Tab |
| 134 | +* Structured threaded layout |
| 135 | +* Controlled indentation depth |
| 136 | +* Clear reply visibility |
| 137 | +* Sorting dropdown aligned to section header |
| 138 | +* Clean comment input field with clear submit action |
| 139 | + |
| 140 | +Empty State Example: |
| 141 | +> No comments yet. Start the discussion. |
| 142 | +
|
| 143 | +--- |
| 144 | + |
| 145 | +Empty State Strategy |
| 146 | +Each tab includes a purposeful empty state to avoid dead screens: |
| 147 | +* Encourage action |
| 148 | +* Maintain tone consistency |
| 149 | +* Support engagement goals |
| 150 | + |
| 151 | +--- |
| 152 | + |
| 153 | +Error State Strategy |
| 154 | +Each tab and interactive component must handle failures gracefully to maintain clarity, trust, and engagement. |
| 155 | + |
| 156 | +General Principles |
| 157 | +* Display a clear, concise error message in context |
| 158 | +* Offer a retry action when appropriate |
| 159 | +* Maintain the same layout structure as loading and empty states |
| 160 | +* Keep messaging professional and consistent with tone |
| 161 | + |
| 162 | +Tab-Level Examples |
| 163 | +Details / Team / Milestones / Voters / Backers / Comments Tabs |
| 164 | + * Error message: “Something went wrong while loading this content.” |
| 165 | + * Retry CTA: “Try again” button positioned centrally within the tab content area |
| 166 | + * Maintain spacing and typography consistency with other states |
| 167 | + |
| 168 | +Comment Submission Failure |
| 169 | + * Inline error: “Your comment could not be submitted.” |
| 170 | + * Preserve typed input so users don’t lose their content |
| 171 | + * Include a retry button adjacent to the input field |
| 172 | + |
| 173 | + Vote / Back Action Failure |
| 174 | + * Inline or toast notification: “Your vote could not be recorded.” |
| 175 | + * Provide immediate retry option |
| 176 | + * Ensure visual distinction from primary actions to avoid confusion |
| 177 | + |
| 178 | +Deliverables for Implementation |
| 179 | +* Error-state mockups for all tabs and key actions |
| 180 | +* Retry interaction designs and user flow diagrams |
| 181 | +* Copy for all error messages and notifications |
| 182 | + |
| 183 | +--- |
| 184 | + |
| 185 | +UX Improvements |
| 186 | +* Single primary CTA above the fold |
| 187 | +* Sticky action area improves conversion |
| 188 | +* Stronger reading experience |
| 189 | +* Consistent spacing system |
| 190 | +* Clear separation of primary vs secondary actions |
| 191 | +* Reduced cognitive load |
| 192 | + |
| 193 | +--- |
| 194 | + |
| 195 | +Visual System Adjustments |
| 196 | +* Reduced shadow usage |
| 197 | +* Controlled border radius for consistency |
| 198 | +* Green accent reserved primarily for key actions and highlights |
| 199 | +* Improved typography hierarchy |
| 200 | +* Balanced whitespace for clarity |
| 201 | + |
| 202 | +> The page now feels lighter, more modern, and more trustworthy. |
| 203 | +
|
| 204 | +--- |
| 205 | + |
| 206 | +Responsiveness Strategy |
| 207 | +* Sidebar collapses into header on smaller screens |
| 208 | +* Horizontal tab scroll |
| 209 | +* Content reflows naturally |
| 210 | +* No feature disparity between device sizes |
| 211 | + |
| 212 | +--- |
| 213 | + |
| 214 | +Deliverables |
| 215 | +* Desktop full-page mockups (all tabs) |
| 216 | +* Mobile full-page mockups (all tabs) |
| 217 | +* Component-level breakdown |
| 218 | +* Loading, empty, and error state designs |
| 219 | +* Retry interaction and UX flow documentation |
| 220 | +* UX recommendations |
| 221 | + |
| 222 | +Figma link: |
| 223 | +https://www.figma.com/design/EMNGAQl1SGObXcsoa24krt/Boundless_Project-Details?node-id=0-1&t=TAP62qLgaqjB5B1K-1 |
0 commit comments