Custom loader markdown clarity

[paul-sachs]

The docs read to me as if whether you're using a custom loader (inline or otherwise), there's a way to access the rendered content but this is only the case with the glob or file loaders. Currently, custom loaders need a lot more additional logic in order to leverage the markdown processor to move local files externally and match behaviour.

Either we should modify docs to make that obvious or we should add some utilities to the loader to make grabbing the markdown processor much easier.

[paul-sachs]

I suspect part of the confusion is due to expanding content collections to include external sources. This line here says that it's not built into anything but content collections, but now that content collections seem to include custom loaders, maybe just a little more clarity there would be sufficient?

[sarah11918]

Thanks @paul-sachs , I think you're right about this!

Maybe we could update the sentence to just remove that altogether?

Astro does not include built-in support for remote Markdown.

By the way, there has been discussion about publicly exposing Astro's Markdown parser (and, I think someone who found and was able to use it anyway? 😄 ) as it's a popular request. You can see the proposal here: withastro/roadmap#1094 So, I hope one day this sentence will be true, but I fear that right now it's not!

Do you think removing that reference to content collections would be a marginal improvement here

[paul-sachs]

I think so. Definitely looking forward to the proposal making progress but for now, adjusting the docs should prevent this confusion for anyone else looking to do exactly this.

[sarah11918]

Sounds good @paul-sachs . Would you like to make a PR to that docs page and simply remove the linked part? If not, I can take care of it!

[paul-sachs]

I can manage that, no worries

[paul-sachs]

Created: #12335