Deciding which modules to use for profiles

	Usage	Pros	Cons
Bio	Download, install, and enable the Bio module. Setup at admin/user/bio Add CCK fields as needed	Integrates with the account page just by checking boxes in settings Uses any node type for the biography or can extend the built in type with CCK Can easily get rid of all the misc stuff that ends up on the view account page and just have the profile there. Lets you link to the bio from content without any special coding Automatically enforces one bio per user	Doesn't seem to be a way to have the user fill out the biography during registration.
Usernode	The usernode module can be used to create user profiles by adding fields to it with CCK.	No need to add extra modules. Just install usernode (and CCK if you don't have that) and add fields Usernodes are automatically created / deleted with users You can use views with your profiles	If you decide later you'd rather have multiple pages in your profile, you're out of luck No facility for adding the profile fields to the registration form Adding the profile into the user page requires jumping through some hoops
Nodeprofile	Nodeprofile is very simililar to the bio module so it was tough deciding between the two. In the end, I decided to go with nodeprofile and help add some more functionality to the module to get the one thing it didn't have (see below).	Can integrate with the user account page Can add node profiles to the registration page Can have multiple content types that are node profiles Is part of a family of modules including usernode and pageroute that give you a ton of options	The integration with the user account page isn't ideal (IMO) but that is being addressed at http://drupal.org/node/140592

Original post from: http://shellmultimedia.com/articles/deciding-which-modules-use-profiles