currently a new map has to use a google-internal tool (beck-map, hence the beck/ folder, named after harry beck of TfL London Underground fame).
We should instead be able to build the map directly from an index and set of docs files. this would require:
- use of a graph language, eg dot
- the corresponding graph markup (edges, rows, columns)
- a flexible enough UI to provide click-through or popup detail pages for docs/ content
- future work:
- overlays: a subgraph, to review a single tool or common bundle of capabilities
- inverse maps: given a technology, what capabilities am i getting?
- "paths" and/or a "checklist": provide a way for teams to record their current status, their goal, and map their intended course
the resulting page should continue to be standalone site, hostable anywhere that can run jekyll
currently a new map has to use a google-internal tool (beck-map, hence the beck/ folder, named after harry beck of TfL London Underground fame).
We should instead be able to build the map directly from an index and set of docs files. this would require:
the resulting page should continue to be standalone site, hostable anywhere that can run jekyll