2042f981bd
Added redirect for non-secretariat users from ietf.secr.proceedings.views.select to ietf.meeting.views.materials. Added a note to the secr upload_footer pointing to where material upload is now done. Modified the links on the group meetings page to make it less likely to miss the link to the session materials. Used class anchor target to clean up landing on the right session of multiple sessions on a group's session details page. Modified the materials page to only add a fragment asking for that anchor for non-ag/wg/rg groups. Only show the link to the (now) secretariat-only proceedings manipulation page if the user is the secretariat. Relabelled the link to better reflect the page's remaining purpose. Changed the session_details "Artifacts" panel header to "Agenda, Minutes, and Bluesheets". Added a footer to the "Slides" panel calling out drag-and-drop reordering. Commit ready for merge. - Legacy-Id: 12018 |
||
|---|---|---|
| bin | ||
| bootstrap | ||
| buildbot/masters/datatracker | ||
| data | ||
| docker | ||
| etc | ||
| form_utils | ||
| hooks | ||
| ietf | ||
| media/photo | ||
| notes | ||
| redesign | ||
| static | ||
| test | ||
| timedelta | ||
| vzic | ||
| .editorconfig | ||
| .eslintrc.js | ||
| .gitignore | ||
| .pylintrc | ||
| changelog | ||
| changelog.py | ||
| control | ||
| debug.py | ||
| hold-for-merge | ||
| INSTALL | ||
| LICENSE | ||
| LICENSE.django | ||
| PLAN | ||
| README-CDN.rst | ||
| README.datatracker | ||
| ready-for-merge | ||
| release-coverage.json.gz | ||
| requirements.txt | ||
| tzparse.py | ||
The "new" datatracker uses Twitter Bootstrap for the UI. Get familiar with http://getbootstrap.com/getting-started/ and use those UI elements instead of cooking up your own. We have some site-wide customization applied to the bootstrap version we keep in bootstrap/ (from which the minified dist version is built); it modifies some stuff under less/ We also apply some additional custiomizations in static/css/ietf.css; we should eventually move that under bootstrap/less/ if possible. (ietf.css was what Lars used initially for customization with an unmodified bootstrap.) Some ground rules: * Think hard before tweaking the bootstrap CSS, it will make it harder to upgrade to future releases. * No <style> tags in the HTML! Put CSS into the "morecss" block of a template instead. * CSS that is used by multiple templates goes into static/css/ietf.css. * Javascript that is only used on one template goes into the "js" block of that template. * Javascript that is used by multiple templates goes into static/js/ietf.js. * Every template includes jquery, so write jquery code and not plain Javascript. It's shorter and often faster. * No CSS, HTML styling or Javascript in the python code! * Templates that use jquery or bootstrap plugins include the css file in the "pagehead" block, and the Javascript in the "js" block.