Open mehimself opened 4 years ago
vs flat
repo/courses/courseAlias/episodes/episodeAlias/materials/materialAlias/#heading
vs.
repo/type/itemAlias
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
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
file structure
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