Store & access data: Maps are being transferred from the Github base-map repo to the API. The API is in working condition with the ability to store map data, edit data through changesets, import GeoJSONs, access data through a RESTful interface, and export GeoJSON (though very slowly for now).
Edit data: Using any GIS editing application that can export to GeoJSON.
Render maps: Using TileMill, a desktop mapmaking app from MapBox, to style and render map tiles from API-exported GeoJSONs.
Access maps: Using a paid MapBox account to store and serve tile images.
View maps: The version 1 of Atlastory.js uses Leaflet and other custom code to display demo maps on a timeline at map.atlastory.com.
Collaboration: A combination of Google Groups (for mapping) Github issues (for development).
Documentation: Using markdown files on Github + API documentation.
Roadmap to Phase II
API — The API and database are fully functional, managing all map data and associated changesets for users, with full documentation and fast response times (see the more detailed api/TODO).
Tile-renderer — A single-use application that (1) takes inputs of map area, layers, and period to retrieve raw map data from the database; (2) renders it into vector-tiles; and (3) stores the tiles on a static server.
Tile-server — A server allowing users to request via URL map tiles in any format (vector, PNG, JPG). It takes both raw vector tiles from a static server and a map stylesheet and renders them realtime using Mapnik into finished tiles.