Big changes are happening inside Elements — and it starts with saying goodbye to the blog.
Yep, it’s gone. But don’t worry, it’s not a loss… it’s a serious upgrade.
We’re replacing the blog with something way more powerful: a full CMS, built right into Elements. It’s faster, more flexible, and ready for whatever you throw at it.
Watch the video below to see what I’ve been building these past couple of weeks
One of the biggest reasons we decided to scrap the blog and rebuild it as a full CMS was your feedback on the Blogging Preview video.
So we want your input again — check out the new CMS video preview, tell us what you love, what’s missing, and what you’d like to see next.
Your feedback directly shapes the future of Elements — and helps us build the best website builder. Period.
I don’t think we’re too far away from shipping this in Elements, however, we do have a few core features left to really nail down before we ship a first version.
That’s very nice and I’m looking forward to see this feature released soon.
I’ve a question regarding the long run of the CMS feature, though. We work a lot with a headless CMS and would love to see Elements get the ability to retrieve CMS data via API calls. Is that something, that is already on the roadmap?
It would be useful to be able to specify the sort order for the CMS collections: Ascending | Descending. Use case is to show events planned for the future.
Another thing would be to add the time to the post so that the publishing time can be set e.g. from midday on a particular date.
I also use the date and time to indicate when a planned event will take place. So it might be ‘2025-05-24-10-00-event-slug.md’
The blog I have been working on looks like it is being rapidly superseded by your efforts which in someways is a relief as I am sure it is going to be much better due to its full integration within Elements.
It seems that the Custom Fields that will allow an easier integration of Foundry Alloy Posts. It would be useful to have a translation facility to change say the Foundry Alloy metadata name for an image which is ‘topper’ to ‘image’ and likewise with the ‘topper-alt’ field etc. Of course this could be done by a one-off program to convert to the standard Elements metadata tags where appropriate.
I presume the Markdown files for the collections are stored in folders that will be readily accessible from outside of Elements in order to use an external editor.
I use Sitelok (by @vibralogix ) and have built logic into my CMS to permit or not markdown editing. For when you get round to doing the markdown content editor, it would be useful to be able to have some hooks in it for external integrations like Sitelok.
Anyway, great job - I am looking forward to trying it out.
Funny you should mention that because myself and Dan were just chatting about that yesterday. It’s not going to make it in to the 1.0 version, but it is definitely something we’d like to support — can’t promise if/when though
Yes, I forgot to mention that. Sort order will be available on all collections
This is already supported, so you can schedule a post to go live on at a certain time of the day.
We could look at an import tool so you could migrate other services, if the demand is there!
100%.
The CMS is based on standard markdown files — anyone/anything can easily integrate with this CMS by simply creating/deleting/updating the markdown files stored on your server.
We want to offer an API for the CMS — so anyone could build an admin area, for example — but I can’t say yet how that is going to work.
We need to develop the in-app experience first, and then we’ll get to the online editing and integrations with other services
This is going to have a huge impact on my sites. I can see so many use cases that are covered with this that will save me a lot of time and effort and make updating the data more straightforward.
The one thing I did not see but which might have been covered in the earlier blog videos, was what happens if I have images embedded in my markdown file. Especially, if they are images on my server that I’m linking, too.
Can you link to images in the markdown that are in the Elements resources?
One of my sites I just finished is going to be dramatically impacted by the addition of the CMS. I can’t wait to get my hands on this new feature.
So is it now gonna require your servers? Or will that just be for those using the Cloud Storage that is included with their licenses and not those whom self host?
Elements allows you to build sites and host them wherever you want - you’re not locked in to our servers in any way.
The same goes for these CMS components - build your site in Elements, add the CMS components/data as needed, and publish to your host. Nothing will be on our servers.
Hey @DaveMac, totally fair to ask for clarification, I know these things can sometimes get a little mixed in translation between posts, especially when there’s such fast ongoing development. I appreciate you keeping us on our toes!
By the way, just curious… are you using Elements yourself yet, or keeping an eye on things from the sidelines for now? Would love to hear what you think of it if you’ve had a chance to try it out.
It looks really impressive and flexible but with that comes some complexity. I’m really looking forward to learn and experiment with this but I’m already seeing a few use cases for me: building a changelog and of course, a real blog.
@ben For the sample you showed where you were using the CMS to setup a header, will this sort of data that uses a custom field always be setup in the front matter?
Would the body of the markdown file then be empty as the data would all be in the front matter, correct?
Reference to Elements resources continue within the videos - the resources can be warehoused items I assume?
In terms of an Elements sitemap(s) are such sitemaps available and can these be manually configured to incorporate reference to images, videos, pdf’s etc?
