CodeForPhilly / CodeForPhilly/codeforphilly.org

UX audit of our https://codeforphilly.org/volunteer page

未關閉
#94 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
redesign
主要語言
CSS
星號
10
分支
7
PR 合併指標
30 天內沒有已合併 PR

描述

Currently, many parts of codeforphilly.org direct people to our volunteer page (https://codeforphilly.org/volunteer). Since this page is so central to getting started, making it easier to follow may go a long way toward helping people get started.

I am a UX barbarian, so if you are a content writer, or interested in UX / a UX practitioneer, please reach out on the Code for Philly [#cfp-homepage-redesign](https://codeforphilly.org/chat?channel=cfp-homepage-redesign) channel!

Big questions:

* What do people want to do when they reach this page? (assuming they want to join a project, or connect with the CfP community e.g. via slack)
* How long does it take them to get through the page?
* Are there any tricky points? (e.g. I tried to click the steps at the top of the page, but they are not links, but I might not be very representative)
* How could we make this easier / feel better?

貢獻指南

這個儲存庫沒有索引到貢獻指南

研究方向

先檢視 https://codeforphilly.org/volunteer 上的志工頁面,並觀察訪客可以如何加入專案或與 Code for Philly 社群建立連結。使用 issue 中的問題來確認目標、完成頁面所需的時間,以及令人困惑的互動,並在 #cfp-homepage-redesign 中討論發現。完成的標準是產出一份取得共識的 UX 稽核與建議。

由索引模型根據 Issue 內容生成。

評估

領域
design
Issue 類型
功能
難度
5/5
預估耗時
一週以上
活躍度
停滯
描述清晰度
需要釐清
新手友好度
25/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。