This question has been answered by sottwell. See the first response.

If that's all the site is doing, then indeed a more specific customized application may be a better choice. MODX is a general-purpose web application framework, with a CMS built-in, so it is more complicated to create any specific application.
However, MODX can easily handle this task. In fact, I'm working on the user part right now, modifying the MemberPages plugin and working to more easily incorporate the different features that need to be installed and configured.
As it is, this plugin creates a user group and resource group, a resource, and a file folder for each new user. It puts the new user in a common pre-existing group and his new user-specific group, and puts the new resource into the new user-specific resource group. The file folder is for any images or other files the user can upload.
I use the migxResourceMediaPath snippet for a Media Source that is dynamic for each user, and BobRay's NewsPublisher for the users to edit their resources in the front-end. At this time, the whole package only works together in Revolution 2.2.15, as the file access through the TinyMCE file browser feature doesn't work in Revo 2.3. If users will not be uploading or selecting images or other files, though, the rest of it works fine in 2.3
I also have a Policy Template and a Policy exported .xml file which were tuned to control access permissions just for this purpose
I'm working on the user part right now, modifying the MemberPages plugin and working to more easily incorporate the different features that need to be installed and configured.If I read you right you are also working on this application?
If that's all the site is doing, then indeed a more specific customized application may be a better choice. MODX is a general-purpose web application framework, with a CMS built-in, so it is more complicated to create any specific application.
However, MODX can easily handle this task. In fact, I'm working on the user part right now, modifying the MemberPages plugin and working to more easily incorporate the different features that need to be installed and configured.
As it is, this plugin creates a user group and resource group, a resource, and a file folder for each new user. It puts the new user in a common pre-existing group and his new user-specific group, and puts the new resource into the new user-specific resource group. The file folder is for any images or other files the user can upload.
I use the migxResourceMediaPath snippet for a Media Source that is dynamic for each user, and BobRay's NewsPublisher for the users to edit their resources in the front-end. At this time, the whole package only works together in Revolution 2.2.15, as the file access through the TinyMCE file browser feature doesn't work in Revo 2.3. If users will not be uploading or selecting images or other files, though, the rest of it works fine in 2.3
I also have a Policy Template and a Policy exported .xml file which were tuned to control access permissions just for this purpose