Timeline

Timelines show sequence without turning updates into a stack of cards. Use grouped entries when several changes share a date or roadmap phase, and keep descriptions concise enough to scan.

Recent updates

Use chronological labels for changelogs, release histories, and editorial update feeds. A group can contain one or several related entries.

What's new

View all updates

1. July 20–24, 2026

   Compare deployment engines with measured results

   Review latency, memory, and flash measurements together before selecting a deployment path.

   Copy configuration examples directly from guides

   Code blocks now keep the filename, language, and relevant lines visible.

2. July 13–17, 2026

   Follow the HELIA workflow from model to device

   A clearer journey connects model preparation, runtime selection, profiling, and deployment.

Roadmap

Use phase labels instead of dates when timing is directional. Accent color may clarify state, but the content and sequence should remain primary.

1. Now
   In progress

   Reusable developer-site foundations

   Polish navigation, code, data display, tutorial, and editorial components.

2. Next
   Planned

   Ecosystem and customer-journey pages

   Explain product relationships and guide developers toward the right runtime.

   Planned

   SDK and native symbol reference

   Document C and C++ APIs, configuration, compatibility, and command-line workflows.

3. Later
   Exploring

   Interactive notebook examples

   Evaluate browser-hosted examples when WebAssembly package compatibility is sufficient.

Usage guidance

• Prefer a timeline when sequence or recency is part of the meaning.
• Group related changes under one date or phase rather than repeating labels.
• Keep the rail visually subordinate to titles and descriptions.
• Link only entries that have a meaningful destination.
• On small screens, place the date or phase above its entries.