Describe the bug
Description
The Subscribe button located at the top of the Dynamic Programming Visualizer page appears clickable but does not perform any visible action or trigger any functionality.
This creates confusion for users, as it gives the impression that they can subscribe to updates or features — but nothing happens after clicking it.
To Reproduce
Steps to Reproduce
Go to https://algovisualizer.rhythmpahwa.tech/dp
.
Locate the green “Subscribe” button below the main heading.
Click the button.
Observe that no visual change, message, or redirect occurs.
Expected behavior
Expected Behavior
The button should either:
Perform a specific action (e.g., open a subscription modal, link to a newsletter, or trigger a toast message), or
Be removed if not yet implemented.
Actual Behavior
The button is clickable but does nothing — no feedback, no visual change, no console log, no API call.
🧩 Option 1: Implement a modal or toast (e.g., “Coming soon” or “Feature under development”).
🧩 Option 2: Link it to an actual subscription endpoint or newsletter page.
🧩 Option 3: Remove the button entirely until a working subscription feature exists.
Additional context
Describe the bug
Description
The Subscribe button located at the top of the Dynamic Programming Visualizer page appears clickable but does not perform any visible action or trigger any functionality.
This creates confusion for users, as it gives the impression that they can subscribe to updates or features — but nothing happens after clicking it.
To Reproduce
Steps to Reproduce
Go to https://algovisualizer.rhythmpahwa.tech/dp
.
Locate the green “Subscribe” button below the main heading.
Click the button.
Observe that no visual change, message, or redirect occurs.
Expected behavior
Expected Behavior
The button should either:
Perform a specific action (e.g., open a subscription modal, link to a newsletter, or trigger a toast message), or
Be removed if not yet implemented.
Actual Behavior
The button is clickable but does nothing — no feedback, no visual change, no console log, no API call.
🧩 Option 1: Implement a modal or toast (e.g., “Coming soon” or “Feature under development”).
🧩 Option 2: Link it to an actual subscription endpoint or newsletter page.
🧩 Option 3: Remove the button entirely until a working subscription feature exists.
Additional context