Build a rich profile customization module (deferred area)

[Lakes41]

Difficulty: Advanced | Type: Feature

Background: "Rich profile customization" is explicitly listed as deferred, beyond the existing basic "profile summary."

Problem: Members currently have minimal ability to personalize their public-facing profile (e.g. display name, avatar, bio, social links), limiting the platform's community-identity features.

Expected Outcome: An expanded profile editor supports avatar (URL-based or upload-stub), display name, bio, and social links, with appropriate client-side validation (building on #18) and a public-facing profile view usable by other members/admins.

Suggested Implementation: Extend the profile data model in lib/api/types.ts (coordinating with the backend contract for new fields), build an expanded editor UI, and add a read-only public profile route (app/members/[address]/page.tsx or similar) rendering the customized fields.

Acceptance Criteria:

• Editor supports all listed new fields with client-side validation.
• A public profile view renders another member's customized profile correctly.
• Backward-compatible with members who haven't set any custom fields (sensible defaults/empty states).

Likely Affected Files/Directories: app/(member)/*, app/members/* (new), lib/api/types.ts

Labels: feature, architecture, GrantFox OSS, Maybe Rewarded, Official Campaign | FWC26

[didi168]

My approach would be to extend the profile model to support display names, avatars, bios, and social links while keeping the experience backward-compatible for existing members who haven't configured any profile data.
On the frontend, I'll build an expanded profile editor with appropriate client-side validation and sensible UX around optional fields. I'll also add a public profile view that renders customized member information cleanly while handling empty states gracefully.

I have experience designing and implementing React/Next.js features that span data models, forms, validation, and public-facing views, and I'm comfortable coordinating changes with the backend contract where needed. I'll aim for a clean, maintainable implementation with strong test coverage and documentation.

[grantfox-oss]

🦊 GrantFox — @didi168 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #254)
2. Your PR will be reviewed by the Adamantine-guild maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@didi168's PR #309 was approved and merged by @Lakes41.

🏆 @didi168: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (121 total points). Track your full progress on GrantFox.

👏 Great work, @didi168! Keep contributing to Adamantine-guild.