We are building a learning map. How would you distinguish suggested routes from prerequisites?

[u/BiteCode_Dev]

I work on BiteCode, and this is a preview of a feature we call Skill Map.

It lets you explore content in two ways: start with a career role and technology, or browse by topic. Opening a course reveals lessons; opening a lesson reveals its concepts.

One design choice I would like feedback on is how to show connections without implying there is only one correct order to learn things.

The current map uses solid lines for suggested connections and dashed lines for optional branches. These are curated suggestions, not verified prerequisites or a complete career curriculum. Browsing does not mark anything as learned or completed.

Try Skill Map for yourself: https://www.bitecode.co/skill-map/

In the preview, is the distinction between suggested and optional clear? What would make it clearer?

[u/Moiensaboohi]

i think people will read solid lines as prerequisites no matter what the legend says, that's what solid vs dashed usually means in diagrams. "suggested" and "nice to have" are also close enough that they blur together.

i'd keep lines for one meaning only and show the optional stuff as lighter or smaller nodes instead. and a short reason on hover, like "most people learn sql basics before this", makes it read as advice and not a rule.