FleekDash 1.2.2 introduces a clearer and more resilient avatar strategy across the interface: a 3-level hierarchy that prioritizes user identity while avoiding broken images.
What's New
Level 1, Uploaded avatar (preferred): if the user has a custom uploaded avatar, FleekDash renders it first.
Level 2, Gravatar fallback: when no uploaded avatar is available, FleekDash attempts to resolve a Gravatar based on the user identity/email context.
Level 3, Native FleekDash letter avatar: if Gravatar is unavailable or missing, FleekDash renders a lightweight generated avatar with user initials as the final fallback.
How it works
FleekDash checks whether a valid uploaded avatar URL exists and loads it.
If not, it tries Gravatar.
If Gravatar also fails or is unavailable, FleekDash generates a native letter avatar instantly.
This keeps avatar rendering predictable on slow networks, privacy-restricted environments, and partially configured user profiles.
What's Improved
Fewer broken avatar states: users no longer see empty image slots when external providers fail.
Better performance and consistency: lightweight letter avatars ensure fast first paint and coherent UI identity across tables, cards, and search results.
