Ramadan Activities System

The participant dashboard lists the current month's active activities as daily cards. Each card communicates state through color: missed tasks, tasks completed late, tasks completed on the correct day, today's task, and upcoming tasks. That made the experience feel like a simple plan rather than a generic content archive.

Admins can create and edit activities with a title, rich content, day label, date, publish status, Quran toggle, YouTube video id, and optional audio file. The goal was to let organizers prepare the full Ramadan sequence without needing to touch the code for each new reading or media item.

When a participant opens an activity, the page includes a completion action that saves a UserActivity record for the signed-in user. The dashboard then compares the completion date with the activity date, so the system can separate on-time completion from catch-up completion.

Not every activity is ordinary text. The app added an isQuran path so Quran readings can render through a dedicated Quran presentation with custom typography and a bismillah opening, while other activities can use regular rich text, audio, or embedded video.

The registration flow asks for gender, nationality, and birth year alongside the standard Laravel auth fields. A seeded Arabic country list supports the nationality field, and those profile attributes feed the statistics screen rather than staying as unused metadata.

The /statics page counts registered users, created activities, all recorded completions, completions submitted today, and gender distribution. It is a small analytics layer, but it gives the organizer a practical sense of adoption and daily participation.

This was an early Laravel application, and it shows a practical instinct I still value: start with the real workflow, model the smallest data structures that support it, and make the interface clear for the people using it. The code is compact, but the product shape is complete enough to support a seasonal community routine.