Features
Triage

Implement a distinct "Description" Property (like known from Anytype)

What's the scenario?

When the user hovers over an internal link (that leads to another Page), the content of that Page's distinct "Description" Property should become shown, to tell the topic of that link.

What's the goal?

The goal is, to give the user more context information in certain situations.
My example above is only one example (I have more in mind for later, but first we need that distinct Property).

Who is this for?

Like in legacy Anytype, each Object should have such a Property that's reserved for the purpose to become displayed for example in card links (and other situations).

I used the "Description" in quasi all of my Pages.
Since I'm a tester of AnyTwo, I've thought for a while that such a special reserved Property is no longer needed. But meanwhile I've realized that it still is needed and it will become even more important when AnyTwo gets more features (like card links).

A very simple example:
The user hovers on a name of a person: "Anton". He doesn't know anymore who he/she is and there are maybe even multiple persons "Anton" in the contacts or elsewhere.

Hovering on the name would show the content in the description Property:
"One of the two founders of Anytype"
""Neighbour from the house opposite"
"Member of my old sport club"

1 Comment

Sign in to comment

AL
Alex Lins (Bao)·about 1 hour ago

Thanks for the detailed example — the hover-preview use case is clear. A few questions to nail down the scope:

  1. Scope of display: Beyond hover previews on links, where else should this Description show up? You mentioned "card links and other situations" — do you have a priority list, or should we treat hover-preview as the first milestone and design the property to support future use cases as they come?
  2. Property behavior: Should Description be a single text field (like a short bio), or support the same rich formatting (markdown, embeds, etc.) as a regular page body? The "Anton" example suggests plain text is enough, but I want to confirm before we spec it.
  3. Backwards compatibility: For users migrating from Anytype with existing Description data — do you expect an import tool, or is this a fresh start for AnyTwo where people re-populate it as needed?