💡 Feature Idea: Let's build a "Public Calendar" together! 🗓️

[aymanaboghonim]

👋 Hi Community!

We have an exciting opportunity for us to collaborate on a new feature for our website, and we’d love your input and help to make it happen.

The Goal:
We host many amazing open sessions and workshops, but right now, our main website (elmentorprogram.github.io) doesn't show them. It would be great to have a "Public Calendar" or "Upcoming Events" section so visitors can instantly see what's coming up next.

🤔 Exploring Our Options

To get the conversation started, here are a few ways we could approach this. What do you think would work best for us?

• Option A: A Simple Static List
  We could just hard-code the next few events directly into the page. It’s the easiest way to start, though it means we’d need to update the code manually for every new event.

• Option B: A Full Calendar View
  We could integrate a library (like react-big-calendar) to show a full monthly grid. It looks professional, but might be a bit complex given that we usually only have a few events per month.

• Option C: The "Smart Integration" (Fetching from our Blog) 🚀
  Since we already post events on our Blog, we could potentially "fetch" that data automatically. This is a cool "Headless CMS" style pattern—we update the blog, and the website updates itself!

---

🗺️ A Potential Roadmap (Draft)

If we decided to go with something like Option C, here is a rough idea of what that journey might look like. This could be a great learning project for anyone interested in React Hooks and APIs:

1. The Data Side (Blog)
We could create a small file on our blog (e.g., events.json) that simply lists our events in a machine-readable format. It acts like a little "Static API."

2. The Website Side (React)
We could build a simple component (UpcomingEventsSection) that:

• Fetches that file when the page loads.
• Displays the next 3 events as simple cards (Date, Title, Link).

This is just a starting point—you might have an even better way to do it!

🤝 Let's Discuss!

We want this to be a community effort.

• Which approach do you think strikes the right balance between "cool feature" and "easy to maintain"?
• Do you have a completely different elegant solution?

Let’s discuss the best approach below. Once we agree on a direction, we can turn this into an Issue and someone (or a team!) can take the lead on building it. 🚀

[ShereenS]

Love this 🥳😍