Deploy bluecheese on groups.drupal.org

Integrate improvements to comment/voting display http://groups.drupal.org/node/65763

New homepage issue: #1074224: Redesign groups homepage for authenticated users.

(Priority set to major for our upcoming sprint; all issues that will need review with the new theme.)

Postponed until #1054426: Groups.drupal.org redesign navigation is fixed, perhaps even some big wins like #1074224: Redesign groups homepage for authenticated users. or #954708: Redesign groups.drupal.org events view

Just want to chime in and say we'd like to help this issue along at a theme-related code sprint at this year's design camp in Los Angeles.

I went ahead and updated drupalorg and bluecheese to deploy http://bluecheese-groups.redesign.devdrupal.org/. I put what I've done in the deployment section of the issue summary.

I think the next big win is enabling the theme, but not making it the default, on live, to get block arrangement done. Blocks don't appreciate programatic change, so configuration on live is best.

This looks great. Is there a way to see the site as a logged-in user?

Actually, now that I look at it more, blocks do not need re-placement for now. I was thrown off by the login block. A few recommendations for configuration changes on the live site:

- Disable the login block. There is a login link in the primary navigation
- Show Working and regional Groups & Meetups and Hot content this week blocks only on the home page instead of every page
- Move the mission text to a custom block shown only on the front page. This follows a pattern like "Help Us Maintain Documentation" at http://drupal.org/documentation
- Change the site name from groups.drupal.org to Drupal Groups. The site names have been moving to "Drupal Something"

Logging in - the dev sites have had their password hashes zeroed out for privacy & security. You can log in with drush uli, I sent a URL from that to your contact form. If you can help out with site building, see http://drupal.org/node/1018084.

Cool!

Agree with drumm in #9 about disabling the login block.
"Working and regional Groups & Meetups" title doesn't make sense... can we change it back to New Groups as it is on live?

As for showing Hot Content and the group list, they should probably appear on all non-group-specific pages ... e.g. /groups would be naked without those blocks. Unless there are some other blocks that could go there instead.

If you want to test as a logged-in user, try user bacon, pass bacon.

Mmmm. Bacon.

Add deployment steps

It is great to see consistency come to gdo. Thanks for the progress here. At the same time, a dense information site like GDO really suffers with the fixed width design of bluecheese. Expand your browser wide and compare:

http://groups.drupal.org/nyc
http://bluecheese-groups.redesign.devdrupal.org/nyc

Dunno what we can really do about it but I'd like to register a complaint :)

One of the possible ways to make group look so-so ok with the new fixed layout will be to disable "show sidebar blocks", like Media group does. Though currently it still looks not so good on dev site. We will need to let group content expand on all 12 grids instead of 8, it will look like this then:

I will be going over missing/needs change styles in the next couple of days + work needs to be done to implement #1074224: Redesign groups homepage for authenticated users.. Let's please not turn Bluecheese on on the live site until we are done with that to make sure g.d.o looks really good before switch!

I've updated issue summary with the remaining tasks I came up with for now.

added latest list of tasks

some edits

added 1 more item

added lullapad link

updating status

more updates

Updated issue summary again with current progress.

Attached is archive with css file for groupsorg module and patch to add styles + changes from #1427708: Allow group's content expand on grid-12 when right sidebar is empty.

Real quick feedback on making full-width pages. I have not fully reviewed things outside of http://pastie.org/3329643.

On other parts of the site, we use <div class="grid-12 alpha omega"> in the main content area to expand it. THis doesn't come with the extra page template that mostly duplicates the one page template.

In general, I'd like to keep the CSS and other theme elements centralized as much as practical. That should help sites be consistent, including if any groups-specific elements get deployed on other sites. I might be moving some stuff out of groupsorg-styles.css for this.

some fixes

added logo link

Remember, any configuration that isn't done on the live site is not actually done. For example, "Move the mission text to a custom block shown only on the top of front page." hasn't happened on the live site.

Any configuration that won't work with the old theme needs to have clear deployment instructions in the issue summary.

added another issue

I did a bit of cleanup for the mission, bringing it more in line with http://drupal.org/ and http://localize.drupal.org/. The rounded green box didn't really fit wit th. I decided on a more "action-oriented" heading, since we don't need to restate that we are on groups.drupal.org. I added some grid classes so it doesn't take up too much vertical space. I updated the block on the live site to match, so it is ready to deploy.

I also removed a couple of the sidebar styles to keep the site consistent with Drupal.org.

The remaining work is

• Double check that we have configuration changes done on live or documented
• Clean up .activity CSS to match Bluecheese's styles. In general- vertical measurements should be in em matching up to increments of the line height, which comes out to 9px for half a line and 18px for full; horizontal sohuld match the grid system whenever practical.
• Move all CSS into Bluecheese itself.

