Extract hardcoded values into a centralized constants file

[Akatenvictor]

What

Identify hardcoded strings, numbers, URLs, and magic values across the codebase and extract them into centralized constants files.

Why

Hardcoded values scattered across files are hard to update and easy to mistype. Centralized constants ensure consistency and simplify configuration changes.

Scope

In: API URLs, cache durations, UI constants (breakpoints, z-indices), validation limits, error messages
Out: Environment-specific constants

Acceptance Criteria

• API base URLs extracted to constants
• Cache duration values centralized
• UI breakpoint values in one location
• Z-index scale documented and centralized
• Validation limits (max bio length, etc.) in constants
• Error message strings centralized

Technical Context

• Create lib/constants.ts for app constants
• Create lib/config.ts for configuration values
• Import from constants instead of hardcoding

[supremeproton01]

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

I would love to work on this, kindly assign me

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

[sunnykid-02]

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

I’d like to work on this issue because centralizing hardcoded values is a valuable refactoring that improves code readability, maintainability, and consistency across the project. Having a single source of truth for shared constants makes future updates easier, reduces duplication, and minimizes the risk of inconsistencies.

I have experience refactoring codebases to improve organization and maintainability, including extracting shared configuration, constants, and reusable utilities.

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

[BigMick03]

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

Hi there Maintainer. I will like to work on this.

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

[drips-wave]

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

🧑‍💻 @balisdev: 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 🌊

[drips-wave]

This issue has been completed by @balisdev as part of the Stellar Wave Program's 7th Wave 🥳

😎 @balisdev: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.