hypothesis / hypothesis/product-backlog

Implement the revised onBoarding/Getting Started work

Open
#411 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Design
Dominant language
No language data
Stars
122
Forks
7
PR merge metrics
No merged PRs in 30d

Description

Background:

As part of the eLife work, the 'Getting Started' card was revised to be more clear and user friendly.

It was decided that the 'Getting Started' card should be universally implemented across the client.

However, the design was only implemented for eLife due to time constraints, so the outstanding work is to push out the revised getting started card to all Hypothesis users.

The previous issue which contained both pieces or work has since been closed, so adding the revised 'Getting Started' designs below.

Thanks!

@sheetaluk implemented the eLife 'Getting Started' configuration so please liaise with her as a design pattern exists already for this but what needs to change is the content/text block instructions (Hypothesis has more instructions than eLife) and the colours of the CTA (eLife: blue -> Hypothesis grey).

Revised Getting Started Design:

getting started - hypothesis2

Existing Getting Started Card:

getting started - getting started
getting started - no annotations

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 by reviewing the existing eLife Getting Started configuration and the two supplied designs, then liaise with @sheetaluk about the established pattern. Update the card for all Hypothesis users with the Hypothesis-specific instruction text and grey CTA, and verify that the revised card appears consistently across the client.

Written by the indexing model from the issue text.

Assessment

Domain
design, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.