[BE-41] Hub settings & branding API — name, logo, colors, contact details

[yusuftomilola]

Overview

The hub's identity (name, logo, brand color, support contacts) is hardcoded across the frontend and email templates (COMPANY_NAME/SUPPORT_EMAIL env vars in backend/.env.example). A settings API makes ManageHub deployable for any hub without code changes — the first step toward white-labeling.

Proposed Design

New module backend/src/hub-settings/:

• Single-row HubSettings entity (enforce singleton in the service): hubName, logoUrl (Cloudinary — reuse backend/src/cloudinary/), faviconUrl (nullable), primaryColor (hex, validated), supportEmail, supportPhone, address, socialLinks (JSONB: twitter/instagram/linkedin), openingHours (JSONB per weekday, nullable).

Endpoints

Method	Path	Access
GET	/hub-settings	Public — everything above is public-safe
PATCH	/hub-settings	ADMIN/SUPER_ADMIN
POST	/hub-settings/logo	ADMIN — multipart upload via Cloudinary

Tasks

• Module + singleton row (created with sensible defaults on first read if absent — seed from the existing env values for backward compatibility).
• Email templates consume settings (hub name, support email, logo) instead of env constants where straightforward — at minimum the shared header/footer partials in backend/src/email/.
• Hex color and email/phone validation in the DTO; Swagger docs.
• Migration included.

Acceptance Criteria

• GET /hub-settings works unauthenticated and returns defaults on a fresh install.
• Updating the name/logo reflects in subsequently sent emails.
• Invalid hex colors are rejected with 400.

Dependencies

Blocks [FE-29].

Notes for Contributors

Good first issue. Comment below to be assigned.

[midenotch]

I'd like to work on this issue.

My approach is to implement a dedicated hub-settings module centered around a singleton HubSettings entity, ensuring a single source of truth for branding and contact information. The service will automatically initialize the settings with sensible defaults on first access, using the existing environment values to maintain backward compatibility for fresh deployments.

I'll implement the public GET /hub-settings endpoint alongside secured PATCH and logo upload endpoints, reusing the existing Cloudinary integration for asset management. The DTOs will include robust validation for hex color values, email addresses, and phone numbers, with complete Swagger documentation for the new API.

In addition, I'll update the shared email template components to consume hub settings dynamically—replacing hardcoded environment-based branding with the stored hub name, logo, and support email—so that branding changes are reflected in all newly generated emails without requiring code changes or redeployment.

Finally, I'll include the required database migration and verify the complete flow with appropriate tests, ensuring unauthenticated reads return default values on fresh installations and invalid branding inputs are correctly rejected.

I have experience building NestJS/Node.js backend services, REST APIs, Cloudinary integrations, database migrations, and validation-driven architectures, and I'm confident I can deliver a solution that aligns with the project's design and future white-labeling goals.

[wumibals]

@wumibals has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I have reviewed this issue and its acceptance criteria carefully. The requirements are clear and well-scoped (large complexity). I have hands-on experience with database migrations and can implement this following the patterns and conventions already in the codebase. I will deliver complete, tested code that satisfies every acceptance criterion without requiring follow-up corrections. I can start immediately and am happy to discuss approach details with the maintainer beforehand.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @wumibals to this issue.

[drips-wave]

Congratulations, @wumibals! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @wumibals: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