Replies: 2 comments 4 replies
-
|
I agree & this would be good for integrations as well to be able to separate the content away from source code. Eg. In my case I'm planning to integrate Stackbit later to the project that mentions
It would be great to understand what limits Astro to do this currently & how this relates to their Image optimization etc. I'm interested to optimize the images in md files as well, which currently is out of the box possible only in .mdx files |
Beta Was this translation helpful? Give feedback.
-
|
Even for MDX this feels like a hack to me. Naturally Astro should resolve this. IDK why astro doesn't support this by default |
Beta Was this translation helpful? Give feedback.
-
|
I suspect this will be supported in the future when the project matures. Thanks for the integration. However, I'm going with the Astro official Image integration as it handles optimization for images and works out of the box. I will just put my content folder in the src/ folder and use mdx files instead of md. |
Beta Was this translation helpful? Give feedback.
-
|
Optimizing images with Astro is something different from what we achieved here. Tbh in Gridsome this was fully automatic(content, images in markdown etc) all were optimized(its even better than Astro images, gridsome also blurs images) Lets see if we can achieve this also, its like out of scope of the integration |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, responsive optimized images is my primary concern. Having the content folder outside src is secondary as I believe eg. Stackbit doesn't mind where the content dir lives. And I believe astro Image will get better over time. No idea how it compares to next image currently. |
Beta Was this translation helpful? Give feedback.
-
|
It's now possible https://docs.astro.build/en/guides/images/#images-in-markdown-files |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Problem:
When using Astro for a content site(blog) Markdown is often used. Currently, Astro cannot resolve files outside the
publicorassetsdirectories.I don't want to keep my content inside the
srcfolder, app and content are two separate things.Here is how you can usually organize content clean and separate from the app source code.
Solution
When you find a relative resource file referenced in
.mdor.mdx, Astro should automatically detect this and serve the resource to the client without additional steps. This is the most convenient way to handle it. (maybe introduce a new config param to disable this behaviour).On production build, Astro should treat these resources, as usual
Note: Hugo, Gridsome, Gatsby supports this out of the box
Beta Was this translation helpful? Give feedback.
All reactions