Wagn 1.14 - the future of history

cards revision history have long been among Wagn's strengths.  And the more we make it that everything is a card – Skin in version 1.12,  accounts and JavaScript in 1.13, and now Email template in version 1.14 were all recently converted to cards) – the more useful those revisions have become as a log of your creative work.

But the revision system had some key flaws.  For example, Wagn didn't track name or type changes, and it didn't group together edits to multiple cards that took place as part of one submission.  It was also very difficult to navigate changes for structured cards; you had to look through one field card at a time.

Wagn 1.14 fixes all of those issues and adds a much more compelling interface to boot.  Now you can...

• review and revert changes to a card's name and/or type in addition to content.
• browse through lists of acts on a card, each of which might include actions on multiple cards.  You can then expand actions to see more detail.
• load changes to content-heavy pages much more quickly.
• view all changes to included cards as part of the same revision list.

In parallel, we began an overhaul of the system for following cards (receiving notifications for changes).  Now you can:

• see the actual content changed in the email (emails will include diffs in Wagn 1.16)
• view and edit the list of cards that you're following by editing your card name+*following.
• customize follower notification email

In fact, not just follower emails but all Wagn emails are now handled in cards and fully customizable, including:

• verification email, which are sent out to verify emails used for Sign up.
• signup alert email, which are sent to notify interested users of a new signup. 
• password reset email, which are sent out when someone has lost a password and clicks "RESET PASSWORD" on the Sign in page.

A bit more on the geeky side, it's also worth noting that Wagn 1.14 marks a major milestone for Wagn in that it's the first release in which all actions can be accomplished via our RESTful Web API.  That is to say that every server action you'll ever take on Wagn, from signing up to signing in to opening a card to following it to anything else will involve a simple CRUD (create, read, update, or delete) operation on a card.