@ onthemarkdesign, Well now I do feel happy, more than likely will contribute my thoughts and ideas knowing my thinking out of the box may well be accepted at times in a new community I have stumbled across and already addicited too.

Should we set up a new group? (Don't think one has been for this subject yet)

It needs a clear mission statement, a few of us can kick ideas about what categories subjects should be on the most important to do list first, then medium and low video, image and text tutorials.

Also so it doesn't get messy with anybody wanting to chip in and contribute their part, should we also decide on exactly what file formats etc and any other relevant information they would need to adhere too.

So if we are to be able to have the tutorials dropped in to a plugin, that can then be put in a widget, there wouldn't be a nightmare trying to get everything to sync and work nicely together?

Although the latter two I wouldn't be able to help with as I am not that good lol.

Regards,

@Cash - True most of the info is for the "back end" of Joomla, but if a wiki was created for the 'front end' user for Elgg that would be something that would differentiate Elgg from other Open Source CMS project.  I'm working with the JFusion Documentation Team, so I'll probably right in the middle of things regarding the Joomla/Elgg project using JFusion to bridge them!  

@Rob - If there's not a Group not already going for the End User Documentation, I'd say "start it"!  It will take time, and with each new version of Elgg, the End User Documentation (EUD) will need to be updated.  Just the planning for the core EUD will take some time, since we are creating it for the first time. 

I'd say as far as the "code" of it, core EUD must be made so it's instantly upgradeable by the webmaster of the site.  Give them an auto update or manual option on the EUD updating.

OK, thanks for the responses, I think I will make a bit of a start on one section myself then figure out how best to share it. I was going to do something in OpenOffice.org or Google Docs, but the pages plugin seems a more Elggish way to do it, and I guess it could end up as a documentation plugin

@ onthemarkdesign, Well now I do feel happy, more than likely will contribute my thoughts and ideas knowing my thinking out of the box may well be accepted at times in a new community I have stumbled across and already addicited too.

Should we set up a new group? (Don't think one has been for this subject yet)

It needs a clear mission statement, a few of us can kick ideas about what categories subjects should be on the most important to do list first, then medium and low video, image and text tutorials.

Also so it doesn't get messy with anybody wanting to chip in and contribute their part, should we also decide on exactly what file formats etc and any other relevant information they would need to adhere too.

So if we are to be able to have the tutorials dropped in to a plugin, that can then be put in a widget, there wouldn't be a nightmare trying to get everything to sync and work nicely together?

Although the latter two I wouldn't be able to help with as I am not that good lol.

Regards,

@Cash - True most of the info is for the "back end" of Joomla, but if a wiki was created for the 'front end' user for Elgg that would be something that would differentiate Elgg from other Open Source CMS project.  I'm working with the JFusion Documentation Team, so I'll probably right in the middle of things regarding the Joomla/Elgg project using JFusion to bridge them!  

@Rob - If there's not a Group not already going for the End User Documentation, I'd say "start it"!  It will take time, and with each new version of Elgg, the End User Documentation (EUD) will need to be updated.  Just the planning for the core EUD will take some time, since we are creating it for the first time. 

I'd say as far as the "code" of it, core EUD must be made so it's instantly upgradeable by the webmaster of the site.  Give them an auto update or manual option on the EUD updating.

OK, thanks for the responses, I think I will make a bit of a start on one section myself then figure out how best to share it. I was going to do something in OpenOffice.org or Google Docs, but the pages plugin seems a more Elggish way to do it, and I guess it could end up as a documentation plugin

Alan,

I do understand your request, because obviously parents would want to be involved, even with older kids. I believe strongly in parent involvement, but you need some sort of trade off between parent's wish to see/control/understand what their kids are doing, for a number of reasons. At the same, obviously, kids do not really want their parents to look over their shoulder, for even more reasons. For younger kids, the parent could simply share their password and look .-) For older kids, maybe parents could be allowed to see everything, expect what kids put in their 'private' folder. It makes sense to separate in some way. To let inquisitive mothers loose everywhere will not be popular with most teenage kids I know.

Anyway, I think it would take a lot of clever coding to create such a 'ghost' user, and the security aspect here is another thing. Not simple, from where I sit.

Let us know how you fare :-)

Hmm ;;;-|

sounds similar to the concept a client approcached me with where they wanted to have a *hierarchy of users for a different commercial purpose.

The basics should not be too hard to start off with metadata.. the subsequent administration and accesses might become a little more complicated.. needing overloading (or overriding) to Elgg functions.

I will post more thoughts later

( This is one of those topics that would go well on one of my  techie groups.. ;-O)

I want to start with the principal that sharing passwords is a bad idea. I want the children to have their own passwords and the freedom to change them, learning password management is an objective. There will probably be an upper age limit of 12, kids get kicked out when they become teenagers. Then they can take off the armbands and join a different community.

Alan,

I do understand your request, because obviously parents would want to be involved, even with older kids. I believe strongly in parent involvement, but you need some sort of trade off between parent's wish to see/control/understand what their kids are doing, for a number of reasons. At the same, obviously, kids do not really want their parents to look over their shoulder, for even more reasons. For younger kids, the parent could simply share their password and look .-) For older kids, maybe parents could be allowed to see everything, expect what kids put in their 'private' folder. It makes sense to separate in some way. To let inquisitive mothers loose everywhere will not be popular with most teenage kids I know.

Anyway, I think it would take a lot of clever coding to create such a 'ghost' user, and the security aspect here is another thing. Not simple, from where I sit.

Let us know how you fare :-)

Hmm ;;;-|

sounds similar to the concept a client approcached me with where they wanted to have a *hierarchy of users for a different commercial purpose.

The basics should not be too hard to start off with metadata.. the subsequent administration and accesses might become a little more complicated.. needing overloading (or overriding) to Elgg functions.

I will post more thoughts later

( This is one of those topics that would go well on one of my  techie groups.. ;-O)

I want to start with the principal that sharing passwords is a bad idea. I want the children to have their own passwords and the freedom to change them, learning password management is an objective. There will probably be an upper age limit of 12, kids get kicked out when they become teenagers. Then they can take off the armbands and join a different community.