[development] Getting both better internal and external APIs intoDrupal 7

[Victor Kane]

Just want to put to the attention and consideration of all the following.

I am someone looking for a CMS.

I go to the joomla page.

http://www.joomla.org/

I click on the extensions primary menu option.

http://extensions.joomla.org/

I don't need to spend a jolt-cola sip in order to know what "module" means
or to know what "profile... meta..." means.

I see "extensions".

Some of them are "core enhancements", some of them are "admin tools", some
of them are "e-Commerce", and, hey, ... some of them are "vertical markets"
(auto & vehicles, education...).

ok!

Now if I were a developer, I would go to the developer primary menu option
and take a look at stuff like the Framework Overview, and Framework API,
where I learn with interest that ... ooh, a nice little diagram that shows
me Components, modules, templates, on one tier, and the application tier and
the framework tier, and since I am a developer I ... care.

saludos,

Victor Kane
http://awebfactory.com.ar

the KISS we need.

Victor Kane
http://awebfactory.com.ar


On Jan 2, 2008 12:51 PM, Earnie Boyd <earnie at users.sourceforge.net> wrote:

> Quoting "blogdiva at culturekitchen.com" <blogdiva at culturekitchen.com>:
>
> > On  01.Jan.2008, at 06:16 PM, Victor Kane wrote:
> >
> >> But we need to focus on marketing
> >
> > Before we even speak of marketing, we need to think in terms of
> > usability first and foremost.
>
> I am remembering my searching for CMS software and Drupal (4.7.x at the
> time) was the easiest for me to use.  Let's not get hung up on terms
> and make sure the documentation to explain the terms we use are in
> place.  If we denote properly so that we can avoid the wrong connote
> then we can use the more general term profile for different objects.
> Kind of like using node for more than one object which makes sense in
> terms of expandability as has been described recently but for those
> using Drupal a while and not involved with development might be a bit
> confusing due to the connotation already ingrained.
>
> Profile: Meta data that describes different objects within Drupal.
> 1) User profile - Meta data about a user such as birth date, email
> address, etc.
> 2) Package profile - Meta data describing the default look and feel of
> a Drupal installation such as a blog profile, forum profile, etc.
>
> Earnie -- http://for-my-kids.com/
> -- http://give-me-an-offer.com/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20080102/0ad57195/attachment.htm