Enhancing User Onboarding with Mentorship and Progressive Community Badges in Laravel

Introduction

In our landing project, which focuses on connecting users with community opportunities, we recognized a need to deepen user engagement and foster a stronger sense of community leadership. Our existing onboarding flow, while functional, concluded after users defined their community projects, potentially leaving an untapped opportunity to guide them towards active mentorship and leadership roles.

The Challenge

The previous onboarding experience was missing a crucial link: promoting active participation in mentorship and recognizing users for their contributions. We needed to achieve several goals:

1. Guide new users: Introduce the concept of mentorship and community leadership early in the user journey.
2. Recognize contributions: Implement a system to award users for progressively deeper levels of community engagement, beyond just initial project setup.
3. Showcase impact: Allow users to proudly display their mentorship achievements on their public profiles.

The Solution

We addressed these challenges by extending the onboarding process to include a dedicated mentorship step and implementing a progressive badge system. This involved several key architectural changes, leveraging Laravel's capabilities:

1. Extended Onboarding Flow: A 5th onboarding step was introduced, specifically designed to inform users about mentorship opportunities and community leadership. The CommunityProjectOnboardingController was updated to redirect to this new step instead of marking onboarding complete.
2. Progressive Badges: We introduced three new badges – Community Contributor, Community Leader, and Community Champion – each awarded based on specific engagement criteria (e.g., publishing a service, completing 1 session, completing 5 sessions). This logic was encapsulated within a dedicated MentorBadgeService.
3. Community Impact Section: A new 'Community Impact' section was added to user portfolio stats pages, displaying metrics like the number of completed mentoring sessions and unique mentees helped. This data aggregation was handled by a CommunityImpactService.
4. Middleware Update: The EnsureCommunityOnboarded middleware was modified to correctly recognize the new, longer onboarding path.

Here's an illustrative example of how a MentorBadgeService might handle awarding a badge:

namespace App\Services;

use App\Models\User;
use App\Models\Badge;
use App\Enums\BadgeType;

class MentorBadgeService
{
    public function awardContributorBadge(User $user): void
    {
        // Check if user has published a service and doesn't already have the badge
        if ($user->hasPublishedService() && !$user->hasBadge(BadgeType::COMMUNITY_CONTRIBUTOR)) {
            $badge = Badge::firstWhere('type', BadgeType::COMMUNITY_CONTRIBUTOR);
            if ($badge) {
                $user->badges()->attach($badge->id);
                // Trigger event or notification
            }
        }
    }

    public function awardLeaderBadge(User $user): void
    {
        // Check if user has completed at least one mentoring session
        if ($user->completedMentoringSessions()->count() >= 1 && !$user->hasBadge(BadgeType::COMMUNITY_LEADER)) {
            $badge = Badge::firstWhere('type', BadgeType::COMMUNITY_LEADER);
            if ($badge) {
                $user->badges()->attach($badge->id);
            }
        }
    }

    // ... similar methods for other badge types
}

Key Decisions

• Service Layer Encapsulation: Decoupling badge awarding logic and community impact calculations into dedicated Service Layer classes (MentorBadgeService, CommunityImpactService) ensures maintainability, testability, and adherence to the single responsibility principle.
• Progressive Recognition: Introducing multiple badge tiers encourages continuous engagement and provides a clear progression path for community members.
• Idempotency: Badge awarding logic was designed to be idempotent, meaning multiple calls to award a badge would not result in duplicate entries or errors if a user already possesses it.
• Middleware for Flow Control: Utilizing Laravel's Middleware Pattern (EnsureCommunityOnboarded) effectively manages the onboarding state and ensures users follow the intended multi-step process.

Results

By implementing these features, we've created a more guided and rewarding experience for new users. The extended onboarding clearly communicates the value of mentorship, while the progressive badges and 'Community Impact' section provide visible recognition for active contributors. This fosters a more engaged and leadership-driven community.

Lessons Learned

Building out a comprehensive onboarding and recognition system underscores the importance of a well-defined Service Layer and judicious use of middleware. By clearly separating concerns, we were able to introduce significant new functionality with minimal impact on existing code and ensure high test coverage. Always consider how to make engagement visible and rewarding; it’s a powerful driver for community growth.