Have tried a number of times to publish, but the cms-folder is still empty on the server. Probably an easy fix of some sort?
Best regard,
Kjell Are
I assume you have to toggle the “visibility” of the cms folder and subfolders by clicking on the “eye”-icon in the correspindig list entry in the files column. So these folders will be exported/published and can be used by the projects CMS.
They currently have the same visibility status (eye with a diagonal strikethrough). One of them is uploaded, the other is not. I do not want them to be listed in the menu of my site. That is the background for these settings. Maybe we have to involve @ben in figuring out why one folder is uploaded, while the other is not.
Are the markdown pages in the folder set to publish (i.e. they don’t have a cloud icon with an x by them)?
If you export it locally, do they appear in the export?
And finally, if you share your project via Elements Cloud we can take a look.
Thank you @dan . I simply did a re-export of everything, and all the files are exported correctly.
However - I notice that while @ben is having his markdown images in the Resources-section of the UI, I have a separate sub-folder in my markdown-file folder with images in. Is this a no-go?
This may explain why I do not get my images (coverImage) shown?
Is there a way of specifying where the markdown files will get their images, or do I have to move them out to be Resources to make them appear?
All my markdown file images are now in /cms/posts/images/
UPDATE: or so it would seem. Elements did not upload the images (or drafts) folder within posts. This seems to be part of the struggle mentioned earlier. That Elements do not upload nested folders correctly.
You should not be storing images in the CMS folder, we don’t support that. Move them out to the Resources area/location.
Noted. This is just the way the conversion script exported my Wordpress data. Expect other WP users to face the same challenge.
There are a hundred+ images in that image folder inside posts. In @ben s demo, the images seem to be root level Resources. Storing them on the root level of Resources in my project could become messy even in the short future. Hope there soon will be a way of letting them reside inside a folder?
Best regards,
Kjell Are
Slight development here this morning. When I moved posts-images out into resources as advised by @dan , and guessing the image CMS address of the posts-page image to be:
/resources/cms_posts_images/{{item.coverImage}}
…these changes seems to have solved the issue of image-loading for me.
Storing posts-page images in a sub-folder, I do not have to clutter up my main resources folder with 323 images. 
Could this be a topic for an even more in-depth CMS video from @ben ?
Best regards,
Kjell Are