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.
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
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.
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.
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…
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.
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.
