Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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
Comment #1
dbazuin CreditAttribution: dbazuin commentedComment #1.0
dbazuin CreditAttribution: dbazuin commentedSmall text alteration
Comment #2
kay_v CreditAttribution: kay_v as a volunteer commentedI 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)
Comment #3
Divyanshi.addweb CreditAttribution: Divyanshi.addweb commented