Changelog – Skyenet.live

← Back to project

Version 1.1
Skyenet.live

Version 1.1 focuses on turning the SKYEnet homepage into a modern, readable hub for all public systems, backed by a single, reliable status layer. The release balances visual clarity for new visitors with operational visibility for ongoing maintenance.

## New

  • Central systems hub
  • Introduced a dedicated hub page that lists all public systems (Upload, MAYA, Discord Panel, Dino Game) in a cohesive layout.
  • Added direct navigation links to projects and contact from the top navigation.
  • Health endpoints
  • Created lightweight JSON health endpoints for Upload, MAYA, Discord web tools, and the Dino Game so their status can be queried without hitting full applications.
  • Exposed a health route on the Discord bot API that reports readiness, WebSocket status, and uptime.
  • Status aggregation
  • Implemented a single status API that queries all system health endpoints and returns a unified status payload.
  • Added short-lived caching in the aggregator to avoid hammering individual services while still providing near‑real‑time status.
  • Status by system panel
  • Added a “Status by system” section on the hub that shows each service with a clear online/degraded/offline indicator plus latency and HTTP response information.
  • Included the Discord bot in the status panel so connectivity issues are visible without exposing internal admin tools.

## Changed

  • Landing page design
  • Replaced the original “techy” gradient-heavy layout with a darker, more minimal design inspired by modern product dashboards.
  • Split the page into two main sections: a public systems grid and a status panel, minimizing distractions and focusing on clarity.
  • Shifted color usage so blue acts as an accent, not the dominant background, improving readability and reducing visual noise.
  • System cards
  • Enlarged cards and converted them into content‑first tiles with titles, subtitles, descriptive copy, and key bullet points.
  • Standardized actions into primary and secondary buttons (for opening a system and viewing its FAQ), making the grid feel consistent.
  • Ensured each card clearly explains what the system is for and how it fits into the wider SKYEnet ecosystem.
  • Status surfacing
  • Moved detailed status information into the lower “Status by system” area, keeping the main cards focused on product description and entry points.
  • Adjusted wording to distinguish between “Offline” and “Unreachable” so users can tell whether a system is actually down or just failing health checks.
  • Admin and changelog exposure
  • Removed admin‑only links from the public hub to avoid clutter and accidental exposure of internal tools.
  • Consolidated changelog responsibilities under the MAYA issue tracker, with the hub linking conceptually to that single source of truth.

## Improved

  • Responsiveness and layout
  • Tuned the grid to show two larger cards per row on desktop and a single column on smaller screens.
  • Ensured the hub shell and footer align cleanly on different viewport heights without leaving awkward empty bands.
  • Animation and motion
  • Softened or removed aggressive glow and pulse effects, with an option for status updates to happen quietly in place instead of constantly resetting to “checking”.
  • Copy and onboarding
  • Updated hub copy to better explain SKYEnet to first‑time visitors, including clearer descriptions of how Upload, MAYA, Discord Panel, and the Dino Game fit together.
  • Emphasized that MAYA is the canonical location for detailed changelogs and release history.

## Fixed

  • Clarified status behavior so services that are reachable but responding with errors are treated as “degraded” rather than strictly “offline”.
  • Resolved cases where systems would appear perpetually “checking” due to front‑end assumptions that no longer matched the new layout.
  • Ensured that the Discord bot’s status could be checked even when the web panel is unavailable, by relying on the internal health route instead of external signals.