Assets key for Frontmatter CMS

[louiss0]

I have decided to talk about this as a feature idea because. I didn't think of the problem as an issue as in bug. But what I'm going to talk about is a restriction. As of today you are only allowed to use one assets folder. This is not good for people like me who use mono-repos.

Right now this is all I can do. If can could specify multiple files they would look like this.

This is what I want to do. The benefit of this is that the key could be the name of the place where each asset is displayed. The value is the folder to use. This means that pictures and where they come from can be specified in a mono-repo. even outside of a mono-repo developers can organize where each set of images are in a folder.

[estruyf]

Thank you for opening this discussion @louiss0. Think this would indeed be great for people that split their assets from the website.

What is the URL of the images you are inserting in your articles?

[estruyf]

I get you to have two different image folders in two project folders (blog and portfolio). What I am still missing is, do you have two Astro sites. One for blog and one for portfolio?

Might be helpful to show a screenshot of your monorepo tree view.

[louiss0]

I get you to have two different image folders in two project folders (blog and portfolio). What I am still missing is, do you have two Astro sites. One for blog and one for portfolio?

Might be helpful to show a screenshot of your monorepo tree view.

Here is a snapshot of my repo

As you should see the apps folder is where all of my apps are. The blog and the portfolio folder live there.

[louiss0]

It seems like you don't understand what is going on. I have an Nx mono-repo where I use the a folder called the apps folder to hold my projects. So far both of them are blog and portfolio. The apps folder lives in the root. The other folders don't matter in this conversation. I plan on storing the pictures for my blog posts inside of the blog folder. The ones for my portfolio will live in the portfolio folder.

The way Astro woks is that I need to have a /public folder for unbundled assets. It will not process them at all. I think there is a way to override this but I won't do it. Even if I could do that I'd have to tell Astro to bundle different assets for different projects. Sooner or later Astro will add another special directory called assets this one has to live in the src directory and must be referenced so that images are bundled. If you create images from directory then use them the images will be built and optimized.

[estruyf]

I get you to have two different image folders in two project folders (blog and portfolio). What I am still missing is, do you have two Astro sites. One for blog and one for portfolio?

So the blog and portfolio are two separate websites. I got it now.

As it was not evident initially, I needed to understand this. It could have been that you split up these images into two folders as you wanted to push these to an image service like Cloudinary.

Will have to think on how Front Matter will be able to support this in a convenient way. Your suggestion is a good one; also still thinking about bringing it to the page folder or content type level, as that is closer to the content configuration itself. It might be that the page folder makes more sense.

[estruyf]

Created an issue to work on it: #548