# Little things missing in CMS V2

**URL:** <https://forums.realmacsoftware.com/t/little-things-missing-in-cms-v2/56413>\
**Category:** Elements CMS\
**Created:** [May 29, 2026, 4:17pm UTC](https://forums.realmacsoftware.com/t/little-things-missing-in-cms-v2/56413 "2026-05-29T16:17:01Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![MichaelDroste](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/michaeldroste/32/37212_2.png) [@MichaelDroste](https://forums.realmacsoftware.com/u/MichaelDroste)\
**Post date:** [May 29, 2026, 4:17pm UTC](https://forums.realmacsoftware.com/t/little-things-missing-in-cms-v2/56413/1 "2026-05-29T16:17:01Z")

</div>

Small Issues:

Can a way be made to preview a post? (with artwork and audio podcast) Otherwise - just guessing everything is in the correct folder…

**Perhaps going to confuse people:**

Need to say to elements users: - work all online  
Or:  
Keep Downloading Changed .md files  
Or:  
A little of both?

For example: I want my self hosted podcast audio in my elements file

Could do it online - but then wouldn’t be in my file on my computer…

This - in my opinion - is going to confuse a lot of people…

**Ideally - we need bidirectional sync - what gets updated online gets updated in our elements computer file**

Don’t know if it’s possible - or how hard it would be to implement…

But this would solve a lot of future issues for you - imho…

---

<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:** [May 29, 2026, 6:36pm UTC](https://forums.realmacsoftware.com/t/little-things-missing-in-cms-v2/56413/2 "2026-05-29T18:36:17Z")

</div>

> [@MichaelDroste](#):
>
> a way be made to preview a post?

if you’re using the Online Editor, you can preview a post. Just enter the Preview URL in the Folder settings and you’ll get a Preview button in the WYSIWYG editor.

> [@MichaelDroste](#):
>
> Ideally - we need bidirectional sync - what gets updated online gets updated in our elements computer file

Yes, I agree. We would like to explore some form of syncing between the online editor and Elements on your Mac. I can’t promise anything or even say if/when it will happen as we’ve not even discussed it internally yet 😅

---

<div class="post-metadata">

**Author:** ![ercross](https://avatars.discourse-cdn.com/v4/letter/e/c57346/32.png) [@ercross](https://forums.realmacsoftware.com/u/ercross)\
**Post date:** [May 29, 2026, 6:51pm UTC](https://forums.realmacsoftware.com/t/little-things-missing-in-cms-v2/56413/3 "2026-05-29T18:51:15Z")

</div>

Wouldn’t this eventually just make the project larger and then run the risk when you republish from Elements, you may override changes?

I’d be happy with just a backed up zip file of Md files and resources on the hosting platform that could be easily downloaded.

---

<div class="post-metadata">

**Author:** ![MichaelDroste](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/michaeldroste/32/37212_2.png) [@MichaelDroste](https://forums.realmacsoftware.com/u/MichaelDroste)\
**Post date:** [May 29, 2026, 10:04pm UTC](https://forums.realmacsoftware.com/t/little-things-missing-in-cms-v2/56413/4 "2026-05-29T22:04:54Z")

</div>

Perhaps on launch of elements - have the software do a an instant sync with online - downloading the most current version…

Remember your .md files are 4-5k small

---

<div class="post-metadata">

**Author:** ![PouwelW](https://avatars.discourse-cdn.com/v4/letter/p/f19dbf/32.png) [@PouwelW](https://forums.realmacsoftware.com/u/PouwelW)\
**Post date:** [May 30, 2026, 12:38pm UTC](https://forums.realmacsoftware.com/t/little-things-missing-in-cms-v2/56413/5 "2026-05-30T12:38:00Z")

</div>

Bidirectional sync would be my preferred solution. But if this is too difficult or too lengthy to implement a solution like @ercross 's zip file would already be very helpful.

---

<div class="post-metadata">

**Author:** ![PouwelW](https://avatars.discourse-cdn.com/v4/letter/p/f19dbf/32.png) [@PouwelW](https://forums.realmacsoftware.com/u/PouwelW)\
**Post date:** [May 30, 2026, 1:07pm UTC](https://forums.realmacsoftware.com/t/little-things-missing-in-cms-v2/56413/6 "2026-05-30T13:07:28Z")

</div>

I would like to add one other little thing missing @ben . I’ve got a small personal website with a blog. The only one posting is me. So I use the free plan and am very pleased with all the features I have. I can finally leave Markdown behind. To be honest this free online editor is the reason I still use Elements and didn’t switch back to WordPress which I used in the past.

But I miss the status field in the free plan. I can understand that adding your own fields is not part of the free plan. But having the ability to change the status of a post is so basic to blogging. Blogging requires time for thinking and (re)writing, so it’s very unfortunate my blog posts are published immediately. Having to pay $99 for just this one field is just a bit too much.

---

<div class="post-metadata">

**Author:** ![MichaelDroste](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/michaeldroste/32/37212_2.png) [@MichaelDroste](https://forums.realmacsoftware.com/u/MichaelDroste)\
**Post date:** [May 30, 2026, 10:28pm UTC](https://forums.realmacsoftware.com/t/little-things-missing-in-cms-v2/56413/10 "2026-05-30T22:28:29Z")

</div>

to make preview work for me: don’t know why - but have to log out - quit safari - clear cache - log back in - then it works! Maybe help to others - 3 hours of this… chat bot - Claude - etc…

---

<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:** [June 1, 2026, 9:55am UTC](https://forums.realmacsoftware.com/t/little-things-missing-in-cms-v2/56413/11 "2026-06-01T09:55:41Z")

</div>

> [@PouwelW](#):
>
> But I miss the status field in the free plan. I can understand that adding your own fields is not part of the free plan. But having the ability to change the status of a post is so basic to blogging. Blogging requires time for thinking and (re)writing, so it’s very unfortunate my blog posts are published immediately. Having to pay $99 for just this one field is just a bit too much.

Hi @PouwelW the online editor should present you with the fields that are in your markdown file. If it’s not doing that, then it’s likely a bug.

I have an idea of why this might be happening, so I’ll investigate and get back to you.

---

<div class="post-metadata">

**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:** [June 1, 2026, 11:18am UTC](https://forums.realmacsoftware.com/t/little-things-missing-in-cms-v2/56413/12 "2026-06-01T11:18:49Z")

</div>

I think some of the problem here is the inconsistencies in CMS that have been introduced over time. If, for example, you select **New Markdown File** you get a Frontmatter header that does not include **Status**. Some of your later projects have included **Status** , some haven’t. Thus, what’s happening is that there’s been no clear definition of what Frontmatter should be required.

You didn’t instantiate what _should_ be in Frontmatter from the get go, and then you’ve used different examples after that. I’d argue that **Status** is an important one and should be in every Frontmatter, as otherwise you have no control over whether something gets published live or not. As @PouwelW says, **Status** is a basic blogging need. It probably should be in the basic Frontmatter the commands in Elements would create (e.g. **New Markdown File** , which includes **Tags** and **Categories** , as well as **Title** and **Date** ). This probably should be something that the community has a say in (i.e. what constitutes “standard” Frontmatter), and then is applied throughout Elements consistently.

---

<div class="post-metadata">

**Author:** ![PouwelW](https://avatars.discourse-cdn.com/v4/letter/p/f19dbf/32.png) [@PouwelW](https://forums.realmacsoftware.com/u/PouwelW)\
**Post date:** [June 1, 2026, 11:44am UTC](https://forums.realmacsoftware.com/t/little-things-missing-in-cms-v2/56413/13 "2026-06-01T11:44:45Z")

</div>

I absolutely agree @thominator and @ben . Status should be in the basic Frontmatter commands that Elements creates. That is exactly what I tried to say when I started this thread. Ben may be right that all Frontmatter fields I use should appear in the online editor. I don’t know. Before the online editor I uploaded posts directly from Elements. There was no need to use a status field, because I only posted if I was satisfied with the text. But new posts created online do have to have that field in my opinion.
