Refactor image handling and add support for saving images as base64 s…

[NoamMuallem]

As mentioned in the #8, to really use notion as a CMS, one needs to save the encoded images to the data-store.json to get all the benefits of a statically generated website.

[netlify]

👷 Deploy request for travel-tiger-x-daphne pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	cccfba2

[NoamMuallem]

@NotWoods let me know if you have any preference as to where to place the new function, I am currently struggling with the typing a little bit...

[NotWoods]

Thank you for the PR! Reviews are going to be a bit slow right now as I'm on bereavement leave but I wanted to give some early feedback.

I like the idea of being able to store the images, but I'm interested in using Astro's image APIs rather than just converting to base64. Base64 is pretty inefficient and will hurt the end-user experience as it will pages take much longer to download.

Astro MDX uses a rehype parser to convert <img> tags into Astro Image components and I'd like to explore something similar here. It might even be possible to just import the existing rehype parser.

[NoamMuallem]

cool idea, like using the getImage function and store the optimized image?
About the parser, and the astro Image components, for me (and I think, for the package), it is out of scope because it effects the rendering of the stored content, and not the stored content itself...

[NotWoods]

Yeah, I'm thinking of the getImage function. Astro loaders do handle rendering so I don't feel that it's out of scope but you might be able to get the same effect working with Notion blocks.