I started my Small Book of CMS which will do what you want for the CMS. But I’ve got a lot of other stuff I’m working on (four major site redesigns, a new service, three books, and more).
@dan The problem is that all of us trying to use Elements for production work don’t have just one thing, we have a list. But the one thing that’s the biggest struggle is Typography, which isn’t good enough for what we need to do with it.
So my vote is this: pick the thing that’s not there or broken first and foremost. Those asking for “better forms” or “Tailwind 4” are asking for nuance when there are more important things that aren’t done yet or don’t work (like RSS).
I would like this to be revisited: Portal code insertion ordering?
I have had to modify the page template to get the order correct which isn’t something a normal user would want to do using associated DevPacks or Components.
The issue isn’t about being first but that of ordering; so that with two related components, one of them will always be before the other. If another component from another developer goes first, that doesn’t matter.
Thanks for all the feedback so far. It’s helping us prioritise features and fixes for the new year.
We know we still have a lot left to do (we store all requests in our bug tracker). We’ll get around to fixing ALL THE THINGS. Promise.
Our priority right now is finishing the Store to make it usable for third-parties. As soon as that’s done we’ll be back on polishing Elements. Good times ahead for sure ![]()
Keep the feedback coming: But Only post ONE thing. No replies, no +1’s, etc.
Cheers!
Resources → Open in (external app)
My one must have request would be right click open in / open with in Resources to make quick changes / edits to files in resources so we don’t have to take the file out, make changes, and then return to resources.
Highlite changed controls.
Sometimes it is hard to find, what i have changed and what is the default. Just bold the changed value and italic the default. or so…
A list of all dev diaries with time stamps for things that would be of use to someone still learning the ropes, all indexed and searchable.
Less complicated SEO. The third party tool I use is tedious. Once you make changes to the page, especially really large changes, none of that work will get updated in the SEO. So what I would ask for is an automatic way to work with that data. This really shouldn’t require a third party tool since it is so basic to all web design users.
In “All Components” having Markdown as part of the Content options - without having to use CMS.
Since I can only choose one. Text UNDO/REDO
CMS working,
With images, and nice layouts for display of content and entries.
Having a Manual for this whole Frontmatter/Twig/Yaml “thing”.
Or better still a set of premade examples one could import and that work.
Optional would be to have the CMS with a site login, to be updated online.. but that is for later.
Your write “versioning control with github”? Has anyone made that work.
I for my part cannot even make images show up on my blogs.
Have you tried weglot.com ?
I absolutely cannot change to elements until it is able to read data from a Google sheet like live data and also to write to a Google sheet as per the formsnap stack. My website will not function without this.
More setting options in the component Image Slider like the stack Shutter from Elixer Graphics.
Adding my own themes within Elements. Start from an existing one, copy, modify, save as… with my own name and icon.
- The CMS works. I’ve got one site using it that’s public facing. Some of the fine details some of us might want added or fixed (I’m looking at you RSS) are still to come, but you can deploy today with it.
- Images and layouts work with the current CMS. Images is pretty easy once you know the “secrets”. Laying it out can get tricky and is something I’m still coming to grips with.
- A “manual” (from me) is coming. Not just for YAML, but for the entire CMS.
- You might not have noticed the CMS bits in the Essentials section of the Templates panel (part of Elements issues are what I mentioned from the get go: naming; you have to come to grips with Realmac’s naming to understand things).
So, to make an image work in your blog, you need the image somewhere. The best place is to create an images folder (all lowercase for anything CMS, no spaces, will get you a long way) in the Resources section of your Resources panel (see what I mean about naming? This is a bit like watching Apple TV in the Apple TV app on an Apple TV). Then, in your Markdown file you need:

There’s much more that can be done (such as auto heading images, multiple images, etc.) but that should get you started.
Just adding a tidbit to adding images in CMS…
After all of what he said to do (which you have to do)
RENDER it in Safari!!!
Didn’t know this…
Thought the “?” meant it didn’t work… but in reality it was working…
Table component
It would be the ability to support multiple languages on a single site, automatically detected from browser preferences.
I do not want to create three sites with endings of /eng, /fr,/de, etc.
That to me would be a game changer!
I was going to ask for this exact samething. This would be a HUGE improvement.