Social: add a DEV Community cover image template
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- design
Research direction
Start with docs/first-contribution.md, then copy the structure of lib/social/templates/telegram.ts or substack.ts for a 1000 x 420 DEV template. Register it in lib/social/registry.ts and check the type in lib/social/types.ts. Done when the template shows in the Social Media Studio list and the ZIP export, and the template tests pass for light and dark brand tokens with a 60-character name and website.
Written by the indexing model from the issue text.
Description
Summary
Add a DEV (dev.to) post cover at 1000 x 420.
Where to look
docs/first-contribution.md(a full walkthrough of adding a template)lib/social/templates/telegram.tsandsubstack.ts: recent templates to copylib/social/registry.tsandlib/social/types.ts
Behaviour
- DEV crops the cover to a wide strip in feeds: keep the title in the central area and mark it as the safe area.
Acceptance criteria
- The template appears in the Social Media Studio list and in the ZIP export.
- Text and logo stay inside the safe area, also with a 60 character name and website (the template tests check this automatically).
- Brand tokens only, light and dark.
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. 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 44m
- Merged PRs (30d)
- 72
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from yakew7/DesignHub
-
area: docs difficulty: medium enhancement help wanted testing v2.0.0
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
accessibility area: ui difficulty: medium enhancement help wanted v2.0.0
Difficulty 4/5 3-5 days Newbie friendliness 57/100
Maintainers usually reply within 1 day
-
area: projects difficulty: easy enhancement good first issue help wanted v2.0.0
Difficulty 3/5 1-2 days Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
area: backgrounds difficulty: easy enhancement good first issue help wanted testing v2.0.0
Difficulty 3/5 1-2 days Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area: projects difficulty: medium enhancement help wanted performance v2.0.0
Difficulty 3/5 1-2 days Newbie friendliness 84/100
Maintainers usually reply within 1 day
All issues in yakew7/DesignHub
Similar issues
-
desktop v3 windows
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
esengine/DeepSeek-Reasonix#15016 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
readest/readest#7413 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: medium size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
content triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eliasstravik/herdr-projects#788 ·