5f4082d595
From a user perspective: Use friendlier URLs for lists. Reuse the search results table for displaying lists. Simplify the management pages and improve the search rule UI to help fill in the values and validating them, instead of just providing a text field. Fixes #1874. Add an explicit button for adding individual documents. Include all changes in the document change streams, not just some changes. Fix a concurrency issue that allows changed documents to escape the search rules. Don't create an empty list just be logging in. From a code maintenance perspective: Clean up the models. Replace the background caching scheme with direct queries. Get rid of a big chunk of code. Speed up the code that adds track buttons to search results. Add tests of all community views. Fixes #1422. Also fix some minor bugs and oddities here and there. There's still some work to do with respect to integrating the group lists better. - Legacy-Id: 10921 |
||
|---|---|---|
| bin | ||
| bootstrap | ||
| buildbot/masters/datatracker | ||
| data | ||
| docker | ||
| etc | ||
| form_utils | ||
| hooks | ||
| ietf | ||
| notes | ||
| redesign | ||
| static | ||
| test | ||
| timedelta | ||
| vzic | ||
| .editorconfig | ||
| .eslintrc.js | ||
| .gitignore | ||
| 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.