Mercurial > hg > discussions
changeset 1:79ba50af9443
add more notes
author | k0s <k0scist@gmail.com> |
---|---|
date | Mon, 04 Jan 2010 21:17:41 -0500 |
parents | c904249afb04 |
children | 910fa7e781b9 |
files | discusssions/templates/member.html whitepaper.txt |
diffstat | 2 files changed, 60 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/discusssions/templates/member.html Mon Jan 04 21:17:41 2010 -0500 @@ -0,0 +1,25 @@ + +<a py:if="member['show_email']" href="mailto:${member['email']}"> +${member['email']} +</a> + +<div> +<h2>Your forums:</h2> +<ul> +<li py:for="forum in forums"> +<a href="${forum['link']}"> +<img py:if="'image' in forum" src="forum['image']"/> +${forum['name']} +</a> +<!-- unsubscribed or subscribe --> +</li> +</ul> +</div> + +<div> +<h2>Recent discussions:</h2> +<!-- TODO --> +</div> + +<!-- TODO: subscriptions: subscriber, digest: 'daily', 'monthly', etc --> +
--- a/whitepaper.txt Sat Jan 02 13:36:23 2010 -0500 +++ b/whitepaper.txt Mon Jan 04 21:17:41 2010 -0500 @@ -3,9 +3,25 @@ All Discussions objects are basically the same. You get a set of options which are inherited from the parent or provided. +== Roles and Permissions == + +A member can be in one of three states with respect to a resource: + + * administrator: has all rights over a resource except as set by + above resources; Administrators of the root ('/') resource are + site administrators and have all rights. + + * members: has permissions of a resource as dictated by the + administrator (view, post, etc). [different types of members? + groups? probably not] + + * non-members: if an agent isn't a member of a resource, they + generally have lowest level priveleges. + == Options == -Options can be in one of three states: unset, set, and locked. In +Options can be in one of three states: unset, set, and locked (and +set + locked). In the case where the option is locked, all children inherit the setting as well: @@ -32,4 +48,21 @@ == Preferences == -Member preferences can also be set from the site level. \ No newline at end of file +Member preferences can also be set from the site level. + += Digest = + +Different templates can be used to display different digest methods. +For instance, you could display a brief form of the message with just +the links: + +{{{ +Example of .ini configuration: + +[digest:daily] +template = /path/to/templates/daily-digest.txt + +}}} + +This can be used to facilitate a moderated digest. Roundup emails can +be sent about a discussion written and editted by the moderator. \ No newline at end of file