It looks like someone had added this story about the new book "Drupal 6 Content Administration" to the home page schedule, but not created a webmaster issue for it. Since I think it is a story worthy of home page promotion, I'm creating an issue now, and I've also edited the post to add an image of the book and correct one minor typo. I am also directly contacting the author of the post to make sure he has no objection to this getting promoted at some point in the next couple of weeks.

Comments

gdemet’s picture

The author has approved this post for home page promotion, so it's ready to go pending at least one more "+1" from another member of the webmaster's team.

vm’s picture

Status: Active » Postponed (maintainer needs more info)

the author of the page should be contacted and chime in here at this point.

gdemet’s picture

Status: Postponed (maintainer needs more info) » Active

Sorry, I wasn't clear in my previous post: I contacted bithead, the author of the post (and the book) directly via email and asked if he was okay with it being promoted to the home page. His reply was:

That's great news!
...
At this point there aren't any needed changes that come to mind, other than the cover photo that you'll be putting in place. I'm very excited about the book, because it seems that the non-developer types represent a large percentage of the people coming to #drupal-support, completely lost as to what to do with the new Drupal site they've acquired. I think this will be a help for them.

The cover photo has been added, and IMO this post is ready for promotion, pending review by another maintainer and placement on the calendar.

avpaderno’s picture

Title: Promote "New Drupal Book - Drupal 6 Content Administration" story to home page » Promote "New Drupal Book - Drupal 6 Content Administration" to home page

It seems fine, to me. I don't see any reasons to not promote it to front page.

gdemet’s picture

Assigned: Unassigned » gdemet
Status: Active » Fixed

Promoted.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.