Learned the wrong output

Lounge
1

After working with Claude for 2 days on web browsers, rendering, frontmatter, DreamHost, and tons of elements options - all in trying to fix my CMS

I learned to not mess with it now…. One little , or . Can take down the whole CMS

I’m just happy to have it working again.

I still have to edit 215 files - but haven’t wanted to do it - don’t want to mess it up again…

Mind you - I know the problem now - and how to check it for errors…

So my question :man_raising_hand: Has this happened to you before?
Ever work so hard and long - fixing a problem - you don’t want to touch it and go back in?

2

Absolutely.

This is why version control like Git are so good, you can make commits as you go along, then if something goes wrong you can rollback to a previous version.

Alternatively, if you don’t want to mess with Git, you can just make sure you backup/make copies of your projects as you go along.

3

@dan Any plans to make Elements cloud larger?

4

A few people have requested this, but obviously Cloud Storage is an ongoing cost so we need to be careful about how much we include for free…

What were you thinking in terms of storage and cost?

5

I have no problem at the moment. I delete old copies when I’m getting near the limit. But it might be smart to move and save the backup zip file when publishing to one’s Mac every once in a while.

6

Backing up locally on publish (or to your server) is a good idea also, Make sure the backup option is enabled :+1:

CleanShot 2026-07-24 at 12 .03.16@2x
CleanShot 2026-07-24 at 12 .03.16@2x1682×1032 109 KB

7

I would give different cloud sizes according to the purchased plan. For Pro I would be a bit more generous than the 1GB. Thats then another reason to switch to a higher plan.