diff --git a/.gitignore b/.gitignore index bea14c073..1057c5040 100644 --- a/.gitignore +++ b/.gitignore @@ -3,3 +3,4 @@ build source/.DS_Store .idea/ sphinx-env/ +venv/ diff --git a/source/educators/migration_wip/images/Course_Outline_LMS.png b/source/_images/educator_concepts/Course_Outline_LMS.png similarity index 100% rename from source/educators/migration_wip/images/Course_Outline_LMS.png rename to source/_images/educator_concepts/Course_Outline_LMS.png diff --git a/source/educators/migration_wip/images/Discussion_MarkAsAnswer.png b/source/_images/educator_concepts/Discussion_MarkAsAnswer.png similarity index 100% rename from source/educators/migration_wip/images/Discussion_MarkAsAnswer.png rename to source/_images/educator_concepts/Discussion_MarkAsAnswer.png diff --git a/source/educators/migration_wip/images/Discussion_Pin.png b/source/_images/educator_concepts/Discussion_Pin.png similarity index 100% rename from source/educators/migration_wip/images/Discussion_Pin.png rename to source/_images/educator_concepts/Discussion_Pin.png diff --git a/source/educators/migration_wip/images/Discussion_ReadUnreadNew.png b/source/_images/educator_concepts/Discussion_ReadUnreadNew.png similarity index 100% rename from source/educators/migration_wip/images/Discussion_ReadUnreadNew.png rename to source/_images/educator_concepts/Discussion_ReadUnreadNew.png diff --git a/source/educators/migration_wip/images/Discussion_vote.png b/source/_images/educator_concepts/Discussion_vote.png similarity index 100% rename from source/educators/migration_wip/images/Discussion_vote.png rename to source/_images/educator_concepts/Discussion_vote.png diff --git a/source/educators/migration_wip/images/discussion_add_post_group_selection.png b/source/_images/educator_concepts/discussion_add_post_group_selection.png similarity index 100% rename from source/educators/migration_wip/images/discussion_add_post_group_selection.png rename to source/_images/educator_concepts/discussion_add_post_group_selection.png diff --git a/source/educators/migration_wip/images/discussion_filter_by_groups.png b/source/_images/educator_concepts/discussion_filter_by_groups.png similarity index 100% rename from source/educators/migration_wip/images/discussion_filter_by_groups.png rename to source/_images/educator_concepts/discussion_filter_by_groups.png diff --git a/source/educators/migration_wip/images/post_visible_all.png b/source/_images/educator_concepts/post_visible_all.png similarity index 100% rename from source/educators/migration_wip/images/post_visible_all.png rename to source/_images/educator_concepts/post_visible_all.png diff --git a/source/educators/migration_wip/images/post_visible_default.png b/source/_images/educator_concepts/post_visible_default.png similarity index 100% rename from source/educators/migration_wip/images/post_visible_default.png rename to source/_images/educator_concepts/post_visible_default.png diff --git a/source/educators/migration_wip/images/post_visible_group.png b/source/_images/educator_concepts/post_visible_group.png similarity index 100% rename from source/educators/migration_wip/images/post_visible_group.png rename to source/_images/educator_concepts/post_visible_group.png diff --git a/source/educators/migration_wip/images/Add_general_topic_name_edx_discussions.png b/source/_images/educator_how_tos/Add_general_topic_name_edx_discussions.png similarity index 100% rename from source/educators/migration_wip/images/Add_general_topic_name_edx_discussions.png rename to source/_images/educator_how_tos/Add_general_topic_name_edx_discussions.png diff --git a/source/educators/migration_wip/images/Bulk_email_history.png b/source/_images/educator_how_tos/Bulk_email_history.png similarity index 100% rename from source/educators/migration_wip/images/Bulk_email_history.png rename to source/_images/educator_how_tos/Bulk_email_history.png diff --git a/source/educators/migration_wip/images/Bulk_email_list.png b/source/_images/educator_how_tos/Bulk_email_list.png similarity index 100% rename from source/educators/migration_wip/images/Bulk_email_list.png rename to source/_images/educator_how_tos/Bulk_email_list.png diff --git a/source/educators/migration_wip/images/Bulk_email_pending.png b/source/_images/educator_how_tos/Bulk_email_pending.png similarity index 100% rename from source/educators/migration_wip/images/Bulk_email_pending.png rename to source/_images/educator_how_tos/Bulk_email_pending.png diff --git a/source/educators/migration_wip/images/Bulk_email_scheduled_emails_table.png b/source/_images/educator_how_tos/Bulk_email_scheduled_emails_table.png similarity index 100% rename from source/educators/migration_wip/images/Bulk_email_scheduled_emails_table.png rename to source/_images/educator_how_tos/Bulk_email_scheduled_emails_table.png diff --git a/source/educators/migration_wip/images/Bulk_email_sent.png b/source/_images/educator_how_tos/Bulk_email_sent.png similarity index 100% rename from source/educators/migration_wip/images/Bulk_email_sent.png rename to source/_images/educator_how_tos/Bulk_email_sent.png diff --git a/source/educators/migration_wip/images/Bulk_email_states.png b/source/_images/educator_how_tos/Bulk_email_states.png similarity index 100% rename from source/educators/migration_wip/images/Bulk_email_states.png rename to source/_images/educator_how_tos/Bulk_email_states.png diff --git a/source/educators/migration_wip/images/CertificateDeleteIcon.png b/source/_images/educator_how_tos/CertificateDeleteIcon.png similarity index 100% rename from source/educators/migration_wip/images/CertificateDeleteIcon.png rename to source/_images/educator_how_tos/CertificateDeleteIcon.png diff --git a/source/educators/migration_wip/images/Cohorts_AddContentGroup.png b/source/_images/educator_how_tos/Cohorts_AddContentGroup.png similarity index 100% rename from source/educators/migration_wip/images/Cohorts_AddContentGroup.png rename to source/_images/educator_how_tos/Cohorts_AddContentGroup.png diff --git a/source/educators/migration_wip/images/Cohorts_AssociateWithContentGroup.png b/source/_images/educator_how_tos/Cohorts_AssociateWithContentGroup.png similarity index 100% rename from source/educators/migration_wip/images/Cohorts_AssociateWithContentGroup.png rename to source/_images/educator_how_tos/Cohorts_AssociateWithContentGroup.png diff --git a/source/_images/educator_how_tos/Discussion_MarkAsAnswer.png b/source/_images/educator_how_tos/Discussion_MarkAsAnswer.png new file mode 100644 index 000000000..0b9462930 Binary files /dev/null and b/source/_images/educator_how_tos/Discussion_MarkAsAnswer.png differ diff --git a/source/_images/educator_how_tos/Discussion_Pin.png b/source/_images/educator_how_tos/Discussion_Pin.png new file mode 100644 index 000000000..2beb2f109 Binary files /dev/null and b/source/_images/educator_how_tos/Discussion_Pin.png differ diff --git a/source/_images/educator_how_tos/Discussion_ReadUnreadNew.png b/source/_images/educator_how_tos/Discussion_ReadUnreadNew.png new file mode 100644 index 000000000..c63a00ee5 Binary files /dev/null and b/source/_images/educator_how_tos/Discussion_ReadUnreadNew.png differ diff --git a/source/educators/migration_wip/images/Discussion_blackout_dates_configuration.png b/source/_images/educator_how_tos/Discussion_blackout_dates_configuration.png similarity index 100% rename from source/educators/migration_wip/images/Discussion_blackout_dates_configuration.png rename to source/_images/educator_how_tos/Discussion_blackout_dates_configuration.png diff --git a/source/educators/migration_wip/images/Discussion_category_subcategory.png b/source/_images/educator_how_tos/Discussion_category_subcategory.png similarity index 100% rename from source/educators/migration_wip/images/Discussion_category_subcategory.png rename to source/_images/educator_how_tos/Discussion_category_subcategory.png diff --git a/source/educators/migration_wip/images/Discussion_tile_in_pages_and_resources.png b/source/_images/educator_how_tos/Discussion_tile_in_pages_and_resources.png similarity index 100% rename from source/educators/migration_wip/images/Discussion_tile_in_pages_and_resources.png rename to source/_images/educator_how_tos/Discussion_tile_in_pages_and_resources.png diff --git a/source/educators/migration_wip/images/Discussion_toggle_cohort_coursewide.png b/source/_images/educator_how_tos/Discussion_toggle_cohort_coursewide.png similarity index 100% rename from source/educators/migration_wip/images/Discussion_toggle_cohort_coursewide.png rename to source/_images/educator_how_tos/Discussion_toggle_cohort_coursewide.png diff --git a/source/_images/educator_how_tos/Discussion_vote.png b/source/_images/educator_how_tos/Discussion_vote.png new file mode 100644 index 000000000..1a02a3943 Binary files /dev/null and b/source/_images/educator_how_tos/Discussion_vote.png differ diff --git a/source/educators/migration_wip/images/Discussions_toggle_cohort.png b/source/_images/educator_how_tos/Discussions_toggle_cohort.png similarity index 100% rename from source/educators/migration_wip/images/Discussions_toggle_cohort.png rename to source/_images/educator_how_tos/Discussions_toggle_cohort.png diff --git a/source/educators/migration_wip/images/General_discussion_topics_edx_discussions.png b/source/_images/educator_how_tos/General_discussion_topics_edx_discussions.png similarity index 100% rename from source/educators/migration_wip/images/General_discussion_topics_edx_discussions.png rename to source/_images/educator_how_tos/General_discussion_topics_edx_discussions.png diff --git a/source/educators/migration_wip/images/Gradebook_Edit_Grades.png b/source/_images/educator_how_tos/Gradebook_Edit_Grades.png similarity index 100% rename from source/educators/migration_wip/images/Gradebook_Edit_Grades.png rename to source/_images/educator_how_tos/Gradebook_Edit_Grades.png diff --git a/source/educators/migration_wip/images/Grading_Configuration.png b/source/_images/educator_how_tos/Grading_Configuration.png similarity index 100% rename from source/educators/migration_wip/images/Grading_Configuration.png rename to source/_images/educator_how_tos/Grading_Configuration.png diff --git a/source/educators/migration_wip/images/Grading_Configuration_Studio.png b/source/_images/educator_how_tos/Grading_Configuration_Studio.png similarity index 100% rename from source/educators/migration_wip/images/Grading_Configuration_Studio.png rename to source/_images/educator_how_tos/Grading_Configuration_Studio.png diff --git a/source/educators/migration_wip/images/HTML_PowerPastePop.png b/source/_images/educator_how_tos/HTML_PowerPastePop.png similarity index 100% rename from source/educators/migration_wip/images/HTML_PowerPastePop.png rename to source/_images/educator_how_tos/HTML_PowerPastePop.png diff --git a/source/educators/migration_wip/images/HTML_source_code.png b/source/_images/educator_how_tos/HTML_source_code.png similarity index 100% rename from source/educators/migration_wip/images/HTML_source_code.png rename to source/_images/educator_how_tos/HTML_source_code.png diff --git a/source/educators/migration_wip/images/Learner_Gradebook.png b/source/_images/educator_how_tos/Learner_Gradebook.png similarity index 100% rename from source/educators/migration_wip/images/Learner_Gradebook.png rename to source/_images/educator_how_tos/Learner_Gradebook.png diff --git a/source/educators/migration_wip/images/New_general_discussion_topic.png b/source/_images/educator_how_tos/New_general_discussion_topic.png similarity index 100% rename from source/educators/migration_wip/images/New_general_discussion_topic.png rename to source/_images/educator_how_tos/New_general_discussion_topic.png diff --git a/source/educators/migration_wip/images/NumSectionHighlights.png b/source/_images/educator_how_tos/NumSectionHighlights.png similarity index 100% rename from source/educators/migration_wip/images/NumSectionHighlights.png rename to source/_images/educator_how_tos/NumSectionHighlights.png diff --git a/source/educators/migration_wip/images/PowerPaste_KeepFormatting.png b/source/_images/educator_how_tos/PowerPaste_KeepFormatting.png similarity index 100% rename from source/educators/migration_wip/images/PowerPaste_KeepFormatting.png rename to source/_images/educator_how_tos/PowerPaste_KeepFormatting.png diff --git a/source/educators/migration_wip/images/PowerPaste_RemoveFormatting.png b/source/_images/educator_how_tos/PowerPaste_RemoveFormatting.png similarity index 100% rename from source/educators/migration_wip/images/PowerPaste_RemoveFormatting.png rename to source/_images/educator_how_tos/PowerPaste_RemoveFormatting.png diff --git a/source/educators/migration_wip/images/SAD_Answer_Review.png b/source/_images/educator_how_tos/SAD_Answer_Review.png similarity index 100% rename from source/educators/migration_wip/images/SAD_Answer_Review.png rename to source/_images/educator_how_tos/SAD_Answer_Review.png diff --git a/source/educators/migration_wip/images/SAD_Column_Chart.png b/source/_images/educator_how_tos/SAD_Column_Chart.png similarity index 100% rename from source/educators/migration_wip/images/SAD_Column_Chart.png rename to source/_images/educator_how_tos/SAD_Column_Chart.png diff --git a/source/educators/migration_wip/images/Tile_for_edx_discussion_provider.png b/source/_images/educator_how_tos/Tile_for_edx_discussion_provider.png similarity index 100% rename from source/educators/migration_wip/images/Tile_for_edx_discussion_provider.png rename to source/_images/educator_how_tos/Tile_for_edx_discussion_provider.png diff --git a/source/educators/migration_wip/images/a_b_test_child_expanded.png b/source/_images/educator_how_tos/a_b_test_child_expanded.png similarity index 100% rename from source/educators/migration_wip/images/a_b_test_child_expanded.png rename to source/_images/educator_how_tos/a_b_test_child_expanded.png diff --git a/source/educators/migration_wip/images/anonymous-posting.png b/source/_images/educator_how_tos/anonymous-posting.png similarity index 100% rename from source/educators/migration_wip/images/anonymous-posting.png rename to source/_images/educator_how_tos/anonymous-posting.png diff --git a/source/educators/migration_wip/images/archived.png b/source/_images/educator_how_tos/archived.png similarity index 100% rename from source/educators/migration_wip/images/archived.png rename to source/_images/educator_how_tos/archived.png diff --git a/source/educators/migration_wip/images/component_access_indicator.png b/source/_images/educator_how_tos/component_access_indicator.png similarity index 100% rename from source/educators/migration_wip/images/component_access_indicator.png rename to source/_images/educator_how_tos/component_access_indicator.png diff --git a/source/educators/migration_wip/images/component_access_select_grouptype.png b/source/_images/educator_how_tos/component_access_select_grouptype.png similarity index 100% rename from source/educators/migration_wip/images/component_access_select_grouptype.png rename to source/_images/educator_how_tos/component_access_select_grouptype.png diff --git a/source/educators/migration_wip/images/component_access_settings.png b/source/_images/educator_how_tos/component_access_settings.png similarity index 100% rename from source/educators/migration_wip/images/component_access_settings.png rename to source/_images/educator_how_tos/component_access_settings.png diff --git a/source/educators/migration_wip/images/component_move_icon.png b/source/_images/educator_how_tos/component_move_icon.png similarity index 100% rename from source/educators/migration_wip/images/component_move_icon.png rename to source/_images/educator_how_tos/component_move_icon.png diff --git a/source/educators/migration_wip/images/component_move_navigation.png b/source/_images/educator_how_tos/component_move_navigation.png similarity index 100% rename from source/educators/migration_wip/images/component_move_navigation.png rename to source/_images/educator_how_tos/component_move_navigation.png diff --git a/source/educators/migration_wip/images/components_restricted_access_indicator.png b/source/_images/educator_how_tos/components_restricted_access_indicator.png similarity index 100% rename from source/educators/migration_wip/images/components_restricted_access_indicator.png rename to source/_images/educator_how_tos/components_restricted_access_indicator.png diff --git a/source/educators/migration_wip/images/content_experiment_block.png b/source/_images/educator_how_tos/content_experiment_block.png similarity index 100% rename from source/educators/migration_wip/images/content_experiment_block.png rename to source/_images/educator_how_tos/content_experiment_block.png diff --git a/source/educators/migration_wip/images/content_experiment_container.png b/source/_images/educator_how_tos/content_experiment_container.png similarity index 100% rename from source/educators/migration_wip/images/content_experiment_container.png rename to source/_images/educator_how_tos/content_experiment_container.png diff --git a/source/educators/migration_wip/images/content_experiment_editor.png b/source/_images/educator_how_tos/content_experiment_editor.png similarity index 100% rename from source/educators/migration_wip/images/content_experiment_editor.png rename to source/_images/educator_how_tos/content_experiment_editor.png diff --git a/source/educators/migration_wip/images/content_experiment_editor_group2.png b/source/_images/educator_how_tos/content_experiment_editor_group2.png similarity index 100% rename from source/educators/migration_wip/images/content_experiment_editor_group2.png rename to source/_images/educator_how_tos/content_experiment_editor_group2.png diff --git a/source/educators/migration_wip/images/content_experiment_group_config_link.png b/source/_images/educator_how_tos/content_experiment_group_config_link.png similarity index 100% rename from source/educators/migration_wip/images/content_experiment_group_config_link.png rename to source/_images/educator_how_tos/content_experiment_group_config_link.png diff --git a/source/educators/migration_wip/images/content_experiment_page_group_config_link.png b/source/_images/educator_how_tos/content_experiment_page_group_config_link.png similarity index 100% rename from source/educators/migration_wip/images/content_experiment_page_group_config_link.png rename to source/_images/educator_how_tos/content_experiment_page_group_config_link.png diff --git a/source/educators/migration_wip/images/course_export_page.png b/source/_images/educator_how_tos/course_export_page.png similarity index 100% rename from source/educators/migration_wip/images/course_export_page.png rename to source/_images/educator_how_tos/course_export_page.png diff --git a/source/educators/migration_wip/images/course_grades_page_graderange.png b/source/_images/educator_how_tos/course_grades_page_graderange.png similarity index 100% rename from source/educators/migration_wip/images/course_grades_page_graderange.png rename to source/_images/educator_how_tos/course_grades_page_graderange.png diff --git a/source/educators/migration_wip/images/course_import_page.png b/source/_images/educator_how_tos/course_import_page.png similarity index 100% rename from source/educators/migration_wip/images/course_import_page.png rename to source/_images/educator_how_tos/course_import_page.png diff --git a/source/educators/migration_wip/images/course_license.png b/source/_images/educator_how_tos/course_license.png similarity index 100% rename from source/educators/migration_wip/images/course_license.png rename to source/_images/educator_how_tos/course_license.png diff --git a/source/educators/migration_wip/images/create-group-config.png b/source/_images/educator_how_tos/create-group-config.png similarity index 100% rename from source/educators/migration_wip/images/create-group-config.png rename to source/_images/educator_how_tos/create-group-config.png diff --git a/source/educators/migration_wip/images/creative-commons-license-course.png b/source/_images/educator_how_tos/creative-commons-license-course.png similarity index 100% rename from source/educators/migration_wip/images/creative-commons-license-course.png rename to source/_images/educator_how_tos/creative-commons-license-course.png diff --git a/source/educators/migration_wip/images/discussion-enabled.png b/source/_images/educator_how_tos/discussion-enabled.png similarity index 100% rename from source/educators/migration_wip/images/discussion-enabled.png rename to source/_images/educator_how_tos/discussion-enabled.png diff --git a/source/educators/migration_wip/images/discussion-sidebar.png b/source/_images/educator_how_tos/discussion-sidebar.png similarity index 100% rename from source/educators/migration_wip/images/discussion-sidebar.png rename to source/_images/educator_how_tos/discussion-sidebar.png diff --git a/source/_images/educator_how_tos/discussion_add_post_group_selection.png b/source/_images/educator_how_tos/discussion_add_post_group_selection.png new file mode 100644 index 000000000..c4325829c Binary files /dev/null and b/source/_images/educator_how_tos/discussion_add_post_group_selection.png differ diff --git a/source/_images/educator_how_tos/discussion_filter_by_groups.png b/source/_images/educator_how_tos/discussion_filter_by_groups.png new file mode 100644 index 000000000..b66d3fa6f Binary files /dev/null and b/source/_images/educator_how_tos/discussion_filter_by_groups.png differ diff --git a/source/educators/migration_wip/images/display-name.png b/source/_images/educator_how_tos/display-name.png similarity index 100% rename from source/educators/migration_wip/images/display-name.png rename to source/_images/educator_how_tos/display-name.png diff --git a/source/educators/migration_wip/images/display_names_problem.png b/source/_images/educator_how_tos/display_names_problem.png similarity index 100% rename from source/educators/migration_wip/images/display_names_problem.png rename to source/_images/educator_how_tos/display_names_problem.png diff --git a/source/educators/migration_wip/images/drag_child_component.png b/source/_images/educator_how_tos/drag_child_component.png similarity index 100% rename from source/educators/migration_wip/images/drag_child_component.png rename to source/_images/educator_how_tos/drag_child_component.png diff --git a/source/educators/migration_wip/images/edx_discussions_configurations_page.png b/source/_images/educator_how_tos/edx_discussions_configurations_page.png similarity index 100% rename from source/educators/migration_wip/images/edx_discussions_configurations_page.png rename to source/_images/educator_how_tos/edx_discussions_configurations_page.png diff --git a/source/educators/migration_wip/images/enable-discussion.png b/source/_images/educator_how_tos/enable-discussion.png similarity index 100% rename from source/educators/migration_wip/images/enable-discussion.png rename to source/_images/educator_how_tos/enable-discussion.png diff --git a/source/educators/migration_wip/images/grade_range.png b/source/_images/educator_how_tos/grade_range.png similarity index 100% rename from source/educators/migration_wip/images/grade_range.png rename to source/_images/educator_how_tos/grade_range.png diff --git a/source/educators/migration_wip/images/grade_range_b.png b/source/_images/educator_how_tos/grade_range_b.png similarity index 100% rename from source/educators/migration_wip/images/grade_range_b.png rename to source/_images/educator_how_tos/grade_range_b.png diff --git a/source/educators/migration_wip/images/group-configuration-delete.png b/source/_images/educator_how_tos/group-configuration-delete.png similarity index 100% rename from source/educators/migration_wip/images/group-configuration-delete.png rename to source/_images/educator_how_tos/group-configuration-delete.png diff --git a/source/educators/migration_wip/images/group_configurations_edit.png b/source/_images/educator_how_tos/group_configurations_edit.png similarity index 100% rename from source/educators/migration_wip/images/group_configurations_edit.png rename to source/_images/educator_how_tos/group_configurations_edit.png diff --git a/source/educators/migration_wip/images/group_configurations_experiments.png b/source/_images/educator_how_tos/group_configurations_experiments.png similarity index 100% rename from source/educators/migration_wip/images/group_configurations_experiments.png rename to source/_images/educator_how_tos/group_configurations_experiments.png diff --git a/source/educators/migration_wip/images/group_configurations_one_listed.png b/source/_images/educator_how_tos/group_configurations_one_listed.png similarity index 100% rename from source/educators/migration_wip/images/group_configurations_one_listed.png rename to source/_images/educator_how_tos/group_configurations_one_listed.png diff --git a/source/educators/migration_wip/images/inactive_groups.png b/source/_images/educator_how_tos/inactive_groups.png similarity index 100% rename from source/educators/migration_wip/images/inactive_groups.png rename to source/_images/educator_how_tos/inactive_groups.png diff --git a/source/educators/migration_wip/images/open_course.png b/source/_images/educator_how_tos/open_course.png similarity index 100% rename from source/educators/migration_wip/images/open_course.png rename to source/_images/educator_how_tos/open_course.png diff --git a/source/educators/migration_wip/images/outline-delete.png b/source/_images/educator_how_tos/outline-delete.png similarity index 100% rename from source/educators/migration_wip/images/outline-delete.png rename to source/_images/educator_how_tos/outline-delete.png diff --git a/source/educators/migration_wip/images/outline-drag-new-location-collapsed.png b/source/_images/educator_how_tos/outline-drag-new-location-collapsed.png similarity index 100% rename from source/educators/migration_wip/images/outline-drag-new-location-collapsed.png rename to source/_images/educator_how_tos/outline-drag-new-location-collapsed.png diff --git a/source/educators/migration_wip/images/outline-drag-new-location.png b/source/_images/educator_how_tos/outline-drag-new-location.png similarity index 100% rename from source/educators/migration_wip/images/outline-drag-new-location.png rename to source/_images/educator_how_tos/outline-drag-new-location.png diff --git a/source/educators/migration_wip/images/outline-drag-select.png b/source/_images/educator_how_tos/outline-drag-select.png similarity index 100% rename from source/educators/migration_wip/images/outline-drag-select.png rename to source/_images/educator_how_tos/outline-drag-select.png diff --git a/source/educators/migration_wip/images/outline-publish-icon-section.png b/source/_images/educator_how_tos/outline-publish-icon-section.png similarity index 100% rename from source/educators/migration_wip/images/outline-publish-icon-section.png rename to source/_images/educator_how_tos/outline-publish-icon-section.png diff --git a/source/educators/migration_wip/images/outline-publish-icon-subsection.png b/source/_images/educator_how_tos/outline-publish-icon-subsection.png similarity index 100% rename from source/educators/migration_wip/images/outline-publish-icon-subsection.png rename to source/_images/educator_how_tos/outline-publish-icon-subsection.png diff --git a/source/educators/migration_wip/images/outline-publish-icon-unit.png b/source/_images/educator_how_tos/outline-publish-icon-unit.png similarity index 100% rename from source/educators/migration_wip/images/outline-publish-icon-unit.png rename to source/_images/educator_how_tos/outline-publish-icon-unit.png diff --git a/source/educators/migration_wip/images/outline-publish-icons.png b/source/_images/educator_how_tos/outline-publish-icons.png similarity index 100% rename from source/educators/migration_wip/images/outline-publish-icons.png rename to source/_images/educator_how_tos/outline-publish-icons.png diff --git a/source/educators/migration_wip/images/outline-unit-settings.png b/source/_images/educator_how_tos/outline-unit-settings.png similarity index 100% rename from source/educators/migration_wip/images/outline-unit-settings.png rename to source/_images/educator_how_tos/outline-unit-settings.png diff --git a/source/educators/migration_wip/images/post-anonymously.png b/source/_images/educator_how_tos/post-anonymously.png similarity index 100% rename from source/educators/migration_wip/images/post-anonymously.png rename to source/_images/educator_how_tos/post-anonymously.png diff --git a/source/_images/educator_how_tos/post_visible_all.png b/source/_images/educator_how_tos/post_visible_all.png new file mode 100644 index 000000000..3435a1df6 Binary files /dev/null and b/source/_images/educator_how_tos/post_visible_all.png differ diff --git a/source/_images/educator_how_tos/post_visible_group.png b/source/_images/educator_how_tos/post_visible_group.png new file mode 100644 index 000000000..821672dd8 Binary files /dev/null and b/source/_images/educator_how_tos/post_visible_group.png differ diff --git a/source/educators/migration_wip/images/prerequisite-percent-complete.png b/source/_images/educator_how_tos/prerequisite-percent-complete.png similarity index 100% rename from source/educators/migration_wip/images/prerequisite-percent-complete.png rename to source/_images/educator_how_tos/prerequisite-percent-complete.png diff --git a/source/educators/migration_wip/images/raw_html_editor.png b/source/_images/educator_how_tos/raw_html_editor.png similarity index 100% rename from source/educators/migration_wip/images/raw_html_editor.png rename to source/_images/educator_how_tos/raw_html_editor.png diff --git a/source/educators/migration_wip/images/save-group-config.png b/source/_images/educator_how_tos/save-group-config.png similarity index 100% rename from source/educators/migration_wip/images/save-group-config.png rename to source/_images/educator_how_tos/save-group-config.png diff --git a/source/educators/migration_wip/images/section-delete.png b/source/_images/educator_how_tos/section-delete.png similarity index 100% rename from source/educators/migration_wip/images/section-delete.png rename to source/_images/educator_how_tos/section-delete.png diff --git a/source/educators/migration_wip/images/section-edit-icon.png b/source/_images/educator_how_tos/section-edit-icon.png similarity index 100% rename from source/educators/migration_wip/images/section-edit-icon.png rename to source/_images/educator_how_tos/section-edit-icon.png diff --git a/source/educators/migration_wip/images/section-settings-box.png b/source/_images/educator_how_tos/section-settings-box.png similarity index 100% rename from source/educators/migration_wip/images/section-settings-box.png rename to source/_images/educator_how_tos/section-settings-box.png diff --git a/source/educators/migration_wip/images/settings-icons.png b/source/_images/educator_how_tos/settings-icons.png similarity index 100% rename from source/educators/migration_wip/images/settings-icons.png rename to source/_images/educator_how_tos/settings-icons.png diff --git a/source/educators/migration_wip/images/studio-locked-content.png b/source/_images/educator_how_tos/studio-locked-content.png similarity index 100% rename from source/educators/migration_wip/images/studio-locked-content.png rename to source/_images/educator_how_tos/studio-locked-content.png diff --git a/source/educators/migration_wip/images/subsection-delete.png b/source/_images/educator_how_tos/subsection-delete.png similarity index 100% rename from source/educators/migration_wip/images/subsection-delete.png rename to source/_images/educator_how_tos/subsection-delete.png diff --git a/source/educators/migration_wip/images/subsections-settings-icon.png b/source/_images/educator_how_tos/subsections-settings-icon.png similarity index 100% rename from source/educators/migration_wip/images/subsections-settings-icon.png rename to source/_images/educator_how_tos/subsections-settings-icon.png diff --git a/source/_images/educator_how_tos/subsections-settings-icon.textClipping b/source/_images/educator_how_tos/subsections-settings-icon.textClipping new file mode 100644 index 000000000..a704ba619 Binary files /dev/null and b/source/_images/educator_how_tos/subsections-settings-icon.textClipping differ diff --git a/source/educators/migration_wip/images/unit-access-groupselected.png b/source/_images/educator_how_tos/unit-access-groupselected.png similarity index 100% rename from source/educators/migration_wip/images/unit-access-groupselected.png rename to source/_images/educator_how_tos/unit-access-groupselected.png diff --git a/source/educators/migration_wip/images/unit-access-indicator.png b/source/_images/educator_how_tos/unit-access-indicator.png similarity index 100% rename from source/educators/migration_wip/images/unit-access-indicator.png rename to source/_images/educator_how_tos/unit-access-indicator.png diff --git a/source/educators/migration_wip/images/unit-access-settings-gear-icon.png b/source/_images/educator_how_tos/unit-access-settings-gear-icon.png similarity index 100% rename from source/educators/migration_wip/images/unit-access-settings-gear-icon.png rename to source/_images/educator_how_tos/unit-access-settings-gear-icon.png diff --git a/source/educators/migration_wip/images/unit-access-settings.png b/source/_images/educator_how_tos/unit-access-settings.png similarity index 100% rename from source/educators/migration_wip/images/unit-access-settings.png rename to source/_images/educator_how_tos/unit-access-settings.png diff --git a/source/educators/migration_wip/images/unit-configure-icon.png b/source/_images/educator_how_tos/unit-configure-icon.png similarity index 100% rename from source/educators/migration_wip/images/unit-configure-icon.png rename to source/_images/educator_how_tos/unit-configure-icon.png diff --git a/source/educators/migration_wip/images/unit-delete.png b/source/_images/educator_how_tos/unit-delete.png similarity index 100% rename from source/educators/migration_wip/images/unit-delete.png rename to source/_images/educator_how_tos/unit-delete.png diff --git a/source/educators/migration_wip/images/unit-drag-moved.png b/source/_images/educator_how_tos/unit-drag-moved.png similarity index 100% rename from source/educators/migration_wip/images/unit-drag-moved.png rename to source/_images/educator_how_tos/unit-drag-moved.png diff --git a/source/educators/migration_wip/images/unit-drag-selected.png b/source/_images/educator_how_tos/unit-drag-selected.png similarity index 100% rename from source/educators/migration_wip/images/unit-drag-selected.png rename to source/_images/educator_how_tos/unit-drag-selected.png diff --git a/source/educators/migration_wip/images/unit-dup.png b/source/_images/educator_how_tos/unit-dup.png similarity index 100% rename from source/educators/migration_wip/images/unit-dup.png rename to source/_images/educator_how_tos/unit-dup.png diff --git a/source/educators/migration_wip/images/unit-edit-icon.png b/source/_images/educator_how_tos/unit-edit-icon.png similarity index 100% rename from source/educators/migration_wip/images/unit-edit-icon.png rename to source/_images/educator_how_tos/unit-edit-icon.png diff --git a/source/educators/migration_wip/images/unit-edit.png b/source/_images/educator_how_tos/unit-edit.png similarity index 100% rename from source/educators/migration_wip/images/unit-edit.png rename to source/_images/educator_how_tos/unit-edit.png diff --git a/source/educators/migration_wip/images/unit_location.png b/source/_images/educator_how_tos/unit_location.png similarity index 100% rename from source/educators/migration_wip/images/unit_location.png rename to source/_images/educator_how_tos/unit_location.png diff --git a/source/educators/migration_wip/images/AccessibilityCheckerWidget.png b/source/_images/educator_references/AccessibilityCheckerWidget.png similarity index 100% rename from source/educators/migration_wip/images/AccessibilityCheckerWidget.png rename to source/_images/educator_references/AccessibilityCheckerWidget.png diff --git a/source/educators/migration_wip/images/Grade-Report-with-enroll-status.png b/source/_images/educator_references/Grade-Report-with-enroll-status.png similarity index 100% rename from source/educators/migration_wip/images/Grade-Report-with-enroll-status.png rename to source/_images/educator_references/Grade-Report-with-enroll-status.png diff --git a/source/educators/migration_wip/images/Groups_ViewCourseAs.png b/source/_images/educator_references/Groups_ViewCourseAs.png similarity index 100% rename from source/educators/migration_wip/images/Groups_ViewCourseAs.png rename to source/_images/educator_references/Groups_ViewCourseAs.png diff --git a/source/educators/migration_wip/images/HTML_VisualView_Toolbar.png b/source/_images/educator_references/HTML_VisualView_Toolbar.png similarity index 100% rename from source/educators/migration_wip/images/HTML_VisualView_Toolbar.png rename to source/_images/educator_references/HTML_VisualView_Toolbar.png diff --git a/source/educators/migration_wip/images/HTMLandDisc.png b/source/_images/educator_references/HTMLandDisc.png similarity index 100% rename from source/educators/migration_wip/images/HTMLandDisc.png rename to source/_images/educator_references/HTMLandDisc.png diff --git a/source/educators/migration_wip/images/Pacing_COIndicator.png b/source/_images/educator_references/Pacing_COIndicator.png similarity index 100% rename from source/educators/migration_wip/images/Pacing_COIndicator.png rename to source/_images/educator_references/Pacing_COIndicator.png diff --git a/source/educators/migration_wip/images/Pacing_CustomPacing.png b/source/_images/educator_references/Pacing_CustomPacing.png similarity index 100% rename from source/educators/migration_wip/images/Pacing_CustomPacing.png rename to source/_images/educator_references/Pacing_CustomPacing.png diff --git a/source/educators/migration_wip/images/Pacing_DefaultPacing.png b/source/_images/educator_references/Pacing_DefaultPacing.png similarity index 100% rename from source/educators/migration_wip/images/Pacing_DefaultPacing.png rename to source/_images/educator_references/Pacing_DefaultPacing.png diff --git a/source/educators/migration_wip/images/Pacing_StepOne.png b/source/_images/educator_references/Pacing_StepOne.png similarity index 100% rename from source/educators/migration_wip/images/Pacing_StepOne.png rename to source/_images/educator_references/Pacing_StepOne.png diff --git a/source/educators/migration_wip/images/Pacing_StepTwo.png b/source/_images/educator_references/Pacing_StepTwo.png similarity index 100% rename from source/educators/migration_wip/images/Pacing_StepTwo.png rename to source/_images/educator_references/Pacing_StepTwo.png diff --git a/source/educators/migration_wip/images/Pacing_SubSettingsWithCustomPacing.png b/source/_images/educator_references/Pacing_SubSettingsWithCustomPacing.png similarity index 100% rename from source/educators/migration_wip/images/Pacing_SubSettingsWithCustomPacing.png rename to source/_images/educator_references/Pacing_SubSettingsWithCustomPacing.png diff --git a/source/educators/migration_wip/images/PrereqAboutPage.png b/source/_images/educator_references/PrereqAboutPage.png similarity index 100% rename from source/educators/migration_wip/images/PrereqAboutPage.png rename to source/_images/educator_references/PrereqAboutPage.png diff --git a/source/educators/migration_wip/images/Prereq_StudentDashboard.png b/source/_images/educator_references/Prereq_StudentDashboard.png similarity index 100% rename from source/educators/migration_wip/images/Prereq_StudentDashboard.png rename to source/_images/educator_references/Prereq_StudentDashboard.png diff --git a/source/educators/migration_wip/images/Problem_Grade_Report_Example.png b/source/_images/educator_references/Problem_Grade_Report_Example.png similarity index 100% rename from source/educators/migration_wip/images/Problem_Grade_Report_Example.png rename to source/_images/educator_references/Problem_Grade_Report_Example.png diff --git a/source/educators/migration_wip/images/Progress_CertificateStatus.png b/source/_images/educator_references/Progress_CertificateStatus.png similarity index 100% rename from source/educators/migration_wip/images/Progress_CertificateStatus.png rename to source/_images/educator_references/Progress_CertificateStatus.png diff --git a/source/educators/migration_wip/images/Progress_CompletionChart.png b/source/_images/educator_references/Progress_CompletionChart.png similarity index 100% rename from source/educators/migration_wip/images/Progress_CompletionChart.png rename to source/_images/educator_references/Progress_CompletionChart.png diff --git a/source/educators/migration_wip/images/Progress_DetailedGrades.png b/source/_images/educator_references/Progress_DetailedGrades.png similarity index 100% rename from source/educators/migration_wip/images/Progress_DetailedGrades.png rename to source/_images/educator_references/Progress_DetailedGrades.png diff --git a/source/educators/migration_wip/images/Progress_GradeSummary.png b/source/_images/educator_references/Progress_GradeSummary.png similarity index 100% rename from source/educators/migration_wip/images/Progress_GradeSummary.png rename to source/_images/educator_references/Progress_GradeSummary.png diff --git a/source/educators/migration_wip/images/Progress_Grades.png b/source/_images/educator_references/Progress_Grades.png similarity index 100% rename from source/educators/migration_wip/images/Progress_Grades.png rename to source/_images/educator_references/Progress_Grades.png diff --git a/source/educators/migration_wip/images/Progress_tab.png b/source/_images/educator_references/Progress_tab.png similarity index 100% rename from source/educators/migration_wip/images/Progress_tab.png rename to source/_images/educator_references/Progress_tab.png diff --git a/source/educators/migration_wip/images/UnitIdentifier.png b/source/_images/educator_references/UnitIdentifier.png similarity index 100% rename from source/educators/migration_wip/images/UnitIdentifier.png rename to source/_images/educator_references/UnitIdentifier.png diff --git a/source/educators/migration_wip/images/Units_LMS.png b/source/_images/educator_references/Units_LMS.png similarity index 100% rename from source/educators/migration_wip/images/Units_LMS.png rename to source/_images/educator_references/Units_LMS.png diff --git a/source/educators/migration_wip/images/about-page-course-start.png b/source/_images/educator_references/about-page-course-start.png similarity index 100% rename from source/educators/migration_wip/images/about-page-course-start.png rename to source/_images/educator_references/about-page-course-start.png diff --git a/source/educators/migration_wip/images/about_page.png b/source/_images/educator_references/about_page.png similarity index 100% rename from source/educators/migration_wip/images/about_page.png rename to source/_images/educator_references/about_page.png diff --git a/source/educators/migration_wip/images/child-components-a.png b/source/_images/educator_references/child-components-a.png similarity index 100% rename from source/educators/migration_wip/images/child-components-a.png rename to source/_images/educator_references/child-components-a.png diff --git a/source/educators/migration_wip/images/component_container.png b/source/_images/educator_references/component_container.png similarity index 100% rename from source/educators/migration_wip/images/component_container.png rename to source/_images/educator_references/component_container.png diff --git a/source/educators/migration_wip/images/course_dates.png b/source/_images/educator_references/course_dates.png similarity index 100% rename from source/educators/migration_wip/images/course_dates.png rename to source/_images/educator_references/course_dates.png diff --git a/source/educators/migration_wip/images/course_grades_page_assignmenttypes.png b/source/_images/educator_references/course_grades_page_assignmenttypes.png similarity index 100% rename from source/educators/migration_wip/images/course_grades_page_assignmenttypes.png rename to source/_images/educator_references/course_grades_page_assignmenttypes.png diff --git a/source/_images/educator_references/course_license.png b/source/_images/educator_references/course_license.png new file mode 100644 index 000000000..d43f6ed3e Binary files /dev/null and b/source/_images/educator_references/course_license.png differ diff --git a/source/_images/educator_references/creative-commons-license-course.png b/source/_images/educator_references/creative-commons-license-course.png new file mode 100644 index 000000000..0a316db63 Binary files /dev/null and b/source/_images/educator_references/creative-commons-license-course.png differ diff --git a/source/educators/migration_wip/images/dashboard-course-start-and-end.png b/source/_images/educator_references/dashboard-course-start-and-end.png similarity index 100% rename from source/educators/migration_wip/images/dashboard-course-start-and-end.png rename to source/_images/educator_references/dashboard-course-start-and-end.png diff --git a/source/educators/migration_wip/images/learner_course_license.png b/source/_images/educator_references/learner_course_license.png similarity index 100% rename from source/educators/migration_wip/images/learner_course_license.png rename to source/_images/educator_references/learner_course_license.png diff --git a/source/educators/migration_wip/images/learner_video_license.png b/source/_images/educator_references/learner_video_license.png similarity index 100% rename from source/educators/migration_wip/images/learner_video_license.png rename to source/_images/educator_references/learner_video_license.png diff --git a/source/educators/migration_wip/images/nested_components_student_view.png b/source/_images/educator_references/nested_components_student_view.png similarity index 100% rename from source/educators/migration_wip/images/nested_components_student_view.png rename to source/_images/educator_references/nested_components_student_view.png diff --git a/source/educators/migration_wip/images/outline-expand-collapse.png b/source/_images/educator_references/outline-expand-collapse.png similarity index 100% rename from source/educators/migration_wip/images/outline-expand-collapse.png rename to source/_images/educator_references/outline-expand-collapse.png diff --git a/source/educators/migration_wip/images/outline-with-units.png b/source/_images/educator_references/outline-with-units.png similarity index 100% rename from source/educators/migration_wip/images/outline-with-units.png rename to source/_images/educator_references/outline-with-units.png diff --git a/source/educators/migration_wip/images/student_answer_calc.png b/source/_images/educator_references/student_answer_calc.png similarity index 100% rename from source/educators/migration_wip/images/student_answer_calc.png rename to source/_images/educator_references/student_answer_calc.png diff --git a/source/educators/migration_wip/images/student_answer_excel.png b/source/_images/educator_references/student_answer_excel.png similarity index 100% rename from source/educators/migration_wip/images/student_answer_excel.png rename to source/_images/educator_references/student_answer_excel.png diff --git a/source/educators/migration_wip/images/unit-hide.png b/source/_images/educator_references/unit-hide.png similarity index 100% rename from source/educators/migration_wip/images/unit-hide.png rename to source/_images/educator_references/unit-hide.png diff --git a/source/educators/migration_wip/images/unit-never-published.png b/source/_images/educator_references/unit-never-published.png similarity index 100% rename from source/educators/migration_wip/images/unit-never-published.png rename to source/_images/educator_references/unit-never-published.png diff --git a/source/educators/migration_wip/images/unit-page.png b/source/_images/educator_references/unit-page.png similarity index 100% rename from source/educators/migration_wip/images/unit-page.png rename to source/_images/educator_references/unit-page.png diff --git a/source/educators/migration_wip/images/unit-pending-changes.png b/source/_images/educator_references/unit-pending-changes.png similarity index 100% rename from source/educators/migration_wip/images/unit-pending-changes.png rename to source/_images/educator_references/unit-pending-changes.png diff --git a/source/educators/migration_wip/images/unit-published.png b/source/_images/educator_references/unit-published.png similarity index 100% rename from source/educators/migration_wip/images/unit-published.png rename to source/_images/educator_references/unit-published.png diff --git a/source/educators/migration_wip/images/unit-published_unreleased.png b/source/_images/educator_references/unit-published_unreleased.png similarity index 100% rename from source/educators/migration_wip/images/unit-published_unreleased.png rename to source/_images/educator_references/unit-published_unreleased.png diff --git a/source/educators/migration_wip/images/workflow-create-content.png b/source/_images/educator_references/workflow-create-content.png similarity index 100% rename from source/educators/migration_wip/images/workflow-create-content.png rename to source/_images/educator_references/workflow-create-content.png diff --git a/source/educators/migration_wip/images/workflow-create-unit.png b/source/_images/educator_references/workflow-create-unit.png similarity index 100% rename from source/educators/migration_wip/images/workflow-create-unit.png rename to source/_images/educator_references/workflow-create-unit.png diff --git a/source/educators/migration_wip/images/workflow-revise-content.png b/source/_images/educator_references/workflow-revise-content.png similarity index 100% rename from source/educators/migration_wip/images/workflow-revise-content.png rename to source/_images/educator_references/workflow-revise-content.png diff --git a/source/_tags/tagsindex.rst b/source/_tags/tagsindex.rst new file mode 100644 index 000000000..987b6c635 --- /dev/null +++ b/source/_tags/tagsindex.rst @@ -0,0 +1,11 @@ +:orphan: + +.. _tagoverview: + +Tags overview +############# + +.. toctree:: + :caption: Tags + :maxdepth: 1 + diff --git a/source/educators/migration_wip/1_general_information/edx_site.rst b/source/community/how-tos/receive_announcements_by_email.rst similarity index 79% rename from source/educators/migration_wip/1_general_information/edx_site.rst rename to source/community/how-tos/receive_announcements_by_email.rst index dc6d2de33..9438ba52d 100644 --- a/source/educators/migration_wip/1_general_information/edx_site.rst +++ b/source/community/how-tos/receive_announcements_by_email.rst @@ -1,8 +1,8 @@ -.. :diataxis-type: reference +.. :diataxis-type: how-to -*********************** -The Open edX Site -*********************** +************************************************* +Receive Open edX Platform Announcements by Email +************************************************* The `Open edX Portal`_ is the destination for learning about hosting an Open edX instance, extending the Open edX platform, and contributing to the Open edX project. In @@ -12,10 +12,6 @@ community resources. All users can view content on the Open edX site without creating an account and logging in. -=============================== -Release Announcements by Email -=============================== - To receive and share product and release announcements by email, you can subscribe to announcements on one of the edX portal sites. @@ -30,4 +26,4 @@ subscribe to announcements on one of the edX portal sites. You will now receive email messages when new announcements of the types you selected are posted. -.. include:: ../links/links.rst +.. include:: ../../educators/migration_wip/links/links.rst diff --git a/source/community/index.rst b/source/community/index.rst index 209ba7a51..e87bc1e84 100644 --- a/source/community/index.rst +++ b/source/community/index.rst @@ -6,3 +6,4 @@ Community Home release_notes/index security_policy/index + how-tos/receive_announcements_by_email diff --git a/source/educators/migration_wip/5_accessibility/edX_accessib_guidelines.rst b/source/educators/concepts/accessibility/accessibility_guidelines.rst similarity index 88% rename from source/educators/migration_wip/5_accessibility/edX_accessib_guidelines.rst rename to source/educators/concepts/accessibility/accessibility_guidelines.rst index 7d6e9b8d5..87d1e3d56 100644 --- a/source/educators/migration_wip/5_accessibility/edX_accessib_guidelines.rst +++ b/source/educators/concepts/accessibility/accessibility_guidelines.rst @@ -1,9 +1,13 @@ +.. :diataxis-type: concept + .. _edX Accessibility Guidelines: =============================================================== What Is The edX Accessibility Best Practices Guidance Based On? =============================================================== +.. note:: This content has been migrated from legacy edx.org docs and has not yet been adjusted for the Open edX® Community + edX measures and evaluates accessibility primarily using the World Wide Web Consortium's `Web Content Accessibility Guidelines (WCAG) 2.1 `_ (05 June 2018). All features that are merged into edX repositories are @@ -37,4 +41,12 @@ support. These trained professionals typically provide the following services, w For more information, see the following topics. * :ref:`Supporting Learners with Diverse Needs` -* :ref:`Accessibility Best Practices for Course Content Development` \ No newline at end of file +* :ref:`Accessibility Best Practices for Course Content Development` + +.. seealso:: + :class: dropdown + + :ref:`Accessibility Best Practices for Course Content Development` (concept) + :ref:`Designing for Mobile` (concept) + :ref:`Supporting Learners with Diverse Needs` (concept) + :ref:`Accessibility Checker` (reference) \ No newline at end of file diff --git a/source/educators/migration_wip/5_accessibility/best_practices_course_content_dev.rst b/source/educators/concepts/accessibility/best_practices_course_content_dev.rst similarity index 99% rename from source/educators/migration_wip/5_accessibility/best_practices_course_content_dev.rst rename to source/educators/concepts/accessibility/best_practices_course_content_dev.rst index 00385921f..58b2e9531 100644 --- a/source/educators/migration_wip/5_accessibility/best_practices_course_content_dev.rst +++ b/source/educators/concepts/accessibility/best_practices_course_content_dev.rst @@ -1052,4 +1052,12 @@ guidelines. Universal Design for Learning Resources ======================================= -* `The National Center on Universal Design for Learning `_ provides a helpful overview on Universal Design for Learning. \ No newline at end of file +* `The National Center on Universal Design for Learning `_ provides a helpful overview on Universal Design for Learning. + +.. seealso:: + :class: dropdown + + :ref:`edX Accessibility Guidelines` (concept) + :ref:`Designing for Mobile` (concept) + :ref:`Supporting Learners with Diverse Needs` (concept) + :ref:`Accessibility Checker` (reference) \ No newline at end of file diff --git a/source/educators/migration_wip/4_reaching_learners/design_for_mobile.rst b/source/educators/concepts/accessibility/design_for_mobile.rst similarity index 87% rename from source/educators/migration_wip/4_reaching_learners/design_for_mobile.rst rename to source/educators/concepts/accessibility/design_for_mobile.rst index 24549d6d2..7a399f2a9 100644 --- a/source/educators/migration_wip/4_reaching_learners/design_for_mobile.rst +++ b/source/educators/concepts/accessibility/design_for_mobile.rst @@ -1,9 +1,20 @@ -.. :diataxis-type: reference +.. :diataxis-type: concept + +.. _Designing for Mobile: ############################################### Designing Your Course For a Mobile Experience ############################################### +Keep in +mind that the courses and course content that you create should be accessible +to everyone, regardless of any physical limitation that they might have, and +regardless whether they are accessing your course using a Web browser or using +mobile apps. + +For information about accessibility best practices, see :ref:`Accessibility +Index `. + The percentage of learners who access MOOCs using smartphones is increasing every day. Most courses on edx.org can be viewed on smartphones using the edX Android and iPhone apps, although we still recommend that learners complete @@ -87,4 +98,12 @@ renders as you expect it to. .. note:: Keep in mind that course updates that you make might not be immediately reflected in the edX mobile apps. In particular, newly - published content can take up to an hour to update on the Android app. \ No newline at end of file + published content can take up to an hour to update on the Android app. + +.. seealso:: + :class: dropdown + + :ref:`Accessibility Best Practices for Course Content Development` (concept) + :ref:`edX Accessibility Guidelines` (concept) + :ref:`Supporting Learners with Diverse Needs` (concept) + :ref:`Accessibility Checker` (reference) \ No newline at end of file diff --git a/source/educators/concepts/accessibility/index.rst b/source/educators/concepts/accessibility/index.rst new file mode 100644 index 000000000..7f765890d --- /dev/null +++ b/source/educators/concepts/accessibility/index.rst @@ -0,0 +1,24 @@ +.. _Accessibility: + +############################# +Accessibility +############################# + +Courses and course content developed on our platform should be accessible to +everyone, regardless of any physical limitation that they might have. + +The topics in this section are intended to help course teams understand how to +develop courses that can serve the widest possible audience. + +.. note:: Course teams should familiarize themselves with this best practices + guidance and distribute it to any members of their teams who are + responsible for creating course content. + +.. toctree:: + :maxdepth: 1 + :glob: + + best_practices_course_content_dev + supporting_learners_diverse_needs + accessibility_guidelines + design_for_mobile \ No newline at end of file diff --git a/source/educators/migration_wip/5_accessibility/supporting_learners_diverse_needs.rst b/source/educators/concepts/accessibility/supporting_learners_diverse_needs.rst similarity index 95% rename from source/educators/migration_wip/5_accessibility/supporting_learners_diverse_needs.rst rename to source/educators/concepts/accessibility/supporting_learners_diverse_needs.rst index df8b63f0b..53d319cea 100644 --- a/source/educators/migration_wip/5_accessibility/supporting_learners_diverse_needs.rst +++ b/source/educators/concepts/accessibility/supporting_learners_diverse_needs.rst @@ -83,4 +83,12 @@ from supporting on-campus students, we encourage you to develop a plan to respond to students who inform you of accessibility barriers to learning. However, given the large numbers of learners enrolling in many of the courses, you will quickly see how important it is to address accessibility concerns -when creating a course. \ No newline at end of file +when creating a course. + +.. seealso:: + :class: dropdown + + :ref:`Accessibility Best Practices for Course Content Development` (concept) + :ref:`edX Accessibility Guidelines` (concept) + :ref:`Designing for Mobile` (concept) + :ref:`Accessibility Checker` (reference) \ No newline at end of file diff --git a/source/educators/migration_wip/12_course_features/cohorts/cohorts_overview.rst b/source/educators/concepts/advanced_features/cohorts_overview.rst similarity index 96% rename from source/educators/migration_wip/12_course_features/cohorts/cohorts_overview.rst rename to source/educators/concepts/advanced_features/cohorts_overview.rst index 8df30d2d8..0819d5b6c 100644 --- a/source/educators/migration_wip/12_course_features/cohorts/cohorts_overview.rst +++ b/source/educators/concepts/advanced_features/cohorts_overview.rst @@ -1,3 +1,5 @@ +.. :diataxis-type: concept + .. _Cohorts Overview: ############################# @@ -263,7 +265,7 @@ discussion posts. If you want learners to see a different name for the default cohort, you can change its name. For details about renaming cohorts, see :ref:`Renaming a Cohort`. -.. image:: ../../images/post_visible_default.png +.. image:: /_images/educator_concepts/post_visible_default.png :alt: A discussion topic post with "This post is visible to Default Group" above the title. :width: 600 @@ -277,3 +279,13 @@ previously saw will seem to have "disappeared". To avoid negatively affecting the learner experience, any cohort assignment changes should be done as early in the course run as possible, so that learners' views of discussion posts and contributions remain consistent over time. + +.. seealso:: + :class: dropdown + + :ref:`Manage Course Cohorts` (how-to) + :ref:`Create Cohort Specific Course Content` (how-to) + :ref:`About Divided Discussions` (concept) + :ref:`Managing Divided Discussion Topics` (concept) + :ref:`Moderating_discussions` (concept) + :ref:`Setting Up Divided Discussions` (how-to) diff --git a/source/educators/migration_wip/12_course_features/content_experiments/content_experiments_overview.rst b/source/educators/concepts/advanced_features/content_experiments_overview.rst similarity index 91% rename from source/educators/migration_wip/12_course_features/content_experiments/content_experiments_overview.rst rename to source/educators/concepts/advanced_features/content_experiments_overview.rst index ba66c6f73..76a4e7f08 100644 --- a/source/educators/migration_wip/12_course_features/content_experiments/content_experiments_overview.rst +++ b/source/educators/concepts/advanced_features/content_experiments_overview.rst @@ -1,21 +1,11 @@ +.. :diataxis-type: concept + .. _Overview of Content Experiments: ################################# Overview of Content Experiments ################################# -This section provides an introduction to using content experiments. - -.. contents:: - :local: - :depth: 1 - -For more information, see :ref:`Configure Your Course for Content Experiments` -and :ref:`Add Content Experiments to Your Course`. - -********* -Overview -********* You use content experiments to show different course content to different groups of learners. Also known as "A/B tests" or "split tests", content @@ -28,6 +18,9 @@ from the instructor dashboard includes a column identifying the experiment group that each learner has been assigned to. For more information, see :ref:`Interpret the Grade Report`. +For more information, see :ref:`Configure Your Course for Content Experiments` +and :ref:`Add Content Experiments to Your Course`. + For information about analyzing events from content experiments, see :ref:`AB_Event_Types` in the *EdX Research Guide*. @@ -60,8 +53,8 @@ experiment to be independent and use a different grouping. To determine the available groupings of learners, you set up group configurations :ref:`using Studio ` -or :doc:`subsection_content_experiments_policies`. +or :ref:`Set Up Group Configuration for OLX Courses`. You then select which group configuration to use when you add a content experiment :ref:`using Studio ` or -:doc:`subsection_content_experiments_OLX`. +:ref:`Add a Content Experiment in OLX`. diff --git a/source/educators/concepts/advanced_features/group_configurations.rst b/source/educators/concepts/advanced_features/group_configurations.rst new file mode 100644 index 000000000..bda948e37 --- /dev/null +++ b/source/educators/concepts/advanced_features/group_configurations.rst @@ -0,0 +1,36 @@ +.. :diataxis-type: concept + +.. _Overview of Group Configurations: + +**************************************** +Overview of Group Configurations +**************************************** + +Before you can create :ref:`content experiments`, you must specify at least one group configuration for your +course. + +A group configuration defines how many groups of learners are in an experiment. +You can have any number of group configurations in your course. When you create +a content experiment, you select the group configuration to use. + +For example, you might want to run two different content experiments at +different times during your course. In one content experiment, learners either +see a video or complete a reading assignment. You can then include problems so +that you can see which group learned the material more completely. For this +content experiment, you need a group configuration that assigns your learners +to two experiment groups. + +In the other content experiment, you can present the same question using four +different types of problems. For this content experiment, you need a +group configuration that assigns your learners to four experiment groups. + +.. seealso:: + :class: dropdown + + :ref:`Offering Differentiated Content` (concept) + :ref:`Configure Your Course for Content Experiments` (how-to) + :ref:`Experiment Group Configurations` (reference) + :ref:`Add a Content Experiment in OLX` (how-to) + :ref:`Set Up Group Configuration for OLX Courses` (how-to) + :ref:`Guidelines for Modifying Group Configurations` (concept) \ No newline at end of file diff --git a/source/educators/migration_wip/12_course_features/content_experiments/subsection_content_experiments_group_modify_guidelines.rst b/source/educators/concepts/advanced_features/guidlines_modifying_group_configuration.rst similarity index 81% rename from source/educators/migration_wip/12_course_features/content_experiments/subsection_content_experiments_group_modify_guidelines.rst rename to source/educators/concepts/advanced_features/guidlines_modifying_group_configuration.rst index 3dc41e116..ec072531c 100644 --- a/source/educators/migration_wip/12_course_features/content_experiments/subsection_content_experiments_group_modify_guidelines.rst +++ b/source/educators/concepts/advanced_features/guidlines_modifying_group_configuration.rst @@ -1,4 +1,6 @@ +.. :diataxis-type: concept .. Section is shared in CA and OLX guides +.. _Guidelines for Modifying Group Configurations: ********************************************* Guidelines for Modifying Group Configurations @@ -46,3 +48,14 @@ the problems in the experiment group content to which they are reassigned. Removing an experiment group affects event data for the course. Ensure that researchers who are evaluating your course results are aware of the experiment group that you removed and the date on which you removed it. + + +.. seealso:: + :class: dropdown + + :ref:`Offering Differentiated Content` (concept) + :ref:`Overview of Content Experiments` (concept) + :ref:`Configure Your Course for Content Experiments` (how-to) + :ref:`Experiment Group Configurations` (reference) + :ref:`Add a Content Experiment in OLX` (how-to) + :ref:`Set Up Group Configuration for OLX Courses` (how-to) \ No newline at end of file diff --git a/source/educators/concepts/advanced_features/index.rst b/source/educators/concepts/advanced_features/index.rst new file mode 100644 index 000000000..b5bf2f4c7 --- /dev/null +++ b/source/educators/concepts/advanced_features/index.rst @@ -0,0 +1,9 @@ +############################# +Advanced Features +############################# + +.. toctree:: + :maxdepth: 1 + :glob: + + * \ No newline at end of file diff --git a/source/educators/migration_wip/12_course_features/diff_content/index.rst b/source/educators/concepts/advanced_features/offering_differentiated_content.rst similarity index 95% rename from source/educators/migration_wip/12_course_features/diff_content/index.rst rename to source/educators/concepts/advanced_features/offering_differentiated_content.rst index 09ac7b15c..874457c67 100644 --- a/source/educators/migration_wip/12_course_features/diff_content/index.rst +++ b/source/educators/concepts/advanced_features/offering_differentiated_content.rst @@ -1,3 +1,5 @@ +.. :diataxis-type: concept + .. _Offering Differentiated Content: ####################################################### @@ -65,3 +67,8 @@ customized course experience. For information about creating differentiated content using cohorts, see :ref:`Cohorts Overview` and :ref:`Cohorted Courseware Overview`. +.. seealso:: + :class: dropdown + + :ref:`Enrollment Track Specific Courseware Overview` (how-to) + diff --git a/source/educators/concepts/communication/about_divided_discussions.rst b/source/educators/concepts/communication/about_divided_discussions.rst new file mode 100644 index 000000000..252be1edc --- /dev/null +++ b/source/educators/concepts/communication/about_divided_discussions.rst @@ -0,0 +1,69 @@ +.. :diataxis-type: concept + +.. _About Divided Discussions: + +################################### +About Divided Discussion Topics +################################### + +This section provides information about setting up discussions that are +divided by learner groups (cohorts) within your course. + +.. contents:: + :local: + :depth: 1 + +For overview information about discussions in a course, see :ref:`Discussions`. + +For more information about creating differentiated course content for learners +in different groups (cohorts), see :ref:`Offering Differentiated Content`. + + +****************************** +What Are Divided Discussions? +****************************** + +With divided discussions, discussion topics are visible to all learners, but +the posts, responses, and comments within these topics are divided so that +learners participate in the discussion only with other members of the same +group (cohort). + +Discussion topics that are not divided are unified, meaning that all learners +in the course can see and respond to posts, responses, and comments from any +other learner in the course. + +======================================= +Best Practices for Divided Discussions +======================================= + +If you divide discussions, a good practice is to use a naming convention for +discussion topics, so that learners clearly understand the audience for a +discussion topic before they add posts to that topic. For information about +naming conventions, see :ref:`Apply Naming Conventions to Discussion Topics`. + +You can also appoint learners as Community TAs or Group Commmunity +TAs to help you to moderate course discussions. You might use Group +Community TAs if the content of discussion topics by one group (cohort) should not be +shared with another group. Group Community TAs are themselves members of +learner groups (cohorts) that you use in your course. As discussion moderators, they can +only see and respond to posts by other members of their own group (cohort). For information, +see :ref:`Assigning_discussion_roles`. + +For more information about managing discussions, see :ref:`Managing Divided +Discussion Topics` and :ref:`Running_discussions`. + +.. note:: + + Another method of providing different discussion experiences for learners in + different groups in your course is to use the access settings of discussion + components. For example, you can add multiple discussion components and use + each component's access settings to restrict access to each discussion + component to a specific content group. You can then assign these content + groups to learner groups (cohorts). For more information, + see :ref:`Setting Up Divided Discussions`. + +.. seealso:: + :class: dropdown + + :ref:`Setting Up Divided Discussions` (how-to) + \ No newline at end of file diff --git a/source/educators/concepts/communication/course_discussions.rst b/source/educators/concepts/communication/course_discussions.rst new file mode 100644 index 000000000..a5a763ead --- /dev/null +++ b/source/educators/concepts/communication/course_discussions.rst @@ -0,0 +1,107 @@ +.. :diataxis-type: concept + +.. _Discussions: + +About Course Discussions +########################### + +Discussions in an edX course include both course-wide topics of interest to +all learners (such as "Feedback", "Troubleshooting", or "Technical Help") as +well as content-specific topics that you add to course units as discussion +components. You can create both types of discussion topics in Studio. + +For information about creating discussion topics, see the following sections. + +For information about creating discussions in which learners in a group (cohort) +only interact with posts from other learners in the same group, +see :ref:`About Divided Discussions`. + +For information about running and moderating course discussions, see +:ref:`Running_discussions` and :ref:`Moderating_discussions`. + +.. _Visibility of Discussion Topics: + +Understanding When Learners Can See Discussion Topics +***************************************************** + +The names that you specify as the category and subcategory names for discussion +components are not visible on the Discussion page in the LMS until after +the course has started and the unit is released. + +However, "seed" posts that you create in content-specific discussion topics +before a course starts, or before the unit is released, are immediately visible +on the Discussion page, even though the containing category or subcategory +names are not visible. EdX recommends that you do not create posts in +content-specific discussion topics before a unit is released. For more +information about release dates and the visibility of components, see +:ref:`Controlling Content Visibility`. + +In contrast, :ref:`course-wide discussion topics` that you create on the edx discussions configuration page in Studio, +including the default "General" discussion topic, are immediately visible, +regardless of whether the course has started. They are not associated with any +particular section or subsection of the course, and are not subject to +release dates. + +.. _Discussions on Mobile Apps: + +Discussions in the edX Mobile App +********************************* + +Learners can participate in course discussions using the edX mobile app as +they do on the edX site, but there are some differences in the actions that +moderators can take in discussions using the mobile app. To perform moderation +or administrative tasks for your course discussions, you need to work in a web +browser. + +The following actions are not supported on the edX mobile apps. + + * Pinning posts + * Marking responses to question posts as answers + * Endorsing responses to discussion posts + * Closing posts + +.. _The Upgraded Discussion Forum: + +***************************************** +The Upgraded Discussion Forum +***************************************** + +Course runs created on or after May 16, 2023, use an upgraded version of +the edX discussion forum. Learn more about it `here`_. + +.. _here: https://openedx.atlassian.net/wiki/spaces/COMM/pages/3470655498/Discussions+upgrade+Sidebar+and+new+topic+structure. + +.. _Content Specific Discussion Topics: + +============================================ +Content-specific Discussion Topics (Legacy) +============================================ + +To create a content-specific discussion topic, you add a discussion component +to a unit. Typically, you do this while you are designing and creating your +course in Studio. Follow the instructions in :ref:`Working with Discussion +Components`. The result is a discussion topic associated with a unit and its +content. Learners can access content-specific topics both in the course unit +and on the Discussion page. + +.. warning:: Follow the recommended steps to add discussion components. Do not + create discussion topics by using the Duplicate button in Studio, and do + not reference the same discussion ID in more than one place in your course. + Duplicated discussion components result in discussion topics that contain the + same conversations, even if learners post in different discussion topics. + +For information about the visibility of content-specific discussion +topics, see :ref:`Visibility of Discussion Topics`. + +.. note:: In courses with cohorts enabled, when you add discussion components to + units in Studio, these discussion topics are by default unified. All learners + in the course can see and respond to posts from all other learners. You can + change content-specific discussion topics to be divided, so that only members + of the same group can see and respond to each other's posts. For information, + see :ref:`Divide All Content Specific Discussion Topics`. + +.. seealso:: + :class: dropdown + + :ref:`Configuring Edx Discussions` (how-to) diff --git a/source/educators/migration_wip/17_manage_discussions/discussion_guidance_moderators.rst b/source/educators/concepts/communication/discussion_guidance_moderators.rst similarity index 97% rename from source/educators/migration_wip/17_manage_discussions/discussion_guidance_moderators.rst rename to source/educators/concepts/communication/discussion_guidance_moderators.rst index 19eadf2e4..26e54ee90 100644 --- a/source/educators/migration_wip/17_manage_discussions/discussion_guidance_moderators.rst +++ b/source/educators/concepts/communication/discussion_guidance_moderators.rst @@ -1,3 +1,5 @@ +.. :diataxis-type: concept + .. _Guidance for Discussion Moderators: ###################################### @@ -170,3 +172,10 @@ Feature Requests * Search the discussions for other similar requests, and respond to and close those as well. + +.. seealso:: + :class: dropdown + + :ref:`Guidance for Discussion Moderators` (concept) + :ref:`Assigning_discussion_roles` (how-to) + :ref:`Administer Discussions` (how-to) diff --git a/source/educators/concepts/communication/index.rst b/source/educators/concepts/communication/index.rst new file mode 100644 index 000000000..cbd907038 --- /dev/null +++ b/source/educators/concepts/communication/index.rst @@ -0,0 +1,9 @@ +############################# +Communication +############################# + +.. toctree:: + :maxdepth: 1 + :glob: + + * \ No newline at end of file diff --git a/source/educators/migration_wip/17_manage_discussions/manage_divided_discussions.rst b/source/educators/concepts/communication/manage_divided_discussions.rst similarity index 91% rename from source/educators/migration_wip/17_manage_discussions/manage_divided_discussions.rst rename to source/educators/concepts/communication/manage_divided_discussions.rst index 86c4fb6c3..c396010ab 100644 --- a/source/educators/migration_wip/17_manage_discussions/manage_divided_discussions.rst +++ b/source/educators/concepts/communication/manage_divided_discussions.rst @@ -1,3 +1,5 @@ +.. :diataxis-type: concept + .. _Managing Divided Discussion Topics: ################################### @@ -29,20 +31,10 @@ particular group. For learners, this is the only noticeable difference between discussions in courses that use divided discussions, and courses that do not have groups and do not use divided discussions. -.. only:: Partners - - You can share the examples in the :ref:`Read the Group Indicator in Posts` - section with your learners. The `course discussions index`_ - section in the *EdX Learner's Guide* also provides useful information to help - learners make the most of their participation in course discussions. - -.. only:: Open_edX - - You can share the examples in the :ref:`Read the Group Indicator in Posts` - section with your learners. The `course discussions index`_ - section in the *Open edX Learner's Guide* also provides useful information to - help learners make the most of their participation in course discussions. - +You can share the examples in the :ref:`Read the Group Indicator in Posts` +section with your learners. The `course discussions index`_ +section in the *Open edX Learner's Guide* also provides useful information to +help learners make the most of their participation in course discussions. Course team members who have the Discussion Admin, Discussion Moderator, Community TA or Group Community TA role see the indicator of who can read each @@ -100,14 +92,14 @@ Every post includes a sentence that identifies whether everyone can see and contribute to it, or only the members of a group in the course. Examples follow. -.. image:: ../images/post_visible_all.png +.. image:: /_images/educator_concepts/post_visible_all.png :alt: A discussion topic post with the indicator "This post is visible to everyone". :width: 600 .. extra line -.. image:: ../images/post_visible_group.png +.. image:: /_images/educator_concepts/post_visible_group.png :alt: A discussion topic post with the indicator "This post is visible to Alumni". :width: 600 @@ -164,7 +156,7 @@ field. This example shows a new post being added to a content-specific discussion topic. -.. image:: ../images/discussion_add_post_group_selection.png +.. image:: /_images/educator_concepts/discussion_add_post_group_selection.png :alt: The fields and controls that appear when a course team member with discussion admin privileges clicks "Add a Post" for a divided topic. @@ -226,7 +218,7 @@ groups** filter is selected by default. You see every post when you make this selection. To limit the list so that you can view the same set of posts as the members of a particular group, select the name of that group. -.. image:: ../images/discussion_filter_by_groups.png +.. image:: /_images/educator_concepts/discussion_filter_by_groups.png :alt: An image showing the discussion navigation pane on the Discussion page, with a dropdown menu showing the options to select "in all groups" or a specific group by name. diff --git a/source/educators/migration_wip/17_manage_discussions/moderate_discussions.rst b/source/educators/concepts/communication/moderating_discussions.rst similarity index 52% rename from source/educators/migration_wip/17_manage_discussions/moderate_discussions.rst rename to source/educators/concepts/communication/moderating_discussions.rst index f5516eaa0..a079a5b01 100644 --- a/source/educators/migration_wip/17_manage_discussions/moderate_discussions.rst +++ b/source/educators/concepts/communication/moderating_discussions.rst @@ -1,3 +1,5 @@ +.. :diataxis-type: concept + .. _Moderating_discussions: ####################### @@ -105,78 +107,6 @@ the following roles. with a **Community TA** identifier. -.. _Assigning_discussion_roles: - -************************************* -Assigning Discussion Moderation Roles -************************************* - -You must either be the course author, or have the Admin role, to add people to -discussion moderation roles. - -You must obtain the email address or username for each person that you want to -add. - -* To obtain the email address or username for a course team member, in the LMS - select **Instructor**, then select **Membership**. In the **Course Team - Management** section, select the current course team role (Staff or Admin) of - the person whose information you are looking for. From the list of course - team members with the selected role locate the required email address or - username. - -* To obtain the email address or username for an enrolled learner, in the LMS - select **Instructor**, then select **Data Download**. In the - **Reports** section, select **Download profile information as a CSV**. In the - downloaded file, locate the required email address or username. - - -==================================== -Add Someone To a Discussion Role -==================================== - -You can add any user who is already enrolled in your course to a discussion -moderation role. - -.. note:: To add someone to the Discussion Admin role, you must be the course - author or a course team member who has the Admin role. - -#. View the live version of the course. - -#. Select **Instructor**, and then select **Membership**. - -#. In the **Course Team Management** section, select the discussion role that - you want to assign: **Discussion Admins**, **Discussion Moderators**, - **Group Community TA**, or **Community TA**. - -#. Under the list of users who currently have that role, enter the email address - or username of the person you want to add. - -#. Select **Add** for the role type. - - The person who you added appears in the list. - - -====================================== -Remove Someone from a Discussion Role -====================================== - -To remove someone from a discussion moderation role, you must be the course -author or have the Admin role. - -#. View the live version of the course. - -#. Select **Instructor**, and then select **Membership**. - -#. In the **Course Team Management** section, select the discussion role from - which you want to remove the user: **Discussion Admins**, **Discussion - Moderators**, **Group Community TA**, or **Community TA**. - -#. In the list of users who currently have that role, locate the user you - want to remove, and then select **Revoke access**. - - The person who you removed no longer appears in the list. - - ******************************* Provide Guidelines for Learners ******************************* @@ -186,20 +116,10 @@ them available to learners as a course handout file or on a defined page in your course. These guidelines can define your expectations and optionally introduce features of edX discussions. -.. only:: Partners - - You can also refer learners to the `course discussions index`_ - section in the *EdX Learner's Guide*. Consider referring learners in your - courses to that section, which describes the structure and features of edX - course discussions, and provides useful information to help learners make the - most of their participation in course discussions. - -.. only:: Open_edX - - You can also refer learners to the `course discussions index`_ section in the *Open EdX Learner's Guide*. Consider referring learners - in your courses to that section, which describes the structure and features of - edX course discussions, and provides useful information to help learners make - the most of their participation in course discussions. +You can also refer learners to the `course discussions index`_ section in the *Open EdX Learner's Guide*. Consider referring learners +in your courses to that section, which describes the structure and features of +edX course discussions, and provides useful information to help learners make +the most of their participation in course discussions. .. For a template that you can use to develop your own guidelines, see .. :ref:`Discussion Forum Guidelines`. @@ -265,7 +185,7 @@ dark gray titles and icons. When new responses and comments are made on posts that you have read, a "new" indicator displays with the number of new responses or comments that you have not yet read. -.. image:: ../images/Discussion_ReadUnreadNew.png +.. image:: /_images/educator_concepts/Discussion_ReadUnreadNew.png :width: 300 :alt: The discussion navigation pane, showing some unread and some read posts, including a post that has been read but now has additional new @@ -283,117 +203,9 @@ all** drop-down menu. * **Flagged**, to list only posts that learners have reported as inappropriate. +.. seealso:: + :class: dropdown -**************** -Edit Messages -**************** - -Team members with the Discussion Moderator, Discussion Admin, Community TA or -Group Community TA role can edit the content of posts, responses, and -comments. Messages that include spoilers or solutions, or that contain -inappropriate or off-topic material, should be edited quickly to remove text, -images, or links. - -.. removed note for open edx re edit behavior in mobile apps. Posts can -.. now be edited in the mobile apps (though ability depends on permissions) -.. CT April 25, 2016 - -#. View the live version of the course. - -#. On the **Discussions** page, open the post with the content that requires - editing. You can select a single topic from the drop-down list of - discussion topics, apply a filter, or search to locate the post. - -#. For the post or for the response or comment that you want to edit, select - the "More" icon and then **Edit**. - -#. Remove the problematic portion of the message, or replace it with standard - text such as "[REMOVED BY MODERATOR]". - -#. Communicate the reason for your change. For example, "Posting a solution - violates the honor code." - -**************** -Delete Messages -**************** - -Team members with the Discussion Moderator, Discussion Admin, Community TA or -Group Community TA role can delete posts, responses, or comments. It might be -more appropriate to delete rather than edit posts that consist of spam or -include abusive language. - -.. removed note for open edx re deletion behavior in mobile apps. Posts can -.. now be deleted in the mobile apps (though ability depends on permissions) -.. CT April 25, 2016 - -#. View the live version of the course. - -#. On the **Discussion** page, open the post with the content that requires - deletion. You can select a single topic from the drop-down list of - discussion topics, apply a filter, or search to locate the post. - -#. For the post or for the response or comment that you want to delete, select - the "More" icon and then **Delete**. - -#. Select **OK** to confirm the deletion. - -.. important:: If a message is threatening or indicates serious harmful - intent, contact campus security at your institution. Report the incident - before taking any other action. - - -******************************** -Respond to Reports of Misuse -******************************** - -Learners have the option to report contributions that they find inappropriate. -Team members with the Discussion Moderator, Discussion Admin, Community TA or -Group Community TA role can check for messages that have been flagged in this -way and edit or delete them as needed. - -.. removed note for open edx re flag behavior in mobile apps. Posts can -.. now be flagged in the mobile apps. CT April 25, 2016 - -#. View the live version of your course and select **Discussion** at the top of - the page. - -#. In the discussion navigation pane at the side of the page, use the filter - drop-down list (set to **Show all** by default) to select **Flagged**. - -#. Review listed posts. A post is listed if it or any of its responses or - comments has been reported. The reported contribution includes a - **Reported** identifier. - -#. Edit or delete the post, response, or comment. Alternatively, remove the - flag: select the "More" icon and then **Unreport**. - - -***************************************************** -View Profile Information for Discussion Participants -***************************************************** - -To find out more about a specific discussion participant, you can view that -learner's edX profile from their linked username on discussion posts. - -To access a learner's profile from a discussion post that they contributed, -follow these steps. - -#. On the **Discussion** page, select a username in a post, response, or - comment. - -#. On the discussion page for that learner, select the linked username. - -The learner's account profile page opens. Learners can have either a limited -profile or a full profile. - -For more information about profiles, see `SFD Dashboard `_. - - -**************** -Block Users -**************** - -If a learner repeatedly misuses course discussions despite being warned, you -can unenroll that learner from the course. For more information, see -:ref:`unenroll_student`. The learner cannot re-enroll in the course if the -enrollment period for the course is over. + :ref:`Guidance for Discussion Moderators` (concept) + :ref:`Assigning_discussion_roles` (how-to) + :ref:`Administer Discussions` (how-to) diff --git a/source/educators/migration_wip/17_manage_discussions/running_discussions.rst b/source/educators/concepts/communication/running_discussions.rst similarity index 78% rename from source/educators/migration_wip/17_manage_discussions/running_discussions.rst rename to source/educators/concepts/communication/running_discussions.rst index 1fc20e320..455c74268 100644 --- a/source/educators/migration_wip/17_manage_discussions/running_discussions.rst +++ b/source/educators/concepts/communication/running_discussions.rst @@ -1,5 +1,6 @@ -.. _Running_discussions: +.. :diataxis-type: concept +.. _Running_discussions: ############################ Running Course Discussions @@ -45,23 +46,12 @@ The dialog created by a post, its responses, and the comments on those responses is sometimes called a thread. Discussion threads are saved as part of the course history. -.. only:: Partners - - For information about participating in discussions, see the - `course discussions index`_ section in the *EdX Learner's Guide*. - Consider referring learners in your courses to that section, which describes - the structure and features of edX course discussions, and provides useful - information to help learners make the most of their participation in course - discussions. - -.. only:: Open_edX - - For information about participating in discussions, see the - `course discussions index`_ section in the *Open edX - Learner's Guide*. Consider referring learners in your courses to that section, - which describes the structure and features of course discussions, and provides - useful information to help learners make the most of their participation in - course discussions. +For information about participating in discussions, see the +`course discussions index`_ section in the *Open edX +Learner's Guide*. Consider referring learners in your courses to that section, +which describes the structure and features of course discussions, and provides +useful information to help learners make the most of their participation in +course discussions. ************************************************ @@ -138,7 +128,7 @@ discussion. your own post and then pin it, or pin a post by any author. Select the "More" icon and then **Pin**. - .. image:: ../images/Discussion_Pin.png + .. image:: /_images/educator_concepts/Discussion_Pin.png :alt: The pin icon for discussion posts. * Mark responses as answered or endorsed. Depending on whether a post is a @@ -151,7 +141,7 @@ discussion. To mark a response as answered or endorsed, select the "check mark" icon. You cannot mark your own responses as answers or as endorsed. - .. image:: ../images/Discussion_MarkAsAnswer.png + .. image:: /_images/educator_concepts/Discussion_MarkAsAnswer.png :alt: The "check mark" icon for marking a response as the correct answer to a question. @@ -160,7 +150,7 @@ discussion. read and responded to. Select the "plus" icon for the response. You cannot vote for your own posts. - .. image:: ../images/Discussion_vote.png + .. image:: /_images/educator_concepts/Discussion_vote.png :alt: The "plus" icon for voting for discussion posts. * Close posts. You can respond to a redundant post by (optionally) pasting in @@ -204,41 +194,9 @@ units and all course-wide topics are affected. affected when you close the discussions for a course. Users with these roles can continue to add to discussions. +.. seealso:: + :class: dropdown -============================================ -Specify When Discussions Are Closed -============================================ - -.. note:: You can only close discussions when you work in a web browser. You - cannot close discussions when you work in an edX mobile app. - -To define when discussions are closed to new contributions and when they -reopen, follow these steps. - -1. Navigate to edx discussion configuration page -(see :ref:`Configuring Edx Discussions`). - -2. Scroll down to **Discussion Blackout Dates** field. - -3. Create a new blackout date range by clicking on **Add blackout date range**. - -.. image:: ../images/Discussion_blackout_dates_configuration.png - :width: 300 - :alt: Option for configuring discussion blackout dates. - -4. Add start and end dates and times in the format specified. - -.. note:: The dates and times that you enter are in Coordinated Universal - Time (UTC), not in your local time zone. You might want to verify that you - have specified the times that you intend by using a time zone converter. - -.. note:: To close the course discussions permanently, specify an end date - and time far in the future. - -5. You can add more than one blackout date ranges using step 3 and 4 above. - -6. Select **Save Changes**. - - - - + :ref:`Discussions` (concept) + :ref:`Configuring Edx Discussions` (how-to) + :ref:`Closing Discussions` (how-to) diff --git a/source/educators/concepts/data/index.rst b/source/educators/concepts/data/index.rst new file mode 100644 index 000000000..e17ec8e19 --- /dev/null +++ b/source/educators/concepts/data/index.rst @@ -0,0 +1,8 @@ +Data & Analytics Concepts +############################# + +.. toctree:: + :maxdepth: 1 + :glob: + + * diff --git a/source/educators/concepts/data/learner_data.rst b/source/educators/concepts/data/learner_data.rst new file mode 100644 index 000000000..addfe2b0b --- /dev/null +++ b/source/educators/concepts/data/learner_data.rst @@ -0,0 +1,76 @@ +.. :diataxis-type: concept + +.. _Learner Data: + +############################ +Learner Data +############################ + +You can access data about the individuals who are enrolled in your course at +any time after you create the course. + +.. contents:: + :local: + :depth: 2 + +.. _PII: + +*************************************************************** +Guidance for Working with Personal Information +*************************************************************** + +The information that edX collects from site registrants includes personal +information that can be used to identify, contact, and locate individuals. This +information is available to course team members with the Admin or Staff role +for the learners who are enrolled in their courses. + +Members of the course team should follow the policies established by their +organizations and comply with the legal requirements of their locales to +prevent public distribution or misuse of this information. + +.. _Access_student_data: + +**************************** +Accessing Learner Data +**************************** + +In the LMS, you can download data about the individuals who are currently +enrolled in your course in a .csv (comma-separated values) file. You can also +view data for enrolled learners on the instructor dashboard. For more +information, see :ref:`View and download student data`. + +For information about course enrollment, see :ref:`Enrollment`. + +=========================== +About Learner-Reported Data +=========================== + +When learners create, or register, their user accounts, they select a public +username and supply their full names and email addresses. Learners also have +the option to provide personal demographic information, including highest +level of education completed, gender, year of birth, and preferred language. +Because this information is optional, not all of the learners who are enrolled +in your course provide it. + +After learners create an account, they can enroll in as many individual courses +as they choose. + +* The learner data that is available from the instructor dashboard reflects the + set of live, current enrollments. Data for the course team, who are also + enrolled in the course, is included. + +* Learners can enroll in your course throughout the defined enrollment period, + and they can unenroll from a course at any time. + +* Learners can update their personal information at any time on the + Account Settings page. + +As a result, you might want to download learner data periodically to gain an +understanding of how the learner population changes over time. + +.. seealso:: + :class: dropdown + + :ref:`Columns in the Student Profile Report` (reference) + :ref:`View and download student data` (how-to) + :ref:`Access Anonymized Learner IDs ` (how-to) \ No newline at end of file diff --git a/source/educators/migration_wip/14_grading/graded_subsections.rst b/source/educators/concepts/grading/graded_subsections.rst similarity index 90% rename from source/educators/migration_wip/14_grading/graded_subsections.rst rename to source/educators/concepts/grading/graded_subsections.rst index 946d8bc2e..89df9c582 100644 --- a/source/educators/migration_wip/14_grading/graded_subsections.rst +++ b/source/educators/concepts/grading/graded_subsections.rst @@ -1,3 +1,5 @@ +.. :diataxis-type: concept + .. _Graded Subsections: ********************************************** @@ -46,3 +48,11 @@ see :ref:`Set the Assignment Type and Due Date for a Subsection`. For more information about how to designate a subsection as a timed exam, see :ref:`Timed Exams`. + +.. seealso:: + :class: dropdown + + :ref:`Gradebook Assignment Types` (reference) + :ref:`The Learner View of Grades` (reference) + :ref:`Set the Grade Range` (how-to) + :ref:`Set the Grace Period` (how-to) diff --git a/source/educators/concepts/grading/index.rst b/source/educators/concepts/grading/index.rst new file mode 100644 index 000000000..0f22a66e4 --- /dev/null +++ b/source/educators/concepts/grading/index.rst @@ -0,0 +1,9 @@ +############################# +Grading +############################# + +.. toctree:: + :maxdepth: 1 + :glob: + + * \ No newline at end of file diff --git a/source/educators/concepts/index.rst b/source/educators/concepts/index.rst index d86281710..27a936e08 100644 --- a/source/educators/concepts/index.rst +++ b/source/educators/concepts/index.rst @@ -8,3 +8,12 @@ Educators: Concepts :glob: instructional_design/index + open_edx_platform/index + accessibility/index + data/index + communication/index + releasing-course/index + grading/index + proctored_exams/index + planning_course_run_information/index + advanced_features/index diff --git a/source/educators/concepts/open_edx_platform/index.rst b/source/educators/concepts/open_edx_platform/index.rst new file mode 100644 index 000000000..a76ba06de --- /dev/null +++ b/source/educators/concepts/open_edx_platform/index.rst @@ -0,0 +1,13 @@ +Instructional Design Concepts +############################# + +.. toctree:: + :maxdepth: 1 + :glob: + + outline_studio_lms + what_is_course_dashboard + what_is_lms + what_is_profile_page + what_is_programs_page + what_is_studio \ No newline at end of file diff --git a/source/educators/migration_wip/7_developing_course/outline_studio_lms.rst b/source/educators/concepts/open_edx_platform/outline_studio_lms.rst similarity index 89% rename from source/educators/migration_wip/7_developing_course/outline_studio_lms.rst rename to source/educators/concepts/open_edx_platform/outline_studio_lms.rst index 741bc28e0..c26c83354 100644 --- a/source/educators/migration_wip/7_developing_course/outline_studio_lms.rst +++ b/source/educators/concepts/open_edx_platform/outline_studio_lms.rst @@ -1,7 +1,15 @@ +.. :diataxis-type: concept + +.. _Course Outline: + +================== +Course Outline +================== + In the following image, the Studio view of the course outline is on the left. On the right is the view of the course outline in the LMS. -.. image:: ../images/Course_Outline_LMS.png +.. image:: /_images/educator_concepts/Course_Outline_LMS.png :alt: Sections, subsections, and units in the course outline in Studio and in the LMS. :width: 600 diff --git a/source/educators/concepts/open_edx_platform/what_is_course_dashboard.rst b/source/educators/concepts/open_edx_platform/what_is_course_dashboard.rst new file mode 100644 index 000000000..475bdb665 --- /dev/null +++ b/source/educators/concepts/open_edx_platform/what_is_course_dashboard.rst @@ -0,0 +1,39 @@ +.. :diataxis-type: concept + +****************************************** +What is the Course Dashboard? +****************************************** + +Your dashboard lists all of the courses that you are enrolled in. When you +create an account or enroll in a course, you automatically go to your +dashboard. You can also access your dashboard by selecting the dropdown menu +icon next to your username at the top of any page. + +.. image:: ../../migration_wip/images/dashboard_menu.png + :width: 300 + :alt: The menu that appears on the website when you select the + dropdown icon next to your username. The Dashboard option is circled, and + the other options are Profile, Account, and Sign Out. + +.. note:: Your dashboard is available only from the LMS. If you are currently + working in Studio, view the live version of your course to access your + dashboard. + +You can find information about your courses and change course-specific email +subscription settings on your dashboard. For more information, see :doc:`update_course_specific_settings <../../how-tos/update_course_specific_settings>`. + +.. only:: Partners + +The dashboard has three main pages. + +* The **Courses** page provides information about your courses and allows you to change course settings. By + default, the dashboard opens to the **Courses** page. The **Courses** page on the dashboard now includes two main categories of filters with subcategories in each main category. **Course Status** includes 'In progress,' 'Not Started,' 'Done,' 'Not Enrolled,' and 'Upgraded.' These different filters allow you to filter all of the courses based on the course status. **Sort** includes 'Last enrolled' and 'Title (A-Z).' These filters allow you to filter the course alphabetically or when you were last enrolled in the course. + +* The **Programs** page lists any programs, such as XSeries or MicroMasters programs, that edX offers for courses that you are enrolled in. Programs appear on this page if you are enrolled in any course that is part of that program. This page also shows how many courses in the program you have completed, how many are in progres, and the number of remaining courses you have left in the program. For more information, see :ref:`Explore edX Programs `. + +* The **Discover New** page take you to `the edX website `_ and will allow you to search for any courses on the edX platform that interest you. + +.. seealso:: + :class: dropdown + + :doc:`share_courses_social_media <../../how-tos/share_courses_social_media>` (how-to) diff --git a/source/educators/migration_wip/2_getting-started/what_is_lms.rst b/source/educators/concepts/open_edx_platform/what_is_lms.rst similarity index 100% rename from source/educators/migration_wip/2_getting-started/what_is_lms.rst rename to source/educators/concepts/open_edx_platform/what_is_lms.rst diff --git a/source/educators/concepts/open_edx_platform/what_is_profile_page.rst b/source/educators/concepts/open_edx_platform/what_is_profile_page.rst new file mode 100644 index 000000000..6be1a833e --- /dev/null +++ b/source/educators/concepts/open_edx_platform/what_is_profile_page.rst @@ -0,0 +1,48 @@ +.. :diataxis-type: concept + +******************************** +What is the User Profile Page? +******************************** + +Your personal profile allows you to optionally share information about yourself +with other participants in the courses that you take. If you choose to add +profile information, course teams and other learners in your courses can view +the information that you share. + +You can share either a limited profile or a full profile. + + .. note:: If you are under 13 years of age, your limited profile only + includes your username. You cannot add a profile picture. + +* A limited profile shares only your username. You can also add a profile + picture, if you are over 13 years of age. + + .. image:: ../../migration_wip/images/SFD_Profile_Limited.png + :width: 500 + :alt: A learner's limited profile showing only username and image. + +* A full profile includes the following details. + + * Your full name + * Your username + * Your profile image (optional) + * The date that you joined edX + * Your language (optional) + * Your location (optional) + * Information about you (optional) + * Links to any course certificates that you have earned + * Links to your social media accounts (optional) + + .. image:: ../../migration_wip/images/SFD_Profile_Full.png + :width: 500 + :alt: A learner's full profile shows full name, join date, location, + language, biographical information, links to course certificates, and + linked social media icons, in addition to username and profile image. + +.. seealso:: + :class: dropdown + + :doc:`add_update_limited_profile <../../how-tos/add_update_limited_profile>` (how-to) + :doc:`add_update_full_profile <../../how-tos/add_update_full_profile>` (how-to) + :doc:`add_links_to_social_media_accounts <../../how-tos/add_links_to_social_media_accounts>` (how-to) + :doc:`view_another_learners_profile <../../how-tos/view_another_learners_profile>` (how-to) \ No newline at end of file diff --git a/source/educators/concepts/open_edx_platform/what_is_programs_page.rst b/source/educators/concepts/open_edx_platform/what_is_programs_page.rst new file mode 100644 index 000000000..d599bf49b --- /dev/null +++ b/source/educators/concepts/open_edx_platform/what_is_programs_page.rst @@ -0,0 +1,31 @@ +.. :diataxis-type: how-to + +####################################### +What is the Programs Page? +####################################### + +The **Programs** page lists the programs that you have +enrolled in. You see a program on this page if you are enrolled in any courses +that are part of that program. + +On the **Programs** page, you can perform the following actions. + +* Access information about a program and enroll in more of the program's + courses. + + To access information about a program, select that program. A page opens + that provides details about the program, as well as links to enroll in or + upgrade to the verified track in all courses in that program. + +* View your progress for each program. + + Under the name of each program are indications of your progress through the + program. You see the number of courses in the program that you have + completed, the number of courses in the program that you are enrolled in, + and the number of courses in the program that you are not yet enrolled in. + +* Access any program certificates you have earned. + + In the right pane, a **Program Certificates** list shows the names of + programs for which you have earned certificates. For more information about + the program, or to view the certificate, select the name of the program. diff --git a/source/educators/migration_wip/2_getting-started/what_is_studio.rst b/source/educators/concepts/open_edx_platform/what_is_studio.rst similarity index 100% rename from source/educators/migration_wip/2_getting-started/what_is_studio.rst rename to source/educators/concepts/open_edx_platform/what_is_studio.rst diff --git a/source/educators/migration_wip/6_set_up_course/planning_course_run_information/additional_course_run_information.rst b/source/educators/concepts/planning_course_run_information/additional_course_run_information.rst similarity index 65% rename from source/educators/migration_wip/6_set_up_course/planning_course_run_information/additional_course_run_information.rst rename to source/educators/concepts/planning_course_run_information/additional_course_run_information.rst index fee657ece..99df6ca7e 100644 --- a/source/educators/migration_wip/6_set_up_course/planning_course_run_information/additional_course_run_information.rst +++ b/source/educators/concepts/planning_course_run_information/additional_course_run_information.rst @@ -1,3 +1,5 @@ +.. :diataxis-type: concept + .. _Additional Course Run Information: ################################# @@ -8,17 +10,7 @@ Optional additional information that may change with each course run includes information about the languages that course content is available in, as well as the time you expect learners to spend with your course. -.. only:: Partners - - For edx.org courses, you enter this information in Publisher. For more - information, see `Pub Create a Course`_. - - For courses on Edge, you enter this content in Studio. For more - information, see :ref:`Creating a Course About Page `. - -.. only:: Open_edX - - For information about how to enter this content in Studio, see :ref:`Creating a Course About Page `. +For information about how to enter this content in Studio, see :ref:`Creating a Course About Page `. .. _Language Guidelines: diff --git a/source/educators/concepts/planning_course_run_information/index.rst b/source/educators/concepts/planning_course_run_information/index.rst new file mode 100644 index 000000000..2eb98aa58 --- /dev/null +++ b/source/educators/concepts/planning_course_run_information/index.rst @@ -0,0 +1,9 @@ +############################# +Plan Course Run +############################# + +.. toctree:: + :maxdepth: 1 + :glob: + + * \ No newline at end of file diff --git a/source/educators/migration_wip/6_set_up_course/index.rst b/source/educators/concepts/planning_course_run_information/set_up_course.rst similarity index 70% rename from source/educators/migration_wip/6_set_up_course/index.rst rename to source/educators/concepts/planning_course_run_information/set_up_course.rst index bb2125a7f..38431d43f 100644 --- a/source/educators/migration_wip/6_set_up_course/index.rst +++ b/source/educators/concepts/planning_course_run_information/set_up_course.rst @@ -1,3 +1,5 @@ +.. :diataxis-type: concept + .. _Setting up Your Course Index: ################################ @@ -13,15 +15,5 @@ types of basic information about your course. * **Course run** information changes every time the course runs. This is information such as the course staff and start and end dates. -This section provides information about how to determine required course and -course run information, as well as how to enter this information in Studio. - -.. toctree:: - :maxdepth: 2 - - planning_course_information/index - planning_course_run_information/index - studio_add_course_information/index - For information about how to develop your course content in the Studio course outline, see :ref:`Developing Your Course Index `. diff --git a/source/educators/concepts/proctored_exams/index.rst b/source/educators/concepts/proctored_exams/index.rst new file mode 100644 index 000000000..bc272c7fe --- /dev/null +++ b/source/educators/concepts/proctored_exams/index.rst @@ -0,0 +1,9 @@ +############################# +Proctored Exams +############################# + +.. toctree:: + :maxdepth: 1 + :glob: + + * \ No newline at end of file diff --git a/source/educators/concepts/proctored_exams/preparing_learners_proctored_exams.rst b/source/educators/concepts/proctored_exams/preparing_learners_proctored_exams.rst new file mode 100644 index 000000000..dcbb361a4 --- /dev/null +++ b/source/educators/concepts/proctored_exams/preparing_learners_proctored_exams.rst @@ -0,0 +1,74 @@ +.. _Preparing Learners for Proctored Exams: + +###################################### +Preparing Learners for Proctored Exams +###################################### + +To prepare learners for a proctored exam, follow these guidelines. + + +only:: Open_edX + +* Emphasize that learners must be aware of the requirements before taking the + exam, and that some of the requirements might take some preparation. +* Well before the exam, provide learners with information about the grading + policy in your course. +* Explain what proctored exams are, and provide learners with links to the + `OE SFD Proctored Exams`_ topic in the *Open edX + Learner’s Guide*. +* Communicate the rules for proctored exams, including the :ref:`online + proctoring rules` in the *Open edX Learner’s + Guide* as well as any specific rules for a particular exam. For information + about creating specific rules, see + :ref:`specifying_exam_rules_and_exceptions`. + +.. _CA_LearnerExperience_Proctored Exams: + +***************************************** +The Learner Experience of Proctored Exams +***************************************** + +The learner experience of a proctored exam depends on the proctoring service +that your course or organization uses. Typically, learners can expect to +download and install proctoring software, verify their identities, and use +their webcams to scan the testing environment before they take the exam. For +more information, see `OE SFD Proctored Exams`_ in the *Open +edX Learner's Guide*. + +.. _Practice Proctored Exams: + +************************ +Practice Proctored Exams +************************ + +You can create an ungraded practice proctored exam for your course so that +learners can become familiar with the process of installing proctoring +software and performing the required checks ahead of time. Depending on the +proctoring service, learners might complete the following steps for a +practice proctored exam. + +* Install the proctoring software. +* Complete identity checks. +* Complete a room scan. +* Complete any example problems in the exam. + +.. note:: + Learners who complete practice exams must usually complete the same + software installation and environment scan steps again when they take an + actual proctored exam. + +.. seealso:: + :class: dropdown + + :ref:`ProctoredExams_Overview` (concept) + :ref:`Enable Proctored Exams` (how-to) + :ref:`Online Proctoring Rules` (reference) + :ref:`Manage Proctored Exams` (how-to) + :ref:`Allow Opting Out of Proctored Exams` (how-to) + :ref:`Create a Proctored Exam with Proctortrack` (how-to) + :ref:`PT Proctored Session Results File` (reference) + :ref:`Review PT Proctored Session Results` (how-to) + :ref:`Create a Proctored Exam with RPNow` (how-to) + :ref:`RPNow Proctored Session Results File` (reference) + :ref:`Review RP Proctored Session Results` (how-to) + diff --git a/source/educators/migration_wip/13_proctored_exams/overview.rst b/source/educators/concepts/proctored_exams/proctored_exams_overview.rst similarity index 75% rename from source/educators/migration_wip/13_proctored_exams/overview.rst rename to source/educators/concepts/proctored_exams/proctored_exams_overview.rst index 0bb3924b8..c6e2fea2d 100644 --- a/source/educators/migration_wip/13_proctored_exams/overview.rst +++ b/source/educators/concepts/proctored_exams/proctored_exams_overview.rst @@ -1,4 +1,4 @@ -.. _CA_ProctoredExams_Overview: +.. _ProctoredExams_Overview: ############################ Proctored Exam Overview @@ -89,36 +89,17 @@ Learners must satisfy the following criteria to pass a proctored exam. For more information about the way that learners experience proctored exams, see `Taking Timed and Proctored Exams` in the edX Help Center. -.. _Allow Opting Out of Proctored Exams: - -*************************************************** -Allow Opting Out of Proctored Exams -*************************************************** - -When a proctored exam opens, by default, verified learners must take the exam -with proctoring. - -If you want to allow Verified or Master's learners the option to take proctored exams -without proctoring, please contact your edX partner manager to enable this option. - -.. note:: - If a learner opts to take an exam without proctoring, the exam will not be - timed either. In effect, learners who opt out of proctoring will have - unlimited time to complete the exam and could return to problem sets at - any time. You can reduce the ability to view the exam by selecting a due - date for the exam. - -.. only:: Open_edX - - To enable the option for learners to opt out of proctored exams for a course, - follow these steps. - - #. In Studio, select **Settings**, then select **Proctored Exam Settings**. - - #. Locate the **Allow Opting Out of Proctored Exams** policy key. The default - value is ``No``, which requires Verified and Master's learners to take - proctored exams with proctoring. - - #. Change the value of the setting to ``Yes``. - - #. Select **Submit**. +.. seealso:: + :class: dropdown + + :ref:`Enable Proctored Exams` (how-to) + :ref:`Preparing Learners for Proctored Exams` (concept) + :ref:`Online Proctoring Rules` (reference) + :ref:`Manage Proctored Exams` (how-to) + :ref:`Allow Opting Out of Proctored Exams` (how-to) + :ref:`Create a Proctored Exam with Proctortrack` (how-to) + :ref:`PT Proctored Session Results File` (reference) + :ref:`Review PT Proctored Session Results` (how-to) + :ref:`Create a Proctored Exam with RPNow` (how-to) + :ref:`RPNow Proctored Session Results File` (reference) + :ref:`Review RP Proctored Session Results` (how-to) \ No newline at end of file diff --git a/source/educators/migration_wip/15_releasing_course/beta_testing.rst b/source/educators/concepts/releasing-course/beta_testing.rst similarity index 51% rename from source/educators/migration_wip/15_releasing_course/beta_testing.rst rename to source/educators/concepts/releasing-course/beta_testing.rst index 54c372e3c..31d5afabb 100644 --- a/source/educators/migration_wip/15_releasing_course/beta_testing.rst +++ b/source/educators/concepts/releasing-course/beta_testing.rst @@ -1,32 +1,13 @@ +.. :diataxis-type: reference + .. _Beta_Testing: ############################# Beta Testing a Course ############################# -This topic describes how to beta test your course. - -.. contents:: - :local: - :depth: 1 - -**************************** -Overview -**************************** - -When you are designing a course in Studio, you can use the **Preview** or -**View Live** options to test the course content, find gaps and errors, and -mimic the learner experience. For more information, see :ref:`Testing Your -Course Content`. - To gather information about the overall experience of taking a course, you can -also conduct a beta test of the course. - -.. _Beta_Process: - -****************************************** -The Beta Testing Process -****************************************** +recruit beta testers to test your course before it is available to general learners. During a beta test, you gather information about the experience of taking your course in an effort to improve its quality. The phases of the beta testing @@ -208,177 +189,8 @@ unit`. be tested. If that first unit is not available, an error occurs when testers attempt to access any other content in the course. -================================ -Define When the Beta Test Starts -================================ - -To define the start of the beta test, you use Studio to specify a number of -days before the course start date for self-paced courses or before the section -and subsection release dates for instructor-paced courses. For more -information, see :ref:`How_Testers_See_Course`. - -#. In Studio, from the **Settings** menu, select **Advanced Settings**. - -#. In the field for the **Days Early for Beta Users** policy key, enter the - number of days before content releases for beta testers to have access. - -#. Select **Save Changes**. - -=========== -Example -=========== - -.. Is this example helpful? how can we assess whether it is frightening/confusing to course team, or helpful? - -Beta tester access to course content for an instructor-paced course with **Days -Early for Beta Users** = 20 and 2 sections: - - -.. list-table:: - :widths: 60 40 - - * - Course enrollment date = 31 August - - 31 August; earlier if enrolled by course team - * - Course start date = 15 September - - 26 August - * - Section 1 release day = 15 September - - 26 August - * - section 2 release day = 22 September - - 2 September - * - Subsection 1 release day = 22 September - - 2 September - * - Subsection 2 release day = 24 September - - 4 September - * - Subsection 2, unit 1 visibility = public - - 4 September - * - Subsection 2, unit 2 visibility = public; draft in progress - - 4 September for public version; no access to draft - * - Subsection 2, unit 3 visibility = private - - No access - -In this example, the beta testers cannot access all of the content on the -**Course** page when the beta test starts on 26 August: they can access section -1 but not section 2. You may want to provide a schedule of section availability -to your testers so that they can plan their time appropriately. Future release -dates do not display to the beta testers in the course. - -.. _Add_Testers: - -********************************* -Adding Beta Testers -********************************* - -Before you can add beta testers: - -* You need the email address or username of each beta tester. - -* Each beta tester must register and activate a user account for that email - address/username. - -When you add beta testers, note the following. - -* If the beta test starts before the course **Enrollment Start Date**, testers - cannot enroll themselves in your course. However, you can enroll the beta - testers prior to the **Enrollment Start Date**. - -* If you add the beta testers after the defined start of the beta test, and - they are enrolled in the course, they see your course on their **Current - Courses** dashboards when they log in. - -* If you add beta testers before the test starts, or if they are not enrolled, - they do not see your course on their dashboards. You can enroll the beta - testers in the course yourself, and you may want to send an email message to - remind them when the test begins. - -.. _Add_Testers_Bulk: - -================================ -Add Multiple Beta Testers -================================ - -If you have a number of beta testers that you want to add, you can use the -"batch add" option to add them all at once, rather than individually. With this -feature, you have options to enroll the beta testers in the course (before or -after the **Enrollment Start Date**) and send an email message to notify the -beta testers that they have been added. - -To add multiple beta testers: - -#. View the live version of your course. - -#. Select **Instructor**, and then select **Membership**. - -#. In the **Batch Beta Tester Addition** section of the page, enter one or more - addresses or usernames separated by commas or line feeds (the Enter key). - You can also copy data from a CSV file of email addresses and paste it here. - -#. To enroll the beta testers in your course, leave **Auto Enroll** selected. - If the beta test starts before the course **Enrollment Start Date**, testers - cannot enroll themselves in your course. - -#. To send an email message to the beta testers, leave **Notify users by - email** selected. An example of the message that is sent to a beta tester - who is not enrolled in the course follows.:: - - Dear betatester, - - You have been invited to be a beta tester for *course* at edge.edx.org - by a member of the course team. - - Visit https://edge.edx.org/courses/course-name/about to join the course - and begin the beta test. - - -#. Select **Add beta testers**. - -To remove the Beta Tester role from one or more users, enter their email -addresses in the **Batch Add Beta Testers** field and then select **Remove beta -testers**. - -.. note:: When you select **Remove beta testers**, the **Auto Enroll** option is - not affected. The user's role as a beta tester is removed, but they remain - enrolled in the course. - - -================================ -Add Beta Testers Individually -================================ - - -#. View the live version of the course. - -#. Select **Instructor**, and then select **Membership**. - -#. In the **Course Team Management** section, select **Beta Testers**. - -#. Under the list of users who currently have that role, enter the email address - or username of the person you want to add. - -#. Select **Add Beta Tester**. - - The person who you added appears in the list of beta testers. - - -.. note:: If the beta test starts before the **Enrollment Start Date** of your - course, you can also enroll the beta tester. See :ref:`Enrollment`. - - -To remove the Beta Tester role from users individually, find the user in the -list of beta testers, and then select **Revoke access** to the right of that -user's email address. - - -.. _Issue_Reporting_During_Course: - -********************************* -Reporting Issues During a Course -********************************* - -Despite the efforts of the course team and the beta testers, additional -problems, questions, and issues can occur while a course is running. +.. seealso:: + :class: dropdown -* Often, learners report issues by asking questions in a discussion. Your - discussion moderation team can watch for posts that indicate problems. + :ref:`Add_Beta_Testers` (how-to) -* To let learners know the best way to report problems, you can post information - in the course welcome message, or post it in a discussion. diff --git a/source/educators/migration_wip/15_releasing_course/course_launching.rst b/source/educators/concepts/releasing-course/course_launching.rst similarity index 99% rename from source/educators/migration_wip/15_releasing_course/course_launching.rst rename to source/educators/concepts/releasing-course/course_launching.rst index d39042386..8aad0049f 100644 --- a/source/educators/migration_wip/15_releasing_course/course_launching.rst +++ b/source/educators/concepts/releasing-course/course_launching.rst @@ -1,7 +1,9 @@ +.. :diataxis-type: concept + .. _Launch: ########################### -Course Launching Activities +Launching a Course ########################### To launch a course, you prepare the course itself, the course team, and the diff --git a/source/educators/concepts/releasing-course/index.rst b/source/educators/concepts/releasing-course/index.rst new file mode 100644 index 000000000..30bd5b582 --- /dev/null +++ b/source/educators/concepts/releasing-course/index.rst @@ -0,0 +1,12 @@ +.. _Releasing Your Course_Concept: + +############################# +Releasing your Course +############################# + +.. toctree:: + :maxdepth: 1 + :glob: + + beta_testing + course_launching \ No newline at end of file diff --git a/source/educators/how-tos/add_links_to_social_media_accounts.rst b/source/educators/how-tos/add_links_to_social_media_accounts.rst new file mode 100644 index 000000000..9847dfb05 --- /dev/null +++ b/source/educators/how-tos/add_links_to_social_media_accounts.rst @@ -0,0 +1,44 @@ +.. :diataxis-type: how-to + +================================================= +Add Links to Your Personal Social Media Accounts +================================================= + +If you select the **Full Profile** option, you can add social media icons on +your profile that link to your personal Twitter, Facebook, or LinkedIn account +pages. + +To add links to your social media accounts to your profile, follow these steps. + +#. At the top of any page, select **Account** from the dropdown menu icon next + to your username. + +#. On the **Account Settings** page, under **Social Media Links**, enter + either your username or the URL to the profile page for each social media + account that you want to add to your profile. + + For example, if your Facebook username is ``edx``, you can enter either + ``edx`` or ``https://www.facebook.com/edx``. + + For LinkedIn, note that your username might include numbers. For example, + if the URL of your LinkedIn profile page is ``https://www.linkedin.com/in + /firstname-lastname-123456/``, your LinkedIn username is ``firstname- + lastname-123456``. + +The site saves your changes when you click outside the text field. + +When you view your profile, icons for the social media icons that you added +links for appear below your username. Other learners or course team members +can click those icons to visit your social media account page. + + .. image:: ../../educators/migration_wip/images/SFD_Profile_Full_SocialMediaIcons.png + :width: 500 + :alt: A learner's full profile, with social media icons circled. + +.. seealso:: + :class: dropdown + + :doc:`what_is_profile_page <../concepts/open_edx_platform/what_is_profile_page>` (concept) + :doc:`add_update_full_profile` (how-to) + :doc:`add_update_limited_profile` (how-to) + :doc:`view_another_learners_profile` (how-to) \ No newline at end of file diff --git a/source/educators/how-tos/add_update_full_profile.rst b/source/educators/how-tos/add_update_full_profile.rst new file mode 100644 index 000000000..ab1eed1bb --- /dev/null +++ b/source/educators/how-tos/add_update_full_profile.rst @@ -0,0 +1,69 @@ +.. :diataxis-type: how-to + +================================ +Add or Update a Full Profile +================================ + +.. note:: You must specify your year of birth on the **Account Settings** page + before you can share a full profile. If you are under 13 years of age, you + can share only a `Create or Edit a Limited Profile`_. + +If you create a full profile, you share the following information in +addition to your username and profile image. + +* Your full name. + +* Your location. + +* Your language. + +* A paragraph about yourself. You might include your interests, goals, or + other information that you want to share. This paragraph can contain up to + 300 characters. + +* Links to your personal social media accounts. + +To add or update your profile, follow these steps. + +#. At the top of any page, select **Dashboard** from the dropdown menu icon next + to your username, then select the **Profile** tab. + +#. In the header area of your profile page, for **Profile Visibility**, select + **Full Profile**. + +#. (optional) Add a profile image. + + Your image must be a .gif, .jpg, or .png file that is less than 1 MB in + size. If you do not add an image, the placeholder image appears as your + profile image. + + #. Move your cursor over the placeholder image, and click **Upload an + image**. + + #. In the file navigation window, select the image file that you want to + use as your profile image, and then click **Open**. + + To change or remove your profile image, move your cursor over your image, + and then select either **Change image** or **Remove**. When you remove your + profile image, the placeholder image appears as your profile image. + +#. On your profile page, move your cursor over the information that you want + to change. + +#. Click inside the field to choose an option from the list, or enter text. + +The site saves your changes automatically. + +.. note:: If you change your profile type from **Full Profile** to **Limited + Profile**, your full name, location, language, and descriptive paragraph + are no longer visible on your profile page. However, this information is + saved, and becomes visible again to other learners and course teams if you + change your profile back to **Full Profile**. + +.. seealso:: + :class: dropdown + + :doc:`what_is_profile_page <../concepts/open_edx_platform/what_is_profile_page>` (concept) + :doc:`add_update_limited_profile` (how-to) + :doc:`add_links_to_social_media_accounts` (how-to) + :doc:`view_another_learners_profile` (how-to) diff --git a/source/educators/how-tos/add_update_limited_profile.rst b/source/educators/how-tos/add_update_limited_profile.rst new file mode 100644 index 000000000..31399759d --- /dev/null +++ b/source/educators/how-tos/add_update_limited_profile.rst @@ -0,0 +1,48 @@ +.. :diataxis-type: how-to + +================================ +Add or Update a Limited Profile +================================ + +A limited profile includes only your username and, optionally, an image. + +.. note:: If you are under 13 years of age, your limited profile only includes + your username. You cannot add a profile picture. + +To add or update a limited profile, follow these steps. + + +#. At the top of any page, select **Dashboard** from the dropdown menu icon next + to your username, then select the **Profile** tab. + +#. In the header area of your profile page, for **Profile Visibility**, select + **Limited Profile**. + +#. (optional) Add an image that you want to associate with your username. + Your image must be a .gif, .jpg, or .png file. The image must be between + 100 bytes and 1 MB in size. If you do not add an image, the placeholder + image appears as your profile image. + + #. Move your cursor over the placeholder image, and click **Upload an + image**. + + .. image:: ../../educators/migration_wip/images/SFD_Profile_UploadImage.png + :width: 250 + :alt: A profile with the image upload area selected. + + #. In the file navigation window, select the image file that you want to + use as your profile image, and then click **Open**. + + To change or remove your profile image, move your cursor over your image, + and then select either **Change image** or **Remove**. When you remove your + profile image, the placeholder image appears as your profile image. + +The site saves your changes automatically. + +.. seealso:: + :class: dropdown + + :doc:`what_is_profile_page <../concepts/open_edx_platform/what_is_profile_page>` (concept) + :doc:`add_update_full_profile` (how-to) + :doc:`add_links_to_social_media_accounts` (how-to) + :doc:`view_another_learners_profile` (how-to) \ No newline at end of file diff --git a/source/educators/migration_wip/12_course_features/content_experiments/content_experiments_add.rst b/source/educators/how-tos/advanced_features/add_content_experiments.rst similarity index 90% rename from source/educators/migration_wip/12_course_features/content_experiments/content_experiments_add.rst rename to source/educators/how-tos/advanced_features/add_content_experiments.rst index 8b4d9d17c..d8e282520 100644 --- a/source/educators/migration_wip/12_course_features/content_experiments/content_experiments_add.rst +++ b/source/educators/how-tos/advanced_features/add_content_experiments.rst @@ -72,7 +72,7 @@ Create a Content Experiment A new content experiment is added to the unit. - .. image:: ../../images/content_experiment_block.png + .. image:: /_images/educator_how_tos/content_experiment_block.png :width: 600 :alt: An image showing the content experiment component in a unit page in Studio. @@ -85,7 +85,7 @@ Create a Content Experiment #. Select either **Select a Group Configuration** or **Edit** to open the content experiment component. - .. image:: ../../images/content_experiment_editor.png + .. image:: /_images/educator_how_tos/content_experiment_editor.png :alt: An image of the content experiment editor in Studio. :width: 600 @@ -117,7 +117,7 @@ each group that is defined in the group configuration you selected. For example, if you select a group configuration that defines two groups, Group A and Group B, you see the following page. -.. image:: ../../images/content_experiment_container.png +.. image:: /_images/educator_how_tos/content_experiment_container.png :alt: An image of the content experiment page in Studio, with two groups. :width: 600 @@ -127,7 +127,7 @@ Other Components`. For example, you can add a Text component and a video to Group A. -.. image:: ../../images/a_b_test_child_expanded.png +.. image:: /_images/educator_how_tos/a_b_test_child_expanded.png :alt: An image of an expanded content experiment component with an HTML and video component. :width: 600 @@ -156,7 +156,7 @@ groups, as well as create new components. #. In the content experiment component, select **Edit**. - .. image:: ../../images/content_experiment_editor_group2.png + .. image:: /_images/educator_how_tos/content_experiment_editor_group2.png :alt: An image of the content experiment editor in Studio, with a group configuration selected. :width: 600 @@ -172,7 +172,7 @@ groups, as well as create new components. that you had added to groups in the previous configuration are now moved to a section called **Inactive Groups**. - .. image:: ../../images/inactive_groups.png + .. image:: /_images/educator_how_tos/inactive_groups.png :alt: An image of a content experiment in Studio, with components in an inactive group. :width: 600 @@ -180,6 +180,10 @@ groups, as well as create new components. #. Drag and drop components from the **Inactive Groups** section into the new groups. You can also create new components in the new groups. -.. import OLX-content experiment doc that's shared in OLX guide. +.. seealso:: + :class: dropdown -.. include:: subsection_content_experiments_OLX.rst + :ref:`Offering Differentiated Content` (concept) + :ref:`Overview of Content Experiments` (concept) + :ref:`Configure Your Course for Content Experiments` (how-to) + :ref:`Add a Content Experiment in OLX` (how-to) diff --git a/source/educators/migration_wip/12_course_features/content_experiments/subsection_content_experiments_OLX.rst b/source/educators/how-tos/advanced_features/add_content_experiments_olx.rst similarity index 87% rename from source/educators/migration_wip/12_course_features/content_experiments/subsection_content_experiments_OLX.rst rename to source/educators/how-tos/advanced_features/add_content_experiments_olx.rst index fafdb10f5..f89c60313 100644 --- a/source/educators/migration_wip/12_course_features/content_experiments/subsection_content_experiments_OLX.rst +++ b/source/educators/how-tos/advanced_features/add_content_experiments_olx.rst @@ -1,5 +1,7 @@ .. This section is shared in course authors and OLX guides. +.. _Add a Content Experiment in OLX: + **************************************** Add a Content Experiment in OLX **************************************** @@ -81,4 +83,14 @@ In this example: ``url_name`` equal to ``group_a``. Therefore, learners in group 0 see the content in that vertical. -For information about the ``policy.json`` file, see :doc:`subsection_content_experiments_policies`. +For information about the ``policy.json`` file, see :ref:`Set Up Group Configuration for OLX Courses`. + +.. seealso:: + :class: dropdown + + :ref:`Offering Differentiated Content` (concept) + :ref:`Overview of Content Experiments` (concept) + :ref:`Configure Your Course for Content Experiments` (how-to) + :ref:`Experiment Group Configurations` (reference) + :ref:`Set Up Group Configuration for OLX Courses` (how-to) + :ref:`Guidelines for Modifying Group Configurations` (concept) diff --git a/source/educators/migration_wip/12_course_features/cohorts/cohorted_courseware.rst b/source/educators/how-tos/advanced_features/cohorted_courseware.rst similarity index 95% rename from source/educators/migration_wip/12_course_features/cohorts/cohorted_courseware.rst rename to source/educators/how-tos/advanced_features/cohorted_courseware.rst index 75d5038a5..0cb1911dd 100644 --- a/source/educators/migration_wip/12_course_features/cohorts/cohorted_courseware.rst +++ b/source/educators/how-tos/advanced_features/cohorted_courseware.rst @@ -1,7 +1,9 @@ -.. _Cohorted Courseware Overview: +.. :diataxis-type: how-to + +.. _Create Cohort Specific Course Content: ########################################### -Creating Cohort-Specific Course Content +Create Cohort-Specific Course Content ########################################### This section provides information about setting up content for specific @@ -132,7 +134,7 @@ To create a content group, follow these steps. #. On the **Group Configurations** page, select **New content group**. - .. image:: ../../images/Cohorts_AddContentGroup.png + .. image:: /_images/educator_how_tos/Cohorts_AddContentGroup.png :width: 600 :alt: Button on Group Configurations page for adding first content group. @@ -214,7 +216,7 @@ To associate a cohort with a content group, follow these steps: #. From the content group drop down list, select the content group that you want your cohort to be associated with. - .. image:: ../../images/Cohorts_AssociateWithContentGroup.png + .. image:: /_images/educator_how_tos/Cohorts_AssociateWithContentGroup.png :alt: Select a content group to associate with the cohort. #. Select **Save**. @@ -310,3 +312,14 @@ Delete Content Groups #. In the confirmation message, select **Delete** again to confirm the deletion. + + +.. seealso:: + :class: dropdown + + :ref:`Cohorts Overview` (concept) + :ref:`Manage Course Cohorts` (how-to) + :ref:`About Divided Discussions` (concept) + :ref:`Managing Divided Discussion Topics` (concept) + :ref:`Moderating_discussions` (concept) + :ref:`Setting Up Divided Discussions` (how-to) \ No newline at end of file diff --git a/source/educators/migration_wip/12_course_features/content_experiments/content_experiments_configure.rst b/source/educators/how-tos/advanced_features/configure_content_experiments.rst similarity index 69% rename from source/educators/migration_wip/12_course_features/content_experiments/content_experiments_configure.rst rename to source/educators/how-tos/advanced_features/configure_content_experiments.rst index 4bcae0594..23749374c 100644 --- a/source/educators/migration_wip/12_course_features/content_experiments/content_experiments_configure.rst +++ b/source/educators/how-tos/advanced_features/configure_content_experiments.rst @@ -46,60 +46,6 @@ To enable content experiments in your course, you add ``split_test`` to the #. Select **Save Changes**. -.. _Overview of Group Configurations: - -**************************************** -Overview of Group Configurations -**************************************** - -Before you can create :ref:`content experiments`, you must specify at least one group configuration for your -course. - -A group configuration defines how many groups of learners are in an experiment. -You can have any number of group configurations in your course. When you create -a content experiment, you select the group configuration to use. - -For example, you might want to run two different content experiments at -different times during your course. In one content experiment, learners either -see a video or complete a reading assignment. You can then include problems so -that you can see which group learned the material more completely. For this -content experiment, you need a group configuration that assigns your learners -to two experiment groups. - -In the other content experiment, you can present the same question using four -different types of problems. For this content experiment, you need a -group configuration that assigns your learners to four experiment groups. - -======================================= -Assigning Learners to Experiment Groups -======================================= - -The edX Platform assigns learners to each experiment group in a group -configuration. - -Experiment group assignments have the following characteristics. - -* Dynamic - - The edX Platform assigns a learner to an experiment group the first time he - or she views a content experiment that uses the group configuration. - -* Random - - You cannot control which learners are assigned to which experiment group. - -* Evenly distributed - - The edX Platform keeps track of the size of experiment groups, and assigns - new learners to groups evenly. For example, if you have two experiment groups - in a configuration, each group includes 50% of the learners in the course; if - you have four experiment groups, each group includes 25% of the learners. - -* Permanent - - Learners remain in their assigned experiment groups regardless of how many - content experiments you set up that use the same group configuration. .. _Set up Group Configurations in edX Studio: @@ -131,7 +77,7 @@ You can create a group configuration at any time. #. On the **Group Configurations** page, under **Experiment Groups**, select **New Experiment Group**. The following page opens: - .. image:: ../../images/create-group-config.png + .. image:: /_images/educator_how_tos/create-group-config.png :width: 800 :alt: An image of the Create a New Group Configuration page in Studio. @@ -158,7 +104,7 @@ The group configuration is then listed in the page. You can see the number of groups that the configuration contains, as well as whether the configuration is in use in the course: -.. image:: ../../images/group_configurations_one_listed.png +.. image:: /_images/educator_how_tos/group_configurations_one_listed.png :width: 800 :alt: The Group Configurations page with one group configuration listed. @@ -170,20 +116,19 @@ Edit a Group Configuration .. important:: You can change the name of a group configuration at any time. However, before you modify any other characteristics of a group - configuration that is currently used in a running course, review `Guidelines - for Modifying Group Configurations`_. + configuration that is currently used in a running course, review :ref:`Guidelines for Modifying Group Configurations`. #. On the **Group Configurations** page, hover over the group configuration and select **Edit**. - .. image:: ../../images/group_configurations_edit.png + .. image:: /_images/educator_how_tos/group_configurations_edit.png :alt: An image of the Group Configurations page with Edit button highlighted. :width: 800 The following page opens: - .. image:: ../../images/save-group-config.png + .. image:: /_images/educator_how_tos/save-group-config.png :alt: An image of the Edit a Group Configuration page. :width: 800 @@ -209,7 +154,7 @@ Delete a Group Configuration #. On the **Group Configurations** page, hover over the group configuration and select the Delete icon. - .. image:: ../../images/group-configuration-delete.png + .. image:: /_images/educator_how_tos/group-configuration-delete.png :alt: The Delete icon circled for a group configuration. :width: 800 @@ -228,7 +173,7 @@ On the **Group Configurations** page, select the name of a group to see its details. You see links to the content experiments that use this group configuration. -.. image:: ../../images/group_configurations_experiments.png +.. image:: /_images/educator_how_tos/group_configurations_experiments.png :alt: An image of a group configuration with the content experiments using the configuration circled. :width: 800 @@ -245,7 +190,7 @@ configuration used by that experiment in two ways. * In a unit that contains a content experiment, in the content experiment block, select the name of the group configuration. - .. image:: ../../images/content_experiment_group_config_link.png + .. image:: /_images/educator_how_tos/content_experiment_group_config_link.png :alt: An image of the content experiment in the unit page with the group configuration link circled :width: 800 @@ -253,14 +198,14 @@ configuration used by that experiment in two ways. * At the top of the content experiment page, select the name of the group configuration. - .. image:: ../../images/content_experiment_page_group_config_link.png + .. image:: /_images/educator_how_tos/content_experiment_page_group_config_link.png :alt: An image of the content experiment page with the group configuration link circled. :width: 800 In both cases, the group configuration opens. -.. image:: ../../images/group_configurations_experiments.png +.. image:: /_images/educator_how_tos/group_configurations_experiments.png :alt: An image of the Group Configuration page with the experiments using it circled. :width: 800 @@ -268,8 +213,12 @@ In both cases, the group configuration opens. You can use the link in the group configuration to return to the unit that contains the content experiment. -.. import OLX-content experiment doc that's shared in OLX guide. - -.. include:: subsection_content_experiments_group_modify_guidelines.rst +.. seealso:: + :class: dropdown -.. include:: subsection_content_experiments_policies.rst + :ref:`Offering Differentiated Content` (concept) + :ref:`Overview of Content Experiments` (concept) + :ref:`Experiment Group Configurations` (reference) + :ref:`Add a Content Experiment in OLX` (how-to) + :ref:`Set Up Group Configuration for OLX Courses` (how-to) + :ref:`Guidelines for Modifying Group Configurations` (concept) diff --git a/source/educators/migration_wip/12_course_features/diff_content/enroll_track_courseware.rst b/source/educators/how-tos/advanced_features/create_content_for_specific_enrollment_tracks.rst similarity index 97% rename from source/educators/migration_wip/12_course_features/diff_content/enroll_track_courseware.rst rename to source/educators/how-tos/advanced_features/create_content_for_specific_enrollment_tracks.rst index ae996c609..233b1a041 100644 --- a/source/educators/migration_wip/12_course_features/diff_content/enroll_track_courseware.rst +++ b/source/educators/how-tos/advanced_features/create_content_for_specific_enrollment_tracks.rst @@ -1,9 +1,11 @@ +.. :diataxis-type: how-to + :orphan: .. _Enrollment Track Specific Courseware Overview: ####################################################### -Creating Course Content for Specific Enrollment Tracks +Create Course Content for Specific Enrollment Tracks ####################################################### This section provides information about creating different content for @@ -172,3 +174,8 @@ Content`. For details see :ref:`Testing Your Course Content` and :ref:`Roles for Viewing Course Content`. + +.. seealso:: + :class: dropdown + + :ref:`Offering Differentiated Content` (concept) \ No newline at end of file diff --git a/source/educators/how-tos/advanced_features/index.rst b/source/educators/how-tos/advanced_features/index.rst new file mode 100644 index 000000000..b5bf2f4c7 --- /dev/null +++ b/source/educators/how-tos/advanced_features/index.rst @@ -0,0 +1,9 @@ +############################# +Advanced Features +############################# + +.. toctree:: + :maxdepth: 1 + :glob: + + * \ No newline at end of file diff --git a/source/educators/migration_wip/12_course_features/cohorts/cohort_config.rst b/source/educators/how-tos/advanced_features/managing_cohorts.rst similarity index 98% rename from source/educators/migration_wip/12_course_features/cohorts/cohort_config.rst rename to source/educators/how-tos/advanced_features/managing_cohorts.rst index 73418a532..d99070fe5 100644 --- a/source/educators/migration_wip/12_course_features/cohorts/cohort_config.rst +++ b/source/educators/how-tos/advanced_features/managing_cohorts.rst @@ -1,7 +1,9 @@ -.. _Enabling and Configuring Cohorts: +.. :diataxis-type: how-to + +.. _Manage Course Cohorts: ############################################ -Enabling and Configuring the Cohorts Feature +Manage Course Cohorts ############################################ This section provides information about setting up cohorts in your course. @@ -612,3 +614,14 @@ To disable cohorts in your course, follow these steps. All course content and discussion posts that were previously divided by cohort immediately become visible to all students. + + +.. seealso:: + :class: dropdown + + :ref:`Cohorts Overview` (concept) + :ref:`Create Cohort Specific Course Content` (how-to) + :ref:`About Divided Discussions` (concept) + :ref:`Managing Divided Discussion Topics` (concept) + :ref:`Moderating_discussions` (concept) + :ref:`Setting Up Divided Discussions` (how-to) \ No newline at end of file diff --git a/source/educators/migration_wip/12_course_features/content_experiments/subsection_content_experiments_policies.rst b/source/educators/how-tos/advanced_features/set_up_group_configuration_olx.rst similarity index 90% rename from source/educators/migration_wip/12_course_features/content_experiments/subsection_content_experiments_policies.rst rename to source/educators/how-tos/advanced_features/set_up_group_configuration_olx.rst index 179eb4941..9f5a6b273 100644 --- a/source/educators/migration_wip/12_course_features/content_experiments/subsection_content_experiments_policies.rst +++ b/source/educators/how-tos/advanced_features/set_up_group_configuration_olx.rst @@ -1,5 +1,7 @@ .. Section is shared in CA and OLX guides +.. _Set Up Group Configuration for OLX Courses: + ************************************************ Set Up Group Configuration for OLX Courses ************************************************ @@ -94,3 +96,13 @@ experiment groups, and the second divides learners into three experiment groups. As this example shows, each group configuration is independent. Group IDs and names must be unique within a group configuration, but not across all group configurations in your course. + +.. seealso:: + :class: dropdown + + :ref:`Offering Differentiated Content` (concept) + :ref:`Overview of Content Experiments` (concept) + :ref:`Configure Your Course for Content Experiments` (how-to) + :ref:`Experiment Group Configurations` (reference) + :ref:`Add a Content Experiment in OLX` (how-to) + :ref:`Guidelines for Modifying Group Configurations` (concept) diff --git a/source/educators/migration_wip/12_course_features/content_experiments/content_experiments_test.rst b/source/educators/how-tos/advanced_features/test_content_experiments similarity index 98% rename from source/educators/migration_wip/12_course_features/content_experiments/content_experiments_test.rst rename to source/educators/how-tos/advanced_features/test_content_experiments index fab41bf8c..5f907130b 100644 --- a/source/educators/migration_wip/12_course_features/content_experiments/content_experiments_test.rst +++ b/source/educators/how-tos/advanced_features/test_content_experiments @@ -1,3 +1,5 @@ +.. _diataxis-type: how-to + .. This file is linked to from the OLX topic about testing content .. experiments. We did not use an include because file structure differs in .. the OLX guide and shared relative paths did not work. CT Nov 2015 diff --git a/source/educators/how-tos/communication/administer_discussions.rst b/source/educators/how-tos/communication/administer_discussions.rst new file mode 100644 index 000000000..82cfa2de4 --- /dev/null +++ b/source/educators/how-tos/communication/administer_discussions.rst @@ -0,0 +1,128 @@ +.. :diataxis-type: how-to + +.. _Administer Discussions: + +########################## +Administer Discussions +########################## + +**************** +Edit Messages +**************** + +Team members with the Discussion Moderator, Discussion Admin, Community TA or +Group Community TA role can edit the content of posts, responses, and +comments. Messages that include spoilers or solutions, or that contain +inappropriate or off-topic material, should be edited quickly to remove text, +images, or links. + +.. removed note for open edx re edit behavior in mobile apps. Posts can +.. now be edited in the mobile apps (though ability depends on permissions) +.. CT April 25, 2016 + +#. View the live version of the course. + +#. On the **Discussions** page, open the post with the content that requires + editing. You can select a single topic from the drop-down list of + discussion topics, apply a filter, or search to locate the post. + +#. For the post or for the response or comment that you want to edit, select + the "More" icon and then **Edit**. + +#. Remove the problematic portion of the message, or replace it with standard + text such as "[REMOVED BY MODERATOR]". + +#. Communicate the reason for your change. For example, "Posting a solution + violates the honor code." + +**************** +Delete Messages +**************** + +Team members with the Discussion Moderator, Discussion Admin, Community TA or +Group Community TA role can delete posts, responses, or comments. It might be +more appropriate to delete rather than edit posts that consist of spam or +include abusive language. + +.. removed note for open edx re deletion behavior in mobile apps. Posts can +.. now be deleted in the mobile apps (though ability depends on permissions) +.. CT April 25, 2016 + +#. View the live version of the course. + +#. On the **Discussion** page, open the post with the content that requires + deletion. You can select a single topic from the drop-down list of + discussion topics, apply a filter, or search to locate the post. + +#. For the post or for the response or comment that you want to delete, select + the "More" icon and then **Delete**. + +#. Select **OK** to confirm the deletion. + +.. important:: If a message is threatening or indicates serious harmful + intent, contact campus security at your institution. Report the incident + before taking any other action. + + +******************************** +Respond to Reports of Misuse +******************************** + +Learners have the option to report contributions that they find inappropriate. +Team members with the Discussion Moderator, Discussion Admin, Community TA or +Group Community TA role can check for messages that have been flagged in this +way and edit or delete them as needed. + +.. removed note for open edx re flag behavior in mobile apps. Posts can +.. now be flagged in the mobile apps. CT April 25, 2016 + +#. View the live version of your course and select **Discussion** at the top of + the page. + +#. In the discussion navigation pane at the side of the page, use the filter + drop-down list (set to **Show all** by default) to select **Flagged**. + +#. Review listed posts. A post is listed if it or any of its responses or + comments has been reported. The reported contribution includes a + **Reported** identifier. + +#. Edit or delete the post, response, or comment. Alternatively, remove the + flag: select the "More" icon and then **Unreport**. + + +***************************************************** +View Profile Information for Discussion Participants +***************************************************** + +To find out more about a specific discussion participant, you can view that +learner's edX profile from their linked username on discussion posts. + +To access a learner's profile from a discussion post that they contributed, +follow these steps. + +#. On the **Discussion** page, select a username in a post, response, or + comment. + +#. On the discussion page for that learner, select the linked username. + +The learner's account profile page opens. Learners can have either a limited +profile or a full profile. + +For more information about profiles, see `SFD Dashboard `_. + + +**************** +Block Users +**************** + +If a learner repeatedly misuses course discussions despite being warned, you +can unenroll that learner from the course. For more information, see +:ref:`unenroll_student`. The learner cannot re-enroll in the course if the +enrollment period for the course is over. + +.. seealso:: + :class: dropdown + + :ref:`Guidance for Discussion Moderators` (concept) + :ref:`Moderating_discussions` (concept) + :ref:`Assigning_discussion_roles` (how-to) diff --git a/source/educators/how-tos/communication/assigning_discussion_roles.rst b/source/educators/how-tos/communication/assigning_discussion_roles.rst new file mode 100644 index 000000000..5840f934e --- /dev/null +++ b/source/educators/how-tos/communication/assigning_discussion_roles.rst @@ -0,0 +1,81 @@ +.. :diataxis-type: how-to + +.. _Assigning_discussion_roles: + +************************************* +Assigning Discussion Moderation Roles +************************************* + +You must either be the course author, or have the Admin role, to add people to +discussion moderation roles. + +You must obtain the email address or username for each person that you want to +add. + +* To obtain the email address or username for a course team member, in the LMS + select **Instructor**, then select **Membership**. In the **Course Team + Management** section, select the current course team role (Staff or Admin) of + the person whose information you are looking for. From the list of course + team members with the selected role locate the required email address or + username. + +* To obtain the email address or username for an enrolled learner, in the LMS + select **Instructor**, then select **Data Download**. In the + **Reports** section, select **Download profile information as a CSV**. In the + downloaded file, locate the required email address or username. + + +==================================== +Add Someone To a Discussion Role +==================================== + +You can add any user who is already enrolled in your course to a discussion +moderation role. + +.. note:: To add someone to the Discussion Admin role, you must be the course + author or a course team member who has the Admin role. + +#. View the live version of the course. + +#. Select **Instructor**, and then select **Membership**. + +#. In the **Course Team Management** section, select the discussion role that + you want to assign: **Discussion Admins**, **Discussion Moderators**, + **Group Community TA**, or **Community TA**. + +#. Under the list of users who currently have that role, enter the email address + or username of the person you want to add. + +#. Select **Add** for the role type. + + The person who you added appears in the list. + + +====================================== +Remove Someone from a Discussion Role +====================================== + +To remove someone from a discussion moderation role, you must be the course +author or have the Admin role. + +#. View the live version of the course. + +#. Select **Instructor**, and then select **Membership**. + +#. In the **Course Team Management** section, select the discussion role from + which you want to remove the user: **Discussion Admins**, **Discussion + Moderators**, **Group Community TA**, or **Community TA**. + +#. In the list of users who currently have that role, locate the user you + want to remove, and then select **Revoke access**. + + The person who you removed no longer appears in the list. + +.. seealso:: + :class: dropdown + + :ref:`Guidance for Discussion Moderators` (concept) + :ref:`Moderating_discussions` (concept) + :ref:`Administer Discussions` (how-to) + + diff --git a/source/educators/how-tos/communication/closing_discussions.rst b/source/educators/how-tos/communication/closing_discussions.rst new file mode 100644 index 000000000..8a5f4e1dd --- /dev/null +++ b/source/educators/how-tos/communication/closing_discussions.rst @@ -0,0 +1,44 @@ +.. :diataxis-type: how-to + +.. _Closing Discussions: + +============================================ +Closing Discussions +============================================ + +.. note:: You can only close discussions when you work in a web browser. You + cannot close discussions when you work in an edX mobile app. + +To define when discussions are closed to new contributions and when they +reopen, follow these steps. + +1. Navigate to edx discussion configuration page +(see :ref:`Configuring Edx Discussions`). + +2. Scroll down to **Discussion Blackout Dates** field. + +3. Create a new blackout date range by clicking on **Add blackout date range**. + +.. image:: /_images/educator_how_tos/Discussion_blackout_dates_configuration.png + :width: 300 + :alt: Option for configuring discussion blackout dates. + +4. Add start and end dates and times in the format specified. + +.. note:: The dates and times that you enter are in Coordinated Universal + Time (UTC), not in your local time zone. You might want to verify that you + have specified the times that you intend by using a time zone converter. + +.. note:: To close the course discussions permanently, specify an end date + and time far in the future. + +5. You can add more than one blackout date ranges using step 3 and 4 above. + +6. Select **Save Changes**. + +.. seealso:: + :class: dropdown + + :ref:`Discussions` (concept) + :ref:`Running_discussions` (concept) + :ref:`Configuring Edx Discussions` (how-to) \ No newline at end of file diff --git a/source/educators/migration_wip/17_manage_discussions/discussions.rst b/source/educators/how-tos/communication/configure-discussions.rst similarity index 55% rename from source/educators/migration_wip/17_manage_discussions/discussions.rst rename to source/educators/how-tos/communication/configure-discussions.rst index afbf5d992..6309c6495 100644 --- a/source/educators/migration_wip/17_manage_discussions/discussions.rst +++ b/source/educators/how-tos/communication/configure-discussions.rst @@ -1,27 +1,4 @@ -.. _Discussions: - -Creating Course Discussions -########################### - -Discussions in an edX course include both course-wide topics of interest to -all learners (such as "Feedback", "Troubleshooting", or "Technical Help") as -well as content-specific topics that you add to course units as discussion -components. You can create both types of discussion topics in Studio. - -For information about creating discussion topics, see the following sections. - -.. contents:: - :local: - :depth: 1 - - -For information about creating discussions in which learners in a group (cohort) -only interact with posts from other learners in the same group, -see :ref:`About Divided Discussions`. - -For information about running and moderating course discussions, see -:ref:`Running_discussions` and :ref:`Moderating_discussions`. - +.. :diataxis-type: how-to .. _Configuring Edx Discussions: @@ -38,21 +15,21 @@ To open edx discussions configuration page, follow these steps. This will take you to the discussions configuration page where you can select a discussion provider. -.. image:: ../images/Discussion_tile_in_pages_and_resources.png +.. image:: /_images/educator_how_tos/Discussion_tile_in_pages_and_resources.png :width: 300 :alt: Appearance of Discussion tile in Pages & Resources. 4. Select edx as discussion provider by checking the box on top-right of **edx** tile. Click Next. -.. image:: ../images/Tile_for_edx_discussion_provider.png +.. image:: /_images/educator_how_tos/Tile_for_edx_discussion_provider.png :width: 300 :alt: Appearance of tile for edx discussion provider in configuration. 5. This is the edx discussions configuration page. All configuration options for edx discussions can be found here. -.. image:: ../images/edx_discussions_configurations_page.png +.. image:: /_images/educator_how_tos/edx_discussions_configurations_page.png :width: 300 :alt: Appearance of edx discussions configurations page. @@ -84,13 +61,13 @@ To create a course-wide discussion topic, follow these steps. 2. Scroll down to **General discussion topics**. You would see a topic named **General** already there. This topic cannot be deleted but can be renamed. -.. image:: ../images/General_discussion_topics_edx_discussions.png +.. image:: /_images/educator_how_tos/General_discussion_topics_edx_discussions.png :width: 300 :alt: A topic named General will already exist in General discussion topics. 3. Click on **Add topic** and add a topic name (e.g. "Course Q&A") -.. image:: ../images/Add_general_topic_name_edx_discussions.png +.. image:: /_images/educator_how_tos/Add_general_topic_name_edx_discussions.png :width: 300 :alt: Adding general topic name. @@ -99,7 +76,7 @@ already there. This topic cannot be deleted but can be renamed. When learners select the **Discussion** page for your course, the drop-down Discussion list now includes the topic you added. -.. image:: ../images/New_general_discussion_topic.png +.. image:: /_images/educator_how_tos/New_general_discussion_topic.png :width: 300 :alt: A new topic named Course Q&A in the list of discussion topics. @@ -110,29 +87,18 @@ Discussion list now includes the topic you added. :ref:`Divide Course Wide Discussion Topics`. -.. _Create ContentSpecific Discussion Topics: - -Create Content-Specific Discussion Topics -***************************************** - -Course runs created on or after May 16, 2023, use an upgraded version of -the edX discussion forum. Learn more about it `here`_. The creation of content-specific discussion topics for both the legacy and the upgraded versions -of the discussion forums are explained separately in the sections below. - -.. _here: https://openedx.atlassian.net/wiki/spaces/COMM/pages/3470655498/Discussions+upgrade+Sidebar+and+new+topic+structure. - Upgraded Edx Forum ================== Discussion can be enabled for a course unit, which is equivalent to adding -a content-specific discussion topic in that unit in the legacy version of -the forum. To enable discussion on a course unit: +a content-specific discussion topic in that unit in the :ref:`legacy version of +the forum `. To enable discussion on a course unit: 1. Open unit’s configuration in Studio. 2. Check the **Enable discussion** checkbox. -.. image:: ../images/enable-discussion.png +.. image:: /_images/educator_how_tos/enable-discussion.png :width: 700 :align: center :alt: Toggle switches for anonymous posts in edx discussions configuration. @@ -142,7 +108,7 @@ the forum. To enable discussion on a course unit: Discussions will be enabled on the unit within 1 minute. Units that have discussions enabled for them will show a **Discussion enabled** label in Studio. -.. image:: ../images/discussion-enabled.png +.. image:: /_images/educator_how_tos/discussion-enabled.png :width: 700 :align: center :alt: Toggle switches for anonymous posts in edx discussions configuration. @@ -157,7 +123,7 @@ discussions enabled for them will show a **Discussion enabled** label in Studio. Users can participate in these discussions using the **Discussion** tab or via the discussion sidebar visible alongside the course unit. -.. image:: ../images/discussion-sidebar.png +.. image:: /_images/educator_how_tos/discussion-sidebar.png :width: 300 :align: center :alt: Toggle switches for anonymous posts in edx discussions configuration. @@ -172,7 +138,7 @@ tab. Otherwise it will be deleted. If discussion is enabled again for this unit, the archived topic will be restored along with the threads contained within it. -.. image:: ../images/archived.png +.. image:: /_images/educator_how_tos/archived.png :width: 300 :height: 400 :alt: Toggle switches for anonymous posts in edx discussions configuration. @@ -188,56 +154,6 @@ with the threads contained within it. contain any threads). Un-marking the subsection will restore archived topics and replace deleted topics with new ones. -Legacy Edx Forum -================ - -To create a content-specific discussion topic, you add a discussion component -to a unit. Typically, you do this while you are designing and creating your -course in Studio. Follow the instructions in :ref:`Working with Discussion -Components`. The result is a discussion topic associated with a unit and its -content. Learners can access content-specific topics both in the course unit -and on the Discussion page. - -.. warning:: Follow the recommended steps to add discussion components. Do not - create discussion topics by using the Duplicate button in Studio, and do - not reference the same discussion ID in more than one place in your course. - Duplicated discussion components result in discussion topics that contain the - same conversations, even if learners post in different discussion topics. - -For information about the visibility of content-specific discussion -topics, see :ref:`Visibility of Discussion Topics`. - -.. note:: In courses with cohorts enabled, when you add discussion components to - units in Studio, these discussion topics are by default unified. All learners - in the course can see and respond to posts from all other learners. You can - change content-specific discussion topics to be divided, so that only members - of the same group can see and respond to each other's posts. For information, - see :ref:`Divide All Content Specific Discussion Topics`. - -.. _Visibility of Discussion Topics: - -Understanding When Learners Can See Discussion Topics -***************************************************** - -The names that you specify as the category and subcategory names for discussion -components are not visible on the Discussion page in the LMS until after -the course has started and the unit is released. - -However, "seed" posts that you create in content-specific discussion topics -before a course starts, or before the unit is released, are immediately visible -on the Discussion page, even though the containing category or subcategory -names are not visible. EdX recommends that you do not create posts in -content-specific discussion topics before a unit is released. For more -information about release dates and the visibility of components, see -:ref:`Controlling Content Visibility`. - -In contrast, :ref:`course-wide discussion topics` that you create on the edx discussions configuration page in Studio, -including the default "General" discussion topic, are immediately visible, -regardless of whether the course has started. They are not associated with any -particular section or subsection of the course, and are not subject to -release dates. - .. _Anonymous_posts: @@ -257,7 +173,7 @@ To allow anonymous discussion posts in your course, follow these steps. 2. Toggle the **Allow anonymous discussion posts to peers** to enable learners to make posts that are anonymous to everyone other learners. - .. image:: ../images/anonymous-posting.png + .. image:: /_images/educator_how_tos/anonymous-posting.png :width: 400 :alt: Toggle switches for anonymous posts in edx discussions configuration. @@ -266,25 +182,13 @@ make posts that are anonymous to everyone other learners. Once the toggle has been enabled, forum users will have the option to create posts that are anonymous to other learners, as seen below. - .. image:: ../images/post-anonymously.png + .. image:: /_images/educator_how_tos/post-anonymously.png :width: 600 :align: center :alt: Options for anonymous posting while creating a post. -.. _Discussions on Mobile Apps: - -Discussions in the edX Mobile App -********************************* - -Learners can participate in course discussions using the edX mobile app as -they do on the edX site, but there are some differences in the actions that -moderators can take in discussions using the mobile app. To perform moderation -or administrative tasks for your course discussions, you need to work in a web -browser. - -The following actions are not supported on the edX mobile apps. +.. seealso:: + :class: dropdown - * Pinning posts - * Marking responses to question posts as answers - * Endorsing responses to discussion posts - * Closing posts + :ref:`Discussions` (concept) + \ No newline at end of file diff --git a/source/educators/how-tos/communication/index.rst b/source/educators/how-tos/communication/index.rst new file mode 100644 index 000000000..cbd907038 --- /dev/null +++ b/source/educators/how-tos/communication/index.rst @@ -0,0 +1,9 @@ +############################# +Communication +############################# + +.. toctree:: + :maxdepth: 1 + :glob: + + * \ No newline at end of file diff --git a/source/educators/how-tos/communication/review_sent_messages.rst b/source/educators/how-tos/communication/review_sent_messages.rst new file mode 100644 index 000000000..5c6160bf4 --- /dev/null +++ b/source/educators/how-tos/communication/review_sent_messages.rst @@ -0,0 +1,46 @@ +.. :diataxis-type: how-to + +.. _Review Sent Messages: + +******************************** +Review Sent Messages +******************************** + +You can review a list of all of the messages that have been sent for the +course. For any listed message, you can review the subject, the username of the +person who sent it, the date and time sent, its selected recipients, and the +message text. + +#. View the live version of your course. + +#. Select **Instructor**, and then select **Email**. + +#. In the **Email Task History** section of the page, select **Show Sent Email + History**. The list of sent messages displays. + +.. image:: /_images/educator_how_tos/Bulk_email_list.png + :alt: A tabular list of sent messages, with columns for subject, sent by, + time sent, and number sent. + +#. To review additional information for a sent message, select its subject. The + message opens in a dialog box. + +.. image:: /_images/educator_how_tos/Bulk_email_sent.png + :alt: A dialog box with the subject, sent by, date and time sent, sent to, + and message for an email message, and an option to Copy Email + to Editor. + +#. Optionally, use the message as the basis for a new message: select **Copy + Email to Editor**. The dialog box closes and you can edit the text, links, + and formatting that were duplicated into the **Subject** and **Message** + fields. + + When you create a message by copying a previously-sent message, be sure to + review and test it thoroughly before you send it to all course participants. + +.. seealso:: + :class: dropdown + + :ref:`Bulk Email` (reference) + :ref:`Send_Bulk_Email` (how-to) + :ref:`Example Messages to Students` (reference) \ No newline at end of file diff --git a/source/educators/how-tos/communication/send_bulk_email.rst b/source/educators/how-tos/communication/send_bulk_email.rst new file mode 100644 index 000000000..1984f659e --- /dev/null +++ b/source/educators/how-tos/communication/send_bulk_email.rst @@ -0,0 +1,98 @@ +.. :diataxis-type: how-to + +.. _Send_Bulk_Email: + +************************************************** +Send an Email Message to Course Participants +************************************************** + +.. Important:: You cannot cancel non-scheduled bulk email messages after you send them. + + Before you send a message to a wide audience, send the message only to + yourself to test and review it. Make sure it displays as you intend it to, + and that any links or media function correctly. + +To send an email message to course participants, follow these steps. + +#. View the live version of your course. + +#. Select **Instructor**, and then select **Email**. + +#. From the **Send to** option, select one or more groups of email recipients. + + .. note:: Make sure you understand who is included or excluded when you + send a message to one, or a combination, of the recipient groups. For + details, see :ref:`Bulk Email Who Is Included or Excluded` + +#. In the **Subject** field, enter a subject for the message. + +#. In the **Message** box, enter the text for the message. + + For details about options for composing your message, see + :ref:`Options for Email Message Text`. + +#. Select **Send Email**. A bulk email task is queued for processing. + +Multiple courses use the same queue to complete these tasks, so it can take +some time for your message to be sent to all of its recipients. You can +perform other tasks on the instructor dashboard or navigate to other pages +while you wait for your message to be sent. + +.. _Send_Scheduled_Bulk_Email: + +********************************************************* +Send a Scheduled Email Message to Course Participants +********************************************************* + +We have introduced a way to schedule a bulk email message to be sent at a +specified date and time in the future. Once a message has been scheduled, +and until the message has been sent, it will be possible to view, edit, or +cancel these messages. + +.. Important:: Messages may not be sent at the *exact* time specified + + .. note:: We check the message schedules every fifteen minutes. For example, + A message scheduled to be sent at 09:10:00 will not be processed until + 09:15:00. Once the schedule for a message has elapsed it will be sent. + When processed, these messages will be placed on the same queue that + non-scheduled messages use, so it may take some time for your message to + be sent to all recipients. + +To send a scheduled email message to course participants, follow these steps. + +#. View the live version of your course. + +#. Select **Instructor**, and then select **Email**. + +#. From the **Send to** option, select one or more groups of email recipients. + + .. note:: Make sure you understand who is included or excluded when you + send a message to one, or a combination, of the recipient groups. For + details, see :ref:`Bulk Email Who Is Included or Excluded` + +#. In the **Subject** field, enter a subject for the message. + +#. In the **Message** box, enter the text for the message. + + For details about options for composing your message, including using keywords to make the message more personal, see + :ref:`Options for Email Message Text`. + +#. Check the **Schedule this email for a future date** checkbox. This also + updates the **Send Email** button to a **Schedule Email** button. + +#. Enter a date (in the future) within the **Send date** field, or optionally + click on the calendar icon to open up a date picker to assist in selecting a + date for the message. + +#. Enter a time within the **Send time** field, or optionally + click on the clock icon to open up a time picker. + +#. Select **Schedule Email**. A bulk email task is then scheduled for + processing. + +.. seealso:: + :class: dropdown + + :ref:`Bulk Email` (reference) + :ref:`Review Sent Messages` (how-to) + :ref:`Example Messages to Students` (reference) \ No newline at end of file diff --git a/source/educators/migration_wip/17_manage_discussions/set_up_divided_discussions.rst b/source/educators/how-tos/communication/setting_up_divided_discussions.rst similarity index 60% rename from source/educators/migration_wip/17_manage_discussions/set_up_divided_discussions.rst rename to source/educators/how-tos/communication/setting_up_divided_discussions.rst index 344e21d2a..2e8a3fb55 100644 --- a/source/educators/migration_wip/17_manage_discussions/set_up_divided_discussions.rst +++ b/source/educators/how-tos/communication/setting_up_divided_discussions.rst @@ -1,65 +1,4 @@ -.. _About Divided Discussions: - -################################### -About Divided Discussion Topics -################################### - -This section provides information about setting up discussions that are -divided by learner groups (cohorts) within your course. - -.. contents:: - :local: - :depth: 1 - -For overview information about discussions in a course, see :ref:`Discussions`. - -For more information about creating differentiated course content for learners -in different groups (cohorts), see :ref:`Offering Differentiated Content`. - - -****************************** -What Are Divided Discussions? -****************************** - -With divided discussions, discussion topics are visible to all learners, but -the posts, responses, and comments within these topics are divided so that -learners participate in the discussion only with other members of the same -group (cohort). - -Discussion topics that are not divided are unified, meaning that all learners -in the course can see and respond to posts, responses, and comments from any -other learner in the course. - -======================================= -Best Practices for Divided Discussions -======================================= - -If you divide discussions, a good practice is to use a naming convention for -discussion topics, so that learners clearly understand the audience for a -discussion topic before they add posts to that topic. For information about -naming conventions, see :ref:`Apply Naming Conventions to Discussion Topics`. - -You can also appoint learners as Community TAs or Group Commmunity -TAs to help you to moderate course discussions. You might use Group -Community TAs if the content of discussion topics by one group (cohort) should not be -shared with another group. Group Community TAs are themselves members of -learner groups (cohorts) that you use in your course. As discussion moderators, they can -only see and respond to posts by other members of their own group (cohort). For information, -see :ref:`Assigning_discussion_roles`. - -For more information about managing discussions, see :ref:`Managing Divided -Discussion Topics` and :ref:`Running_discussions`. - -.. note:: - - Another method of providing different discussion experiences for learners in - different groups in your course is to use the access settings of discussion - components. For example, you can add multiple discussion components and use - each component's access settings to restrict access to each discussion - component to a specific content group. You can then assign these content - groups to learner groups (cohorts). For more information, - see :ref:`Setting Up Divided Discussions`. - +.. :diataxis-type: how-to .. _Setting Up Divided Discussions: @@ -117,7 +56,7 @@ the steps below. 2. Turn on the toggle for **Divide discussions by cohort** to divide all content-specific discussion topics by cohort. -.. image:: ../images/Discussions_toggle_cohort.png +.. image:: /_images/educator_how_tos/Discussions_toggle_cohort.png :width: 300 :alt: An image showing the toggle for dividing content-specific discussion topics @@ -156,14 +95,14 @@ follow these steps. 2. Turn on the toggle for **Divide discussions by cohort** to divide all content-specific discussion topics by cohort. -.. image:: ../images/Discussions_toggle_cohort.png +.. image:: /_images/educator_how_tos/Discussions_toggle_cohort.png :width: 300 :alt: An image showing the toggle for dividing content-specific discussion topics 3. Turn on the toggle for **Divide course-wide discussion topics** to divide all course-wide discussion topics by cohort. -.. image:: ../images/Discussion_toggle_cohort_coursewide.png +.. image:: /_images/educator_how_tos/Discussion_toggle_cohort_coursewide.png :width: 300 :alt: An image showing the toggle and options for dividing course-wide discussion topics @@ -173,3 +112,8 @@ follow these steps. For information about managing discussions that are divided, see :ref:`Managing Divided Discussion Topics`. + +.. seealso:: + :class: dropdown + + :ref:`About Divided Discussions` (concept) diff --git a/source/educators/migration_wip/12_course_features/cohorts/cohorts_setup_discussions.rst b/source/educators/how-tos/communication/setup_cohorted_discussions.rst similarity index 77% rename from source/educators/migration_wip/12_course_features/cohorts/cohorts_setup_discussions.rst rename to source/educators/how-tos/communication/setup_cohorted_discussions.rst index a67cd1c16..ba0de92c9 100644 --- a/source/educators/migration_wip/12_course_features/cohorts/cohorts_setup_discussions.rst +++ b/source/educators/how-tos/communication/setup_cohorted_discussions.rst @@ -1,3 +1,5 @@ +.. :diataxis-type: how-to +.. NOTE: This is a how-to in that it answers a very specific "how" to set up discussions in a cohorted course, even though it does that by pointing to other docs. .. _Set up Discussions in Cohorted Courses: diff --git a/source/educators/how-tos/configure_prerequisite_content.rst b/source/educators/how-tos/configure_prerequisite_content.rst new file mode 100644 index 000000000..4ab7fda2a --- /dev/null +++ b/source/educators/how-tos/configure_prerequisite_content.rst @@ -0,0 +1,118 @@ +.. :diataxis-type: how-to + +.. _configuring_prerequisite_content: + +******************************** +Prerequisite Course Subsections +******************************** + +You can lock subsections of your course until learners complete other, +prerequisite subsections. If a subsection has a prerequisite, it is displayed +in the course outline with a lock icon, and learners cannot view the subsection +content until they have earned a minimum score in the prerequisite subsection. + +.. note:: + You must first :ref:`Enable Course Prerequisites` before + prerequisite course subsections can be used. + +.. _enabling_subsection_gating: + +================================= +Enable Subsection Prerequisites +================================= + +To enable prerequisite subsections in a course, follow these steps. + +#. From the **Settings** menu, select **Advanced Settings**. + +#. In the **Enable Subsection Prerequisites** field, enter ``true``. + +#. Select **Save Changes**. + +.. _creating_a_prerequisite_subsection: + +================================== +Create a Prerequisite Subsection +================================== + +To prevent learners from seeing a subsection of your course until they have +earned a minimum score or completed a minimum portion in a prerequisite +subsection, follow these steps. + +.. note:: + Make sure that you configure subsection prerequisites in the order that you + intend for learners to encounter them in the course content. The + prerequisite configuration controls do not prevent you from creating a + circular chain of prerequisites that will permanently hide them from + learners. + +.. note:: + You cannot use :ref:`open response assessments` that have a point value of 0 as the prerequisite for other course + subsections. + +#. Enable subsection prerequisites for your course. For more information, see + :ref:`enabling_subsection_gating`. + +#. Select the **Configure** icon for the subsection that must be completed + first. This is the prerequisite subsection. + + .. image:: /_images/educator_how_tos/subsections-settings-icon.png + :alt: A subsection in the course outline with the configure icon + indicated. + :width: 600 + +#. Select the **Advanced** tab. + +#. Under **Use as a Prerequisite**, select **Make this subsection available as + a prerequisite to other content**. + +#. Select **Save**. + +#. Select the **Configure** icon for the subsection that + will be hidden until the prerequisite is met. + +#. Select the **Advanced** tab, and then locate the **Limit Access** section. + +#. In the **Prerequisite** list, select the name of the subsection you want to + specify as the prerequisite. + + .. image:: /_images/educator_how_tos/prerequisite-percent-complete.png + :alt: The Limit Access section in the Advanced settings, showing the + Prerequisite, Minimum Score, and Minimum Completion Percentage + controls. + +#. To require that learners achieve a minimum score in the prerequisite + subsection before the current subsection opens, enter the percent of the + total score that learners must earn in the **Minimum Score** field. If + the prerequisite section is not a problem set, set **Minimum Score** to + ``0`` and set **Minimum Completion Percentage** to a value greater than + zero. + + For example, if the prerequisite subsection includes four problems and each + problem is worth the same number of points, set the **Minimum Score** to + ``75`` to require at least three correct answers. + + To require that learners complete a minimum portion of the prerequisite + subsection before the current subsection opens, enter the percent of the + prerequisite subsection that learners must complete in the **Minimum + Completion Percentage** field. + + If you set both the **Minimum Score** field and the **Minimum Completion + Percentage** field to a value greater than zero, then learners must satisfy + both conditions in the prerequisite section before they can view the + current subsection. The default value for both the **Minimum Score** field + and the **Minimum Completion Percentage** field is ``100``. + +#. Select **Save**. + +#. In the course outline, if a subsection has a prerequisite, the prerequisite + name appears under the subsection name. + + .. image:: /_images/educator_how_tos/studio-locked-content.png + :alt: A subsection in the course outline with a prerequsitie indicated. + :width: 600 + + .. note:: Prerequisite course subsection settings are not retained when + you :ref:`export or import a course`, or + when you :ref:`re-run a course`. \ No newline at end of file diff --git a/source/educators/how-tos/course_development/add_edit_components.rst b/source/educators/how-tos/course_development/add_edit_components.rst new file mode 100644 index 000000000..71da9add8 --- /dev/null +++ b/source/educators/how-tos/course_development/add_edit_components.rst @@ -0,0 +1,135 @@ +.. :diataxis-type: how-to +.. _Add a Component: + +******************** +Add a Component +******************** + +To add a component to the unit, follow these steps. + +#. In Studio, open the page for the unit. +#. Under **Add New Component**, select a component type. The default component + types are discussion, HTML, problem, and video. + +For more information, see the documentation for the specific component type +that you want to work with. + +- :ref:`Working with Discussion Components` +- :ref:`Working with Text Components ` +- :ref:`Working with Problem Components` +- :ref:`Working with Video Components` + +After you add a component, it is not visible to learners until you +:ref:`publish the unit`. + +.. _Edit a Component: + +******************** +Edit a Component +******************** + +To edit a component, you select **Edit** in the component's title bar in +Studio. + +.. image:: /_images/educator_how_tos/unit-edit.png + :alt: A component with the Edit icon indicated in the toolbar. + :width: 400 + +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 +:ref:`publish the unit`. + +.. _Set the Display Name for a Component: + +===================================== +Set the Display Name for a Component +===================================== + +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 +reporting and analytics systems. + +The following illustration shows the display name of a problem in Studio and in +the LMS. + +.. image:: /_images/educator_how_tos/display_names_problem.png + :alt: The identifying display name for a problem in Studio, and the LMS. + :width: 800 + +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. + + * For a discussion or video component, the dialog box opens to the list of + settings, including the **Display Name** field. + + * For an HTML or problem component, the dialog box opens to an editing view. + Select **Settings** to show the list of settings, including the **Display + Name** field. + +#. Edit the **Display Name** field. + + .. image:: /_images/educator_how_tos/display-name.png + :alt: The settings dialog box for a problem component. + :width: 500 + +#. Select **Save**. + +Different types of components have different fields in the **Settings** dialog +box, but all of them have a **Display Name** field. + + +.. _Duplicate a Component: + +********************** +Duplicate a Component +********************** + +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. + +.. image:: /_images/educator_how_tos/unit-dup.png + :alt: A unit with the Duplicate icon selected and highlighted. + +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 :ref:`publish the unit`. + +.. note:: Duplicating content experiments after you have configured them is not + supported. + + +.. _Delete a Component: + +********************** +Delete a Component +********************** + +.. caution:: + Be sure you want to delete the component. You cannot undo the deletion. + +To delete a component, follow these steps. + +#. Select the **Delete** icon in the component header. + +.. image:: /_images/educator_how_tos/unit-delete.png + :alt: A unit with the Delete icon circled. + +2. When you receive the confirmation prompt, select **Yes, delete this + component**. + +After you delete a component in Studio, the component remains visible to +learners until you :ref:`publish the unit`. + + + diff --git a/source/educators/migration_wip/8_course_components/create_discussion.rst b/source/educators/how-tos/course_development/create_discussion.rst similarity index 65% rename from source/educators/migration_wip/8_course_components/create_discussion.rst rename to source/educators/how-tos/course_development/create_discussion.rst index db3a1007b..3ebd414cc 100644 --- a/source/educators/migration_wip/8_course_components/create_discussion.rst +++ b/source/educators/how-tos/course_development/create_discussion.rst @@ -1,19 +1,11 @@ +.. :diataxis-type: how-to + .. _Working with Discussion Components: ################################### Working with Discussion Components ################################### -This section describes how to work with discussion components in Studio. - -.. contents:: - :local: - :depth: 1 - -******************* -Overview -******************* - You can add discussion components to a unit to pose questions about other components, such as videos or text, in the unit. A discussion component gives learners a chance to respond to and interact with each other about a specific @@ -66,7 +58,7 @@ Create a Discussion Component visible to learners in the list of discussion topics on the **Discussion** page. - .. image:: ../images/Discussion_category_subcategory.png + .. image:: /_images/educator_how_tos/Discussion_category_subcategory.png :alt: A list of discussions with the "Answering More Than Once" topic indented under "Getting Graded". :width: 400 @@ -78,31 +70,3 @@ Create a Discussion Component started and the unit is released. For more details about when discussion topics are visible, see :ref:`Visibility of Discussion Topics`. -.. _A Students View of the Discussion: - -********************************** -A Learner's View of the Discussion -********************************** - -When you add a discussion component to a unit, in the LMS, learners see only -the discussion, together with the display name of the discussion component, the category, and the subcategory. EdX recommends that you add an HTML -component before each discussion component where you add some text to -introduce the discussion topic. - -In the following example, the discussion component follows an HTML -component. Learners select **Add a Post** to post their own contributions. - -.. image:: ../images/HTMLandDisc.png - :alt: An HTML text component and then a discussion component, as they appear - in the LMS. - -Content-specific topics that you add using discussion components are included -on the course **Discussion** page in the same way as course-wide discussion -topics as included. In the following example, the category (1) and the -subcategory (2) of the discussion component is shown in the list of -discussion topics. - -.. image:: ../images/Discussion_category_subcategory.png - :alt: The list of discussions on the Discussion page in the LMS, showing the - category and subcategory of a content-specific discussion topic. - :width: 400 \ No newline at end of file diff --git a/source/educators/how-tos/course_development/create_edit_publish_subsections.rst b/source/educators/how-tos/course_development/create_edit_publish_subsections.rst new file mode 100644 index 000000000..28025880b --- /dev/null +++ b/source/educators/how-tos/course_development/create_edit_publish_subsections.rst @@ -0,0 +1,113 @@ +.. :diataxis-type: how-to + +.. _Create a Subsection: + +**************************** +Create a Subsection +**************************** + +To create a new subsection, follow these steps. + +#. In the outline, expand the section in which you want to create a new + subsection. +#. Select **New Subsection** at the bottom of the expanded section. A new + subsection appears at the end of the section, with the subsection name + selected. +#. Enter the name for the new subsection. A descriptive name can help learners + locate content in the course. It can also help you select content when you + analyze performance in reporting and analytics systems. +#. :ref:`Add units` to the new subsection as needed. + +It is recommended that you :ref:`test course content ` as you create new subsections. + +******************************** +Change a Subsection Name +******************************** + +To change a subsection name, select the **Edit** icon next to the subsection +name. The name field becomes editable. Enter the new name, and then tab or +click outside of the field to save the name. + +.. _Set a Subsection Release Date: + +******************************** +Set a Subsection Release Date +******************************** + +To set the subsection release date, follow these steps. + +#. Select the **Configure** icon in the subsection box. + + .. image:: /_images/educator_how_tos/subsections-settings-icon.png + :alt: A subsection in the course outline with an arrow pointing to the + configure icon. + :width: 500 + + The subsection settings dialog box opens. + +#. On the **Basic** tab, under **Release Date and Time**, enter the release + date and time for the subsection. + + .. note:: The time that you set is in Coordinated Universal Time (UTC). You + might want to verify that you have specified the time that you intend by + using a time zone converter such as `Time and Date Time Zone Converter`_. + + Learners who have specified a time zone in their account settings see + course dates and times converted to their specified time zone. Learners + who have not specified a time zone in their account settings see course + dates and times on their dashboards, in the body of the course, and on + their **Progress** pages in the time zone that their browsers specify. + Learners see other course dates and times in UTC. + +#. Select **Save**. + +For more information, see :ref:`Release Dates`. + + + +.. _Publish all Units in a Subsection: + +********************************** +Publish All Units in a Subsection +********************************** + +To publish all new and changed units in a subsection, select the **Publish** +icon in the box for the subsection. + +.. image:: /_images/educator_how_tos/outline-publish-icon-subsection.png + :alt: Part of a course outline with the publishing icon for a subsection + circled. + :width: 500 + +.. note:: + The **Publish** icon only appears when there is new or changed content within + the subsection. + +See :ref:`Unit Publishing Status` for information about statuses and visibility +to learners. + + +.. _Delete a Subsection: + +******************************** +Delete a Subsection +******************************** + +When you delete a subsection, you delete all units within the subsection. + +.. warning:: + You cannot restore course content after you delete it. To ensure you do not + delete content that you might need later, you can move any unused content to a + section in your course that you set to never release. + +To delete a subsection, follow these steps. + +#. In the subsection that you want to delete, select the **Delete** icon. + + .. image:: /_images/educator_how_tos/subsection-delete.png + :alt: Part of a course outline showing a subsection with the Delete icon + circled. + +#. When the confirmation prompt appears, select **Yes, delete this + subsection**. diff --git a/source/educators/how-tos/course_development/create_edit_publish_unit.rst b/source/educators/how-tos/course_development/create_edit_publish_unit.rst new file mode 100644 index 000000000..85ca12508 --- /dev/null +++ b/source/educators/how-tos/course_development/create_edit_publish_unit.rst @@ -0,0 +1,247 @@ +.. :diataxis-type: how-to + +.. _Create a Unit: + +**************************** +Create a Unit +**************************** + +You can create a unit from the outline or create a unit in the same subsection +from the unit page. + +To create a unit from the outline, follow these steps. + +#. In the outline, expand the subsection in which you want to create a new + unit. +#. Select **New Unit** at the bottom of the expanded subsection. A new + page opens for you to add components to the unit. +#. On the unit page, the unit name is selected. Supply an identifying name. A + descriptive name can help learners locate content in the course. It can + also help you select content when you analyze performance in reporting and + analytics systems. +#. :ref:`Add components` to the new unit as needed. + +To create a unit from a unit page, follow these steps. + +#. In the **Unit Navigation Bar** area, select **New Unit**. + + ... image:: /_images/educator_how_tos/unit_location.png + :alt: The Unit Navigation Bar in the Unit page. + :width: 660 + + The unit page for the new unit opens automatically. + +#. On the unit page, the unit name is selected. Supply an identifying name. A + descriptive name can help learners locate content in the course. It can + also help you select content when you analyze performance in reporting and + analytics systems. + +#. :ref:`Add components` to the new unit as needed. + +You must then :ref:`publish the unit` to make it visible to +learners. + + +.. _Edit a Unit: + +************** +Edit a Unit +************** + +You can edit a unit in the following ways. + +* Edit the unit name +* Add components to units +* Reorganize Components in Units + +When you make any of these changes, if you previously published the unit, the +state changes to :ref:`Draft Unpublished Changes`. You must then :ref:`publish +the unit` to make your edits visible to learners. + +If you are designing your course to :ref:`offer different content` to different groups of learners, you can also +:ref:`Set access restrictions for the unit` to specify which learner groups a unit is available to. + + +============================== +Edit the Unit Name +============================== + +To edit a unit name, on the unit page in Studio, select **Edit** next to the +name. + +.. image:: /_images/educator_how_tos/unit-edit-icon.png + :alt: The Edit icon for the unit name with the mouseover help showing. + :width: 300 + +The name field becomes editable. Enter the new name, and then tab or click +outside of the field to save the name. + + +============================== +Reorganize Components in Units +============================== + +You can reorganize components within a unit by dragging and dropping them to +new locations. + +To change the location of a component, move your mouse pointer over the **Drag +to reorder** handle on the component toolbar. The pointer changes to a four- +headed arrow. You can then drag the component to the location that you want. + +In the image that follows, the handle for the discussion component is selected. + +.. image:: /_images/educator_how_tos/unit-drag-selected.png + :alt: A discussion component selected so that it can be dragged. + :width: 600 + +A blue outline indicates where the component will land when you release the +mouse button. For example, in the image below, the discussion component is +being moved to the top of the unit. + +.. image:: /_images/educator_how_tos/unit-drag-moved.png + :alt: A component being dragged to a new location. + :width: 600 + + +.. _Delete a Unit: + +******************************** +Delete a Unit +******************************** + +You delete a unit from the course outline in Studio. + +When you delete a unit, you delete all components within the unit. + +.. warning:: + You cannot restore course content after you delete it. To ensure that you do + not delete any content that you need later, move the unit to a + hidden section or subsection instead of deleting it. + +To delete a unit, follow these steps. + +#. On the course outline page in Studio, select the **Delete** icon in the box + for the unit you want to delete. + + .. image:: /_images/educator_how_tos/unit-delete.png + :alt: The Course Outline page with the Delete icons for several units + circled. + :width: 300 + +#. When you receive the confirmation prompt, select **Yes, delete this + unit**. + +.. _Preview a Unit: + +**************************** +Preview a Unit +**************************** + +You preview a unit to review and test the content before it is visible to +learners. + +You can preview a unit before it is published and before the course is live. +In a live course, after the unit is published and if there are no pending +changes, previewing a unit is exactly the same as viewing the live version of +the unit. + +To preview the unit, select **Preview** above the status panel in the Studio +unit page. + +The unit opens in preview mode in the LMS. + +.. note:: When you are revising a previously published unit, it can be helpful + to preview your changes in one browser window and :ref:`view the published + unit` in a second window. + +For information about previewing and testing content, see :ref:`Testing Your +Course Content`. + + +.. _Publish a Unit: + +**************************** +Publish a Unit +**************************** + +Publishing a unit makes the current version of the unit in Studio available to +learners. In an instructor-paced course, the release dates for the section and +subsection must also have passed for learners to access a published unit. + +You publish a unit that has a status of :ref:`Draft Never Published` or :ref:`Draft +Unpublished Changes`. When you publish a unit, the status changes to +Published and Live or Published Not Yet Released. + +You can publish a unit from the unit page or the course outline. + +For more information about instructor-paced and self-paced courses, see +:ref:`Setting Course Pacing`. + +======================================= +Use the Unit Page to Publish a Unit +======================================= + +To publish the unit, select **Publish** in the status panel. + + + +======================================= +Use the Outline to Publish a Unit +======================================= + +To publish a unit from the outline, select the **Publish** icon in the box for +the unit. + +.. image:: /_images/educator_how_tos/outline-publish-icon-unit.png + :alt: The Course Outline page with an arrow pointing to the Publish icon for a + unit. + :width: 500 + +.. note:: + The **Publish** icon only appears when there is new or changed content in the + unit. + +.. _Discard Changes to a Unit: + +**************************** +Discard Changes to a Unit +**************************** + +When you modify a published unit, your changes are saved in Studio, though the +changes are not visible to learners until you publish the unit again. + +If you decide that you never want to publish your changes, you can discard the +changes so that Studio reverts to the last published version of the unit. + +To discard changes and revert the Studio version of the unit to the last +published version, select **Discard Changes** in the status panel. + +.. caution:: + When you discard changes to a unit, the changes are permanently deleted. You + cannot retrieve discarded changes or undo the action. + +.. _View a Published Unit: + +**************************** +View a Published Unit +**************************** + +To view the last published version of a unit in the LMS, select **View Live +Version** at the top of the page. + +The unit page opens in the LMS in Staff view. You might be prompted to log in +to the LMS. + +If the unit status is :ref:`Draft Unpublished Changes`, you do not see your +changes in the LMS until you publish the unit again. + +If the unit status is :ref:`Draft Never Published`, **View Live Version** is not +enabled. + +For information about viewing and testing content, see :ref:`Testing Your +Course Content`. + + + diff --git a/source/educators/how-tos/course_development/create_hide_delete_sections.rst b/source/educators/how-tos/course_development/create_hide_delete_sections.rst new file mode 100644 index 000000000..606b6719c --- /dev/null +++ b/source/educators/how-tos/course_development/create_hide_delete_sections.rst @@ -0,0 +1,158 @@ +.. :diataxis-type: how-to + +.. _Create a Section: + +**************************** +Create a Section +**************************** + +If you do not change the :ref:`course start date` +default value, ``1/1/2030``, when you create a new section, its release date +will be ``Unscheduled``. + +If you have modified the course start date, when you create a new section, the +default release date is the course start date. + +.. caution:: + If the course start date is in the past, newly created sections are + immediately visible to learners. + +To create a new section, follow these steps. + +#. On the **Course Outline** page, select **New Section**. This option appears + at both the top of the page and below the current sections in the outline. + + A new section appears at the end of the course content, with the section + name selected. + +#. Enter the name for the new section. A descriptive name can help learners + locate content in the course. It can also help you select content when + you analyze performance in reporting or analytics systems. + +#. :ref:`Add subsections` to the new section as needed. + +It is recommended that you :ref:`test course content ` as you create new sections. + +******************************** +Change a Section Name +******************************** + +To edit a section name, move your cursor over the section name to show the +**Edit** icon. + +.. image:: /_images/educator_how_tos/section-edit-icon.png + :alt: The Edit Section Name icon. + :width: 500 + +Select the **Edit** icon next to the section name. The name field becomes +editable. Enter the new name, and then tab or click outside of the field to +save the name. + +.. _Set a Section Release Date: + +******************************** +Set a Section Release Date +******************************** + +To set the section release date, follow these steps. + +#. Select the **Configure** icon in the section box. + + .. image:: /_images/educator_how_tos/section-settings-box.png + :alt: The section settings icon circled. + :width: 500 + + The **Settings** dialog box opens. + +#. Enter the release date and time for the section. + + .. note:: + The time that you set is in Coordinated Universal Time (UTC). You might want + to verify that you have specified the time that you intend by using a time + zone converter such as `Time and Date Time Zone Converter`_. + +#. Select **Save**. + +For more information, see :ref:`Release Dates`. + + +.. _Publish all Units in a Section: + +******************************** +Publish All Units in a Section +******************************** + +To publish all new and changed units in a section, select the **Publish** icon +in the box for the section. + +.. image:: /_images/educator_how_tos/outline-publish-icon-section.png + :alt: Publishing icon for a section. + :width: 500 + +.. note:: + The **Publish** icon only appears when there is new or changed content within + the section. + +For more information about statuses and visibility to learners, see :ref:`Unit +Publishing Status`. + +.. _Hide a Section from Students: + +******************************** +Hide a Section from Learners +******************************** + +You can hide all content in a section from learners, regardless of the status +of subsections and units within the section. + +For more information, see :ref:`Content Hidden from Students`. + +To hide a section from learners, follow these steps. + +#. Select the **Configure** icon in the section box. + + .. image:: /_images/educator_how_tos/section-settings-box.png + :alt: The section settings icon circled. + :width: 500 + + The **Settings** dialog box opens. + +#. In the **Section Visibility** section, select **Hide from learners**. + +#. Select **Save**. + +Now, none of the content in the section is visible to learners. + +To make the section visible to learners, repeat these steps and deselect **Hide +from learners**. + +.. warning:: When you deselect **Hide from learners** for a section, not all + content in the section is necessarily made visible to learners. If you + explicitly set a subsection or unit to be hidden from learners, it remains + hidden from learners. Unpublished units remain unpublished, and changes to + published units remain unpublished. + + +******************************** +Delete a Section +******************************** + +When you delete a section, you delete all subsections and units within the +section. + +.. warning:: + You cannot restore course content after you delete it. To ensure you do not + delete content you may need later, you can move any unused content to a + section in your course that you set to never release. + +To delete a section, follow these steps. + +#. Select the **Delete** icon in the section that you want to delete. + + .. image:: /_images/educator_how_tos/section-delete.png + :alt: The section with Delete icon circled. + :width: 500 + +2. When you receive the confirmation prompt, select **Yes, delete this + section**. \ No newline at end of file diff --git a/source/educators/how-tos/course_development/hide_subsections.rst b/source/educators/how-tos/course_development/hide_subsections.rst new file mode 100644 index 000000000..f68264bc2 --- /dev/null +++ b/source/educators/how-tos/course_development/hide_subsections.rst @@ -0,0 +1,109 @@ +.. :diataxis-type: how-to + +.. _Hide a Subsection from Students: + +*********************************** +Hiding a Subsection from Learners +*********************************** + +You can hide a subsection from learners in the following ways. + +* :ref:`Entirely hide the subsection ` so that it + does not appear in course navigation. Subsections that are hidden in this + way are not included when grades are calculated. + +* :ref:`Prevent learners from accessing ` a subsection's contents after its due date (for instructor-led + courses) or the course end date (for self-paced courses) has passed, but + keep the subsection visible in course navigation. Subsections that are + hidden based on date remain included when grades are calculated. + +You can also hide just the answers to problems in the subsection, leaving the +problems visible. For more information, see :ref:`Problem Results Visibility`. + +For more information, see :ref:`Content Hidden from Students`. + + +.. _Entirely Hide a Subsection: + +======================================== +Entirely Hide a Subsection from Learners +======================================== + +You can completely hide a subsection and its content from learners, regardless +of the status of units within the section. Subsections hidden in this way are +not shown in the course navigation, and are not included when grades are +calculated. + +To entirely hide a subsection from learners, follow these steps. + +#. Select the **Configure** icon in the subsection box. + + .. image:: /_images/educator_how_tos/subsections-settings-icon.png + :alt: A subsection in the course outline with an arrow pointing to the + configure icon. + :width: 500 + + The subsection settings dialog box opens. + +#. On the **Visibility** tab, locate **Subsection Visibility**, and then select + **Hide entire subsection**. + +#. Select **Save**. + +None of the content in the subsection is visible to learners. In the course +outline, the subsection is shown with a lock icon, indicating that it is +available only to course staff. + +To make the subsection visible to learners, repeat these steps and select +**Show entire subsection**. + +.. warning:: When you make a previously hidden subsection visible, not all + content in the subsection is necessarily made visible to learners. Units + that were explicitly hidden from learners remain hidden. + + +.. _Hide a Subsection After its Due Date: + +======================================== +Hide a Subsection Based on Date +======================================== + +You can make a subsection's content unavailable based on date. For example, you +might want to make exam questions unavailable after a certain date. For +instructor-led courses, this option uses the subsection's due date. For self- +paced courses, this option uses the course's end date. + +Subsections that are hidden in this way remain visible in the course +navigation, and are included when grades are calculated. However, learners can +no longer access the subsection's content after the due date or the course end +date. + +.. note:: + If you want to continue to show a subsection's content, but hide learners' + results for problems in the subsection, see :ref:`Problem Results + Visibility`. + +To hide a subsection based on date, follow these steps. + +#. Select the **Configure** icon in the subsection box. + + The subsection settings dialog box opens. + +#. On the **Visibility** tab, locate **Subsection Visibility**, and then select + the appropriate option. + + * In instructor-led courses, select **Hide content after due date**. + + * In self-paced courses, select **Hide content after course end date**. + +#. Select **Save**. + +Learners who access the subsection after the due date or course end date has +passed are shown a message indicating that the subsection is no longer +available because the due date (or course end date) has passed. + +In the course outline in Studio, the subsection is shown with an icon and a +"Subsection is hidden after due date" or "Subsection is hidden after course +end date" message under the subsection's display name. + diff --git a/source/educators/how-tos/course_development/hide_units.rst b/source/educators/how-tos/course_development/hide_units.rst new file mode 100644 index 000000000..70ef3d684 --- /dev/null +++ b/source/educators/how-tos/course_development/hide_units.rst @@ -0,0 +1,63 @@ +.. :diataxis-type: how-to + +.. _Hide a Unit from Students: + +**************************** +Hide a Unit from Learners +**************************** + +You can prevent learners from seeing a unit regardless of the unit status or +the release schedules of the section and subsection. + +For more information, see :ref:`Content Hidden from Students`. + +You can hide a unit from learners using the course outline or the unit page. + +======================================= +Use the Unit Page to Hide a Unit +======================================= + +In the status panel, select **Hide from learners**. + +The **Release** section applies only to instructor-paced courses. It does not +appear for units in self-paced courses. + +For more information, see :ref:`Controlling Content Visibility`. + +======================================= +Use the Outline to Hide a Unit +======================================= + +#. Select the **Configure** icon in the unit box. + + .. image:: /_images/educator_how_tos/outline-unit-settings.png + :alt: The Course Outline page with the Configure icon for a unit + indicated. + :width: 500 + + The **Settings** dialog box opens. + +#. In the **Unit Visibility** section, select **Hide from learners**. + +#. Select **Save**. + +======================================= +Make a Hidden Unit Visible to Learners +======================================= + +Before you make a hidden unit visible to learners, be aware that course content +will immediately be visible to learners, as follows. + +* For a hidden unit that previously was published, deselecting **Hide from + learners** publishes the current content for the unit. If you made changes to + the unit while is was hidden, those draft changes are published. + +* When you make a section or subsection that was previously hidden visible to + learners, draft content in units is *not* published. Changes you made since + last publishing units are not made visible to learners. + +You can make a hidden unit visible to learners from the unit page or the course +outline. Follow the instructions above and clear the **Hide from learners** +check box. + +You are prompted to confirm that you want to make the unit visible to learners. diff --git a/source/educators/how-tos/course_development/index.rst b/source/educators/how-tos/course_development/index.rst new file mode 100644 index 000000000..78aacdf2d --- /dev/null +++ b/source/educators/how-tos/course_development/index.rst @@ -0,0 +1,9 @@ +############################# +Course Development +############################# + +.. toctree:: + :maxdepth: 1 + :glob: + + * \ No newline at end of file diff --git a/source/educators/how-tos/course_development/reorganize_components.rst b/source/educators/how-tos/course_development/reorganize_components.rst new file mode 100644 index 000000000..776664f42 --- /dev/null +++ b/source/educators/how-tos/course_development/reorganize_components.rst @@ -0,0 +1,79 @@ + +.. :diataxis-type: how-to + +.. _Reorganizing Components: + +****************************************** +Reorganizing Components +****************************************** + +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. + +.. contents:: + :local: + :depth: 1 + +====================================== +Reorganize Components Within a 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 +:ref:`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. + +.. image:: /_images/educator_how_tos/drag_child_component.png + :alt: A child component being dragged to a new location in a different parent + component. + :width: 400 + +You can also drag a child component outside of a parent, so that the child +moves to the same level as the parent. + +================================ +Move Components to Other Units +================================ + +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. + + .. image:: /_images/educator_how_tos/component_move_icon.png + :alt: The action icons for components, with the Move icon highlighted. + + 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. + + .. image:: /_images/educator_how_tos/component_move_navigation.png + :alt: The Move dialog box displays your course outline tree for + navigating to the unit that you want to move your component to. + :width: 380 + + 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. + +#. Select **Move**. + + 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. + + .. note:: + + 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. + diff --git a/source/educators/how-tos/course_development/set_component_restrictions.rst b/source/educators/how-tos/course_development/set_component_restrictions.rst new file mode 100644 index 000000000..f1ee35233 --- /dev/null +++ b/source/educators/how-tos/course_development/set_component_restrictions.rst @@ -0,0 +1,69 @@ +.. :diataxis-type: how-to + +.. _Set Access Restrictions For a Component: + +*************************************** +Set Access Restrictions for a Component +*************************************** + +If you have more than one enrollment track in your course, or if you have +enabled cohorts, you can limit a component's availability to specific groups of +learners. For information about offering different content to different learner +groups, see :ref:`Offering Differentiated Content`. + +.. note:: Components inherit any group access restrictions that are set for + their parent unit. If you set additional group access restrictions for a + component, make sure the component access settings do not contradict the + unit access settings. For example, you cannot give Group A of learners + access to a component if Group A does not have access to the unit that + contains the component. + +To specify a component's access settings, follow these steps. + +#. In Studio, select **Content**, and then select **Outline**. + +#. On a unit page, for each component for which you want to restrict access to, + select the **Access Settings** icon. + + .. image:: /_images/educator_how_tos/component_access_settings.png + :alt: The access settings icon for a component on a Studio unit page + :width: 500 + +#. In the **Editing access** dialog box, for the **Restrict access to** option, + select the group type by which you want to restrict access. + + .. note:: The **Enrollment Track Groups** option is available only if your + course has more than one :ref:`enrollment track`. + The **Content Groups** option is available only if you have created + :ref:`content groups` for use with cohorts. + + .. image:: /_images/educator_how_tos/component_access_select_grouptype.png + :alt: The access settings dialog for a component, with a dropdown list for + selecting the type of learner group you will use for restricting access. + :width: 300 + + After you have selected a group type, you see a list of the groups that + exist for that group type. + +#. Select the checkbox for each group for which you want the current component + to be available. + +#. Select **Save**. + + The groups which have access to the component are listed under the + component title in the Studio course outline. + + .. image:: /_images/educator_how_tos/component_access_indicator.png + :alt: When a component has restricted access, a message listing the groups + which have access to the component appears under the component title in + the Studio course outline. + :width: 500 + + In addition, on the unit page in Studio, a message in the publishing status + bar indicates that some content in the unit is restricted to specific groups + of learners. + + .. image:: /_images/educator_how_tos/components_restricted_access_indicator.png + :alt: When any component in a unit has restricted access, a message + appears in the unit's publishing status bar. + :width: 250 \ No newline at end of file diff --git a/source/educators/how-tos/course_development/set_course_highlights.rst b/source/educators/how-tos/course_development/set_course_highlights.rst new file mode 100644 index 000000000..806240cdf --- /dev/null +++ b/source/educators/how-tos/course_development/set_course_highlights.rst @@ -0,0 +1,74 @@ +.. :diataxis-type: how-to + +.. _Set Section Highlights for Course Highlight Messages: + +*********************************************************** +Set Section Highlights for Highlight Emails +*********************************************************** + + +If your Open edX system adminstrator has configured your instance of the Open +edX platform to send course highlight emails, you can send automatic email +messages to learners in your course that contain three to five "highlights" +of upcoming course content. A highlight is a brief description of an +important concept, idea, or activity in the section. Your Open edX system +administrator provides the template for this course highlight email, and +you enter the highlights for the email in Studio. + +For more information, contact your Open edX system administrator. + +.. note:: + The highlights that you specify persist when you re-run your course. + + +.. _Set Section Highlights: + +========================================= +Send Highlight Emails +========================================= + +To send highlight emails to your learners, you must first set highlights +for each section. When you have set section highlights, you then enable the +**Course Highlight Emails** setting. + +The number of highlights that you have set for a section is +visible in the course outline, below the name of the section. + +.. image:: /_images/educator_how_tos/NumSectionHighlights.png + :alt: The Course Outline page, showing a section name and "3 Section + Highlights" under the name. + +.. _Set Course Section Highlights: + +Set Course Section Highlights +********************************** + + .. note:: + If your Open edX system adminstrator has not configured your instance of + the Open edX platform to send course highlight messages, learners do + not receive messages even if you enable highlights and enter highlights for + each section. + +To set highlights for a course section, follow these steps. + +#. On the **Course Outline** page, locate the section you want, and then select + **Section Highlights** under the section name. +#. In the **Highlights for
** dialog box, enter three to five + highlights for the section. Enter one highlight in each field. Each + highlight can include up to 250 characters. +#. Select **Save**. + + +.. _Enable Course Highlight Messages: + +Enable Highlight Emails +******************************************** + +.. note:: + If you do not enable highlights, the edX platform does not send + course highlight emails, even if you enter highlights for one or more + sections. + + You cannot disable highlight emails after you enable them. If you do + not want to send highlight emails after you enable them, you can + delete highlights in all sections. diff --git a/source/educators/how-tos/course_development/set_restrictions_unit.rst b/source/educators/how-tos/course_development/set_restrictions_unit.rst new file mode 100644 index 000000000..af6620f7c --- /dev/null +++ b/source/educators/how-tos/course_development/set_restrictions_unit.rst @@ -0,0 +1,78 @@ +.. :diataxis-type: how-to + +.. _Set Access Restrictions For a Unit: + +*********************************** +Set Access Restrictions For a Unit +*********************************** + +If you have more than one enrollment track in your course, or if you have +enabled cohorts, you can limit a unit's availability to specific groups of +learners. For information about offering different content to different learner +groups, see :ref:`Offering Differentiated Content`. + +.. note:: A unit's group access settings are inherited by components in the + unit. If you set additional group access restrictions for a component, make + sure the component access settings do not contradict the unit access + settings. For example, you cannot give Group A of learners access to a + component if Group A does not have access to the unit that contains the + component. + +Tp specify a unit's access settings, follow these steps. + +#. In Studio, select **Content**, and then select **Outline**. + +#. For the unit that you want to restrict access to, select the **Configure** + icon in the unit's toolbar. + + .. image:: /_images/educator_how_tos/unit-configure-icon.png + :alt: The configure icon in a unit's toolbar in the Studio course outline. + :width: 500 + + You can also access the **Restrict access to** option from the gear icon + next to a unit's name on a unit page in Studio. + + + .. image:: /_images/educator_how_tos/unit-access-settings-gear-icon.png + :alt: The gear icon next to a unit's title on the unit page in Studio is + another way to launch the unit access settings dialog. + :width: 400 + + +#. In the unit's **Settings** dialog box, for the **Restrict access to** + option, select the group type by which you want to restrict access. + + The **Enrollment Track Groups** option is available only if your course has + more than one :ref:`enrollment track`. The **Content + Groups** option is available only if you have created :ref:`content + groups` for use with cohorts. + + + .. image:: /_images/educator_how_tos/unit-access-settings.png + :alt: The visibility and access settings dialog for a unit, with a + :width: 200 + + After you select a group type, you see a list of the groups that exist for + that group type. + + +4. Select the checkbox for each group for which you want the current unit to + be available. + + .. image:: /_images/educator_how_tos/unit-access-groupselected.png + :alt: The visibility and access settings dialog for a unit, with + enrollment track groups selected, and two enrollment tracks available for + selecting. + :width: 200 + +#. Select **Save**. + + The groups which have access to the unit are listed under the unit title in + the Studio course outline, as well as under the unit title on the unit page + in Studio. + + .. image:: /_images/educator_how_tos/unit-access-indicator.png + :alt: When a unit has restricted access, a message listing the groups + which have access to a unit appears under the unit title in the Studio + course outline. + :width: 500 \ No newline at end of file diff --git a/source/educators/how-tos/course_development/set_subsection_problem_date.rst b/source/educators/how-tos/course_development/set_subsection_problem_date.rst new file mode 100644 index 000000000..dfc8ea2e6 --- /dev/null +++ b/source/educators/how-tos/course_development/set_subsection_problem_date.rst @@ -0,0 +1,118 @@ +.. :diataxis-type: how-to + +.. _Set the Assignment Type and Due Date for a Subsection: + +******************************************************** +Set the Assignment Type and Due Date for a Subsection +******************************************************** + +You set the assignment type for problems at the subsection level. + +When you set the assignment type for a subsection, all problems in the +subsection are graded and weighted as a single type. For example, if you +designate the assignment type for a subsection as **Homework**, then all +problem types in that subsection are graded as homework. + +.. note:: + Unlike other problem types, by default, ORA assignments are not governed by the + subsection due date, but are instead set in the assignment's settings. There + is, however, a setting that allow ORAs to instead use the subsection due date. + For details, see :ref:`PA ORA Assignment Schedule`. + +To set the assignment type and due date for a subsection, follow these steps. + +#. Select the **Configure** icon in the subsection box. + + The subsection settings dialog box opens. + +#. On the **Basic** tab, locate the **Grading** section. +#. In the **Grade as** list, select the assignment type for this subsection. + +#. For **Due Date** and **Due Time in UTC**, enter or select a due date and + time for problems in this subsection. + + .. note:: The time that you set is in Coordinated Universal Time (UTC). You + might want to verify that you have specified the time that you intend by + using a time zone converter such as `Time and Date Time Zone Converter`_. + + Learners who have specified a time zone in their account settings see + course dates and times converted to their specified time zone. Learners + who have not specified a time zone in their account settings see course + dates and times on their dashboards, in the body of the course, and on + their **Progress** pages in the time zone that their browsers specify. + Learners see other course dates and times in UTC. + +#. Optionally, for a course that has the timed exam feature enabled, select the + **Advanced** tab to set the subsection to be :ref:`timed`. + +#. Select **Save**. + +For more information, see :ref:`Grading Index`. + +.. _Problem Results Visibility: + +********************************* +Set Problem Results Visibility +********************************* + +By default, when learners submit answers to problems, they immediately receive +the results of the problem: whether they answered the problem correctly, as +well as their scores. However, you might want to temporarily hide problem +results from learners when you run an exam, or permanently hide results when +you administer a survey. You can do this by using the **Assessment Results +Visibility** setting. + +.. note:: + The **Assessment Results Visibility** setting is a subsection setting. You + cannot change the visibility of individual problems. The **Assessment Results + Visibility** subsection setting overrides the **Show Answer** setting for + individual problems. Answers to problems are not visible when results are hidden. + +The **Assessment Results Visibility** setting can be used with the following +common problem types. + +* :ref:`Dropdown` +* :ref:`Multi-select` +* :ref:`Numerical Input` +* :ref:`Single Select` +* :ref:`Text Input` + +The **Assessment Results Visibility** setting can be used with the following +advanced problem types. + +* :ref:`Annotation` +* :ref:`Circuit Schematic Builder` +* :ref:`Custom JavaScript Display and Grading` +* :ref:`Custom Python-Evaluated Input` +* :ref:`Image Mapped Input` +* :ref:`Math Expression Input` +* :ref:`Problem Written in LaTeX` +* :ref:`Problem with Adaptive Hint` + +To change the results visibility for your subsection, follow these steps. + +#. Select the **Configure** icon in the subsection box. + + The **Settings** dialog box opens. + +#. Select the **Visibility** tab, and locate **Assessment Results Visibility**. + +#. Select one of the available options. + + * **Always show results**: This is the default setting. Problem results and + subsection scores are visible immediately when learners and staff submit + answers. + * **Never show results**: Subsection scores are visible, but problem results + are never visible to learners or to course staff. + * **Show results when subsection is past due**: For learners, results are + not visible until the subsection due date (for instructor-paced courses) + or the course end date (for self-paced courses) has passed. For course + staff, results are always visible unless the staff member is + :ref:`previewing or viewing the course as a learner`. + + .. note:: + If the subsection does not have a due date, or the course does not have + an end date, results are always visible. + +#. Select **Save**. diff --git a/source/educators/how-tos/course_development/text_components/add_image.rst b/source/educators/how-tos/course_development/text_components/add_image.rst new file mode 100644 index 000000000..fe99eaf7c --- /dev/null +++ b/source/educators/how-tos/course_development/text_components/add_image.rst @@ -0,0 +1,157 @@ +.. :diataxis-type: how-to + +.. _Add an Image to a Text Component: + +********************************* +Add an Image to a Text Component +********************************* + +When you use the Visual Editor, you can add any image from your computer to +a Text component. You can see a preview of the image before you add it to the +component. + +.. note:: + * Before you add an image, make sure that you obtain copyright permissions for + images you use in your course, and that you cite sources appropriately. + * To add effective alternative text for images, review :ref:`Best Practices + for Describing Images`. + * You can only add one image at one time. + * Each individual image file must be smaller than 10 MB. + +To add an image to a Text component, you can use one of the following +procedures. + +* :ref:`Locate an image ` by using the + **Browse Your Computer** option in the **Add Image** dialog box. +* :ref:`Select an image ` that you have - previously uploaded. - -.. _Locate an Image on Your Computer: - -================================ -Locate an Image on Your Computer -================================ - -#. In the Text component, position the cursor where you want to add an image, - and then select the image icon on the toolbar. - -#. In the **Add an Image** dialog box, **Upload a New Image (10 MB max)**. - -#. In the dialog box that opens, locate the file that you want to add, and - then select **Open**, or locate the image in the Image Gallery, and then - select **Next**. - - As soon as your image is selected, the **Image Settings** dialog box - opens. - -#. In the **Edit Image Settings** dialog box, add an image description. - - * In the **Alt Text** field, enter alternative text for - the image. This text becomes the value of the ``alt`` attribute in HTML - and is required for your course to be fully accessible. For more - information, see :ref:`Best Practices for Describing Images`. - - * If your image is a decorative image that does not convey important - information, select the **This image is decorative (no alt text required)** - checkbox. - -#. (optional) Specify the width and height of your image. For more information, - see :ref:`Change the Image Size`. - -#. Select **Save**. - -#. Save the Text component and test the image. - -.. _Select a Previously Uploaded Image: - -================================== -Select a Previously Uploaded Image -================================== - -#. When you upload an image, the image automatically becomes available in a - gallery list that opens when you add an image to a Text component. - -#. In the Text component, position the cursor where you want to add an image, - and then select the image icon on the toolbar. - -#. In the **Add an Image** dialog box, locate the image in the gallery list, - and then select **Next**. There are sort and filter options available for - the gallery list to make it easy to find the image you need. - -#. In the **Image Settings** dialog box, complete one of the following - options. - - * In the **Alt Text** field, enter alternative text for - the image. This text becomes the value of the ``alt`` attribute in HTML - and is required for your course to be fully accessible. For more - information, see :ref:`Best Practices for Describing Images`. - - * If your image is a decorative image that does not convey important - information, select the **This image is decorative (no alt text - required)** checkbox. - -#. (optional) Specify the width and height of your image. For more information, - see :ref:`Change the Image Size`. - -#. Select **Save**. - -#. Save the Text component and test the image. - -.. _Format an Image in a Text Component: - -=================================== -Format an Image in a Text Component -=================================== - -You have several options for formatting an image in a Text component. - -.. contents:: - :local: - :depth: 1 - -.. _Align an Image: - -Align an Image -************** - -To align your image to the right, the left, or the center, follow these steps. - -#. In the Text component, select the image. - -#. On the toolbar, select the left align, right align, or center icon. - -.. _Change the Image Size: - -Change the Image Size -********************* - -To change the size of your image, follow these steps. - -#. In the Text component, select the image that you want to edit, and then - select the Contextual image icon that appears above the image. - -#. In the **Image Settings** dialog box, locate **Image Dimensions**, and - then enter the values that you want for the **Width** and **Height** - options. - - .. note:: - To make sure that the image keeps the same proportions when you change the - image size, make sure that **Lock proportions** is selected, and enter a - number in only the **Width** field or the **Height** field. After you tab - or click outside that field, the number in the other field changes to a - value that maintains the image proportions. - -#. Select **Save**. - -If you want to change the image back to the original size, clear the values in -the **Width** and **Height** fields. - -.. _Power Paste: - -*********** -Power Paste -*********** - -Many course authoring teams rely on copying and pasting content from documents -such as Google docs or Microsoft Word. Correct formatting in Studio and the LMS -can be most easily realized through Power Paste. - -When you copy and paste content into the Text Editor, you will receive a “Paste -Formatting Options” popup on the page. If you choose “Remove formatting”, then -the bullets will be correctly aligned with text in both Studio and the LMS. If -you select “Keep formatting”, then the formatting is unchanged and bullets and -text will not be aligned in Studio or the LMS. - - -.. image:: ../images/HTML_PowerPastePop.png - :alt: an image of the popup that you will receive after copying and - pasting content into the Text Editor. This popup allows you to select - either keep or remove formatting. - :width: 300 - -Below is a bulleted list example, a type of formatting that commonly needs Power -Paste. If you select “Keep formatting”, this is what Studio and LMS will show: - -.. image:: ../images/PowerPaste_KeepFormatting.png - :alt: an image of a bulleted list in LMS in which you have chosen to “keep - formatting” when you were in the editor. The bullets and text are misaligned. - :width: 600 - -However, if you select “Remove formatting”, this is what Studio and LMS will show: - -.. image:: ../images/PowerPaste_RemoveFormatting.png - :alt: an image of a bulleted list in LMS in which you have chosen to “remove - formatting” when you were in the editor. The bullets and text are correctly - aligned. - :width: 600 - - - -.. JRistau (26 Sept 2022) - LaTeX editor support was removed with the rollout of -.. the new Course Authoring based Text Editor. Coursegraph shows ~100 active -.. courses that have enabled the LaTeX advanced module, and we have had no -.. issues reported since rollout of the new text editor. The LaTeX component -.. is listed as “Unsupported” in studio (TNL-9993). For these reasons, edX PM -.. has decided to remove this section of our support documentation. - - -.. _import latex code: - -.. **************************************** -.. Import LaTeX Code into a Text Component -.. **************************************** - -.. You can import LaTeX code into a Text component. You might do this, for -.. example, if you want to create "beautiful math" such as the math in the -.. following image. - -.. .. image:: ../images/HTML_LaTeX_LMS.png - :alt: Math formulas created with LaTeX in a Text component. - -.. .. warning:: - The LaTeX processor that Studio uses to convert LaTeX code to XML is a third - party tool. We recommend that you use this feature with caution. If you use - the tool, make sure that you work with your partner manager. - -.. ========================== -.. Enable the LaTeX Processor -.. ========================== - -.. The LaTeX processor is not enabled by default. To enable it, you have to change -.. the advanced settings in your course. - -.. #. In Studio, select **Settings**, and then select **Advanced Settings**. - -.. #. In the field for the **Enable LaTeX Compiler** policy key, change **false** - to **true**. - -.. #. At the bottom of the page, select **Save Changes**. - -.. ============================================== -.. Add a Text Component that Contains LaTeX Code -.. ============================================== - -.. When the LaTeX processor is enabled, you can create a Text component that -.. contains LaTeX code. - -.. #. In the unit where you want to create the component, select **Text** under - **Add New Component**, and then select **E-text Written in LaTeX**. The new - component is added to the unit. - -.. #. Select **Edit** to open the new component. - -.. #. At the bottom of the component editor, select **Launch Latex Source - Compiler**. - - The LaTeX editor opens. - - .. image:: ../images/HTML_LaTeXEditor.png - :alt: The LaTeX editor. - :width: 500 - -.. #. Add your LaTeX code. To do this, complete either of the following - procedures. - - * In the **High Level Source Editing** field, add your LaTeX code. - - * To upload a LaTeX file from your computer, select **Upload**. - -.. #. Select **Save & Compile to edX XML**. - -.. #. On the unit page, select **Preview** to verify that your content looks - correct in the LMS. - - If you see errors, go back to the unit page. Select **Edit** to open the - component again, and then select **Launch Latex Source Compiler** to edit - the LaTeX code. \ No newline at end of file diff --git a/source/educators/migration_wip/8_course_components/create_problem.rst b/source/educators/migration_wip/8_course_components/create_problem.rst index 3c582f340..904562f3e 100644 --- a/source/educators/migration_wip/8_course_components/create_problem.rst +++ b/source/educators/migration_wip/8_course_components/create_problem.rst @@ -316,7 +316,7 @@ click the pen symbol to the right of the field and enter the desired text. The following illustration shows the display name of a problem in Studio, and in the LMS. -.. image:: ../images/display_names_problem.png +.. image:: /_images/educator_how_tos/display_names_problem.png :alt: The identifying display name for a problem in Studio, and the LMS. :width: 800 diff --git a/source/educators/migration_wip/8_course_components/create_video.rst b/source/educators/migration_wip/8_course_components/create_video.rst deleted file mode 100644 index 45f3c83be..000000000 --- a/source/educators/migration_wip/8_course_components/create_video.rst +++ /dev/null @@ -1,25 +0,0 @@ -.. _Working with Video Components: - -############################# -Working with Video Components -############################# - -You use video components to add videos to your course in Studio. In video -components, you add the name and location of your video, as well as the video -transcript. Learners view your videos in the LMS. - -.. only:: Partners - - For information about the way learners interact with videos, see - `Video Player`_. - -.. only:: Open_edX - - For information about the way learners interact with videos, see - `Video Player`_. - -For more information about adding videos to your course, see :ref:`Creating and -Adding Video Content`. - -For more information about options in the video component, see :ref:`Additional -Video Options`. \ No newline at end of file diff --git a/source/educators/migration_wip/8_course_components/index.rst b/source/educators/migration_wip/8_course_components/index.rst index f4fff7988..a69ab0acf 100644 --- a/source/educators/migration_wip/8_course_components/index.rst +++ b/source/educators/migration_wip/8_course_components/index.rst @@ -18,8 +18,5 @@ page, see :ref:`Developing Your Course Index`. .. toctree:: :maxdepth: 2 - create_html_component - create_video - create_discussion create_problem libraries diff --git a/source/educators/migration_wip/9_video/add_video_to_course.rst b/source/educators/migration_wip/9_video/add_video_to_course.rst index a35561a86..7cac3cad6 100644 --- a/source/educators/migration_wip/9_video/add_video_to_course.rst +++ b/source/educators/migration_wip/9_video/add_video_to_course.rst @@ -1,3 +1,24 @@ +.. :diataxis-type: + +.. _Working with Video Components: + +############################# +Working with Video Components +############################# + +You use video components to add videos to your course in Studio. In video +components, you add the name and location of your video, as well as the video +transcript. Learners view your videos in the LMS. + +For information about the way learners interact with videos, see +`Video Player`_. + +For more information about adding videos to your course, see :ref:`Creating and +Adding Video Content`. + +For more information about options in the video component, see :ref:`Additional +Video Options`. + .. _Adding a Video to a Course: ########################## diff --git a/source/educators/migration_wip/9_video/prepare_video/obtain_transcript.rst b/source/educators/migration_wip/9_video/prepare_video/obtain_transcript.rst index c7bc951be..581377a45 100644 --- a/source/educators/migration_wip/9_video/prepare_video/obtain_transcript.rst +++ b/source/educators/migration_wip/9_video/prepare_video/obtain_transcript.rst @@ -176,7 +176,7 @@ Obtaining a Video Transcript your course is on Edge, you cannot use the integrated video transcript functionality in Studio. Instead, you send your videos to the transcript provider, and the provider sends you the completed transcripts. You later - upload the transcripts when you :doc:`../../8_course_components/create_video`. + upload the transcripts when you :ref:`Create a Video`. If your course is on Edge, integrated transcript functionality is not available even if you work with 3Play Media or cielo24. diff --git a/source/educators/migration_wip/index.rst b/source/educators/migration_wip/index.rst deleted file mode 100644 index 27b152ed0..000000000 --- a/source/educators/migration_wip/index.rst +++ /dev/null @@ -1,33 +0,0 @@ -:orphan: - -Migration WIP -########################### - -This is a collection of WIP docs currently being migrated from https://github.com/openedx/edx-documentation - -.. toctree:: - :numbered: - :maxdepth: 2 - :caption: Sections - :glob: - - 1_general_information/index - 2_getting-started/index - 3_dashboard_profile/index - 4_reaching_learners/index - 5_accessibility/index - 6_set_up_course/index - 7_developing_course/index - 8_course_components/index - 9_video/index - 10_exercises_tools/index - 11_course_assets/index - 12_course_features/index - 13_proctored_exams/index - 14_grading/index - 15_releasing_course/index - 16_manage_live_course/index - 17_manage_discussions/index - 18_student_progress/index - 19_rerun_course/index - 20_glossary/glossary \ No newline at end of file diff --git a/source/educators/migration_wip/links/links.rst b/source/educators/migration_wip/links/links.rst index 74fc132ec..2d862ac07 100644 --- a/source/educators/migration_wip/links/links.rst +++ b/source/educators/migration_wip/links/links.rst @@ -250,7 +250,7 @@ .. _VoiceOver for OS X: https://www.apple.com/accessibility/osx/voiceover/ .. _Creative Commons website: http://creativecommons.org/licenses .. _Google Fonts: https://www.google.com/fonts#UsePlace:use/Collection:Open+Sans -.. _Time and Date Time Zone Converter: http://www.timeanddate.com/worldclock/converter.html + .. _Cross-referencing arbitrary locations: http://www.sphinx-doc.org/en/stable/markup/inline.html#cross-referencing-arbitrary-locations .. _Time Zone Converter: http://www.timezoneconverter.com/cgi-bin/tzc.tzc .. _MOOCdb project: http://moocdb.csail.mit.edu/ diff --git a/source/educators/migration_wip/5_accessibility/accessibility_checker.rst b/source/educators/references/accessibility/accessibility_checker.rst similarity index 95% rename from source/educators/migration_wip/5_accessibility/accessibility_checker.rst rename to source/educators/references/accessibility/accessibility_checker.rst index 0d3d7a825..e5bbf07dc 100644 --- a/source/educators/migration_wip/5_accessibility/accessibility_checker.rst +++ b/source/educators/references/accessibility/accessibility_checker.rst @@ -1,3 +1,5 @@ +.. :diataxis-type: reference + .. _Accessibility Checker: ##################### @@ -27,7 +29,7 @@ sidebar menu with details on each issue found. Navigate between the items to learn about each issue and apply the fixes (see images below). -.. image:: ../images/AccessibilityCheckerWidget.png +.. image:: /_images/educator_references/AccessibilityCheckerWidget.png :alt: an image of the accessibility checker icon and menu. The accessibility checker lists various accessibility issues and includes an auto repair capability. @@ -99,3 +101,8 @@ content: * Tables * Captions * Scopes + +.. seealso:: + :class: dropdown + + :ref:`Accessibility` diff --git a/source/educators/references/accessibility/index.rst b/source/educators/references/accessibility/index.rst new file mode 100644 index 000000000..5ea40e95b --- /dev/null +++ b/source/educators/references/accessibility/index.rst @@ -0,0 +1,8 @@ +Accessibility References +############################### + +.. toctree:: + :maxdepth: 1 + :glob: + + * diff --git a/source/educators/references/advanced_features/experiment_group_configurations.rst b/source/educators/references/advanced_features/experiment_group_configurations.rst new file mode 100644 index 000000000..ef6605d60 --- /dev/null +++ b/source/educators/references/advanced_features/experiment_group_configurations.rst @@ -0,0 +1,43 @@ +.. :diataxis-type: reference + +.. _Experiment Group Configurations: + +======================================= +Experiment Group Configurations +======================================= + +The edX Platform assigns learners to each experiment group in a group +configuration. + +Experiment group assignments have the following characteristics. + +* Dynamic + + The edX Platform assigns a learner to an experiment group the first time he + or she views a content experiment that uses the group configuration. + +* Random + + You cannot control which learners are assigned to which experiment group. + +* Evenly distributed + + The edX Platform keeps track of the size of experiment groups, and assigns + new learners to groups evenly. For example, if you have two experiment groups + in a configuration, each group includes 50% of the learners in the course; if + you have four experiment groups, each group includes 25% of the learners. + +* Permanent + + Learners remain in their assigned experiment groups regardless of how many + content experiments you set up that use the same group configuration. + +.. seealso:: + :class: dropdown + + :ref:`Offering Differentiated Content` (concept) + :ref:`Overview of Content Experiments` (concept) + :ref:`Configure Your Course for Content Experiments` (how-to) + :ref:`Add a Content Experiment in OLX` (how-to) + :ref:`Set Up Group Configuration for OLX Courses` (how-to + :ref:`Guidelines for Modifying Group Configurations` (concept) \ No newline at end of file diff --git a/source/educators/references/advanced_features/index.rst b/source/educators/references/advanced_features/index.rst new file mode 100644 index 000000000..b345a165e --- /dev/null +++ b/source/educators/references/advanced_features/index.rst @@ -0,0 +1,8 @@ +Advanced Features +############################### + +.. toctree:: + :maxdepth: 1 + :glob: + + * diff --git a/source/educators/migration_wip/16_manage_live_course/automatic_email.rst b/source/educators/references/communication/automatic_email.rst similarity index 98% rename from source/educators/migration_wip/16_manage_live_course/automatic_email.rst rename to source/educators/references/communication/automatic_email.rst index 78d45c12c..3c179fc85 100644 --- a/source/educators/migration_wip/16_manage_live_course/automatic_email.rst +++ b/source/educators/references/communication/automatic_email.rst @@ -1,3 +1,5 @@ +.. :diataxis-type: reference + .. _Automatic Email: ################################# @@ -174,7 +176,7 @@ courses. The logic for when the message is sent depends on the Course pacing. For more information, see :ref:`Set Section Highlights for Course Highlight Messages`. -.. include:: ../7_developing_course/course_highlight_message_text.rst +.. include:: ../reusable_references/course_highlight_message_text.rst .. _Discussion Notification: diff --git a/source/educators/references/communication/bulk_email.rst b/source/educators/references/communication/bulk_email.rst new file mode 100644 index 000000000..c22e17971 --- /dev/null +++ b/source/educators/references/communication/bulk_email.rst @@ -0,0 +1,423 @@ +.. :diataxis-type: reference + +.. _Bulk Email: + +######################################## +Bulk Email Messages from the Course Team +######################################## + +For courses on edx.org, you can send bulk email messages to course participants +directly from the instructor dashboard: in the LMS, select **Instructor**, and +then select **Email**. + +Your messages can use HTML styling, and can include links to videos, social +media pages for the course, and other material. All course team members who +have the Staff or Admin role can use bulk email messages to communicate with +course participants before, during, and after the course run. + +Learners are less likely to read and respond to email messages from courses +when they receive too many of them. As a best practice, do not send more than +one email message per week to course participants, unless there is good reason +to do so. + +.. note:: Some courses use third party services such as MailChimp to send bulk + email. Do not use both a third party service and the edX bulk email + service. If you use more than one service to send email message, your + messages are more likely to be marked as spam, and learners might not read + them. + +This section contains the following topics. + +.. contents:: + :local: + :depth: 1 + +.. _bulk_email_message_addressing: + +************************* +Message Addressing +************************* + +When you send a bulk email message from the instructor dashboard, you choose +its recipients by selecting a **Send to** option. You can select one or more +recipient groups for each message. For details about who is included in each +of the preset recipient groups, see :ref:`Bulk Email Who Is Included or +Excluded` + +When you send a message to more than one recipient group, duplicate recipients +are filtered out, so that someone who belongs to more than one of the recipient +groups only receives one copy of the message. For example, if you address an +email message to learners in a particular cohort as well as to learners in the +Verified enrollment track, a learner who is in the cohort AND is in the Verified +enrollment track will only receive one email message. + +The following preset recipient groups are available. + +* **Myself**. Send an email message only to yourself, to test and review the + message before sending it to a larger group. + +* **Staff and Administrators**. Send an email message to members of the course + team who have Staff or Admin privileges. For information about course + team member privileges, see :ref:`Course_Staffing`. + +* **All Learners**. Send an email message to all currently enrolled learners. + This group does not include learners who have not activated their accounts, + or who have opted out of receiving email communications. This group does not + include course team members, even if they are enrolled in the course. + +If you have more than one enrollment track in your course, each enrollment +track is available as a separate recipient group. For more information, see +:ref:`Enrollment Track Recipient Groups`. + +If you have cohorts enabled in your course, each cohort is available as a +separate recipient group. For more information, see :ref:`Bulk Email Cohorts`. + + +.. _Bulk Email Who Is Included or Excluded: + +========================================= +Who Is Included in Each Recipient Group? +========================================= + +When you send a bulk email message to one of the preset recipient groups, you +should be aware of who is included in each group. + +.. note:: It is considered good practice to only send messages to active and + engaged learners. For this reason, regardless of the recipient groups + selected, edX will only send email messages to learners in a course run who + have logged in within the last 18 months. This helps reduce the risk of + messages being marked as spam (or bouncing) and helps ensure the continued + delivery of bulk course email messages through edX's email providers. + +.. list-table:: + :widths: 30 40 40 + :header-rows: 1 + + * - Recipient Group + - Includes + - Does Not Include + + * - Staff and Administrators + - * Any course team member who has the **Staff** role. + * Any course team member who has the **Admin** role. + - * Beta testers who do not also have the **Staff** or **Admin** role. + * Discussion moderators who do not also have the **Staff** or **Admin** + role. + * Discussion administrators who do not also have the **Staff** or + **Admin** role. + * Learners who have the Community TA or Group Community TA discussion + moderator roles. + + * - All Learners + - * All currently enrolled learners in your course, including those who + have enrolled but have not yet accessed the course. + - * Learners who have not replied to the account activation email message + that they received when they registered on edx.org. + * Learners who have opted out of receiving email messages through the + **Email Settings** link for the course on the learner's dashboard. + * Course team members, regardless of whether they are enrolled in the + course. + + +.. _Enrollment Track Recipient Groups: + +================================================================== +Sending Email Messages to Learners in Different Enrollment Tracks +================================================================== + +If you have more than one enrollment track in your course, each enrollment +track is available as a separate recipient group. If your course includes only +a single enrollment track, you will not have a track-based recipient group. + +For example, if your course includes an audit track and a verified certificate +track, you have two additional recipient groups: **Learners in the Audit +Track** and **Learners in the Verified Certificate Track**. + + +.. _Bulk Email Cohorts: + +=================================================== +Sending Email Messages to Learners in Cohorts +=================================================== + +If you enable cohorts in your course, each cohort is available as a separate +recipient group. The recipient groups for individual cohorts only include +enrolled learners who have been assigned to a cohort, whether they were +automatically assigned when they accessed the course or manually assigned to a +cohort by a member of the course team. + +The recipient groups for cohorts do not include enrolled learners who have not +been added to a cohort. This might be the case if they have not accessed the +course or have not been manually added to a cohort by a member of the course +team. To make sure such learners are included in email messages that are +intended for all enrolled learners, select the **All Learners** recipient +group instead of selecting all of the cohort recipient groups. + +If a default cohort exists in your course, a recipient group named **Cohort: +Default Group** is also available. + +.. note:: The default cohort is created only if you have not created at least + one automated assignment cohort in your course by the time the first + learner accesses course content. If learners access the course before you + have created any automated cohorts, they are automatically placed in the + default cohort, to ensure that all learners in the course belong to a + cohort. You can manually reassign learners from the default cohort to + another cohort. For more information, see :ref:`Default Cohort Group`. + + +.. _Options for Email Message Text: + +******************************* +Composing Email Messages +******************************* + +When you compose an email message, you can use the following options. + +.. contents:: + :local: + :depth: 2 + +======= +Styling +======= + +Messages can include HTML styling, including text formatting and links. + +For more information, see :ref:`Working with Text Components`. + +----------------------- +Restricted HTML Content +----------------------- + +The Bulk Course Email tool restricts use of specific HTML elements from being +used in messages. The following HTML elements may not be used in messages +authored with this tool: + +* iframe +* svg +* form +* script + +.. note: If a message contains restricted HTML content it will **not** be + stripped from the message. The HTML code will be converted to plain text. You + should send a test message to yourself first before sending to larger groups + to ensure message content is displayed as desired. + +====== +Images +====== + +Messages can include images. To include an image, you must first add the file +to your course on the **Files & Uploads** page. For an email message, you copy +the **Web** URL that the system assigns to the image. Then, in the email +message editor, you select the **Insert/edit image** icon to add the web URL. + +.. note:: Scalable Vector Graphic (SVG) images are restricted from use in + messages authored with the Bulk Course Email tool. Please see the above note + in the *Restricted HTML Content* section. + +To ensure that your course assets are transmitted securely, add the +``https://`` preface to the web URL. An example follows. + +:: + + https://courses.edx.org/asset-v1:{course}.x+{run}+type@asset+block@{image}.jpg + +For more information, see :ref:`Add Files to a Course`. + +========= +Keywords +========= + +Messages can include variables that represent values that are specific to each +message recipient, such as learner name or user ID. The LMS substitutes these +variables, called keywords, with actual values when it sends a message. + +For more information, see :ref:`Use Keywords in Messages`. + + +===================================== +Managing Scheduled Email Messages +===================================== + +Once a message has been scheduled it will appear in the **Scheduled emails** +table. Each entry will describe *when* the message will be sent (in local time), +the *recipient groups* selected, the *subject* of the message, and the *author* +of the message. + +.. image:: /_images/educator_how_tos/Bulk_email_scheduled_emails_table.png + :alt: A tabular list of scheduled email messages, with columns for + *send date*, *send to*, *subject*, *author*, and *action*. + +Each scheduled email entry in this table will support the following actions: + +* The *View* button will open a modal that allows you to view the contents of + this message. +* The *Delete* button will cancel the scheduled bulk email task and the message + will **not** be sent. This sets the bulk email task's status to **REVOKED**. +* The *Edit* button will allow you to edit the bulk email message. You will be + able to adjust the recipients, subject, message contents, and/or the date and + time the message should be sent. + + +.. _Use Keywords in Messages: + +**************************** +Use Keywords in Messages +**************************** + +You can include keywords in your messages. A keyword is a variable: when you +send the message, a value that is specific to the each recipient is substituted +for the keyword. For example, when you use the ``%%USER_FULLNAME%%`` keyword, +each message contains the name of the recipient. + +.. note:: + Do not use keywords in the Subject line of a message. The keyword in the + subject will not be assigned a value, and the recipient will see the keyword + text. + +=================== +Supported Keywords +=================== + +You can use the following keywords in your messages. + +* ``%%USER_ID%%`` - the anonymous user ID of the message recipient +* ``%%USER_FULLNAME%%`` - the full name of the message recipient +* ``%%COURSE_DISPLAY_NAME%%`` - the display name of the course +* ``%%COURSE_END_DATE%%`` - the end date of the course + +=================== +Keyword Formatting +=================== + +You format keywords as: ``%%Keyword%%``. You can include keywords in any HTML +tags in an email message. An example follows. + +:: + +

