Context Navigation

What to ask in forms and what to show in results?

User information

Setting user preferences

Technical stuff: User's properties can be accessed as properties of MemberFolder?-archetype object, which can be reached from user.getHomeFolder() or portal_membership.getHomeFolder(userid). Setting these properties also mirrors them to user's actual properties so that when you need to get f.ex. users fullname you can get it from user object directly. We're having MemberFolder? to contain user properties, because as an Plone object it can be indexed and we can do faster searches for user properties this way. Especially this will be necessary when we'll have a network of LeMills?, then we need only share an index, not user lists with properties. Only some of the properties need their own catalog index: rule should be that if we are supposed to be able to directly search for that property *or* have value of that property listed in 'tag cloud'.

These are set as archetype fields in MemberFolder?.py, but config has variable member_properties (in caps), which sets the actual user properties. Both member_properties and MemberFolder? should have same fields so they can mirror each others.

id = email (having an option to change your email will then be a feature for some later release. (It will need a script to move all content authored by certain user and group memberships to new user, then delete the old user.)) = email in MemberFolder?, shouldn't be used - if you are in somebodys MemberFolder? there should already be lots of ways to know persons id.