Posted by jazzdrive3 on September 2, 2010 at 3:38pm
| Project: | Drupal.org webmasters |
| Component: | Front page promotion |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I'd like to request that my Drupal showcase post about the WikiWeightWatcher.com upgrade and redesign be promoted.
It seems highly relevant given the release of Drupal 7 coming up, and therefore Drupal 5 not being supported. It also highlights several ways that certain modules can be used.
It even includes the buzzword "iPhone!"
The images for it are attached.
| Attachment | Size |
|---|---|
| wiki-home-old.png | 203.2 KB |
| wiki-rest-old.png | 180.34 KB |
| wiki-front-new.jpg | 59.88 KB |
| wiki-rest-new.jpg | 54.53 KB |
| wiki-user-new.jpg | 33.95 KB |
Comments
#1
Just double checking on this. Thanks.
#2
I'm a -1 on this.
The ads on the site are a huge turnoff to me.
The footer section is really empty.
Does Weight Watchers itself endorse this site and allow you to use their name?
Even if this doesn't make it to the front page, can you explain how you made a page like this?
And the first 2 images link here are too large - they should be about the same size as the others (30-50 kbs or so)
#3
We're not using their name. Splitting hairs, I know, but what we are using (singular form) is not trademarked by them, and especially not the full name wikiweightwatcher.com.
We can remove the ads for a time if required. Although they are pretty much a staple of the internet. Most sophisticated browsers, like those from Drupal.org, probably suffer from extreme banner blindess anyway. ;)
Which part of the page are you talking about? The fundamentals are explained in the case study.
Thanks.
#4
I think the other two points made from silverwing are valid.
#5
Oh yeah. Sorry, forgot to re-size them. My mind is a little addled lately due to the birth of our first daughter earlier this week. Dealing with the joyous windfall that it entails ;)
New ones attached and I've edited the case study to point to the new images.
Also added some more useful content to the footer.
I had to change a bit of the CSS, so be sure to clear your cache.
Thanks!
#6
Actually, forgot to convert them to jpeg to lower the size. Here are the new images attached, and again I have edited the case study to reflect the new names.
Thanks!
#7
I've made some minor tweaks to the text, uploaded, and enabled the optimized images (the first home page got some additional tweaking as it was larger than what we typically display in teasers.
I'd like to see some other site maintainers weigh on whether they think this case study should be promoted to the home page; my biggest concern is that many of the screenshots are full of third-party ads. Ideally, case study screenshots should be used to illustrate the site's functionality, and these ads are so prominent that they distract readers from anything else.
It also seems like this promotion might be a little premature. The case study indicates that the original site was experiencing growing pains under Drupal 5, and I'd like to hear more about how updating to Drupal 6 solved those problems, particularly in regard to performance.
#8
I agree with gdemet; I would like to read how Drupal 6 resolved the problems that were present on the site with Drupal 5.
#9
Ok. I'll redo the image without so many ads, and see if I can add a few more details. Thanks.
#10
Attached are new images. I can't edit the case study anymore, but you should be able to change them accordingly.
Also, please change the following text "First on the agenda: moving from Drupal 5 to Drupal 6. With the inevitable release of Drupal 7 on the horizon, it was simply time to stop putting it off."
To this:
First on the agenda: moving from Drupal 5 to Drupal 6. With the inevitable release of Drupal 7 on the horizon, it was simply time to stop putting it off. It's not that Drupal 5 stumbled or didn't meet our needs. It met our current needs perfectly. But our needs were not going to remain stagnant. So we upgraded for two main reasons:
1. PropDrop has worked exclusively in Drupal 6 for over a year, and our Drupal 5 skillset (theming, module development, etc) was getting a bit rusty. For both maintenance and additional feature development, upgrading made the most sense. We also gained access to the more advanced Drupal 6 versions of certain modules, like Views 2.
2. Drupal 5 will stop being supported with security and bug fix releases after the release of Drupal 7, which, as far as we know, is probably being released this year. We didn't want to be caught with our pants down.
#11
Also, the iPhone app was just approved today, so that little bit can be updated to reflect this new information as well. Good promo for Drupal Services.
http://itunes.apple.com/us/app/wikiweight/id389590293?mt=8
#12
I will give my +1 if 2 things are added to the case study:
1) More info on the developers involved, what kind of experience do they have, who developed the iPhone integration. This will allow future developers to understand how hard it is to integrate iPhone apps with a Drupal site.
2) More details on how the integration between the iPhone app and the Drupal work. This is a unique scenario and I am sure that a lot of people would like to learn how this can be done.
Thanks,
Arnold
#13
Makes sense to me; I've changed the input format back to Filtered to enable the author to make these changes and am marking this issue "Needs work".
#14
Alright. Changes have been made, and I expounded much more on the iPhone applciation integration with services.
Thanks!
#15
Images re-enabled, moving back to "Needs review".
#16
The showcase seems fine to me; the part about the iPhone application has been added, as requested.
#17
Excellent. Thanks for everyone's help. Just let me know when you want to schedule it.
Thanks!
#18
Any updates on this? Thanks!
#19
Home page image resized, this is now RTBC
#20
Promoted.
#21
Automatically closed -- issue fixed for 2 weeks with no activity.