This lets us have a specific Analytics code for the dashboard,
instead of using it for dashboard & docs.
This keeps the pre-existing global one for all things,
but lets us segment out the dashboard.
This is mainly useful for having GA not sample our dashboard traffic,
so we can get real data for it.
* Add changelog and changelog automation
First, update the version in our setup.cfg and changelog:
invoke prepare <version>
Then, hand edit and commit, added any release notes, etc. Tag manually or:
invoke release <version>
Finally, push up your changes.
This:
* Uses setup.cfg instead of setup.py
* Parses setup.cfg for version
* Updates setup.cfg on release prepare task
* Show our release version in our footer
* Uses invoke for task execution
* Uses a node library to hit GitHub and fetch the changelog
* Imports this into our existing changelog
* Fix style with autolint
* Lint fixes
* WIP for integrating persistent messaging for users
Combines notifications so that email/on site messaging will all be maintained in
the same place, and can extend from each other using normal template semantics.
* Add email support, clean up implementation
* Add reqs
* Drop unnecessary string conversion
* Change admin email form to look at templates, not ask for template source
* Add docs, tests, views for processing redirects
* Do the thing I meant to do
* Drop views, just use javascript instead
This adds javascript that intercepts link clicks in notifications,
hits the dismiss url defined on the dom object, and then redirects
to the correct url of the original link.
* Move classes around and rename module
* Drop unused notification for testing
* Clean up usage, drop test uses of the views/notifications
* Add example usage that will be used for notification on resource usage
* Fix mock module path
* Add more docs around implementation
* Add call for contributing on the front page
* Copy changes and footer update
* Copy edit
* Remove copyright
* Kill old commented out stuff in homepage
It seems standalone libs will either export globally or via
require, but not both? Removing standalone and requiring jquery
in the base template creates a global instance of jquery.
* Docs!
* Updated gulpfile, ported changes to corporate gulpfile back here. Changes here include:
* New browserify syntax, dropped banned gulp-browserify module
* Broke out jquery and knockout to standalone vendor packages. Client libraries were bundled with these before. Now, templates that include the client libraries are also responsible for including vendor dependencies
* Vendor libraries are passed through Browserify to provide both global window access as normal, and access to the module via require
* Ported better structure and better watch file support
* Added minifying to javascript and vendor javascript
* Regenerated javascript libraries as minified files
* Added readthedocs/static/vendor path for checked in vendor files
* Adds static file dir for generic readthedocs/static path
* Replaces google CDN jquery with vendored jquery, still v2.0.3
* Pinned bower jquery dependency at 2.0.3
David Fischer
Eric Holscher
Santos Gallegos
Anthony
David Fischer
EdOverflow
Jesse Tan
Joachim Jablon
shubheksha
Aditya Singh
Garen Torikian
Philippe O. Wagner
Thomas Kluyver
YFdyh000
Benjamin Peterson