Ability to "name sections"

[michael]

Concrete example: I want to deep link to a section at /product#for-developers, but currently i can only deep link to a generated nodeid like /product#sRBeBTpUtghMFXKRXKgVHbS

Considerations:

• This is like a pro feature, most of the time people will not bother and not deep link
• Editable needs a tool "rename block" for single block selections. Then you can set your own id. It only accepts ids that are not used on the page already. It will rewrite the graph so that only the id changes, and all references to it
• Currently when you copy & paste or cut and paste, we always generate new ids for the nodes. I guess once we have named blocks we want a name to survive at least a cut and paste.

[michael]

More considerations:

Yes, that seems like a good evolution. An anchor can become a first-class, optional capability of a node, much like href and target are only available for node types that support linking.

For example, a schema could declare:

{
	type: 'section',
	properties: {
		anchor: {
			type: 'string',
			optional: true
		}
	}
}

When a node has an anchor:

• it renders a stable URL fragment such as #for-developers
• the editor can offer a “Copy link to this section” action
• the page can show a small link affordance on hover or focus, similar to GitHub README headings
• the anchor remains separate from the internal node ID
• uniqueness is enforced within the relevant page or document

I would not make every node automatically anchorable. A paragraph, image, or decorative wrapper generally should not expose a deep-link affordance. The schema should decide which nodes can meaningfully be addressed — headings, sections, projects, articles, and similar content blocks.

One distinction from href/target: those properties describe a link rendered by the node, while anchor describes a location that other links can point to. But the schema-driven availability pattern is the same.

You could eventually have a generic node action:

Copy link to this section

and show it only when the selected node supports an anchor property and has a non-empty value. That would give users the GitHub-style experience without requiring every block to become a public URL target.