semmelei: Start page teaser for the newest News Post
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start by reviewing the start page and its existing news components, then inspect prototype variant C on the prototype/semmelei-news-placement branch for the card’s placement and styling. Implement the teaser rule and excerpt extraction in a pure module, and cover the 29-day, 30-day, no-post, and first-paragraph cases with Vitest. Done means the start page conditionally shows the card, and “Weiterlesen” links to /news; run the frontend checks.
Written by the indexing model from the issue text.
Description
Parent
#77
What to build
Customers notice the newest News Post on the shop's start page: a teaser card between hero and catalog, styled as prototype variant C (see the prototype/semmelei-news-placement branch, don't merge its code): eyebrow "Neuigkeit · ", title, excerpt clamped to two lines, and one "Weiterlesen" link to /news.
The card shows only if the newest Published News Post was published less than 30 days ago (fixed in code, no setting). The excerpt is the first paragraph of the body as plain text: headings, lists and quotes before it are skipped; link text and emphasis are kept as text. Teaser rule and excerpt live in a pure module so they can be unit-tested.
Acceptance criteria
- vitest: newest post at 29 days shows, at 30+ days hides, no posts hides
- vitest: excerpt is the first paragraph as plain text; leading heading/list/quote skipped; links and emphasis flattened
- Start page shows the card as in variant C and hides it per the rule; "Weiterlesen" leads to
/news - i18n rules followed; frontend checks green
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 10h 20m
- Merged PRs (30d)
- 36
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 myOmikron/code
-
wayfinder:task
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
wayfinder:task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
myOmikron/code#102 · 2 comments ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 5/5 Over a week Newbie friendliness 18/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
area: image-engine bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
snapotter-hq/SnapOtter#3885 ·
Maintainers usually reply within 1 day
-
Mend: dependency security vulnerability
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug P3 UI/UX
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
openclaw/openclaw#182077 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day