Project: Configurable Enterprise Dashboard

An enterpriseDashboard component whose displayed metric tiles — which ones appear, in what order, with what label — are driven entirely by Dashboard_Tile__mdt Custom Metadata records (Module 16), not hardcoded in the component.

public inherited sharing class DashboardConfigService {
    public static List<DashboardTile> getConfiguredTiles() {
        List<DashboardTile> tiles = new List<DashboardTile>();
        for (Dashboard_Tile__mdt config : [
            SELECT Label__c, Metric_Key__c, Display_Order__c
            FROM Dashboard_Tile__mdt
            WHERE IsActive__c = true
            ORDER BY Display_Order__c
        ]) {
            tiles.add(new DashboardTile(config.Label__c, config.Metric_Key__c));
        }
        return tiles;
    }
}

public with sharing class DashboardController {
    @AuraEnabled(cacheable=true)
    public static List<DashboardTile> getConfiguredTiles() {
        return DashboardConfigService.getConfiguredTiles();
    }
}

An admin can activate, deactivate, relabel, or reorder tiles entirely through Setup — no Apex change, no LWC change, no deployment required for any of that.

<div class="slds-grid slds-wrap slds-gutters">
    <template for:each={tiles} for:item="tile">
        <div key={tile.metricKey} class="slds-col slds-size_1-of-1 slds-medium-size_1-of-3">
            <div class="slds-box slds-text-align_center">
                <h3>{tile.label}</h3>
                <p class="slds-text-heading_large">{tile.value}</p>
            </div>
        </div>
    </template>
</div>

The component renders however many tiles the metadata configuration provides — zero hardcoded assumptions about which metrics exist or how many there are, exactly the "configuration for admin-tunable values" line Module 16 drew, while the actual metric calculation logic itself (not shown) still lives in real, tested Apex code, not configuration.