# Dev Diary 92 - CMS Progress Report

**URL:** <https://forums.realmacsoftware.com/t/dev-diary-92-cms-progress-report/49444>\
**Category:** Elements\
**Created:** [August 4, 2025, 11:23am UTC](https://forums.realmacsoftware.com/t/dev-diary-92-cms-progress-report/49444 "2025-08-04T11:23:52Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![logrunner](https://avatars.discourse-cdn.com/v4/letter/l/59ef9b/32.png) [@logrunner](https://forums.realmacsoftware.com/u/logrunner)\
**Post date:** [August 5, 2025, 11:37am UTC](https://forums.realmacsoftware.com/t/dev-diary-92-cms-progress-report/49444/22 "2025-08-05T11:37:19Z")

</div>

Using a URL, I think? I want to access it directly by folder, not URL.

---

<div class="post-metadata">

**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\
**Post date:** [August 5, 2025, 11:37am UTC](https://forums.realmacsoftware.com/t/dev-diary-92-cms-progress-report/49444/23 "2025-08-05T11:37:54Z")

</div>

> [@logrunner](#):
>
> I have lots of images that are externally added and therefore don’t exist in the Elements resources.

In this case, you can simply enter the full URL to the resource.

---

<div class="post-metadata">

**Author:** ![logrunner](https://avatars.discourse-cdn.com/v4/letter/l/59ef9b/32.png) [@logrunner](https://forums.realmacsoftware.com/u/logrunner)\
**Post date:** [August 5, 2025, 11:39am UTC](https://forums.realmacsoftware.com/t/dev-diary-92-cms-progress-report/49444/24 "2025-08-05T11:39:07Z")

</div>

> [@ben](#):
>
> In this case, you can simply enter the full URL to the resource.

So, I can’t specify a folder directly?

---

<div class="post-metadata">

**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\
**Post date:** [August 5, 2025, 11:43am UTC](https://forums.realmacsoftware.com/t/dev-diary-92-cms-progress-report/49444/25 "2025-08-05T11:43:41Z")

</div>

We won’t be support listing a folder of resources, however, you could manually add the resources as an array of URLs in the front matter of your markdown file.

Something like this

```auto
title: My Markdown file
resources:
  - image:
    - title: Picture 1
    - src: https://my-site.com/resources/picture.webp
  - image2:
    - title: Picture 2
    - src: https://my-site.com/resources/picture-2.webp

```

---

<div class="post-metadata">

**Author:** ![logrunner](https://avatars.discourse-cdn.com/v4/letter/l/59ef9b/32.png) [@logrunner](https://forums.realmacsoftware.com/u/logrunner)\
**Post date:** [August 5, 2025, 12:22pm UTC](https://forums.realmacsoftware.com/t/dev-diary-92-cms-progress-report/49444/26 "2025-08-05T12:22:49Z")

</div>

I probably need to wait until I can try out the beta.😀

At the moment, I just specify in the image in the markdown as:

```auto
image: picture.jpg

```

and the blog PHP code knows to go and pick it up from (for example):

```auto
data/images

```

I am using the following at the moment, which works well with my blog PHP code, to pick the image from my markdown:

 ![CleanShot 2025-08-05 at 13.18.43](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/d/9/d9d970528ca27e175008c53822bb67b0cfddd720.png)

My code substitutes {IMAGE} with the image in the markdown file, prefixed by the image folder.

---

<div class="post-metadata">

**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\
**Post date:** [August 5, 2025, 12:34pm UTC](https://forums.realmacsoftware.com/t/dev-diary-92-cms-progress-report/49444/27 "2025-08-05T12:34:52Z")

</div>

This is an advanced use-case, however, the CMS does support passing in a config. That config can specify where the resources are stored — this is how the CMS automatically prepends the correct relative path to the resources (I mention this in the latest CMS video).

So in theory, if you were to create your own component(s), you could setup the config to point towards a remote folder, something like this:

```auto
<?php

// include the required cms files

$options = [
    'resources' => [
        'path': 'http://my-domain.com/path/to/folder'
    ]
]

$cms = cms($options);
$items = $cms->collection('path/to/folder')->get()

```

This would automatically prepend `http://my-domain.com/path/to/folder` to all resources.

The above code isn’t going to work with the first beta release of the CMS, but this use-case is supported. I’ll need to do a couple of things, including documenting this, before you’ll be able to use it.

[Previous page](https://forums.realmacsoftware.com/t/dev-diary-92-cms-progress-report/49444.md?page=1)