%%COURSE_DISPLAY_NAME%% Updates

+ +

Dear %%USER_FULLNAME%%, this is a reminder that the last day of the course + is %%COURSE_END_DATE%%

+ . . . + +.. _Email_queuing: + +**************************** +Message Workflow States +**************************** + +When you select **Send Email** for a message, the server begins to process a +bulk email task. The server assigns a series of different workflow states to +the task. + +When you select **Schedule Email** for a message, the server creates a bulk +email task and sets it to the **SCHEDULED** state. This task will remain in this +state until it is ready to be processed. + +.. image:: /_images/educator_how_tos/Bulk_email_states.png + :alt: Flowchart of the possible states of a bulk email task. + +Bulk email tasks can have the following workflow states. + +* Queuing: The bulk email task is created and being queued for background + processing. +* Pending: The task is queued and is waiting to run. +* Scheduled: The task has been created and is scheduled to run at a future date + and time. +* Started: Background processing is in progress to create emailing subtasks. +* Progress: The emailing subtasks are in progress. +* Success: All emailing subtasks are complete. Note that the bulk email task + can be in this state even if some or all of its emailing subtasks failed. +* Failure: An error occurred and task processing did not complete successfully. +* Revoked: The task was cancelled before it was processed. + +While the bulk email task is in progress, you can find out what stage it has +reached in the workflow by checking the **Pending Tasks** section on the +**Course Info** page of the Instructor Dashboard. + +.. image:: /_images/educator_how_tos/Bulk_email_pending.png + :alt: Information about an email message, including who submitted it + and when, in tabular format + +When the bulk email task is complete, you can find its final state by checking +the Email Task History report. For more information, see :ref:`Email Task +History Report`. + +.. _Email Task History Report: + +******************************** +Email Task History Report +******************************** + +The Email Task History report can help you keep track of who sent messages, +when, to which groups, and how many messages were successfully sent. For each +message sent, the report includes the username of the requester, the date and +time it was submitted, the duration and state of the entire task, the task +status, and the task progress. + +You can use this history to investigate questions relating to bulk email +messages that have been sent, such as these examples. + +* How frequently learners are sent course-related email messages. +* Whether a message was sent successfully. +* The change in the number of people who were sent course-related messages over + time. + +To produce the Email Task History report, follow these steps. + +#. View the live version of your course. + +#. Select **Instructor**, and then select **Email**. + +#. In the **Email Task History** section of the page, select **Show Email Task + History**. A report like the following example displays on the instructor + dashboard. + +.. image:: /_images/educator_how_tos/Bulk_email_history.png + :alt: A tabular report with a row for each message sent and columns for + requester, date and time submitted, duration, state, task status, + and task progress. + +=========================== +Review Email Task History +=========================== + +For tasks with a **State** of Success, the **Task Progress** column shows an +informational message. These messages can have a format such as "Message +successfully emailed for 13457 recipients (skipping 29) (out of 13486)". To +interpret this message, note that: + +* The first number ("recipients") indicates the number of messages sent to the + selected recipients. + +* The second number ("skipping") indicates the number of enrolled and activated + users who were not sent the message. This count is of learners who have opted + not to receive course email messages. + +* The final number ("out of") indicates the number of users in the set of + recipients you selected who were enrolled in the course (and had activated + their user accounts) when you sent the email message. + +If the "recipients" and "out of" numbers are the same, the message reads +"Message successfully emailed for 13457 recipients" instead. + +Other **Task Progress** messages for tasks with a **State** of Success indicate +that some or all of the emailing subtasks did not successfully send email: + +* "Message emailed for {number succeeded} of {number attempted} recipients" +* "Message failed to be emailed for any of {number attempted} recipients" +* "Unable to find any recipients to be emailed" + +No **Task Progress** messages display for tasks that have a **State** of +Failure. + +.. seealso:: + :class: dropdown + + :ref:`Send_Bulk_Email` (how-to) + :ref:`Review Sent Messages` (how-to) + :ref:`Example Messages to Students` (reference) + + \ No newline at end of file diff --git a/source/educators/references/communication/example_bulk_emails.rst b/source/educators/references/communication/example_bulk_emails.rst new file mode 100644 index 000000000..fee385916 --- /dev/null +++ b/source/educators/references/communication/example_bulk_emails.rst @@ -0,0 +1,456 @@ +.. :diataxis-type: reference + +.. _Example Messages to Students: + +********************************* +Example Messages to Learners +********************************* + +You can use these example messages, prepared for delivery before typical course +milestones, as models for your own course communications. + +.. contents:: + :local: + :depth: 1 + +These messages are styled as email messages, but you could also post this +information in a course discussion topic or in a course update. To use +:ref:`keywords `, you must send email messages; +keywords are not supported in discussion topics. + +.. important:: + Revise these message templates carefully to include facts for + your own course, meet the needs of your learners, and reflect your own + objectives and personality. Search for the "{" and "}" characters to locate + prompts and replace them with course-specific values. + + Some of these messages also contain :ref:`keywords `. Values specific to your course and the recipients will be + substituted for the keywords when you send the messages. Ensure you are using + keywords appropriately for your course and objectives. + +.. _Prelaunch Reminder: + +==================== +Pre-launch Reminder +==================== + +Pre-launch reminders raise awareness of the course start date, publicize the +course, and generate excitement. In addition to the course start date and time, +the example that follows also lets learners know that: + +* UTC is used in edX courses. Alternatively, you could include information + about your course or the edX platform that will contribute to your learners' + success. + +* The course has a companion social media site. Alternatively, you might + include information about planned meetups or other community-building + opportunities. + +You may want to send out more than one message before the course launches: use +this template as a starting point for crafting the different messages you want +to deliver. Replace values enclosed by {braces} with information that applies +to your course. In addition, check that you are using :ref:`keywords ` appropriately. + +:: + + Subject: {course number} Starts Soon! + + Hello %%USER_FULLNAME%%, + + We are excited that you are joining us for {course number} + %%COURSE_DISPLAY_NAME%%, offered by {organization name} through edX. Class + begins on {day}, {date} at {time} UTC (which is {time} {local time zone}). + Note that many dates and times in edX courses appear in your local time zone, + but some might appear in Coordinated Universal Time (UTC). Dates and times + that use your local time zone are followed by an indication of the time + zone: for example, 17:00 Sept. 5, 2016 IOT. UTC dates and times do not + have a time zone indicator. For UTC times, you might want to use a time zone + converter such as {link}. + + In case you haven't already found it, {course number} has its own official + Facebook page {add link}. You can find videos and photos posted there before + the course even begins. + + If this is your first edX course, consider enrolling in the edX Demo course + {add link}. This course gives you an opportunity to explore the edX platform + and learn how to answer problems and track your progress, before {course + number} begins. + + Your {course number} course staff + +.. _Launch Day Welcome: + +=================== +Launch Day Welcome +=================== + +On your course start date, you can send an email message that both welcomes +learners and gives them specific actions to accomplish. This example directs +learners to two of the course pages to encourage exploration and discovery, and +personally introduces the course team leader. Search for the values enclosed by +{braces} in this template and replace them with information for your course. + +:: + + Subject: {course number} Starts Today! + + Hello everyone! + + At this time, edX course {course number} is available from your Dashboard + {add link}, and the staff would like to officially welcome you to the course! + You'll find materials for the first week on the Course page, + including both video lectures and problem sets. + + Please take some time to go to the Home page to read the handouts + and get familiar with course policies and philosophy. + + I will be your course lead and I hope you will all have a great time learning + {subject}! It may be challenging, it may be frustrating, but it will be + rewarding and you will learn a ton. + + On behalf of the staff, welcome, good luck, and have fun! + + {name} and the {course number} staff + +.. _Verified Registration Reminder: + +============================================== +Reminder to Register for Verified Certificate +============================================== + +After your course has launched, you can send an email to remind learners that +the last day to register for a verified certificate is approaching. You can use +this template as a starting point for your own message; search for the values +enclosed by {braces} and replace them with information for your course. In +addition, check that you are using :ref:`keywords ` +appropriately. + +:: + + Subject: Earn an edX verified certificate for {course name}! + + Dear %%USER_FULLNAME%%, + + Interested in using an edX certificate to bolster a college application or to + advance your career? With an edX verified certificate, you can demonstrate to + colleges, employers, and colleagues that you successfully completed a + challenging edX course, while helping to support the edX mission. + + We would like to remind you that {date} is the last day to register for a + verified certificate in %%COURSE_DISPLAY_NAME%%. Registering for a + certificate is easy! Just go to this course on your edX dashboard and click + "Challenge Yourself". + + Good luck! + + {name} and the {course number} staff + +.. _Weekly Highlights: + +================== +Weekly Highlights +================== + +Sending a weekly email to learners can be a great way to keep them engaged and +provide encouragement. At the end of each week you might send learners an email +that summarizes the content covered, and reminds learners about upcoming +assessments or milestones in the course. Optionally, to encourage participation +in the discussion forums, you might also highlight particularly interesting or +important discussions, and provide links to the discussion topics. + +You can use this template as a starting point for designing your own message, +omitting the discussion highlights if they are not appropriate for your course +(the example discussion highlights are from a course about urban solutions to +the global water crisis). Search for the values enclosed by {braces} and +replace them with information for your course. In addition, check that you are +using :ref:`keywords ` appropriately. + +:: + + Subject: {Course Name} Week 1 Highlights + + We hope you all had a great week! Below, we have provided links to some + exciting discussions that have been going on, and a Q&A video with + {Professor} that recaps some of the questions that have come up this week. + + We'd also like to remind you to take this week's quiz by {date} at {time} + UTC. The next module will be available on {Time and Date}. + + {Link to Video} + + Here are a few highlights from the discussion forum this week. Please join us + online and keep the conversation going! + + * There has been quite a debate over whether urban stream restoration is + possible and what types of restoration are desirable. How can we improve + restoration practice and its outcomes? {Link to the Discussion} + + * Please continue to share your stories of urban stream restoration - there + are many great examples here of what is possible! {Link to the Discussion} + + See you next week, + {name} and the {course number} staff + + +.. _Midcourse Encouragement: + +======================== +Mid-Course Encouragement +======================== + +While your course is running, you can send messages to promote community, +remind learners of upcoming due dates, and address any recurring issues. + +This example gives learners guidance on how to keep up with the course schedule +and encourages contributions to the discussions. You may want to send out more +than one message while the course is running. You can use this template as a +starting point for your own messages; search for the values enclosed by +{braces} and replace them with information for your course. In +addition, check that you are using :ref:`keywords ` +appropriately. + +:: + + Subject: {course name} Announcements + + Dear students, + + We hope that you are learning a lot in {course number}! Remember that problem + set {number} is due on {date} at {time} UTC. You can always check the + schedule {add link} on the Home page to plan ahead. + + The contributions to the course discussions have been amazing. You'll also + see on the Home page that we have made several of you community + TAs to thank you for your thoughtful contributions. Keep those conversations + going! + + We have a few additional announcements. + + * Week {number} on {subject} is now available on the Course page. + + * Problem set {number} is also available. It is due on {date} at {time} UTC. + + * Remember that the due dates for problem sets and exams are in UTC (the GMT + time zone). See the current UTC time here {add link}. Please convert the + times given to your own time zone! + + Wishing you continued success in the course, + + {name} and the {course number} staff + +.. _Midcourse Events: + +======================== +Mid-Course Event +======================== + +Before an exam or other significant course event, messages can provide +practical information about the exam, communicate expectations regarding +conduct, and also encourage learners to continue working toward course +completion. This example lets learners know: + +* How long they have to complete the exam, and when they can see answers to + questions. + +* How to communicate any errors or other issues found during the exam to the + course staff. + +* Whether the course discussions will be open or closed during the exam. (In + the example that follows, the discussions will remain **open**.) + +* What constitutes an honor code violation. + +* What technical limitations, if any, are imposed by external tools such as + graders. + +Be sure to search for the values enclosed by {braces} and replace them with +information for your course. In addition, check that you are using +:ref:`keywords ` appropriately. + +:: + + Subject: {course number} Exam Info + + Hello %%USER_FULLNAME%%, + + Great job working through week {number}! As you know, the {course number} + exam is next week. If you missed a problem set, you can still earn a + certificate. Each problem set is worth only {number}% of the overall grade, + but this exam is worth {number}%. + + Please read this important information about the exam before you begin taking + it. + + * The exam starts on {date} at {time} UTC and must be finished by {date} at + {time} UTC. Plan your schedule accordingly. + + * Be sure that you know what time the UTC deadline is in your time zone. See + the current UTC time {add link}. No extensions will be given. + + * The exam is not timed. You can start, stop, and come back to it until the + deadline. + + * Each exam question allows only one answer submission. If you accidentally + click "Check", that problem cannot be reset for you. + + * The exam covers everything (video lectures, reading, and problem sets) from + weeks {number}-{number}. If you missed any of these materials, you will + want to review them before you take the exam. + + * You can use the textbook and the Internet to clarify your knowledge of exam + topics, as long as you are not deliberately looking up answers to exam + questions. + + * Course discussions will remain open during the exam, but anyone who posts + an answer to an exam question will be violating the honor code and risk + being removed from the class, forfeiting the certificate. + + * If you need to alert the staff to an issue with the exam while the exam is + open, add a post to the General discussion topic and include [EXAM] in + the subject line. + + * Check the Home page periodically. It is the fastest way the + staff has to communicate any delays, corrections, or changes. + + Good luck! + + {name} and the {course number} staff + +.. _Technical Issue: + +======================== +Technical Issue +======================== + +In the event of an unanticipated system failure, a message can both alert +learners to the problem and reassure them that the issue is either resolved or +being addressed. The message can also provide information about any changes +made to the course as a result. + +Technical issues can arise during a course for many different reasons, so this +example is likely to need revision to apply to an issue that you encounter. +Keep in mind that to reassure the learners who are affected by the problem, the +message should have a positive tone, and calmly and briefly identify the +problem, the status of its solution, and any after effects. + +:: + + Dear students, + + We've encountered a technical problem with {video, assignment, etc. name}. + {We are working to resolve it now. / This issue has been fixed.} + + As a result of this issue, we have {extended the deadline for / rescored} + this assignment so that it will not affect your grade. + + Thanks for your patience, and we look forward to continuing the course with + you. + + {name} and the {course number} staff + +.. _Course Farewell and Certificates: + +================================= +Course Farewell and Certificates +================================= + +In the last few days before your course ends, a message can direct learners to +a course survey, answer questions about certificates, and provide information +about future access to course materials. Be sure to replace values enclosed by +{braces} with information for your course. + +:: + + Subject: {course number} Final Remarks + + Dear %%USER_FULLNAME%%, + + Thank you for making %%COURSE_DISPLAY_NAME%% so much fun these last few + months! We had a great time getting to know you through the course + discussions. We appreciate the effort that you put into this course, and we + hope that you enjoyed learning {subject} through edX. With or without a + certificate, you should be proud of your accomplishments. + + * Please take a few minutes to answer the exit survey, now available on the + Course page. We will use your responses to improve the course in the + future. + + * If you qualify for a certificate (overall score {number}% or higher), the + edX dashboard will include a link to your certificate in the near future. + While you may see the link in a few days, it can take up to two weeks for + edX to generate all of the course certificates. + + * As an enrolled student, you will have access to the lecture videos even + after the course ends. Assessments will remain, but you will no longer be + able to submit answers to any problem sets or exams with due dates. + + * The {course number} discussions close on {date} at {time} UTC. You will not + be able to add to the discussions after that time, but you will be able to + continue viewing all of the conversations that took place during the + course. + + We hope that you share what you learned in {course number} with your + colleagues, friends, and family. + + Good luck on the final exam and beyond! + + {name} and the {course number} staff + +.. _New Course Run Announcement: + +================================= +New Course Run Announcement +================================= + +When you prepare a course for a new run, you can use the bulk email feature in +its previous run (or runs) to inform an engaged and knowledgeable audience: +your former learners. Announcing a new run to learners of an earlier run gives +you the opportunity to highlight key aspects of the course, such as the quality +and variety of its discussions, or the global interest and relevance of the +subject, as demonstrated by past enrollment. You can also reveal new features +or content that have been added to the new course run. By emphasizing the +value of the course, you get people thinking and talking about their +experiences, build excitement, and encourage re-enrollment. + +This message template offers learners who did not complete the course, or who +did not previously choose the verified certificate track, the opportunity to do +so. It also invites learners to share the course with colleagues and and +friends. + +When preparing a message from this template, search for values enclosed by +{braces} and replace them with information that applies to your course. + +:: + + Subject: Announcing a new run of {course name} + + Hello {course number} learners, + + The next run of {course number} {course name} begins on {date}! We are glad + to share this news with you, the students who made the earlier run{s} of + {course number} so successful. + + {Success story from the previous run.} + + {New content or features for the upcoming run.} + + Perhaps you want to share the {course name} experience with a friend or + colleague, earn an ID-verified certificate of achievement, or work through + course content that you weren't able to complete before. When {course number} + is offered in {time frame}, we welcome you to join the community of learners + again. + + To learn more and to enroll, visit the {course name} page {add link}. + + We hope to see you in the course, + + The {course number} Staff + +.. seealso:: + :class: dropdown + + :ref:`Bulk Email` (reference) + :ref:`Send_Bulk_Email` (how-to) + :ref:`Review Sent Messages` (how-to) \ No newline at end of file diff --git a/source/educators/references/communication/index.rst b/source/educators/references/communication/index.rst new file mode 100644 index 000000000..1b2dd12fd --- /dev/null +++ b/source/educators/references/communication/index.rst @@ -0,0 +1,8 @@ +Communicating with Students +############################### + +.. toctree:: + :maxdepth: 1 + :glob: + + * diff --git a/source/educators/references/communication/learner_view_discussion.rst b/source/educators/references/communication/learner_view_discussion.rst new file mode 100644 index 000000000..b9e8bcfbd --- /dev/null +++ b/source/educators/references/communication/learner_view_discussion.rst @@ -0,0 +1,30 @@ + +.. :diataxis-type: reference +.. _A Students View of the Discussion: + +********************************** +A Learner's View of the Discussion +********************************** + +When you add a discussion component to a unit, in the LMS, learners see only +the discussion, together with the display name of the discussion component, the category, and the subcategory. EdX recommends that you add an HTML +component before each discussion component where you add some text to +introduce the discussion topic. + +In the following example, the discussion component follows an HTML +component. Learners select **Add a Post** to post their own contributions. + +.. image:: /_images/educator_references/HTMLandDisc.png + :alt: An HTML text component and then a discussion component, as they appear + in the LMS. + +Content-specific topics that you add using discussion components are included +on the course **Discussion** page in the same way as course-wide discussion +topics as included. In the following example, the category (1) and the +subcategory (2) of the discussion component is shown in the list of +discussion topics. + +.. image:: /_images/educator_how_tos/Discussion_category_subcategory.png + :alt: The list of discussions on the Discussion page in the LMS, showing the + category and subcategory of a content-specific discussion topic. + :width: 400 \ No newline at end of file diff --git a/source/educators/migration_wip/7_developing_course/controlling_content_visibility.rst b/source/educators/references/controlling_content_visibility.rst similarity index 62% rename from source/educators/migration_wip/7_developing_course/controlling_content_visibility.rst rename to source/educators/references/controlling_content_visibility.rst index 79aa1373e..2ef949463 100644 --- a/source/educators/migration_wip/7_developing_course/controlling_content_visibility.rst +++ b/source/educators/references/controlling_content_visibility.rst @@ -1,3 +1,5 @@ +.. :diataxis-type: reference + .. _Controlling Content Visibility: ######################################### @@ -17,11 +19,10 @@ features. :local: :depth: 1 -.. only:: Open_edX - You can also configure Open edX so that courses or course outlines are visible - to anyone, not just registered and enrolled learners. For information, see - :ref:`Enable Public Course Content`. +You can also configure Open edX so that courses or course outlines are visible +to anyone, not just registered and enrolled learners. For information, see +:ref:`Enable Public Course Content`. .. _Release Dates: @@ -198,119 +199,3 @@ For information about creating differentiated content based on enrollment track, see :ref:`Enrollment Track Specific Courseware Overview`. -.. _configuring_prerequisite_content: - -******************************** -Prerequisite Course Subsections -******************************** - -You can lock subsections of your course until learners complete other, -prerequisite subsections. If a subsection has a prerequisite, it is displayed -in the course outline with a lock icon, and learners cannot view the subsection -content until they have earned a minimum score in the prerequisite subsection. - -.. note:: - You must first :ref:`Enable Course Prerequisites` before - prerequisite course subsections can be used. - -.. _enabling_subsection_gating: - -================================= -Enable Subsection Prerequisites -================================= - -To enable prerequisite subsections in a course, follow these steps. - -#. From the **Settings** menu, select **Advanced Settings**. - -#. In the **Enable Subsection Prerequisites** field, enter ``true``. - -#. Select **Save Changes**. - -.. _creating_a_prerequisite_subsection: - -================================== -Create a Prerequisite Subsection -================================== - -To prevent learners from seeing a subsection of your course until they have -earned a minimum score or completed a minimum portion in a prerequisite -subsection, follow these steps. - -.. note:: - Make sure that you configure subsection prerequisites in the order that you - intend for learners to encounter them in the course content. The - prerequisite configuration controls do not prevent you from creating a - circular chain of prerequisites that will permanently hide them from - learners. - -.. note:: - You cannot use :ref:`open response assessments` that have a point value of 0 as the prerequisite for other course - subsections. - -#. Enable subsection prerequisites for your course. For more information, see - :ref:`enabling_subsection_gating`. - -#. Select the **Configure** icon for the subsection that must be completed - first. This is the prerequisite subsection. - - .. image:: ../images/subsections-settings-icon.png - :alt: A subsection in the course outline with the configure icon - indicated. - :width: 600 - -#. Select the **Advanced** tab. - -#. Under **Use as a Prerequisite**, select **Make this subsection available as - a prerequisite to other content**. - -#. Select **Save**. - -#. Select the **Configure** icon for the subsection that - will be hidden until the prerequisite is met. - -#. Select the **Advanced** tab, and then locate the **Limit Access** section. - -#. In the **Prerequisite** list, select the name of the subsection you want to - specify as the prerequisite. - - .. image:: ../images/prerequisite-percent-complete.png - :alt: The Limit Access section in the Advanced settings, showing the - Prerequisite, Minimum Score, and Minimum Completion Percentage - controls. - -#. To require that learners achieve a minimum score in the prerequisite - subsection before the current subsection opens, enter the percent of the - total score that learners must earn in the **Minimum Score** field. If - the prerequisite section is not a problem set, set **Minimum Score** to - ``0`` and set **Minimum Completion Percentage** to a value greater than - zero. - - For example, if the prerequisite subsection includes four problems and each - problem is worth the same number of points, set the **Minimum Score** to - ``75`` to require at least three correct answers. - - To require that learners complete a minimum portion of the prerequisite - subsection before the current subsection opens, enter the percent of the - prerequisite subsection that learners must complete in the **Minimum - Completion Percentage** field. - - If you set both the **Minimum Score** field and the **Minimum Completion - Percentage** field to a value greater than zero, then learners must satisfy - both conditions in the prerequisite section before they can view the - current subsection. The default value for both the **Minimum Score** field - and the **Minimum Completion Percentage** field is ``100``. - -#. Select **Save**. - -#. In the course outline, if a subsection has a prerequisite, the prerequisite - name appears under the subsection name. - - .. image:: ../images/studio-locked-content.png - :alt: A subsection in the course outline with a prerequsitie indicated. - :width: 600 - - .. note:: Prerequisite course subsection settings are not retained when - you :ref:`export or import a course`, or - when you :ref:`re-run a course`. \ No newline at end of file diff --git a/source/educators/references/course_development/about_image_guidelines.rst b/source/educators/references/course_development/about_image_guidelines.rst new file mode 100644 index 000000000..690cbf463 --- /dev/null +++ b/source/educators/references/course_development/about_image_guidelines.rst @@ -0,0 +1,66 @@ +.. :diataxis-type: reference + +.. _Course and Program Images and Videos: + +########################################## +Images and Videos for a Course or Program +########################################## + +The About page for a course or program includes both a representative image and +a short About video. The course or program image also appears in places such as +learner dashboards and search engine results. + +For information about how to add your course title and number, see +:ref:`Creating a New Course `. + + +.. contents:: + :local: + :depth: 2 + +.. _Course and Program Image Guidelines: + +*********************************** +Representative Image Guidelines +*********************************** + +A representative image is an eye-catching, colorful image that captures the +essence of a course or program. These images are visible in the following +locations. + + +* The About page. +* The learner dashboard. +* Search engine results. + +When you create a course or program image, keep the following guidelines in +mind. + +* The image must not include text or headlines. +* You must have permission to use the image. Possible image sources include + Flickr creative commons, Stock Vault, Stock XCHNG, and iStock Photo. +* Each course in a sequence or program must have a unique image. + + + +.. _Image Size Guidelines: + +===================== +Image Size Guidelines +===================== + +Images must follow specific size guidelines. + + +Course Image Size +***************** + + + +The course image that you add in Studio appears on the About page for the +course and on the learner dashboard. It must be a minimum of 378 pixels in +width by 225 pixels in height, and in .jpg or .png format. Make sure the +image that you upload maintains the aspect ratio of those dimensions so that +the image appears correctly on the dashboard. + + diff --git a/source/educators/references/course_development/about_video_guidelines.rst b/source/educators/references/course_development/about_video_guidelines.rst new file mode 100644 index 000000000..a2367b76b --- /dev/null +++ b/source/educators/references/course_development/about_video_guidelines.rst @@ -0,0 +1,41 @@ +.. :diataxis-type: reference + +.. _Course About Video Guidelines: + +******************************** +Course About Video Guidelines +******************************** + +The course About video should excite and entice potential learners to enroll, +and reveal some of the personality that the course team brings to the course. + +This video should answer these key questions. + +* Who is teaching the course? +* What university or institution is the course affiliated with? +* What topics and concepts are covered in your course? +* Why should a learner enroll in your course? + +This video should deliver your message as concisely as possible and have a run +time of less than two minutes. + +Before you upload a course About video, make sure that it follows the +same :ref:`video guidelines