...
For example: The Collection component would expect CollectionType, Board, Class, Medium, Subject, Framework to list the textbook.
.png?version=1&modificationDate=1571383884077&cacheVersion=1&api=v2&width=600)
.png?version=1&modificationDate=1573544606587&cacheVersion=1&api=v2&height=400)
Similarly, ChapterList component would expect CollectionId and List of content types
.png?version=1&modificationDate=1571384005570&cacheVersion=1&api=v2&width=550)
.png?version=1&modificationDate=1573545196343&cacheVersion=1&api=v2&height=400)
If we put together all the component and its required configurations, actions and possible enhancements into a module/highlevel component the following would be the overall component hierarchy and configuration.
%20(1).jpg?version=1&modificationDate=1573533998659&cacheVersion=1&api=v2)
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"pageAssemblyId":"",
"board":"",
"class":"",
"subject":"",
"medium":"",
"framework":"",
"collectionType":{
"name": "Collection type",
"type": "string",
"enum": "Textbook, Course"
},
"contentTypes": {
"name": "List of contentTypes",
"type": "List",
"enum": ["PracticeQuestionSet", "Lessonplan", "ExperientialResource", "FocusSpot", "CuriosityQuestionSet", "ExplanationResource"]
},
"questionCategories":{
"name": "List of AssessmentItem Categorys",
"type": "List",
"enum": ["VSA", "SA", "LA", "MCQ", "CuriosityQuestion"],
"hints": "When PracticeQuestionSet is set for contentTypes AssessmentItem Categorys must be"
},
"ckEditorConfig": {}
}
|
.png?version=1&modificationDate=1571649627293&cacheVersion=1&api=v2&width=850)
With this basic set of configurations, a program can be created by an admin of the program.
...