t.column :first_name, :string
t.column :last_name, :string
t.column :email, :string
t.column :username, :string
t.column :bio, :text
t.column :photo, :string
t.column :interests, :string
t.column :tags, :string
t.column :passion, :string
t.column :passion_for_learning, :string
Rob, I don’t know exactly how or if it matters what kind of permissions we set on each of the content blocks you listed, but I would think that we might want to separate all of this in the UI as follows:
Details users cannot change:
t.column :first_name, :string
t.column :last_name, :string
t.column :username, :string
Details users can change:
t.column :email, :string
t.column :bio, :text
t.column :photo, :string
t.column :interests, :string
t.column :tags, :string
t.column :passion, :string
t.column :passion_for_learning, :string
This way the vitals are entered during the sign-up process, and once they are logged-in and using the app, they can add content to their own bios.
Additional thoughts?
ps: sorry about all the non-ruby code ;-)