Randomly hijack "Read Latest Summary" button
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript
Research direction
Start by locating the frontend implementation of the "Read Latest Summary" button and the /summary/random route. Check how browser storage is used, then implement the random first-visit behavior described in the issue. Done means the latest button sometimes becomes a random-summary button for returning users while remaining unchanged for first-time visitors.
Written by the indexing model from the issue text.
Description
Currently, the /summary/random route is accessible only by URL, added in #75. It was decided to keep it as a hidden easter egg and avoid adding a permanent button since it'd cause clutter, but there is no way for a user to discover it via frontend.
We can add a client side script that has a low probability (5 percent?) of hijacking "Read Latest Summary" and swap with "Read Random Summary". I also considered that we don't want to do this if the user is a first time visitor, we can simply use localStorage and store a boolean value for that.
10-12 lines of code at max. After considering several other approaches, this seems the easiest, and also the most fun. After all, random summary picker definitely deserves a randomly appearing button :)
- Dominant language
- JavaScript
- Stars
- 19
- Forks
- 18
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 3
Contributor guide
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 OurTechCommunity/catchup
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
OurTechCommunity/catchup#303 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 38/100
OurTechCommunity/catchup#258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
OurTechCommunity/catchup#184 · 2 comments ·
-
CI/CD good first issue
Difficulty 1/5 Under an hour Newbie friendliness 55/100
OurTechCommunity/catchup#172 · 1 comment ·
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 55/100
OurTechCommunity/catchup#154 · 1 reaction ·
All issues in OurTechCommunity/catchup
Similar issues
-
awaiting triage bug Causes friction Hop Gui P1 P2 Transforms
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
georgestephanis/p2026#40 ·
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Margaret-Petersen/food-delivery-app-clone-react-native#1981 ·