Date formats, machine-readable time standards, and conversion references.
This section groups the topics that software, logistics, manufacturing, and operations teams search for when the question is about how time is encoded rather than what time it is right now.
Format pages by user intent
These pages are grouped by what the visitor is actually trying to do.
Look up a current format
- Julian Date
Current ordinal Julian code with conversion help and year charts.
- Unix Timestamp
Current epoch time with converter and system background.
- Day of the Year
Current ordinal day and year-progress references.
Understand the standard
- ISO 8601
Machine-readable date and time strings used in APIs, logs, and data exchange.
- Ordinal Date Format
How YYYY-DDD notation works and where it is actually used.
- Seconds vs Milliseconds
Identify timestamp units before they turn into conversion bugs.
Background and edge cases
- Year 2038 Problem
The signed 32-bit overflow issue that still matters in legacy systems.
- What Is Unix Time?
Editorial background on why epoch-based time became a standard.
- ISO 8601 Explained
Why standard date strings matter in software and operations.
What belongs in the formats section
Not every date-related page belongs here. This hub is specifically for standards, codes, and machine-oriented representations. That includes ordinal year-day notation, Unix epoch counters, ISO interchange formats, and the two different meanings of the phrase “Julian date.”
It does not include general calendar planning, business-day math, or global city clocks. Those belong in their own silos because the user’s job is different. Keeping those boundaries clear helps the site build depth without turning into a pile of overlapping pages.