With every new release, Wagn adds not just more power, but also more harmony. Wagn 1.7 brings new power and harmony to our permissions system.
- Easier management. Our old permissions table stored separate permissions settings for every single card. Since our rules system allows for much more elegant expression of broad patterns, it is now far easier to see and manage your permissions. As an example, imagine you have 1000 user cards that can only be seen by "anyone signed in", and you want to change them so they can be seen by "anyone". In the old system, this would require going to the options tab of 1000 cards. Now this just requires one edit.
- Better interface. Because permissions are now rules, all the new improvements to our rules interface will make it easier to create and edit permissions configurations.
- More flexible assignments. Before, permissions could only be assigned to Roles, or groups of users. Permissions can now be assigned to any combination of Roles and Users that you might want.
- Searching. Since permissions are now in cards, you can now access them through the Wagn Query Language (WQL).
- Simpler API. Now you can create and edit permissions rules through the standard card API.
- Customizability. Because permissions are now managed through cards, you can tweak their editors and other views with our packs API.
As of Wagn 1.6, developers can extend Wagn without forking its code by creating a "pack".
"Packs" are ways to extend Wagn's functionality. In the long term, we envision that a "pack" may refer to several things:
- "modularized" code that can easily be added or subtracted
- a "tradeable" group of configuration cards
- a combination of the above
We'd like people to be able to use Wagn in languages other than English. Some of the text you see in Wagn's interface is in the code, and we are beginning to document that so that we can move cue text to editable cards. But a surprising amount of Wagn's interface is already in cards. New Wagns currently draw all of their default cards from a Wagn called "en" (for English), and it will be fairly straightforward to add an option for new Wagns to draw their default cards from a different Wagn.
So the idea is to set up a Wagn for each new language, with a list of translatable cards, and instructions on what exactly needs translating. That list will look something like this:
New Wagns now come with close to 300 cards by default, and this number is only going to go up as Wagn's power increases and functionality is moved from code into the cards themselves. We want it to be easy for Wagneer to get a sense of what's built in to new Wagns, and what all of these cards do. We're also preparing the way for translating Wagn into other languages (more on that in a later blog entry). So, I've written up a list of all of the cards that come with new Wagns, briefly explaining them and linking to deeper documentation:
There's space at the end of that card for any feedback you'd like to give on how you find it useful, or any suggestions you have for improvements (you can also just edit the card directly of course — I'll be watching it).