roadmap

the general direction in which i'm aiming

implement the egg-any scry

hawk should do backups in the standard way

spine: a web-components library

users should be given more building blocks than basic html without needing to write javascript

put code for all ui elements in the namespace

users should be able to configure everything except the event loop

bring back %eyas-style folding text editors

more ways to view trees

write a few beginner-level interactive hoon tutorials

just the basics of how runes work

generate rss feeds from your namespace

hawk should be the best place to publish content for hooners

expose hawk namespace to +on-peek

hawk should be interoperable with the rest of urbit

cache GET response octs

improves scalability and speed

wiki files

for a more ergonomic knowledge management

port the http handling to use mast

less javascript, more reactive

port the runner logic to a runner that supports the Referrentially Transparent Global Namespace (lain, faye, ...)

allows dependencies between different ships

dynamic peek-time logic

hyper-fracalization overload

proper effects via card passing

code.page should return a (pair (map path card) load)

~2024.11.20 - change type of code.page to $mime and store protocol information there

allow images and audio directly in the namespace

~2024.11.20 - cache +ream-ed code

running on a local moon should feel snappy enough to daily drive

~2024.11.30 - write a good manual

hawk should teach hooners hawk

~2024.11.30 - put tooltips all over the UI

hawk should feel explorable

~2024.11.30 - reduce size of GET request

turn most of the core ui into web components

~2024.12.10 - implement system commands as $info cards

this unlocks a new level of programmability

~2024.12.17 - metadata inheritance and masking

controls have cares (x, y, z)