The order of the steps should be in order of expertise level.
So then the can start with the least difficult and built it up.

If we can use a some kind of tagging or flagging system on the lessons we don't have to edit the start page of the ladder every time a lesson is add.

Comments

dbazuin’s picture

Assigned: Unassigned » dbazuin
dbazuin’s picture

Issue summary: View changes

Small text alteration

kay_v’s picture

Version: 7.x-1.x-dev » 8.x-1.x-dev
Assigned: dbazuin » Unassigned
Priority: Normal » Major
Issue summary: View changes

I strongly agree that this type of feature is core to the purpose of the DrupalLadder, especially considering the range of valid use cases supported by the community. (For some situations, a simple choice will be best where other use cases involve greater complexity). An indication like that described by @dbazuin can be key to addressing the range of options supported by the community.

Possibly a scale that conveys ideas like the following? (this is a quick note, so clearly it will need more consideration and input):
1) simplest viable approach
[...]
n) cover wider (future or current) requirements
[...]
n) enterprise level

updating version and priority (recognizing that though this may be considered a major priority, it may still end up being deferred or switched back to 'normal priority' in a roadmapping effort)

Divyanshi.addweb’s picture

Assigned: Unassigned » Divyanshi.addweb