Re: [development] Getting both better internal and external APIs intoDrupal 7
Quoting Michelle Cox <mcox@charter.net>:
On 12/31/2007 7:50:22 PM, Khalid Baheyeldin (kb@2bits.com) wrote:
I tried my best to have install profiles named something else (packages, distros), but the counter argument is that it was too late to do it.
This will cause a lot of confusion in the future, unless we give profile. module the bullet of mercy in D6 and replace it with bio (or friends) for example.
It will still be confusing. I think anyone who's familiar with social networking sites will tend to associate "profile" with people, even though it does have other meanings.
A profile is nothing more than meta data for a something or a someone. A package install profile is correct. A user profile is correct. A clarifier should be used in both cases to make the meaning understood. Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
Formally, what Ernie says is correct. But we need to focus on marketing, and we need to invoke the "Don't make me think" principal if we are going to compete for the hearts and minds of the toiling millions. "package install profile" is too many modifiers. Makes me have to think. Don't want to think about what color the sky is. Want to check it out, pick and choose, and use, use, use. Can't we have more intuitive names for stuff? Victor Kane http://awebfactory.com.ar On Jan 1, 2008 7:57 PM, Earnie Boyd <earnie@users.sourceforge.net> wrote:
Quoting Michelle Cox <mcox@charter.net>:
On 12/31/2007 7:50:22 PM, Khalid Baheyeldin (kb@2bits.com) wrote:
I tried my best to have install profiles named something else
(packages,
distros), but the counter argument is that it was too late to do it.
This will cause a lot of confusion in the future, unless we give profile. module the bullet of mercy in D6 and replace it with bio (or friends) for example.
It will still be confusing. I think anyone who's familiar with social networking sites will tend to associate "profile" with people, even though it does have other meanings.
A profile is nothing more than meta data for a something or a someone. A package install profile is correct. A user profile is correct. A clarifier should be used in both cases to make the meaning understood.
Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
Quoting "blogdiva@culturekitchen.com" <blogdiva@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/
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@users.sourceforge.net> wrote:
Quoting "blogdiva@culturekitchen.com" <blogdiva@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/
Quoting Victor Kane <victorkane@gmail.com>:
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.
I click on the extensions primary menu option.
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...).
Well, we do have a start [1] at something similar. It does need to be more finely grained, the taxonomy needs work to give real meaning to the likes of "Content display (319)" for example.
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.
And we have [2] for the developer. [1] http://drupal.org/project/Modules [2] http://drupal.org/handbooks Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
On Jan 2, 2008, at 7:51 AM, Earnie Boyd wrote:
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.
Just to sound off from a usability standpoint, using "profile" for installation packages is rather confusing. Liza's point that "profile" already has legacy meaning within Drupal only emphasizes the point, imho. My own personal interpretation of profile in the web world is that of a user profile -- and given that one "web 3.0" trend is to connect all these different profiles we have everywhere, using the word "profile" to describe what really is a bundled distribution or installation package just invites more confusion. Laura • Laura Scott pingVision, LLC 303.415.2559 http://pingv.com
participants (4)
-
blogdiva＠culturekitchen.com -
Earnie Boyd -
Laura Scott -
Victor Kane