What it is

Teleteks brings broadcast teletext — the Ceefax-era TV data service — back to life as a web service. The presentation is authentic teletext: numbered pages, a 40-column × 24-row monospace grid, mosaic block graphics, the bright-on-black palette, Fastext coloured links and a page header with a live clock. But every page is fed by live public data.

Try it: open the live demo, type a page number (100–500) on your keyboard or tap the Fastext coloured links at the bottom of each page. No login, no instructions needed.

The pages

Page Content Live source
P100 Index / home —
P200 Weather: Kendari, Makassar, Jakarta Open-Meteo (key-free)
P300 Earthquakes (Indonesia) BMKG public JSON (autogempa.json, gempaterkini.json)
P400 Markets: BTC, ETH, SOL Binance Vision public API
P500 Headlines Antara News RSS (CNN Indonesia as fallback)

How it works

A small Node.js fetcher polls the sources and writes broadcast.json; the static pages render it. If a source is down, the page keeps showing the last good data with a stale marker — a teletext page never crashes. Zero npm dependencies, no build step; Node.js standard library only.

How Kiro was used

This project was built spec-first with Kiro CLI (v3.3.0):

  • Steering: .kiro/steering/project.md in the repo root fixes the non-negotiables (authentic 40×24 grid, zero dependencies, graceful failure, honest timestamps).
  • Spec-driven workflow: .kiro/specs/teleteks/ holds the full spec — requirements.md (EARS-format requirements), design.md, and tasks.md (checked off only as each task was verified live).
  • Implementation sessions: Kiro CLI sessions in the repo authored the fetcher, the teletext renderer and the page layouts from the spec; every increment was proven against the real APIs before its task box was ticked.

How it differs from my other Kiroween entry (Radar)

Kiroween's rules allow multiple submissions that are unique and substantially different. Teleteks is my Resurrection entry; my other entry, Radar, is in Frankenstein:

  • Different category: Resurrection (reviving dead technology) vs Frankenstein (stitching APIs into a new creature).
  • Different product: Teleteks resurrects a medium — the teletext broadcast page itself is the product. Radar is a verification watchdog.
  • Different sources & pipeline: Teleteks flows fetcher → broadcast.json → teletext pages with no approval gate and no cross-verification — deliberately. Radar's whole design is detect → cross-verify → human approval → publish. The two share no code and no data sources except the Binance Vision public price endpoint family (Radar verifies prices against it; Teleteks displays prices from it).

Disclosure — new project

Teleteks is a new project, conceived and built during the Kiroween 2026 submission period. It uses no starter template and no pre-existing code of mine: the implementation is original, written for this hackathon on top of the Node.js standard library only (zero npm dependencies). Data comes from public, key-free sources (Open-Meteo, BMKG, Binance Vision, Antara RSS), each credited on its page.

Built With

  • antara-news-rss
  • binance-vision-api
  • bmkg-open-data
  • github
  • html/css/js
  • kiro
  • node.js-24
  • open-meteo-api
Share this project:

Updates