Social: add a Hashnode blog cover template
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- nextjs, tailwindcss, typescript
- Domain
- design
Research direction
Start with docs/first-contribution.md, then copy the structure of lib/social/templates/telegram.ts or substack.ts and register the new template in lib/social/registry.ts, typed by lib/social/types.ts. Set the Hashnode cover to 1600 x 840 using brand tokens only, with light and dark variants. Done when the template shows in the Social Media Studio list and ZIP export, and the template tests pass with a 60 character name and website, after running pnpm typecheck, test, lint, format:check, check:dashes and build.
Written by the indexing model from the issue text.
Description
Summary
Add a Hashnode cover at 1600 x 840.
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
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
- 6h 32m
- Merged PRs (30d)
- 31
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: backgrounds difficulty: easy good first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area: ui difficulty: easy good first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
area: social difficulty: easy enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Docs: write a translation guide for contributorsPossibly taken @Muthulakshmikumar claimed this 3 days ago. Openarea: docs difficulty: easy documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
yakew7/DesignHub#225 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
area: brand difficulty: hard enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
All issues in yakew7/DesignHub
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
melgarafael/DeskcommCRM#3000 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
callstackincubator/simlock#639 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
aws/agentcore-cli#2606 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 7 days
-
ai-driven-qa bug Cosmetic
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day