Obsidian editor-behavior priority map

Tier 1: product behavior pages

Start here for editor/product behavior:

• help/en/Editing and formatting/Views and editing mode.md
• help/en/Live preview update.md
• help/en/Editing and formatting/Obsidian Flavored Markdown.md
• help/en/Linking notes and files/Internal links.md
• help/en/Plugins/Backlinks.md
• help/en/Plugins/Outline.md
• help/en/Plugins/Search.md
• help/en/User interface/Settings.md

Why:

• these define editing modes, linking behavior, navigation, and search
• they are the strongest product-facing pages for the editor experience

Tier 2: developer editor surface

Then read:

• developer/en/Plugins/Editor/Editor extensions.md
• developer/en/Plugins/Editor/Editor.md
• developer/en/Plugins/Editor/Markdown post processing.md

Why:

• these explain how Obsidian exposes its editor platform
• they help on architecture and extension-system comparisons

Lower-priority but relevant later

• graph view
• slash commands
• tags view
• CSS-variable editor references

Useful later, not first.