Shared assets directory
ozkriff opened this issue · 1 comments
@ozkriff: Given that Mun posts updates just about every month, might it be a good idea to move the logo into
staticand reuse it between posts, like we do for Amethyst?
Given that Mun posts updates just about every month, might it be a good idea to move the logo into static and reuse it between posts, like we do for Amethyst?
@17cupsofcoffee well, we're not that much consistent about that logo :)
$ find content static -name amethyst-logo.png content/posts/newsletter-013/amethyst-logo.png content/posts/newsletter-009/amethyst-logo.png content/posts/newsletter-004/amethyst-logo.png content/posts/newsletter-008/amethyst-logo.png content/posts/newsletter-010/amethyst-logo.png content/posts/newsletter-006/amethyst-logo.png static/amethyst-logo.png $ g grep amethyst-logo.png content/posts/newsletter-001/index.md: content/posts/newsletter-002/index.md: content/posts/newsletter-003/index.md: content/posts/newsletter-004/index.md: content/posts/newsletter-006/index.md:[][Amethyst] content/posts/newsletter-008/index.md:[][amethyst] content/posts/newsletter-009/index.md:[][amethyst] content/posts/newsletter-010/index.md:[][amethyst] content/posts/newsletter-013/index.md:and I'm still not sure how I feel about using static for reusing images - i don't like that it breaks normal markdown previews. Maybe we should try creating a special directory inside
contentand use relative paths there? something likeRelative paths up aren't that cool too, but it seems like a lesser evil to me.
(comments from #292)
Maybe we should try creating a special directory inside content and use relative paths there? something like
Relative paths up aren't that cool too, but it seems like a lesser evil to me.
Aaaand this breaks Zola builds.
Is there a way to have shared assets that will work both in normal MD previews and Zola builds?