Meteor Boilerplate Todo List
============================

* Figure out how to identify / track where we are in the HTML. Look at how autoform tracks back up the DOM (jQuery I assume), perhaps we could drop "breadcrumbs" along the way to the _id of the elements that we want to be able to reference. Another approach would be to add an ID of some sort to each sub-document as we create it so that we can track back from there. Router.current() isn't always useful – could it be?

* Remove autopublish
* Remove insecure
* Enforce route security


* Generic, nestable, collapsible element template (e.g., for units in courses)
* Drag-and-drop sorting of units (in a generic way if possible)
* Clean up index.html template so that it is not necessary to include navigation templates in each sub-template
* Highlight active tab in top navbar
* Fineprint page templates
* Cleanup server status
	* CSS / padding at right
	* Tooltip vs popup
	* Detailed status
* User profile
* Use the same form to handle autoform inserts and updates – build the machinery for handling this. See here: https://github.com/aldeed/meteor-autoform#can-i-reuse-the-same-quickform-or-autoform-for-both-inserts-and-updates
* Example of code to populate an autoform options list from another collection. This seems useful enough – and on the edge of complex enough – that it would be useful to do as a generic example for the Autoform package. It could be a tutorial and package of sample code.


* Roles
* User account management


* Tests


* Way to autogenerate credits?
* Identify configuration points
* CSS for basic look and feel of the site


* Organize into a "foundation" and "application" structure so that it is easy to see what code is the boilerplate package and what was added to build a particular application.

Meteor Boilerplate Todo List
============================

* Generic, nestable, collapsible element template (e.g., for units in courses)
* Drag-and-drop sorting of units (in a generic way if possible)
* Clean up index.html template so that it is not necessary to include navigation templates in each sub-template
* Highlight active tab in top navbar
* Fineprint page templates
* Cleanup server status
	* CSS / padding at right
	* Tooltip vs popup
	* Detailed status
* User profile
* Use the same form to handle autoform inserts and updates – build the machinery for handling this. See here: https://github.com/aldeed/meteor-autoform#can-i-reuse-the-same-quickform-or-autoform-for-both-inserts-and-updates
* Example of code to populate an autoform options list from another collection. This seems useful enough – and on the edge of complex enough – that it would be useful to do as a generic example for the Autoform package. It could be a tutorial and package of sample code.


* Roles
* User account management


* Tests


* Way to autogenerate credits?
* Identify configuration points
* CSS for basic look and feel of the site


* Organize into a "foundation" and "application" structure so that it is easy to see what code is the boilerplate package and what was added to build a particular application.

Delete items as they are made into issues.
Delete items as they are made into issues.
