Randomly hijack "Read Latest Summary" button

[BhaveshKukreja29]

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 :)

[KartikSoneji]

I don't think we have enough traffic for an easter egg like that to be discovered naturally, but I agree that a button would be nice.
We can reduce the size of the other buttons to make room for it.

[HarshKapadia2]

Thank you for the effort towards improving this feature, @BhaveshKukreja29!

I don't think we should hijack the 'Read Latest Summary' button, as an element not doing what it explicitly says is almost never fun IMO, but a randomly appearing button called 'Read a Random Summary' sounds fun!

In addition, let's make a permanent entry in the burger menu at the top right of the page to be able to navigate to that endpoint at will.

[BhaveshKukreja29]

Just to clarify, by hijack I meant the "Read Latest Summary" Randomly becomes "Read Random Summary", so it'll do exactly what it says. I thought of this because it might go unnoticed and has a low probability, that'd be like the secret is front of your eyes haha.

Ok that sounds good to me too! So we'll do 2 things.

• Add a permanent entry in the burger menue
• Have a randomly appearing button (overwrite latest kr a new button whichever you agree to)

I'll raise a PR soon after trying out the placement of the button :)
Thanks!

[HarshKapadia2]

Ah got you now. Thank you for the clarification, Bhavesh!

We get very few visitors to our site, so getting the few users who do visit the site to their information ASAP is the biggest priority IMO. So, I think adding a new button is better than hijacking the existing button.

Thoughts, @KartikSoneji?