Timezone-Aware Service Booking Calendar with Slot Locking

[meshackyaro]

Description

This issue aims to address the implementation of Timezone-Aware Service Booking Calendar with Slot Locking.

The core objective is to: Deliver a booking calendar that renders provider availability in the visitor's local timezone and prevents double-booking via slot locking.

By completing this feature, we will ensure that the GuildWorkman protocol maintains its high standards for security, usability, and decentralized logic. This issue requires careful attention to the Frontend architecture and adherence to the existing project conventions.

When picking up this issue, please ensure you document any new dependencies or architectural decisions made during development.

Component

Frontend

Difficulty

🔴 Hard

Tasks

• Review Next.js App Router structure
• Implement the UI components for: Timezone-Aware Service Booking Calendar with Slot Locking
• Ensure responsive design using Tailwind CSS or standard modules
• Add caching for npm dependencies in CI
• Run npm run lint and npm run typecheck
• Run npm run build to verify production bundling

Acceptance Criteria

• Feature accurately implements the objective: Deliver a booking calendar that renders provider availability in the visitor's local timezone and prevents double-booking via slot locking.
• Any PR that introduces TypeScript errors is automatically blocked
• CI pipeline runs in under 3 minutes per PR
• Code is properly reviewed and approved by codeowners

Estimated Time

1-3 days

[rexx010]

Hi, I’m interested in working on this issue. I’ve worked on frontend booking flows and concurrency-related problems before, so I’d implement the calendar with timezone-aware availability conversion and a slot-locking mechanism to prevent double bookings. I’d also follow the existing Next.js architecture, ensure responsive behavior, optimize CI dependency caching, and validate the implementation with lint, typecheck, and production builds.

[grantfox-oss]

🦊 GrantFox — @rexx010 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 #28)
2. Your PR will be reviewed by the workman-labs 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!

@rexx010's PR #34 was approved and merged by @meshackyaro.

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

👏 Great work, @rexx010! Keep contributing to workman-labs.