the readme says:

Blog content

Blog articles go in ./content/posts and should have a title, date,
and author.

If you have images to associate with a blog post, add them to content/images. Then, to refer to them in a way that will allow them to be built as siblings of the blog post html, prefix their path with {attach}, like so:

![]({attach}/images/earthrise.png)

If you have files like Asciinema, add those to content/static and refer to them as

{attach}/static/file

this doesn't work for us.

• the blog itself is a separate set of documents, that live at github.com/ipfs/blog and will remain separate.
• each blog entry is its own directory, with an index.md and all the content in that directory, not another. this makes it easy to move, alter, and back up entire blog entries. this is true for BOTH source and product files (source markdown + assets, or product html + assets)

To fixing this disparity, we can approach it two ways:

• continue keeping the blog "in the website", which would involve transforming the blog source materials (directory with markdown and assets) into what the website expects.
• or keep the blog separate, and port over the styling and header to the github.com/ipfs/blog project. (ideally without having to change it to pelican)

Aside, I havent delved much into pelican, does it let us:

• keep content together -- i.e. each blog entry as a self-contained directory, both in source files AND in output files.
• use relative links easily (i think this worked, given the site works :) but i havent confirmed)

?