mehimself / onlinecoursescontent Goto Github PK

push to repo when done

file structure

• courses (h2)
  • episodes (h3)
    • material (h4)
      • points (h6)
      • examples(h5)
      • summary(h5)

vs flat

urls

repo/courses/courseAlias/episodes/episodeAlias/materials/materialAlias/#heading

vs.

repo/type/itemAlias

SWOT

nested:
focus of ease of maintenance: courses
lesser error-risk
lesser error-damage
fragile (non-)permalinks

flat:
focus of ease of maintenance: global material coverage
errors have a high impact
errors are more likely
permalinks

result

nested is better for user experience with better material stability and transparent content paths

flat is better for curating bodies of knowledge aiming for completness