I fixed up the overlap with votes in comments by adding overflow: hidden; to blockquote, ul, and ol. This makes those elements fit into the available width, fixing them for any time we have something to the left, like an image.

Where can I find an example of the gdo-online class being used?

#21 - Yes, the status list in the issue summary is "Progress on dev site", so by done I meant that its done on dev not live.
Lullapad (http://lullapad.com/WBjmxIlIGI) has names of views/blocks/custom pages for each configuration. I will add them to issue summary.

#22 - Mission styles applied not only to front page, but to mission statements for groups, now they have no visual prominence at all compared with the rest of group content (I am not advocating for the green box but they should have at least something).

2 columns on front page mission look great, but it needs some white space above and below.

The sidebar styles (particularly white border) I added because while on d.o sidebar rarely has multiple blocks, on g.d.o it's usually from 5 and up - they need some visual separation from one another.

#24 gdo-online is for "Currently online" block on sidebar of front page (hard to catch it on dev site as usually noone is there).

I noticed a problem between the Votes and a quote.

http://groups.drupal.org/node/213898

I actually just committed a fix for this, #1424454: Updown voting widget overlaps blockquote "quote" graphic. At some point, we will need to destroy this dev site and set up a new one with updated everything. As of right now, groups.staging.devdrupal.org has everything which has been committed.

Update deployment

updating deployment instructions

more updates

I updated deployment section of issue summary with configuration changes, I am not sure how detailed it should be. If there are any questions, I am usually available at #drupal-groups irc.

Tagging.

#19 and #20 are fixed. The only CSS additions remaining in groups_drupalorg go with the new views. We are good to go, except for those. The views must be exported to code with features anyway.

I don't think #1416764: Provide option to switch front page for logged in user is really a blocker. I'm removing it from the issue summary.

I would like to do a round of disabling non-essential blocks and double checking that configuration actually has made it to the live site. Blocks shnould always be contextually-relevant. Group pages should only have blocks specific to the group.

typo fixes

For the about page, I saw http://bluecheese-groups.redesign.devdrupal.org/about replaces http://bluecheese-groups.redesign.devdrupal.org/node/302. I don't see a good reason to do this. Since this is a post in the group, the sidebar is useful. Revisions to the content need to happen on the live site, http://groups.drupal.org/about. If we want the layout, use markup like <div class="grid-2">.

I filed #1482908: Revise about page content for the about page content. The dev site is now back to the old about page.

Remove non-blocker

About page.

about page

Crossing out finished theme changes.

I crossed out a bit in the issue summary to mark things a truly done.

Is there a page to try out "fix nested taxonomy lists not having margins" on?

Has anyone other than tvn looked at the new home page and other view changes, like replacing http://groups.drupal.org/unread?

#33 The point was for About page not to be post in a group, but to replace it with static page. It was discussed at #1054426: Groups.drupal.org redesign navigation. I simply took current About post content and put it on a new page. I do not think it needs any sidebar. I used custom page with panes instead of usual node type page just to show how it would ideally look like, without "posted by ..." and author userpic.

#35 You can see such a list at http://groups.drupal.org/australia - Location list at sidebar.

I committed a fix for "fix nested taxonomy lists not having margins" to Bluecheese, making the margin rule less specific.

cross out more

Fixed that

Already done

Blocks are arranged enough.

I think this is ready enough to deploy. #1074224: Redesign groups homepage for authenticated users., #1484712: Whitespace between header and main content should be added consistently, and other followups don't need to block this.

YESSSSSS

What are the necessary steps for reducing the sidebar width so that the sidebar isn't so gargantuan on groups.drupal.org?

Re: #15, I don't think that asking every group and group organizer to disable the blocks in the sidebar is going to be easy — and IMHO, the wonkingly huge sidebars will reflect badly on groups.drupal.org in general.

christefano - that would be a separate issue. All Drupal.org sidebars are a standard width. For Groups, we could slim down the sidebar a bit more, such as removing "Hot content this week" when the main pages have this info, #1074224: Redesign groups homepage for authenticated users.. #951114: Support all screen sizes should help out too.

Deployed this round of work.

The dev site is quite messy now. I believe everything for followup issues is saved on Drupal.org, so I'll be destroying it and making a new one.

Cross-linking request to bring "My groups" block back on group pages #1504510: Restore the "my groups" block on g.d.o

Also seems "fix nested taxonomy lists not having margins" have not been deployed? (No margins on http://groups.drupal.org/australia still for example)

For nested taxonomy lists - we hadn't cleared the css/js cache, which is done now.