Promote MicroAssist to front page

You're just near the bottom of the front page story queue, that's all. I've marked this as "Needs review"

Generally I like this write-up. My main concern is the structure of the post.

You have the section "Before Drupal" which lists 7 dotnetnuke deficiencies, then you expand on them. I'd suggest changing "Before Drupal" to a "Why Drupal" section.

A conclusion section of some sort would be nice to end with.

Also, the first pic should be a 300 X 200 50kb(ish) screenshot. If you can get it to those specs, that would be great.

I'm not sure what is required of a post to be promoted, but the accessibility section of this post isn't particularly informative. That is, there is no really useful content about accessibility in the Drupal CMS.

Note, I am not saying that the accessibility section is inaccurate, or bad, in any way. Just that it, on its own, doesn't really come across to me as containing unique and / or useful information.

We now got a new case study section: http://drupal.org/case-studies and forum posts not going to be promoted to front page anymore. You can publish a case study for your website (follow guidelines here: http://drupal.org/node/1588136) and then re-open this issue with request for it to be promoted to Featured case studies.

Case study is very detailed but it needs some work to be promoted.

Title should be much shorter - I'd suggest "MicroAssist - from DotNetNuke to Drupal".
Main screenshot should not have white spaces on the sides and shadows around it - for it to look good on the listing page and our future slideshow.

Case study text needs more detailed review, I just glanced over it.

Case study text needs more detailed review, I just glanced over it.

I'm almost done with this task.

Hi scrypt

I've had a proper read through your case study and have attached some suggestions that I think can improve its readability. Some of the suggestions are fairly 'black-and-white', others may be down to my personal writing style. Feel free to ignore those.

You provide many useful tips in this case study, making it well worth the read.

Terry

Hi Pavel

You're very welcome. Let's just say your English is better than my Belarusian, and leave it at that :)

I haven't read through it again, line by line, but one correction that stands out looks to have been introduced by me - only the first letter of Git needs to be capitalized. Apologies for my lack of clarity there.

Two other minor corrections in the 'Completed Drupal site or project URL' section:

Missing word 'us': The Drupal reconstruction enabled us to rapidly develop etc

The following sentence is a difficult one:
For example, our marketing team just asked to add feature to know where from visitor came to webform.

You could try:
For example, our marketing team just asked us to provide a method for tracking a visitor's path to our webform.

Those corrections aside, I'm very happy with all the additional work you've done on this case study.

Terry

You might want to check the spelling in the title. (You'll probably give yourself a little forehead slap when you see it.)

Would it be possible to update the copyright on the MicroAssist site to include 2012?

I think this is ready to promote to the Featured section, but would prefer if that got fixed!

+1

I've just been having a scoot around the website using Firefox, IE8 and Chrome (WinXP SP3) and found a 'broken' footer, here:

http://www.microassist.com/about-microassist/career-opportunities

There's no left sidebar content on this page, which could be related.

Two IE8-related things:
The search widget on the above page doesn't work well in IE8.
The Facebook links (wherever used) don't show up in IE8.

The IE8-related issues are by no means showstoppers, but the career opportunities page footer is certainly worth resolving.

Good (fast!) work, Pavel!

I have no further issues with the website or the case study.

It's ready for promotion so far as I can see.

It may be that we need two reviewers to give it the go ahead after all amendments have been made, Pavel, but I'm new to the team so perhaps I'm being a bit too cautious.

Lisarex gave it the thumbs up pending a change that has now been made. I've given it the thumbs up following a further fix so I'm going to change the status to RTBC and we'll see what the guvnor says :)

@scrypt - you can't RTBC (reviewed & tested by the community) your own posts. (Or any your company worked on, or you helped create, etc.) Standard Drupal policy.

And thanks for being exceptionally patient with us as we made this transition to the new Case Study content type!

scrypt, tvn and I are discussion technical aspects right now on IRC!

and promoted!

changing link to new case study