[Feature] [Studio]: make overview dashboard greeting time-of-day dynamic

[Akshay7057017063]

Description

Updated the overview dashboard greeting to dynamically change based on the current time of day instead of using a hardcoded greeting.

The greeting now automatically displays:

• "Good Morning" during morning hours
• "Good Afternoon" during afternoon hours
• "Good Evening" during evening hours

This improves the user experience by providing a more personalized and dynamic dashboard interface.

Linked Issue

Fixes #109

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🧪 Tests (adding or updating tests)

Checklist

• I have read the [CONTRIBUTING.md](CONTRIBUTING.md) document.
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.

[Gautam25Raj]

Hi @Akshay7057017063,

Thank you for taking the time to contribute to VeriWorkly! We appreciate your effort in making the overview dashboard greeting dynamic.

Before we can review and merge this pull request, please address a few standard project guidelines:

1. Issue Assignment: In the future, please make sure to comment on the issue and wait to be assigned before starting work. This helps avoid duplicate efforts and ensures coordination with the team.

2. PR Title: Our project uses a specific title format. Please rename this PR to:
   [Feature] [Studio]: make overview dashboard greeting time-of-day dynamic

3. Linked Issue: Please link the specific issue this PR addresses in the PR description using the hashtag format (e.g., Fixes #<issue-number>) so GitHub can associate them automatically.

4. PR Checklist: Please edit the PR description to fill out the Type of Change and complete the Checklist by marking the checkboxes as complete (changing [ ] to [x] where applicable).

Once these updates are made, we'll be happy to proceed with the code review!

Thanks again!

[Akshay7057017063]

Hi @Gautam25Raj,

Thank you for the guidance. I have updated the PR title, linked the issue, and completed the checklist.

Could you please approve the pending workflow when you get time?

Thanks!

[Gautam25Raj]

Hi @Akshay7057017063,

Thanks for the contribution.

I noticed the PR title was still not updated to match the required project format, so I’ll update it from my side this time and proceed with the review/merge process if everything else looks good.

For future contributions, please make sure to complete the requested changes before asking for workflow approval. Also, please remember to comment on the related issue and wait to be assigned before starting work, as this helps us avoid duplicate efforts and keeps the project workflow organized.

Thanks again!