The Events handbook (http://drupal.org/events) is totally undiscoverable since it is a standalone book, but it has very useful *documentation* about oraganizing events in it (http://drupal.org/node/247945). Should we move the whole book, or at least the organizing docs, under another book, like Getting Involved, so that people might actually find it? As we organize more sprints, we need to have docs to help people pull things together and make them at least remotely more findable than they now are. I could just do it, but I want to know what other people think, or if there is a better place for this info, before I go yanking things around.

Comments

vm’s picture

Status: Active » Fixed

Looking into this shows a link that has been added to the sibebar pointing to /events on http://drupal.org/node/572830

Is this suffice?

vm’s picture

Status: Fixed » Active

changing status back. sorry.

avpaderno’s picture

Should we move the whole book, or at least the organizing docs, under another book, like Getting Involved, so that people might actually find it?

I think that moving it to Getting Involved could be a good idea. If somebody else can think of a better book, please report it.

lisarex’s picture

This can be marked as fixed, as we came to the same conclusion in #929084: Some Handbooks are "Documentation" and some are information (to the outside world) and I've only just seen this.

That said, the Events book needs some thought. For the Redesign, we link to groups.drupal.org/events so this is more of an events archive than anything. In 2010, there's only San Francisco listed. I think we could do a flatter structure here with links to the event sites.

silverwing’s picture

Project: Drupal.org site moderators » Documentation
Component: Site organization » Placement and navigation

Moving to Documentation and letting lisarex decide if this is now fixed.

arianek’s picture

Status: Active » Fixed

Looks like this was moved to Getting Involved. Marking fixed.

Status: Fixed » Closed (fixed)

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