Site activity log. It's a log of activity — and what it does is this: it keeps track of key changes to your site. So if you and your team are working together — different roles, different responsibilities, maybe different time zones — you can use site activity log for two, really important aspects of development and site management: the first is for tracking changes, having visibility into what's happening. The second is making sure everything's ready before you publish.
Let's look at visibility, tracking changes. So on any site within an enterprise workspace, I can access site activity log from the left panel. And right away, I can see my site activity. The key here is who, what, and when. I can see who's made each change, what change they made, and of course, when they made that change.
For example, if someone's made design changes, like modifying styling on this class or on this component, I can see what elements and even what pages are affected by the change.
It also tracks content changes, changes to CMS content, static content, so I can see what progress content editors are making.
And filters take this a step further. We often work on large teams with lots going on. So I can filter not only by all changes. I can filter by activity type, and even by the team member that's made the changes.
But that's visibility into the who, what, and when for site activity. Let's move to the second part: publishing.
Here, if we go up to publish to open our publishing view. Before we last published to staging, we can see all recent changes and who made them. If we click into any of these? We go to that exact site activity log.
This can be helpful to look into before you publish your site to ensure all changes are ready, tested, and approved. So if we go back up to our publishing view, and actually publish to staging, and while this is loading, I wanted to tell you a personal story. But that has to come later because this is done.
Now, all the changes the team has made are live on our staging domain. Then, if someone on the team makes a new change, it will show up here again.
That's how you can use the publishing summary alongside the site activity log to make sure that you are only publishing the work that should be published.
To learn even more about site activity log, check out our documentation over at the help center site and the Webflow Way site.
But that's it. Let's recap real quick. We talked about visibility — the who, what, and when. And then, we showed how the publishing view works alongside the site activity log.
That's a high-level overview of the site activity log in Webflow.