Skip to content

Flipping over 2025 and getting ready for 2026. #86

Merged
nikolovlazar merged 1 commit into
masterfrom
2026/early-prep
Sep 8, 2025
Merged

Flipping over 2025 and getting ready for 2026. #86
nikolovlazar merged 1 commit into
masterfrom
2026/early-prep

Conversation

@jmanhart

@jmanhart jmanhart commented Sep 8, 2025

Copy link
Copy Markdown
Contributor

Changes

  • Changed root redirect from /projects to /years
  • Updated all countdown timers from 2025-08-18 to 2026-08-17
  • Simplified timer logic (removed complex Friday calculations)
  • Updated micro countdown text to "day till hackweek"

…to next year. Having people go to the archives view first. Adding winners for 2025. 🎉 Victory
Comment on lines +5 to 6
const hackweekDate = new Date('2026-08-17T00:00:00');
const difference = hackweekDate - new Date();

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Potential bug: Countdown timers now use a date string without a timezone, causing them to resolve to the user's local time instead of a single global time.
  • Description: The application's countdown timers were changed to use a hardcoded date string, 2026-08-17T00:00:00, without a timezone specifier. Both the native Date constructor and the moment.js library interpret such strings in the user's local timezone. The previous implementation contained logic to synchronize the countdown to a specific moment in Pacific Time. As a result of this change, users in different timezones will see the countdown end at different absolute times, which can cause significant confusion for a globally coordinated event like a hackweek.

  • Suggested fix: To ensure the countdown is synchronized globally, modify the date string to include a timezone. For example, use an ISO 8601 string with a UTC designator, such as '2026-08-17T07:00:00Z', to represent a specific moment (e.g., midnight Pacific Daylight Time). Alternatively, restore the logic that dynamically calculates the target time in a specific timezone.
    severity: 0.7, confidence: 0.95

Did we get this right? 👍 / 👎 to inform future reviews.

@nikolovlazar nikolovlazar left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I do like the idea of redirecting to /years post-hackweek. Thanks for making these changes @jmanhart!

@nikolovlazar
nikolovlazar merged commit 0d93e40 into master Sep 8, 2025
7 checks passed
@nikolovlazar
nikolovlazar deleted the 2026/early-prep branch September 8, 2025 22:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants