Storage: ask the browser to keep DesignHub's data and say what happened

Closed
  • Is something wrong?
#501 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
nextjs, tailwindcss, typescript
Domain
frontend

Research direction

Start with components/projects/storage-panel.tsx and lib/storage-report.ts, then read docs/storage.md to see how the panel reports sizes and counts today. Wrap navigator.storage.persisted() and navigator.storage.persist() in a small helper that returns protected, not protected, or not supported, and only call persist() from the button's click handler. Done when a unit test with a fake storage object covers all three states, the new strings exist in en, es, fr and hi, and the panel still shows only sizes and counts.

Written by the indexing model from the issue text.

Description

area: projects difficulty: easy enhancement good first issue help wanted v2.0.0

Summary

Browsers may clear a site's storage under pressure unless it is marked persistent. DesignHub keeps people's only copy of their brands there. Add a line to the Storage panel that says whether the data is protected and a button that asks the browser to protect it.

Part of the 2.0.0 plan: fewer, better and fully tested studios, on a calmer and faster site.

Where to look

  • components/projects/storage-panel.tsx and lib/storage-report.ts
  • navigator.storage.persisted() and navigator.storage.persist()
  • docs/storage.md

Behaviour

  • Show Protected or Not protected, and a Protect my data button when it is not and the browser supports it.
  • Say plainly when the browser refuses (some only grant it after installing or using the site often).
  • Never ask without the person pressing the button.

Acceptance criteria

  • A unit test covers the three states (protected, not protected, not supported) with a fake storage object.
  • The text is translated in en, es, fr and hi.
  • The panel still shows only sizes and counts.

Getting started: fork the repo, then pnpm install and pnpm dev (Node 22+, pnpm 11, no API keys). Before opening a PR, run pnpm typecheck && pnpm test && pnpm lint && pnpm format:check && pnpm check:dashes && pnpm build (CI fails on unformatted files, so pnpm format first). See CONTRIBUTING.md and the first contribution walkthrough.

Everything needed is in the repository. This doesn't need maintainer access, secrets or paid services. Comment below to claim it, and ask questions here any time.

Dominant language
TypeScript
Stars
11
Forks
3
Avg merge
5h 23m
Merged PRs (30d)
74

Getting set up

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.

More from yakew7/DesignHub

All issues in yakew7/DesignHub

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.