We need an alias for http://drupal.org/node/310069 so it can be linked from core.

Comments

dave reid’s picture

My suggestion from IRC is developing/api/database since it matches the book tree of "Developing for Drupal > Working with the Drupal API > Database API". Also goes along with the similar page of developing/modules.

laura s’s picture

Following Dave Reid's example, what about:

http://drupal.org/development/api/database-api ?

URLs are becoming increasingly irrelevant these days, and do not have to reflect hierarchy even if menus linking to them are hierarchical. So really the alias could be just

http://drupal.org/database-api

No need to make it longer. The context is visible in the page, and does not need to be extracted from the URL.

dave reid’s picture

I'd prefer to avoid top-level aliases however.

moshe weitzman’s picture

I like top level aliases. Less typing. URLs are free. Use em.

avpaderno’s picture

chx’s picture

To my understanding, Dave's concern is if we are not doing hierarchies then it's impossible to say whether 'database-api' is a development handbook page, a project or a handbook page about said project. This makes sense.

Re development/ or developing/ it seems development is more popular and i like it more too. I will wait a few more days then add development/api/database-api .

dave reid’s picture

Hrm this is a minor bikeshed, but I like 'developing' over 'development' since:
1. The root book page is 'Developing for Drupal'
2. We already have another alias with '/developing/modules'
3. It feels more active and involved than 'development' which implies past-tense.

</blkeshed>

chx’s picture

Status: Active » Fixed
chx’s picture

Status: Fixed » Closed (fixed)

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