# Dev Diary 83: Search, Import, OG Tags — The CMS Just Got Smarter **URL:** \ **Category:** Elements\ **Created:** [May 21, 2025, 7:02am UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678 "2025-05-21T07:02:31Z")\ **Posts on this page:** 20\ **Page:** 1
**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:** [May 21, 2025, 7:02am UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/1 "2025-05-21T07:02:31Z")
Hello again, We’ve been busy — and this week’s CMS update brings three powerful new features: **Search** , **Import** , and **Open Graph tag support**! 🚀 We’re especially excited about bringing **search** to the Elements CMS — it’s fast, flexible, and built right in. Make sure you watch the video to see it in action 🤯 While we’re moving quickly, the CMS isn’t quite ready to ship in Elements just yet. These early previews are your chance to follow along and help shape its development. [![](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/a/4/a485bda9ac08ab658a58af61c91fa06ad9e35f9f.jpeg "Elements CMS Just Got Smarter - Search, Import, OG Tags") ](https://www.youtube.com/watch?v=bA_lVo3uE58) * * * **Move to Elements Today** With version 1.0 just around the corner, the price of Elements will increase starting **June 1st**. If you’ve been thinking about building your site with Elements, now’s a great time to jump in. Visit [elementsapp.io](https://elementsapp.io/) to grab your license and lock in the current pricing! * * * **💬 Thanks for Your Feedback** These features came directly from your suggestions — so as always, we’d love to hear what you think so far. Your feedback truly makes all the difference 😊 Thanks again! See you soon, Ben & Team Realmac. ---
**Author:** ![MartWaring](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/martwaring/32/834_2.png) [@MartWaring](https://forums.realmacsoftware.com/u/MartWaring)\ **Post date:** [May 21, 2025, 8:07am UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/3 "2025-05-21T08:07:02Z")
I build sites for clients. Will there be additional per client charges to use the CMS? Will I be able to build Admin pages that the clients can use to update their own sites? If so can these be password protected? Will the CMS be able to support .webp images with different sizes for different device sizes? ---
**Author:** ![mrTablet](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/mrtablet/32/21819_2.png) [@mrTablet](https://forums.realmacsoftware.com/u/mrTablet)\ **Post date:** [May 21, 2025, 8:34am UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/4 "2025-05-21T08:34:50Z")
@ben This is starting to get really exciting 💪 I hope the launch isn’t too far away because the blog is the only thing I need now to be able to publish my new website 🙏 ---
**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:** [May 21, 2025, 8:58am UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/5 "2025-05-21T08:58:27Z")
> [@MartWaring](#): > > I build sites for clients. Will there be additional per client charges to use the CMS? The **core CMS components** will be included as part of the app — there is no per-client cost for the in-app CMS components, you can use them on as many sites as you like. Just a quick reminder — if you’re building and selling sites to clients, you’ll need to be on the **Pro plan**. > [@MartWaring](#): > > Will I be able to build Admin pages that the clients can use to update their own sites? If so can these be password protected? Yes — we do plan to release a set of **admin components** to enable this functionality. While the initial focus is on getting the core CMS components into the app, **online editing** and a **password-protected admin area** are absolutely on the roadmap. To be completely transparent: the **online editing components** will come with an **additional cost**. These are quite complex to build and maintain, and the added cost helps ensure we can properly support them long term. That said, the CMS itself is **100% open**. You (or another developer) can interact directly with the Markdown files behind the scenes. So there’s **no lock-in** — you can use your own editing interface or workflows if you prefer. > [@MartWaring](#): > > Will the CMS be able to support .webp images with different sizes for different device sizes? Yes — the system we’ve built is capable of supporting that. It will require some additional work on the frontend components to ensure everything behaves responsively and loads correctly, but **it’s definitely possible**. ---
**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:** [May 21, 2025, 8:58am UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/6 "2025-05-21T08:58:59Z")
glad you like what you’re seeing 😃 I’m doing my best to get these in your hands ASAP! 🙏 ---
**Author:** ![PMUK](https://avatars.discourse-cdn.com/v4/letter/p/7993a0/32.png) [@PMUK](https://forums.realmacsoftware.com/u/PMUK)\ **Post date:** [May 21, 2025, 9:45am UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/7 "2025-05-21T09:45:04Z")
This looks like it’s shaping up nicely. As someone who is only starting the “blog” route is it possible to have a template for markdown “posts” that I could start work on now? Whilst I appreciate it may change for final version at least I will be ahead of myself before we get there. TIA ---
**Author:** ![Pegasus](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/pegasus/32/25035_2.png) [@Pegasus](https://forums.realmacsoftware.com/u/Pegasus)\ **Post date:** [May 21, 2025, 10:12am UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/8 "2025-05-21T10:12:21Z")
to keep the motivation high. this is really very good work that you are doing with this CMS. what we can see in the developer diaries is really impressive and is going in the right direction … specific feedback on missing or improvable points - I can probably only give this once you have worked with it. i am ready for a small beta version ^^ 🤣 ---
**Author:** ![thominator](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/thominator/32/35233_2.png) [@thominator](https://forums.realmacsoftware.com/u/thominator)\ **Post date:** [May 21, 2025, 12:37pm UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/9 "2025-05-21T12:37:41Z")
As before: great job. This is shaping up to be everything I need for a variety of functions on my sites. Indeed, as someone else mentioned, CMS is now the gating element to my using [Elements](https://elementsapp.io/) in production, as I’ve satisfied myself by playing that the rest of the components work as I need them to. However, while watching today’s update, I did come up with a question. Let’s say I have that set of blog articles as you demonstrated today. How do I design a component so that it only shows articles published after {{date}}? Or before {{date}} for that matter? (I suspect you’re going to Twig something at me, so maybe I should go over there and start studying.) ---
**Author:** ![Flash](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@Flash](https://forums.realmacsoftware.com/u/Flash)\ **Post date:** [May 21, 2025, 1:00pm UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/10 "2025-05-21T13:00:33Z")
> [@ben](#): > > To be completely transparent: the **online editing components** will come with an **additional cost**. These are quite complex to build and maintain, and the added cost helps ensure we can properly support them long term. Is it safe to assume this applies for the ONLINE UI not the “built in UI,” am I correct these are two different solutions? ---
**Author:** ![Albertkinng](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/albertkinng/32/19017_2.png) [@Albertkinng](https://forums.realmacsoftware.com/u/Albertkinng)\ **Post date:** [May 21, 2025, 1:07pm UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/11 "2025-05-21T13:07:43Z")
I believe the key feature for [Elements](https://elementsapp.io/) will be its Content Management System (CMS). If they can refine the CMS to empower our clients to manage everything online through admin access, [Elements](https://elementsapp.io/) will truly dominate the market. ---
**Author:** ![logrunner](https://avatars.discourse-cdn.com/v4/letter/l/59ef9b/32.png) [@logrunner](https://forums.realmacsoftware.com/u/logrunner)\ **Post date:** [May 21, 2025, 1:20pm UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/12 "2025-05-21T13:20:45Z")
@ben - this continues to look amazing! 😀 With the “import” of Alloy posts, can they reside in a separate folder on the server and therefore be maintained by a separate online editor. I would like to use an external editor to edit / duplicate / add / delete markdown posts. I am probably misunderstanding, but it seemed in the video you were dragging those posts into [Elements](https://elementsapp.io/). So I am not sure how would maintain the individual posts externally? ---
**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:** [May 21, 2025, 1:30pm UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/13 "2025-05-21T13:30:53Z")
> [@PMUK](#): > > is it possible to have a template for markdown “posts” that I could start work on now Most likely it will be in the same, or very similar, format to what I’ve been using in the videos — no promises though, it could change. > [@thominator](#): > > How do I design a component so that it only shows articles published after {{date}}? Or before {{date}} for that matter? This feature is built in to the Collections component — you can filter the collection by date, status, tags, author, featured status. We will likely add more flexibility to this as we get closer to launch 🙂 ![CleanShot 2025-05-21 at 15.29.32@2x](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/8/3/83b294300de1086641c2ea718bd93089c958b7fb.png) ---
**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:** [May 21, 2025, 1:32pm UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/14 "2025-05-21T13:32:29Z")
> [@Flash](#): > > Is it safe to assume this applies for the ONLINE UI not the “built in UI,” am I correct these are two different solutions? The online editing components will come with an additional cost. Adding/Editing markdown files within Elements will come as part of the app. Hope that answers your question! ---
**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:** [May 21, 2025, 1:39pm UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/15 "2025-05-21T13:39:50Z")
> [@logrunner](#): > > With the “import” of Alloy posts, can they reside in a separate folder on the server and therefore be maintained by a separate online editor. I would like to use an external editor to edit / duplicate / add / delete markdown posts. Right now you cannot link the CMS Collection component to a “remote” folder — so you would need to import your alloy posts folder in to [Elements](https://elementsapp.io/) and link that to the Collection component. I’m not familiar with how Alloy worked, but if you’re able to you should point/install the Alloy editor to your newly imported posts folder in [Elements](https://elementsapp.io/) — if that makes sense? As I mentioned above, the CMS is completely open to all users and developers to use any editing tools they want to — we will even have an API available for you to fetch / display data in within your own components. ---
**Author:** ![logrunner](https://avatars.discourse-cdn.com/v4/letter/l/59ef9b/32.png) [@logrunner](https://forums.realmacsoftware.com/u/logrunner)\ **Post date:** [May 21, 2025, 1:43pm UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/16 "2025-05-21T13:43:16Z")
> [@ben](#): > > I’m not familiar with how Alloy worked, but if you’re able to you should point/install the Alloy editor to your newly imported posts folder in [Elements](https://elementsapp.io/) — if that makes sense? Ok, yes that does. How do you get the address of that folder to be able to access it from the external editor? Will it be via the API? ---
**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:** [May 21, 2025, 2:05pm UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/17 "2025-05-21T14:05:33Z")
> [@logrunner](#): > > How do you get the address of that folder to be able to access it from the external editor? Will it be via the API? I’ve not got that far yet, but internally the CMS API works like so: `cms()->collection('path/to/folder')` That returns a “Collection” instance, giving you access to whole bunch of handy functions on that collection of markdown files. Example: `cms()->collection("cms/posts")->getAll()` ---
**Author:** ![logrunner](https://avatars.discourse-cdn.com/v4/letter/l/59ef9b/32.png) [@logrunner](https://forums.realmacsoftware.com/u/logrunner)\ **Post date:** [May 21, 2025, 2:10pm UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/18 "2025-05-21T14:10:51Z")
Ah, OK - that seems good. 👍 I think I should be able to modify what I have already created to interface with this. Looking forward to trying it out. 🙂 ---
**Author:** ![Flash](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@Flash](https://forums.realmacsoftware.com/u/Flash)\ **Post date:** [May 21, 2025, 2:25pm UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/19 "2025-05-21T14:25:09Z")
> [@logrunner](#): > > I think I should be able to modify what I have already created to interface with this. It seems like a script could be written that simply searches for Alloy’s tags and edits them to Element’s tags. The addition of adding the collection for all Alloy posts is brilliant. It seems we can take advantage of this feature and apply a filter. In my mind this would convert Alloy posts over for legacy sake but then allow for all future posts to be made in the native [Elements](https://elementsapp.io/)/Twig format. Maybe I don’t know how complicated this “simple” change is… 😉 ---
**Author:** ![logrunner](https://avatars.discourse-cdn.com/v4/letter/l/59ef9b/32.png) [@logrunner](https://forums.realmacsoftware.com/u/logrunner)\ **Post date:** [May 21, 2025, 2:31pm UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/20 "2025-05-21T14:31:24Z")
My “external editor” already checks for an alloy post and converts it to my current own new format (as you suggest). I will modify it so that it now converts it to the new [Elements](https://elementsapp.io/) format which is what I will now use going forward. I will wait for the CMS to be made available before committing too much time to this, as it could still be in a state of flux. Yes, I agree that going forward, the markdown created by an external editor should be in “native” [Elements](https://elementsapp.io/) format (with maybe customised markdown metadata if required). ---
**Author:** ![PMUK](https://avatars.discourse-cdn.com/v4/letter/p/7993a0/32.png) [@PMUK](https://forums.realmacsoftware.com/u/PMUK)\ **Post date:** [May 21, 2025, 3:05pm UTC](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678/21 "2025-05-21T15:05:12Z")
@Ben thanks for response so the question should have been phrased do you have a template I can use please, I understand it might not be 100% for final version but at least its a start. THANKS [Next page](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678.md?page=2)