Changes between Version 20 and Version 21 of TechnicalDescription
- Timestamp:
- 11/28/14 11:15:39 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TechnicalDescription
v20 v21 161 161 162 162 '''Content pages''' 163 * top level pages/content page /about 164 * topic based landing pages /discover/water-management || /discover/solar-energy 163 * top level pages: ''/about'' 164 165 * topic based landing pages: ''/discover/water-management'' 165 166 166 167 '''Content Types | /content type/content title''' 167 Course: /courses/introduction-aeronautical-engineering 168 Bundle: /specializations/helicopters-maintenance 169 Msc: /msc-programs/msc-aerospace-engineering 170 Profed: /professional-education/rottors-expert 171 Instructor: /instructors/alexander-de-haan 168 169 * '''Course:''' /courses/introduction-aeronautical-engineering 170 171 * '''Bundle:''' ''/specializations/helicopters-maintenance'' 172 173 * '''Msc:''' ''/msc-programs/msc-aerospace-engineering'' 174 175 * '''Profed:''' ''/professional-education/rottors-expert'' 176 177 * '''Instructor:''' ''/instructors/alexander-de-haan'' 172 178 173 179 In the long run, I would prefer to have the slug parent (such as “/courses/”) to be generated automatically, based on specific content type (course, bundle, msc, profed, instructor), with ability to change it manually by admins/superusers. (These are the only users we have now, but I’d like to emphasize the “editor” shouldn’t have the permission to change the slug parent in the future).