CMS ETL BBQ! Herein lie scripts I use to go from Day One exports to fully functional web blog and gemini capsule. FAQ 1. Are they good scripts? No. 2. Do they run without a bunch of external dependencies? Also no. 3. Should other people use this? Thrice no.
Go to file
Joe Mulvaney df49b45063 style fixes 2023-07-06 04:23:22 +00:00
assets style fixes 2023-07-06 04:23:22 +00:00
.gitignore ignore things 2023-07-01 14:37:37 +00:00
DEPENDENCIES text notes of dependencies 2023-07-01 22:49:34 +00:00
README update README 2023-07-03 15:24:00 +00:00
geminiIndexTemplate.js update index pages 2023-07-06 03:56:58 +00:00
geminiTagTemplate.js flesh out tags w their own templates 2023-07-06 03:42:11 +00:00
geminiTemplate.js flesh out tags w their own templates 2023-07-06 03:42:11 +00:00
htmlIndexTemplate.js update index pages 2023-07-06 03:56:58 +00:00
htmlTagTemplate.js flesh out tags w their own templates 2023-07-06 03:42:11 +00:00
htmlTemplate.js flesh out tags w their own templates 2023-07-06 03:42:11 +00:00
package-lock.json Let's keep track of this shit 🛤️ 2023-07-01 13:48:16 +00:00
package.json Let's keep track of this shit 🛤️ 2023-07-01 13:48:16 +00:00
processDayone.js update index pages 2023-07-06 03:56:58 +00:00

README

Given a set of entries from Day One on mac, that is uploaded as a zip file to ~/dayone/ and an empty dir ~/markdown:

$ node processDayone.js --inputZip ~/dayone/<zip> --root ~/markdown

This will:-
1. Run day-one-to-markdown script to get a set of directories each containing one front matter format markdown file
2. Load the frontmatter markdowns, and create gemtext and html
3. Process the images to be ready for distribution (strip EXIF, ensure rotation, smallify)

Note also:
* The DEPENDENCIES file discusses what's needed in the environment that the script is run
* The TODO file is my super-advanced issue tracking system
* There's no license yet