This section describes how you develop course components.
For more information about specific component types, see the following topics.
A component is the part of a unit that contains your actual course content. A unit can contain one or more components.
By default, Studio includes four basic types of components for you to add to your course.
To add a component to the unit, follow these steps.
For more information, see the documentation for the specific component type that you want to work with.
After you add a component, it is not visible to learners until you publish the unit.
To edit a component, you select Edit.
Then, follow instructions for the type of component you are editing.
After you edit a component, the changes are not visible to learners until you publish the unit.
The display name identifies the component. This name appears as a heading above the component in the LMS, and it identifies the component for you in Insights.
The following illustration shows the display name of a problem in Studio, in the LMS, and in Insights.
Unique, descriptive display names help you and your learners identify components quickly and accurately.
To set the display name for a component, follow these steps.
Edit the component. A dialog box opens.
Edit the Display Name field.
Different types of components have different fields in the Settings dialog box, but all of them have a Display Name field.
When you duplicate a component, a new copy of that component is added directly beneath the first component. You can then modify the duplicate. In many cases, duplicating a component and editing the copy is a faster way to create new content.
To duplicate a component, select the Duplicate icon in the component header.
Then, follow instructions for the type of component you are editing.
After you duplicate a component, the new component is not visible to learners until you publish the unit.
Duplicating content experiments after you have configured them is not supported.
Be sure you want to delete the component. You cannot undo the deletion.
To delete a component, follow these steps.
After you delete a component in Studio, the component remains visible to learners until you publish the unit.
You can drag and drop components to a new position within their current unit, or you can move components from one unit to another unit.
To reorganize components within their current unit, you drag and drop components in the same way that you can drag and drop units, subsections, and sections on the Course Outline page. For more information, see Reorganize the Course Outline.
For components that consist of nested components (for example, a content experiment), you can also use drag and drop to move a child component into a different parent component, if both parents are expanded. For example, you can select the video component that is in Child Component A and drag it into Child Component B. Select the video component, and as you drag it into Child Component B, release the mouse button when a dashed outline of the component you are moving appears in the new location.
You can also drag a child component outside of a parent, so that the child moves to the same level as the parent.
To move components to another unit in the course outline, follow these steps.
Select the Move icon for the component that you want to move.
A dialog box appears that displays your course outline tree, starting at the section level.
In the Move dialog box, navigate to the location where you want to move the component by selecting the section, the subsection, and then the unit.
The Move button is enabled only when your selected location is a valid level and location for moving your component. For example, when you move a component, the Move button is enabled only when you have navigated to a unit to which the component can be moved.
The component moves to the new location. A success message appears that provides options to go to the new location or to undo the move.
If the old and new locations of the component that you moved were previously published, your changes are not reflected in the learner’s view of the course until you republish the affected units.
For specific use cases, you configure course content so that components contain other components. For example, if you want to include conditional components or content experiments, you have to create components inside components. See Creating Content Experiments for more information.
The component that contains other components is referred to as the parent; the contained components are referred to as child components, or children.
On a unit page, a parent component appears with its display name and a View link.
A parent component does not directly contain content. Content such as HTML, videos, or problems are in the child components.
A parent component has a display name. When the unit is private or in draft, select Edit in the parent component to change the display name.
Parent components of a specific type, such as content experiments, have additional attributes that you edit.
When you select View in the parent component, the parent component page opens, showing all child components. In this example, Child Component A contains an HTML component and a video.
Select the arrow next to a child component name to collapse it and hide the component’s contents. Select the arrow again to expand the component.
For more information, see the following topics.
If the containing unit is private or in draft, you can add a child component in its parent component.
To add a child component, open and expand the parent component. Then, select the component type that you want under Add New Component within the parent component.
For more information, see the section for the specific component type that you want.
You develop parent and child components in XML, then import the XML course into Studio to verify that the structure is as you intended.
For more information about working with your course’s XML files, including information about terminology, see the EdX Open Learning XML Guide.
The following examples show the XML used to create the unit and components shown in Studio above.
The XML for the unit is as follows.
<vertical display_name="Unit 1"> <html url_name="6a5cf0ea41a54b209e0815147896d1b2"/> <vertical url_name="131a499ddaa3474194c1aa2eced34455"/> </vertical>
<vertical url_name="131a499ddaa3474194c1aa2eced34455"/> element above
references the parent component file that contains the child components.
<vertical display_name="Parent Component"> <vertical url_name="2758bbc495dd40d59050da15b40bd9a5"/> <vertical url_name="c5c8b27c2c5546e784432f3b2b6cf2ea"/> </vertical>
The two verticals referenced by the parent component refer to the child components, which contain the actual content of your course.
<vertical display_name="Child Component A"> <html url_name="4471618afafb45bfb86cbe511973e225"/> <video url_name="fbd800d0bdbd4cb69ac70c47c9f699e1"/> </vertical>
<vertical display_name="Child Component B"> <html url_name="dd6ef295fda74a639842e1a49c66b2c7"/> <problem url_name="b40ecbe4ed1b4280ae93e2a158edae6f"/> </vertical>
Theoretically, there is no limit to the levels of component nesting you can use in your course.
For learners, all parent and child components appear on the unit page.
The visibility of nested components depends on the visibility of the parent unit. The parent unit must be public for learners to see nested components. For more information, see Unit Publishing Status and Visibility to Learners.
The following example shows the learner view of the unit described above.