CUNY Academic Commons

For example, if you are a user who hasn't changed your profile from the older version, we should have some help that says you haven't updated it, leads to docs and examples, etc.

Somehow this feels like a lot to add on to Boone right now since I haven't created it and the release is now. If #2742 do you all think it's OK if we don't do this for now and perhaps think about adding it (if at all) when we do the cuny.is publicity push later? Let me know what you think and if I should get something up on this now or not.

Yes, sounds like it's not ready for today, so let's punt to the cuny.is release if the 9th is reasonable.

Boone, apologies, I thought I updated this with a possible modal overlay but I see I didn't. I don't have the example with me and I'm in class for the rest of the day so it won't come until tonight.

Great, thanks for the edits. I knew I was forgetting something. Boone, if you use Simple Modal you may have to play around with the minHeight in the JS line and the width in #simplemodal-container to fit things.

Looks great, Boone. One thought: we really should provide a link, if possible, that will take people to their profile pages so that they can see these changes in action. I'd change the following sentence: "Close this message and click the Edit button to get started." to the following to do this:

Visit [your profile page] and click the [strong]Edit[/strong] button there to get started.

---> "your profile page" would be a link to the member's profile page and "Edit" would be bolded. I'm a bit worried that people will have trouble finding the Edit button, but I'll trust that they'll figure it out until we hear complaints.

Yes, I can make a link to the profile page/edit. I can't tell from your comment whether you're giving the go-ahead for implementing, or if you need further input from Chris.

Note that I'm currently showing the modal on the first load of any Commons page (at least any page on http://commons.gc.cuny.edu). Is it only supposed to be when looking at a profile page? Only on one's own profile page?

I'm glad you both brought up those points. I was working under the assumption that the modal was for your own profiles page only. If it is on the first loading of any page for a logged in user then the change in wording makes sense.

There was a suggestion as well that we haven't addressed that we add a link to the overlay in the My Profile Sub Navigation. I'm not sure it's necessary. If we did add it then it might make sense to instead have a link named something like Profile Help and take you to a page in the codex or similar with helpful information about the profiles.

When this release is over and we look at our next targets I'd like to revisit the idea of a landing page people go to after they log in. A kind of personal home page / dashboard where people could see Commons content relevant to them. Among other things I think a place like that would be a good place to put overlay messages like this and less obtrusive messages in the future.

Not sure I agree with that choice, though, as many people visit the Commons but don't visit their own profile pages during their visits. Isn't the purpose of the modal alert to draw people's attention to the changes, thus making whatever page they're on when they log in the best option?

I pose these as questions for discussion (even though we have extremely limited time) not directives. Maybe we're out of time.

I think it should appear on log in no matter where the user is. We want to draw attention to this new feature. If it's not to much trouble to change it back to the way it was (with the wording specified in comment 11), that would be great. Many thanks.

I wasn't able to replicate browser differences but this may also happen if someone has a small screen. Boone, you can change the minHeight in cacap-profiles-overlay.php to something smaller, like say 550 or 500. The default CSS they add sets the overflow:auto so scroll bars will appear if the message can't fit on the user's screen.

Chris, can you please create a new ticket for your suggestion in comment #21?