<%! from django.utils.translation import ugettext as _ %> <%inherit file="/main.html" /> <%! from django.core.urlresolvers import reverse %> <%namespace name='static' file='/static_content.html'/> ## ----- Tips on adding something to the new instructor dashboard ----- ## 1. add your input element, e.g. in instructor_dashboard2/data_download.html ## the input includes a reference like data-endpoint="${ section_data['get_anon_ids_url'] }" ## 2. Go to the old dashboard djangoapps/instructor/views/instructor_dashboard.py and ## add in a definition of 'xxx_url' in the right section_data for whatever page your ## feature is on. ## 3. Add a url() entry in api_urls.py ## 4. Over in lms/static/coffee/src/instructor_dashboard/ there there are .coffee files ## for each page which define the .js. Edit this to make your input do something ## when clicked. The .coffee files use the name=xx to pick out inputs, not id= ## 5. Implement your standard django/python in lms/djangoapps/instructor/views/api.py ## 6. And tests go in lms/djangoapps/instructor/tests/ <%block name="headextra"> <%static:css group='course'/> ## NOTE that instructor is set as the active page so that the instructor button lights up, even though this is the instructor_2 page. <%include file="/courseware/course_navigation.html" args="active_page='instructor'" />
##

Instructor Dashboard

## links which are tied to idash-sections below. ## the links are acativated and handled in instructor_dashboard.coffee ## when the javascript loads, it clicks on the first section

% for section_data in sections: ${_(section_data['section_display_name'])} % endfor

## each section corresponds to a section_data sub-dictionary provided by the view ## to keep this short, sections can be pulled out into their own files % for section_data in sections:
<%include file="${ section_data['section_key'] }.html" args="section_data=section_data" />
% endfor