The Good, the Bad, and the Ugly

The designer is the centerpiece of Webflow's product. It's what makes Webflow, Webflow. The photoshop of web design.

We've used it for six years now and we've a lot of things we wish we could fix. Here's a list of some of the main bugs and limitations we regularly run into.

General Issues

1. Fix the issue with the collapsing custom attributes panel
2. Allows CMS-bound attributes on ECom Products and Categories
3. Drag and drop ordering of pages is very bugged
4. Interactions selector and targeting

Designer Modes

1. Editor mode. Actually support editing, especially inline editing of CMS content. We need the WYSIWYG view and currently have to go to the external editor which can not do localization.
2. Add an SEO mode which has limited access to SEO settings and content. No layout access. Essentially an Editor mode.
3. > ? Code
4. Add a Translator mode, which can translate only.
5. Read-only mode is fantastically powerful

Navigation

Left side navigation panel;

1. Expand/contract a single element. Support hotkey and right click menu
2. Differentiate between elements which are display none v. visibility hidden states. These are very different things to a dev. Show visibility hidden elements as grayed, or with a line through them.
3. Make certain the right-edge indicators like visibility are always visible in the nav panel
4. Search in nav panel, for element type etc. Treat this as a filter, when text is entered gray everything, highlight matches ( e.g. element types ) Readonly as well, "find the lightbox... "

Quick-search;

1. Fix it, it rarely finds known pages especially CMS item pages

CMS;

• Quick open the current CMS item when viewing that item in the designer as a page context.
• Quick open a CMS item's page context from the designer.

Designer-Editor-Published Nav;

1. + Can currently nav from the page being viewed to the published versions under the publish button. It would be nice to make this more accessible or hotkey it.
2. Add nav to editor from the designer, to the page currently being viewed
3. ‍

HTML Embeds

1. When an element is hidden but contains a child embed element with CSS, do NOT apply that CSS in the designer
2. Allow slug, ID binding in Embeds
3. Support ISO8601 as a date format.
4. In HTML embeds, allow formatting variations beyond the default, e.g. JSON encoded fields Date ISO 8601

Collection Lists

Editor mode

‍

Read-only mode

‍

Developer mode

• Make code admin ( including site level ) more accessible from the designer.
• Provide access to features devs continually need- data binding to CMS item ID's and Slugs,

Enhancements

Webflow Chrome Extension

FS Chrome Extension

‍

‍