NYCPlanning / NYCPlanning/data-engineering

CEQR Hub: User Experience Feedback (DCP)

Open
#1,635 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

db-ceqr
Dominant language
Python
Stars
43
Forks
3
Avg merge
23h 3m
Merged PRs (30d)
44

Description

We received feedback from DCP designers over email (email subject: Feedback on CEQR Data Hub) -- copying it here for visibility.

Feedback 1

My first impression is that this looks great – it’s clean and very easy to navigate.

One thing you might want to consider is hyperlink formatting. For accessibility purposes, hyperlinks should not be indicated by color alone. I recommend underlining or bolding them by default.

It can also be helpful to set expectations for users about which hyperlinks link to external websites, and in the case of downloads, indicating the file format in a way that’s easy to see when scanning the page.

Image

Feedback 2

Overall the design looks very clean and consistent!

I create a figma file with some comments about minor changes that I caught when looking through the different pages in terms of navigation & header (home page) and the side bar on the dataset page.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Figma feedback and the copied comments, focusing on navigation, the home-page header, and the dataset-page sidebar. Review the existing CEQR Data Hub pages before deciding how to address link styling, external-link expectations, and visible download file formats; done means the agreed feedback has been implemented and checked across the affected pages.

Written by the indexing model from the issue text.

Assessment

Tech stack
figma
Domain
accessibility, design, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.