Dev.to WebDev 🛠 Dev 👁 0 📖 3 min read

For 61 Years, Kodak Ran on a 13-Month Calendar — So I Rebuilt It for 2027 in Vanilla JS

Between 1928 and 1989, one of the largest industrial companies on Earth ran its internal payroll, manufacturing schedules, and financial reporting on a 13-month × 28-day calendar. Eastman Kodak adopted Moses Cotsworth’s

Between 1928 and 1989, one of the largest industrial companies on Earth ran its internal payroll, manufacturing schedules, and financial reporting on a 13-month × 28-day calendar.

Eastman Kodak adopted Moses Cotsworth’s International Fixed Calendar (IFC) so every accounting period would have the exact same number of days (28), four complete weeks, and identical weekday-to-date mapping year after year. Every month started on the exact same weekday, every weekend hit the exact same columns, and monthly reporting never suffered from 28-vs-31-day Gregorian distortion.

To make space for the 13th month, Month 07: SOL sits right between June and July (June 18 – July 15), centered around the June Solstice. The 365th day (December 31) becomes Year Day, standing outside the seven-day week so the whole calendar stays symmetrical.

Ahead of 2027, I rebuilt this entire system as a zero-dependency web explorer, live birthday converter, and print-ready wall archive: SOL-2027 Explorer.

Why Vanilla JS + Zero Build Step Won Here

Calendar tools fail when they feel sluggish or require signup walls. The core math fits inside a single isomorphic zero-dependency script, so every interaction — birthday lookup, 365-day diagonal inspection, and instant 1080×1920 story-card export — runs locally in microseconds.

Mapping any 2027 Gregorian (month, day) onto the 13-month grid uses precomputed cumulative month lengths (CUMULATIVE_DAYS):

  1. Compute 1-based day-of-year doy in [1..365] (2027 is a common year starting Friday, Jan 1).
  2. Handle doy === 365 explicitly as Year Day (December 31, intercalary holiday).
  3. For 1 <= doy <= 364:
    • ifcMonthIndex = Math.floor((doy - 1) / 28) (0 = Jan … 6 = SOL … 12 = Dec)
    • ifcDay = ((doy - 1) % 28) + 1

Look at what happens visually when you plot all 365 days in a 13×28 matrix: the Gregorian 1st of every month marches cleanly down the matrix like a diagonal staircase, because every Gregorian 30- or 31-day month overflows the clean 28-day boundary by 2 or 3 cells:

  • July 1 actually becomes SOL 14
  • October 31 becomes OCT 24
  • December 25 becomes DEC 23

Even February 29 leaplings have a historical Cotsworth–Eastman rule supported directly in the converter: in leap years like 2028, Gregorian Feb 29 becomes Day 60 of 366 — fixed forever on IFC MARCH 4 (Wednesday) — while the IFC inserts its own intercalary Leap Day at JUNE 29, sitting outside the seven-day week right before SOL 1.

An Unexpected 2027 Astronomy Coincidence: Literally 13 New Moons

While computing UTC lunar phases and solar solstices/equinoxes for 2027 using Jean Meeus astronomical algorithms (cross-checked with PyEphem), I noticed a rare gift for 2027 calendar nerds:

2027 has exactly 13 astronomical New Moons (Jan 7 20:25 UTC through Dec 27 20:13 UTC) — meaning one New Moon lands inside every single one of the 13 IFC months.

  • 01 · January (Jan 1 – Jan 28): Jan 7 · 20:25 UTC
  • 02 · February (Jan 29 – Feb 25): Feb 6 · 15:57 UTC
  • 03 · March (Feb 26 – Mar 25): Mar 8 · 09:30 UTC
  • 04 · April (Mar 26 – Apr 22): Apr 6 · 23:52 UTC
  • 05 · May (Apr 23 – May 20): May 6 · 10:59 UTC
  • 06 · June (May 21 – Jun 17): Jun 4 · 19:41 UTC
  • 07 · SOL (Jun 18 – Jul 15): Jul 4 · 03:03 UTC (+ June Solstice on SOL 4)
  • 08 · July (Jul 16 – Aug 12): Aug 2 · 10:06 UTC
  • 09 · August (Aug 13 – Sep 9): Aug 31 · 17:42 UTC
  • 10 · September (Sep 10 – Oct 7): Sep 30 · 02:37 UTC
  • 11 · October (Oct 8 – Nov 4): Oct 29 · 13:37 UTC
  • 12 · November (Nov 5 – Dec 2): Nov 28 · 03:25 UTC
  • 13 · December (Dec 3 – Dec 30): Dec 27 · 20:13 UTC

Client-Side Swiss Typography & 1080×1920 Story Cards

Because the converter itself is the viral hook ("Wait, I was born on SOL 14?!"), I built a client-side HTML5 <canvas> exporter inside the web app. Click Download 1080×1920 Story Card after converting your birthday, and it renders a high-contrast Swiss Editorial or Midnight Celestial card straight to PNG on-device — zero server rendering, zero upload latency, zero watermarks.

And for people who want the system off-screen (especially ADHD visual planners, cycle-syncing trackers, and studio desks), every date cell pairs its large IFC numeral with its exact real-world Gregorian cross-date in the corner — available both as a $0+ Letter/A4 Starter PDF and printed physical editions via SOL-2027 Guides & Editions.

Try Your Date

Curious if anyone else has experimented with non-Gregorian scheduling or custom epoch tooling — drop what your birthday turns into below!

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.