ok the online editor when I setup detected no folders in the markdown folder only the one markdown, as soon I went to make a change it has added all these extra files, these then create extra data on the web page I am using item with custom code. When I edit the md file in my ftp app this did not happen, prior to using the online editor
Make sure you have selected just the folder containing your markdown files.
for example; in this project I’d selected the “posts” folder when I setup the online editor.
Hopefully that will help you get back up and running, let me know if that’s not the issue and we can help dig in further with you 
(a screenshot of the issue would be great).
forgot the video
@dan perhaps it’s my code or the online editor cannot use custom components?
I don’t know the exact issues, but setup wise, you’d probably want each product to be a separate .md file. Editing an array on the sidebar is going to be a bit of a pain in the bum.
Can you post the project file here? without it, it’s hard to see what’s going on.
I created a custom component that is fine until CMS online is used to edit the file
Why is it is ok as a custom component that works, even when I edit vis ftp, but as soon as s cms online sees the md file it tries to add to the array
Sure, but is the contents (and frontmatter) of your markdown file valid?
I assume so as it just is an array being accessed by using twig I the custom component, works with no issues until the cms online line editor sees it
Pause the video and see the markdown file content as that is the only markdown file I use
I am looping through that markdown single file
Unless you share the project I can’t really help any further, it’s like trying to fix a car without the owner letting you see the engine!
No probs I can easily edit via ftp, add more cards and edit each card without the online editor just by using the single md file,
I will not use the online editor for this instance, no issues
It’s just a copy paste inside and change the data as I require
You marked this as a solution but it’s not really a solution because from your video there is obviously something weird going on with your custom component and the online editor, but without your project file, we can’t really find a real solution… 
Hi @upssjw
I’ve taken a look at this one more closely, and the issue is with the way you’re setting sub-array properties (specifically the product.specs sub array).
The online editor’s YAML parser is intentionally minimal and only handles one level of nesting, in block style. It doesn’t understand:
- A list inside a list item (e.g.
specs:under each product) - Inline-flow maps like
- {label: "Laces", value: "Red"}
If you open a file with that structure in the editor and save it, the front matter will be rewritten and the nested specs arrays will be lost (each - {…} line gets misread as a brand-new top-level product).
Suggested approach: one file per product
Rather than packing every product into a single file’s front matter, give each product its own markdown file — e.g. cms/products/autumn-boot.md, cms/products/summer-boot.md, cms/products/winter-boot.md. The front matter for each then stays flat and editor-safe:
---
title: "Autumn Boot"
price: "ÂŁ39.99"
image: "/resources/3.jpg"
specs:
- label: "Laces"
value: "Red"
price: "ÂŁ5.00"
- label: "Size"
value: "UK8, UK9, UK10"
- label: "Grip"
value: "Heavy"
- label: "Return"
value: "Free"
price: "ÂŁ0.00"
---
That’s the deepest structure the editor round-trips cleanly: a top-level key whose value is a list of flat maps. You can then loop over the products/ folder in your template to render the listing, and each product becomes individually editable in the WYSIWYG editor
@ben I to came to that conclusion and could do it that way, except I would like to do it this way as I have been testing with more data and code, I have code in the frontmatter I pass into the custom component. My custom component works this way, the custom component is only for me for a specific project, the site I am testing is concept along with multiple different formats I have tried before I fix it on one
The online editor was just me seeing if it worked, no issues if it didn’t
Thats why I said above it was solved on my side, probably shouldn’t have posted
I am now using vscode with some of the extensions for the md file and can easily just upload to the server along with images, and download to sync with my Elements project, as long as I remember the right order to copy
I have to add my random part to highlight a different product each load with links and associated info + other things I am working with, I have search function built into the custom component, I have it hidden at the moment
https://forums.realmacsoftware.com/t/random-cms-custom-component/56422/3?u=upssjw
https://forums.realmacsoftware.com/t/random-cms-custom-component/56422/9?u=upssjw
And this part different background colours for each card
I’m not sure whether it’s the same issue, but I’ve noticed a similar problem in one of my projects.
When I use the CMS Load More component and click it, I do get additional results — but they are empty. See screenshot:
However, when I use the CMS Pagination component instead, the results are displayed normally.
See the video for reference.
In the online editor does it add the extra items as in my example, I now understand the online editor can old work with level of the array, my additional items are the from the array it cannot work with, unless I split across md files which reduces my options.
Is your md frontmatter more complicated than the basics of examples
Let’s put it this way: I suspect Ben isn’t exactly thrilled with the way I structure my frontmatter.
Probably too much extra stuff … emojis and things like that — although I’ve stopped using emojis by now.
A typical frontmatter I use looks something like this, although some of them are even more extreme. That said, they do work so far. I’m grateful to him for making it possible to use this kind of frontmatter structure in CMS 2.0.
---
title: "IKEA - Hamburg"
# ======================================================
# BASIC PAGE SETTINGS
# ======================================================
site:
slug: "hamburg"
path: "store/ikea/hamburg"
url: "https://www.mydomain.com"
category:
name: "Möbelhäuser"
path: "moebelhaeuser"
# ======================================================
# FILIALDATEN
# ======================================================
moebelhaus:
name: "IKEA - Hamburg"
brand:
name: "IKEA"
path: "moebelhaeuser/ikea"
type: "Möbelhaus"
# ======================================================
# ADRESSE
# ======================================================
address:
street: ""
zusatz: ""
postcode: ""
city:
name: "IKEA"
stadtteil: ""
path: "hamburg/hamburg"
bundesland:
name: "Hamburg"
path: "Hamburg"
region: ""
country: "Deutschland"
# ======================================================
# KONTAKT
# ======================================================
contact:
phone: "+49 (0)"
fax: ""
email: ""
# ======================================================
# OEFFNUNGSZEITEN
# ======================================================
opening_hours:
monday: "10.00 bis 19.00 Uhr"
tuesday: "10.00 bis 19.00 Uhr"
wednesday: "10.00 bis 19.00 Uhr"
thursday: "10.00 bis 19.00 Uhr"
friday: "10.00 bis 19.00 Uhr"
saturday: "10.00 bis 19.00 Uhr"
sunday: "13.00 bis 18.00 Uhr"
# ======================================================
# 🏷️ CATEGORIES & TAGS
# ======================================================
tags: [ikea, hamburg,]
# ======================================================
# 🖼️ IMAGE / MEDIEN
# ======================================================
media:
header:
src: "/0300-stores/0200-moebelmaerkte/ikea/header/800x450/roller-001.webp"
alt: "IKEA"
copyright: ""
type: "remote"
logo:
200x200:
src: "/0300-stores/0200-moebelmaerkte/ikea/logo/200x200/ikea.webp"
300x300:
src: "/0300-stores/0200-moebelmaerkte/ikea/logo/300x300/ikea.webp"
240x120:
src: "/0300-stores/0200-moebelmaerkte/ikea/logo/240x120/ikea.webp"
300x250:
src: "/0300-stores/0200-moebelmaerkte/ikea/logo/300x250/ikea.webp"
alt: "IKEA Logo"
type: "remote"
---
Looks really good, I like detailed/complicated
My understanding the CMS part of Elements is not just a blog it is CMS
How the frontmatter is setup should be to suit the need to display the data
there are probably limitations with online
every custom component I have created so far works no problem when I publish
So far I am really happy I can do this with Elements great stuff​
just getting round to look in to this issue you’re having with the Load More, I can’t replicate it on any of the CMS sites I have locally (even tried on a couple of the sites you’ve previously shared with me).
Could you send me a project where the Load More doesn’t work?
its out now - via upload to support