Streamline the publishing of the Filecoin Dev Digest

[BigLep]

Problem(s) to solve

Creating the bi-weekly Filecoin Dev Digest takes too much human time. We want this to be reduced to 5 minutes or less.

The current process is:

1. Copy content from a google doc tab for the biweekly Filecoin Stack Leads meeting.
2. Convert it to markdown
3. Add a table of contents
4. Strip out any lines that have a 🔒 symbol since those aren't intended to be public
5. Ensure the images in the status update are publicly accessible
6. Ensure images aren't too large
7. Post a github Gist to have others spot check
8. Post it as a new github discussion under discussion https://github.com/filecoin-project/community/discussions/categories/filecoin-dev-digest

This process is usually done by copying the content to an LLM (e.g., Claude) and asking it to do these modification. The manual pain comes from having to copy paste in the content in chunks and to copy/paste in the prompts for the modifications that want done.

We're also relying on images that are stored in Google's domain: https://lh7-rt.googleusercontent.com

Things that don't work out of the box

Google Doc's "download as markdown"

The problem with the markdown that is exported is that all the images are turned into data URIs and those don't render well with GitHub gists.

Potential Solutions

Use Notion

Notion accepts copy/paste from Google Docs well without mangling the formatting and it allows adding a table of contents easily.

Scripting to download as markdown and as a web page .html .zipped

Downloading a good doc tab as a zipped web page causes all the images to be included as separate files. Those images could be uploaded to GitHub and then the markdown inline images could be ocnverted to links to the github hosted images.

Scripting could also add the table of contents and strip out the 🔒 lines.

It would be ideal if this was a hosted webapp where you could

1. just point it at a google doc tab link
   2.it would get permission to use your coredentials to access that file
2. it would download the markdown and zipped html
3. upload the images to GitHub
4. modify the markdown accordingly
   1. use the github hosted images
   2. remove 🔒 lines
   3. add table of contents
5. create the github gist

Doing it as a locally run npm project or as a pythong cli would also work, but the ideal would be for a non technical person to be able to do this.

Sample document(s) for testing

https://docs.google.com/document/d/1DnVwQwDirIIGuKBr0zJEXFl0obg6vohbEUHrUV3JWHU/edit

• Note that it has two tabs simulating that the document will have a new tab for each meeting occurence and we should grab the latest one.

https://www.notion.so/filecoindev/Notion-Test-of-Copy-Pasting-in-Example-Filecoin-Stack-Leads-Document-for-testing-Filecoin-Dev-Digest-1d2dc41950c1800b94dedc608e4f489c?pvs=4

• Example of copy/pasting that document into Notion

[wolfduan]

github