We need this feature for static pages. When working on a new design for a core page of the website, I basically cannot publish ANY other changes made to ANY other pages except CMS... I have clients questioning if this is the right tool for the job.

Really shocked that Webflow does not allow you to select which static pages to publish. What a disappointment. Please add this feature.

As a dev, it's insane to me that this isn't a basic feature. What kind of mess is lurking under the hood that makes it this difficult to un-publish a static page?

has this been resolved? Pathetic if not, seems like an easy fix and everyone clearly wants it.

I'm not an expert web designer, but a business owner currently using Squarespace. Within Squarespace, I can take a single page, work on a draft for that page and bring it back online without blowing up the entire site. How is that not an option within Webflow still? Do visitors to the site get to watch us do live updates to the site pages while we're working on it? In 2022?

You're correct. This is available for CMS pages/items and not static pages. Reopened the idea.

Shipped—Remove CMS content without publishing your entire site

This is cool although it doesn't solve the original idea. The above only works for CMS content. The original idea is that it's on a per page level. You can publish one single page without publishing every page. This way you can work on updating multiple pages at the same time and not have to worry about other page updates going live half finished.

Shipped—Remove CMS content without publishing your entire site

Regarding publishing individual pages instead of the entire site, this is what the Webflow support told me:

"...At the moment, you aren't able to publish individual static pages on your Webflow project.

This feature limitation is known by the team, though I agree that this could be an awesome feature to have in Webflow, I have no timeline to share at the moment as to when this will be possible. My apologies for any inconvenience this may cause..."

Just to agree with people that say in reality the solution implemented for this particular request doesn't really solve the issue.

The idea should be that when working on a project with multiple team members on a website with many pages, it should be possible to make changes to many live pages but only publish the updates for pages that are ready. Saving a page as a draft would take an already live page offline.

By doing the above, this would allow you to make changes to other pages and not worry about them going live/being published before they are ready.

Not necessarily directly related to this feature and can kind of be solved by using work arounds such as Git but would be good if there was just better version management in general. I feel this would benefit a lot of teams that are more than just one or two members.

The current implementation of this feature is not a viable solution for most users, especially businesses with teams. If the page I am drafting already exists on the live site, upon publishing, that draft page will disappear from your live site. I am drafting a new version of an existing page--it doesn't mean you remove the old live page.

ADMINS, any update on this?
This is not shipped!

Wow, is this really not being tackled yet? How is this marked shipped? - Admins please address.

Crazy. Fix this.

This is basics... ouch :/

The inability to publish design changes to a single page (e.g. to fix a bug) while not publishing other pages that are mid-flight (working on major updates) is a real showstopper for our company. It will be one of the key reasons we stop using Webflow.

Ping. This is really necessary. I am shocked this hasn't been implemented yet.

Admin, please remove the "Shipped" tag. This feature is not live!

The current implementation of this feature is not a viable solution for most users, especially businesses with teams. If the page I am drafting already exists on the live site, upon publishing, that draft page will disappear from your live site. I am drafting a new version of an existing page--it doesn't mean you remove the old live page.

Every other CMS system maintains the old live version while you work on the draft page. It should maintain both the live version (Live site) and the new draft version (staging) and replace the live version with the draft once it is out of draft status. And yes, Draft should be pushed to staging so we can actually test the page out on multiple devices and ensure things like iFrame embeds and custom JS/CSS function properly.

Why we have to request such a CMS feature is beyond me in 2021. I would expect a whole publishing/revision system as good or better than Wordpress (which is free) and yet here we are, requesting features that were givens 6-10 years ago.

How is this not a live feature yet?!?! This is aboslutely standard across the web. I