Separating Markdown contents and contentlayer renderer

[nbnsresta]

This is about separating the markdown files and Contentlayer implementation onto separate repos, so that the content writers may not have to worry about messing code up by any chance. I am open for any kind of suggestions at hand.
I understand that all of this is in Git and every thing should go though a review process. The idea itself might look like a footgun but please bear with me. As a thought of safekeeping, and not to let my intrusive thoughts take over, I am trying to see over how this could be implemented.

So far my idea regarding this has been as, contents and core would be their own repositories. The core would pull the latest of contents and run the deploy pipeline when either of them have new changes in main. Now, if the contents were self-sufficient this would be it.
The challenge that I am facing is when they have assets like images. Since this is Nextjs, the images should be put in the public directory to be accessible via markdown. And it defeats the purpose if the images have to be placed manually.

The concern for this discussion is if it is possible to locate the images within the contents repo and visualize the result there while in editor(vscode), as well as the same path working after the deployment.

[nbnsresta]

Maybe an image provider route from pages which serves the content images somehow.

Thank you for any course of suggestion.

[nbnsresta]

For anyone passing by, I successfully separated the contents from core repo.

The pipeline file resides in the core repo while the contents repo only contain the docs/ and images/ with a README to help get started. For viewability in editor, the images should be placed only in the images/ folder and be referenced as /images/<image_name>. This approach works in VSCode but Intellij requires it to be referenced without the "/" at the beginning.
If Intellij is a dependency, we can still configure the image component to append "/" at the beginning of href in the core repo (if it doesn't exist).

The pipeline trigger for when contents is updated is still manual, however I have parameterized the build so that we can type the branch name of the contents repo to be deployed. Automated builds take develop as source. During build, the core repo clones the contents and moves the docs/ to contents/, while the images/ is moved to public/.

Now the content writers don't need to depend on the knowledge of node ecosystem or commands to take it forward. And after the push, they can manually trigger build and see how it looks in live.