Hey Andrew – as I mentioned on Facebook, we didn’t delete anyones post. Turns out there was a weird setting that was on which caused me to see no-ones comments but my own (why they would do that I don’t understand).
We are working on that documentation this week.
As for the email subscription, roescher is working on that literally right now (you must be psychic).
Peter was up till 3am last night documenting, refactoring and organizing.
The good news is that it is all processed.
The obvious consequence is that we broke a couple things while cleaning house and Rob is QA’ing them right now. Hopefully John can fix them this weekend or early next week and we can release 2.0.1 as well as the documentation.
Posting the documentation early wouldn’t make much without access to the updated template tags.
We just put 2.0.1 through QA today and found a few solid bugs that were introduced. I’m guessing we are on track for thursday to fix those and release (as long as Rob doesn’t find more serious bugs to delay).
If you are willing to deal with those bugs of the next few days while we fix them, you can ping Rob at firstname.lastname@example.org and he will send you a copy of the current 2.0.1 build. Here is a quick export of the auto compiled documentation of the template tags and advanced functions. I’ll get a nice style etc when we put it on our site but it should hold you over. http://cl.ly/BFao. Note that these docs are for 2.0.1 (not 2.0) as the template tags got a bit of refactoring for 2.0.1.
Shane- will 2.01 give some standard ways I should bd editing the css? I’m doing some messing with the css right now just to keep my project moving. (I can’t wait until Thursday)
We’ll be pushing it into production over the weekend. Is the release going to be ready by then? Or should I plan on releasing with 2.0 and know I’ll have to go back and adjust the css for 2.01?