I would strongly advise you not to make resources out of all the profiles. In MODX Revolution, the profiles already exist in the database and you can add extra 'extended' fields to them in the Manager. The Profile snippet will show them, and the UpdateProfile snippet will let users update them in the front end (both are part of the Login package). The Peoples package also has snippets that will show views of selected user profiles.
If you have the skills, you can also subclass the user object and add any extra fields to a custom user table, which is more efficient and convenient once you get it set up.
If you make a separate resource for each user, you will be duplicating all the data and carrying all the extra overhead of resources (you have no need for most of the resource fields, but you'll be storing and processing them anyway).
Worse yet, your resources won't necessarily be synchronized with the user data in the database unless you add that functionality and if you decide to add a new user field or reformat the display, you'll have to edit every resource, so maintenance will be a nightmare.
One key to good design is to separate the data (model) from the view. You'd be mixing them in the worst possible way. Instead, I'd suggest a single resource (or a small number of them) to display the user data for any user and maybe another one (or again a small number) to allow editing it.
I hope I don't sound too critical here. I just hate to think of what you'd be facing down the road with that design.
)
