Browser-only utilities for Canto journals. The first tool converts a supported
flat Journey export ZIP to an unencrypted,
import-ready .canto.zip archive.
Everything runs locally in the browser: journal files are never uploaded.
Journey text, dates, tags, valid coordinates, images, videos, and other files
are retained where Canto supports them. Journey-only fields are recorded in an
Imported from Journey Canto comment. The result view shows warnings and can
download a separate local JSON audit report.
The initial release supports the verified flat export layout: one Journey JSON record per entry with matching media files. Corrupt ZIPs and unknown layouts are rejected. Individual malformed entry records are retained as visible Canto warning entries containing their raw source rather than silently discarded.
npm install
npm run dev
npm test
npm run buildUse your own Journey export and keep it outside the repository. If Journey provided an extracted export directory, make a temporary ZIP before uploading:
cd /path/to/journey-export
zip -r /tmp/journey-export.zip .Upload the ZIP to the local site, confirm the staged counts and cancellation
control work, then download/import the generated .canto.zip in Canto. Remove
the temporary ZIP afterwards. The project ignores common Journey inputs and
generated conversion artifacts as a safeguard.
Ideas for new tools and converters are welcome. Please read CONTRIBUTING.md and open an issue with the source-format and Canto-mapping details before starting substantial work.
.github/workflows/deploy-pages.yml builds and deploys the static site on each
push to main. In the repository settings, set GitHub Pages' source to
GitHub Actions once.