Project

General

Profile

Design/UX #4230

Change 'Public Profile Details' in Register (Create Account) form to be consistent

Added by Samantha Raddatz about 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority name:
Normal
Category name:
Registration
Target version:
Start date:
2015-06-25
Due date:
% Done:

0%

Estimated time:

Description

The Register (Create Account) form uses the heading ‘Public Profile Details’ to describe the fields that end up appearing on the ‘Public Portfolio’ page and in the ‘Commons Profile’. These labels should be consistent throughout the site.

Labels should be consistent throughout site, and make it clear to users that these fields will appear on both the ‘Public Portfolio’ and the ‘Commons Profile’.

profile&portfolio_page.png (897 KB) profile&portfolio_page.png Samantha Raddatz, 2015-06-30 12:02 PM

Related issues

Related to CUNY Academic Commons - Design/UX #4207: Profile/Portfolio labelling Resolved2015-06-25

History

#1 Updated by Boone Gorges about 4 years ago

  • Assignee changed from Boone Gorges to Samantha Raddatz
  • Target version set to Future release

See also #4207.

Do you have specific suggestions about how the labeling should work? Should we be dividing up the registration fields based on "Commons Profile" vs "Public Portfolio"? Or is it just that the term "Public Profile" is confusing? How about if we called it "Profile Details" (since some fields can be configured to be non-public) and then added a bit of text with specifics about where the specific fields will appear?

#2 Updated by Samantha Raddatz about 4 years ago

Yes, I like "Profile Details" for the label on the registration page -- it's broader allowing it to refer to both areas. Including a line of text is also a good idea -- maybe something like 'This information will appear as part of your "Public Portfolio" and you can change visibility preferences in "Settings."'

Right now the sections unique to the "Public Portfolio" are not part of the registration process (see attached screenshot). The user must add these in after at the bottom of the "Edit" page. I do think it would be good to add those sections to the initial registration process, otherwise the user may miss those sections.

#3 Updated by Matt Gold about 4 years ago

Samantha Raddatz wrote:

Right now the sections unique to the "Public Portfolio" are not part of the registration process (see attached screenshot). The user must add these in after at the bottom of the "Edit" page. I do think it would be good to add those sections to the initial registration process, otherwise the user may miss those sections.

This is an important point. I've been noticing that many new members never customize their portfolio page, so getting some of that basic info through the registration page would be good. Though, of course, we also need to be wary of more clutter on an already cluttered registration page/process

#4 Updated by Boone Gorges about 4 years ago

  • Category name changed from User Experience to Registration
  • Status changed from New to Assigned
  • Target version changed from Future release to 1.9

Adding "portfolio widget" controls to the registration process is technically complicated. And I strongly agree with the sentiment that it would dramatically increase what is already a too-long registration form. If we're concerned about getting more people to fill out their profiles, we should come up with another mechanism for encouraging them to fill it out.

I've made the heading change, and updated the explanatory text, in https://github.com/cuny-academic-commons/cac/commit/212a42a13eb9d9e393b15ea61597ed78242933ca. You can see this on the Register page of cdev. Sam, will you have a look at the updated language (just below "Profile Details") to see if it makes sense to you.

#5 Updated by Samantha Raddatz about 4 years ago

Looks good to me. Thanks, Boone.

Regarding getting people to fill out their profiles, I agree that it could be a bit much for the registration process. I'm going to create a new ticket for that so it doesn't get forgotten.

#6 Updated by Boone Gorges over 3 years ago

  • Status changed from Assigned to Resolved

Also available in: Atom PDF