Feedback on Release 65's New indentation logic problems

Hi Capacities team,

I wanted to share some feedback about the new list indentation behavior introduced in Release 65 (https://capacities.io/whats-new/release-65#more-standardized-indentation-logic-in-text-editing)

I understand the goal of making the editor behave more like other tools. However, I personally think the previous Capacities behavior was better and more powerful for structured note-taking.

Before, when indenting or outdenting a bullet point that had nested sub-bullets, the whole block moved together. This was very practical because the parent point and its children stayed logically connected.

Now, the parent bullet moves separately from its nested content, which makes it easier to break the structure of a note when reorganizing it.

The same applies when pressing Enter on a parent bullet. Before, it moved to the next sibling point, after the nested content. Now, it creates a new nested bullet inside the current point, like in Notion. I understand why this may feel familiar to users coming from other tools, but I found the previous behavior much more logical and efficient.

To me, it feels unfortunate to reduce one of Capacities’ strengths just to match the behavior of other editors.

The best solution would probably be to support both behaviors through an editor setting:

“Standard indentation behavior”

“Structured block indentation behavior” / “Classic Capacities behavior”

This would give users the best of both worlds. Users coming from tools like Notion could keep the behavior they are used to, while existing users who preferred the previous Capacities workflow could continue using it.

It also seems like a reasonable improvement from a product perspective, since both behaviors have already existed in Capacities. Offering both as an option could help keep current users happy while making onboarding easier for new users from other tools.

Thanks for considering this feedback.