Selected work / Ethereum / learning
Ethereum Roadmap Atlas
A partial, source-linked roadmap atlas with goals, dependencies, timelines and confidence labels.
The idea
Keep uncertainty attached to the roadmap.
This selection keeps the atlas opening, the timeline and the sources. The stills document the public interface as captured in September 2026.
The captured dataset is partial. Roadmap signals and speculative items are not commitments or a statement of current Ethereum plans.
Three selected moments
A closer look.
Move through the selected stills.
01 / Selected moment
The atlas opening
The atlas opening from the captured Ethereum Roadmap Atlas interface.
Open full image ↗
02 / Selected moment
The timeline
The timeline from the captured Ethereum Roadmap Atlas interface.
Open full image ↗
03 / Selected moment
The sources
The sources from the captured Ethereum Roadmap Atlas interface.
Open full image ↗Make something of your own
Build your own.
Take the idea into Codex and adapt it to your own subject, sources and audience.
Reconstructed recipe · Not the original prompts
An end-to-end recreation has not been tested.
01BriefDefine the experience
Build a new interpretation of Ethereum Roadmap Atlas: A partial, source-linked roadmap atlas with goals, dependencies, timelines and confidence labels. Read the repository instructions and preserve existing work first. Reconstruct the idea from this selection; do not promise an exact recreation. Start with one complete useful flow.
02IngredientsPrepare sources and assets
Start from the Fishbiscuit/strawmap-atlas repository when available. Preserve canonical node IDs, typed relationships, source citations, confidence and maturity as separate fields.
03InteractionBuild the core flow
Build a readable atlas and timeline over the same versioned model, with source detail and accessible search. Make graph and 3D views optional and lazy-loaded. Validate references and avoid loading the full graph before a visitor asks for it.
04Verify & preserveLeave a working handoff
Check the real production route, keyboard operation, mobile layout, reduced motion, asset loading and failure states. Record what passed and what remains untested. Leave source, lockfiles, setup instructions, data provenance and unique selected assets in a compact package. Exclude secrets, dependencies and caches. Label reconstructed prompts honestly; a local package is not a NAS backup.