|
»
»
»
Tag clouds and documentation
|
View:
New views
13 Messages
—
Rating Filter:
Alert me
|
 |
Tag clouds and documentation
by Lee Hunter
::
Rate this Message:
John Forsythe of Blamcast has recently blogged this nice tag cloud
showing the top search terms on Drupal.org for the past month http://blamcast.net/articles/top-drupal-search-terms http://blamcast.net/files/drupal-search-terms-cloud.html Wouldn't it be great if the documentation page had a similar tag cloud and each of those terms was a link to ALL the related documentation for that term? In other words, if you clicked "image" you'd see a page that has links to every piece of image-related documentation, regardless of whether it happened to be filed (i.e. hidden) under module documentation, how-to, theming, FAQ, video, developer documentation etc. No more wild goose chases checking whether there's something on images in the how-tos, or the FAQs, or the videos, or the troubleshooting etc etc etc. To me, that would be heaven. Lee Hunter Technical Editor -- Pending work: http://drupal.org/project/issues/documentation/ List archives: http://lists.drupal.org/pipermail/documentation/ |
|
|
Re: Tag clouds and documentation
by Steven Peck-2
::
Rate this Message:
His analysis is NOT of drupal.org search terms, but of his own personal sites.
On Mon, Sep 8, 2008 at 6:14 AM, Lee Hunter <lee.hunter@...> wrote: > John Forsythe of Blamcast has recently blogged this nice tag cloud > showing the top search terms on Drupal.org for the past month > > http://blamcast.net/articles/top-drupal-search-terms > http://blamcast.net/files/drupal-search-terms-cloud.html > > Wouldn't it be great if the documentation page had a similar tag cloud > and each of those terms was a link to ALL the related documentation > for that term? In other words, if you clicked "image" you'd see a page > that has links to every piece of image-related documentation, > regardless of whether it happened to be filed (i.e. hidden) under > module documentation, how-to, theming, FAQ, video, developer > documentation etc. > > No more wild goose chases checking whether there's something on images > in the how-tos, or the FAQs, or the videos, or the troubleshooting etc > etc etc. > > To me, that would be heaven. > > Lee Hunter > Technical Editor > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > Pending work: http://drupal.org/project/issues/documentation/ List archives: http://lists.drupal.org/pipermail/documentation/ |
|
|
Re: Tag clouds and documentation
by Lee Hunter
::
Rate this Message:
Sorry, you're quite right, the cloud is from his sites..
However, it doesn't change the point of my message. The organization of the documentation is seriously fractured and a tag cloud of drupal.org searches (whatever that might be) would help a lot to bring things together. Lee Hunter Technical Editor On Mon, Sep 8, 2008 at 12:24 PM, Steven Peck <sepeck@...> wrote: > His analysis is NOT of drupal.org search terms, but of his own personal sites. > > On Mon, Sep 8, 2008 at 6:14 AM, Lee Hunter <lee.hunter@...> wrote: >> John Forsythe of Blamcast has recently blogged this nice tag cloud >> showing the top search terms on Drupal.org for the past month >> >> http://blamcast.net/articles/top-drupal-search-terms >> http://blamcast.net/files/drupal-search-terms-cloud.html >> >> Wouldn't it be great if the documentation page had a similar tag cloud >> and each of those terms was a link to ALL the related documentation >> for that term? In other words, if you clicked "image" you'd see a page >> that has links to every piece of image-related documentation, >> regardless of whether it happened to be filed (i.e. hidden) under >> module documentation, how-to, theming, FAQ, video, developer >> documentation etc. >> >> No more wild goose chases checking whether there's something on images >> in the how-tos, or the FAQs, or the videos, or the troubleshooting etc >> etc etc. >> >> To me, that would be heaven. >> >> Lee Hunter >> Technical Editor >> -- >> Pending work: http://drupal.org/project/issues/documentation/ >> List archives: http://lists.drupal.org/pipermail/documentation/ >> > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > Pending work: http://drupal.org/project/issues/documentation/ List archives: http://lists.drupal.org/pipermail/documentation/ |
|
|
Re: Tag clouds and documentation
by Tony Narlock
::
Rate this Message:
Lee Hunter wrote:
> Sorry, you're quite right, the cloud is from his sites.. > > However, it doesn't change the point of my message. The organization > of the documentation is seriously fractured and a tag cloud of > drupal.org searches (whatever that might be) would help a lot to bring > things together. > > Lee Hunter > Technical Editor > > On Mon, Sep 8, 2008 at 12:24 PM, Steven Peck <sepeck@...> wrote: > >> His analysis is NOT of drupal.org search terms, but of his own personal sites. >> >> On Mon, Sep 8, 2008 at 6:14 AM, Lee Hunter <lee.hunter@...> wrote: >> >>> John Forsythe of Blamcast has recently blogged this nice tag cloud >>> showing the top search terms on Drupal.org for the past month >>> >>> http://blamcast.net/articles/top-drupal-search-terms >>> http://blamcast.net/files/drupal-search-terms-cloud.html >>> >>> Wouldn't it be great if the documentation page had a similar tag cloud >>> and each of those terms was a link to ALL the related documentation >>> for that term? In other words, if you clicked "image" you'd see a page >>> that has links to every piece of image-related documentation, >>> regardless of whether it happened to be filed (i.e. hidden) under >>> module documentation, how-to, theming, FAQ, video, developer >>> documentation etc. >>> >>> No more wild goose chases checking whether there's something on images >>> in the how-tos, or the FAQs, or the videos, or the troubleshooting etc >>> etc etc. >>> >>> To me, that would be heaven. >>> >>> Lee Hunter >>> Technical Editor >>> -- >>> Pending work: http://drupal.org/project/issues/documentation/ >>> List archives: http://lists.drupal.org/pipermail/documentation/ >>> >>> >> -- >> Pending work: http://drupal.org/project/issues/documentation/ >> List archives: http://lists.drupal.org/pipermail/documentation/ >> >> > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > If there is something that we can do to help people get the documentation they want quicker, by all means. When designing sites, we have things like the "3 click rule". The handbook gives us a hierarchy, with stuff like tags, they can click on "handbook" and see a tag cloud on the top. It we can do it to make it look professional, it doesn't need to be big, just to give a quick link to the most common stuff. See an example here: http://bakery.cakephp.org/ If you take some time to think about what people who are looking for info on... Sometimes they may need a tag to "spark" a particular search word they may other wise not be thinking of. There are cases where you don't want tags+tag clouds, and cases where you do -- this may be a case where it's advantageous. Hope this helps Tony -- Pending work: http://drupal.org/project/issues/documentation/ List archives: http://lists.drupal.org/pipermail/documentation/ |
|
|
Re: Tag clouds and documentation
by Lee Hunter
::
Rate this Message:
That's an excellent example, Tony.
I would imagine that the topic of connecting with databases would be one of the most popular subjects on a PHP framework site and, sure enough, "database" is the largest item in the CakePHP cloud. When I click on "database" I get all the relevant tagged articles. Contrast that with the user experience on Drupal.org. Searching for even the most common topics means that I have to either do a search (which is messy and unreliable) or I make a series of attempts to crawl down some obliquely-labeled rabbit holes (FAQ, How-to, etc.) that lead me into a maze of unhelpful subheadings until I finally stumble across enough information to satisfy my need (although I'll never know whether or not I've found everything on the subject) or I just collapse in exhaustion. :) Lee Hunter Technical Editor On Mon, Sep 8, 2008 at 12:55 PM, Tony Narlock <skiquel@...> wrote: > See an example here: http://bakery.cakephp.org/ -- Pending work: http://drupal.org/project/issues/documentation/ List archives: http://lists.drupal.org/pipermail/documentation/ |
|
|
Re: Tag clouds and documentation
by Steven Peck-2
::
Rate this Message:
Other than saying 'tags will help' do you have a better hierarchy suggestion?
My experience with tags in general on many other sites has been that they also pollute search results into rabbit warrens of unrelated pages. I am not against tags, just not seeing them as a magic bullet currently. I am loathe to just 'tack things on' while we have a redesign project starting up. On Mon, Sep 8, 2008 at 10:13 AM, Lee Hunter <lee.hunter@...> wrote: > That's an excellent example, Tony. > > I would imagine that the topic of connecting with databases would be > one of the most popular subjects on a PHP framework site and, sure > enough, "database" is the largest item in the CakePHP cloud. When I > click on "database" I get all the relevant tagged articles. > > Contrast that with the user experience on Drupal.org. Searching for > even the most common topics means that I have to either do a search > (which is messy and unreliable) or I make a series of attempts to > crawl down some obliquely-labeled rabbit holes (FAQ, How-to, etc.) > that lead me into a maze of unhelpful subheadings until I finally > stumble across enough information to satisfy my need (although I'll > never know whether or not I've found everything on the subject) or I > just collapse in exhaustion. > > :) > > Lee Hunter > Technical Editor > > > On Mon, Sep 8, 2008 at 12:55 PM, Tony Narlock <skiquel@...> wrote: > >> See an example here: http://bakery.cakephp.org/ > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > Pending work: http://drupal.org/project/issues/documentation/ List archives: http://lists.drupal.org/pipermail/documentation/ |
|
|
Re: Tag clouds and documentation
by Lee Hunter
::
Rate this Message:
I don't think there's any way it could be worse than the utterly
inscrutable architecture we have now. :) Using the Cake example, one click gets you all the database articles. On the current Drupal.org you would probably have to click *hundreds* of times (quite literally) before you rounded up everything on databases (and personally I'd get lost and give up long before I got there). The Cake example, does show one of the limitations in that you might get an overwhelming number of results, however this is still preferable to not even knowing where to start. To solve the issue of too many results, one approach I really like is the guided search or faceted search, which is used on quite a few large and complex sites. In fact, there's a module here: http://drupal.org/project/faceted_search Faceted search has several advantages, one of which is that you can see at a glance how your search could be broadened or narrowed by choosing from a list of options. Using the "database" example, there might well be too many results to be useful, but the faceted search would allow me to easily narrow it down by clicking on the "facets" or related tags (and I'd also see how many articles can be found in each related tag). Re. the redesign project, that's one reason I'm raising this issue again now, because I think it would be just tragic if the current non-architecture gets baked into the redesign. To my mind, the total lack of navigability in the documentation is by far the most pressing problem with Drupal.org. A while back, I'd actually proposed an alternative architecture for the documentation (http://drupal.org/node/199388) but I'm now thinking that some kind of organic tagging scheme would work better for this kind of site. Lee Hunter Technical Editor On Mon, Sep 8, 2008 at 1:37 PM, Steven Peck <sepeck@...> wrote: > Other than saying 'tags will help' do you have a better hierarchy suggestion? > > My experience with tags in general on many other sites has been that > they also pollute search results into rabbit warrens of unrelated > pages. I am not against tags, just not seeing them as a magic bullet > currently. I am loathe to just 'tack things on' while we have a > redesign project starting up. -- Pending work: http://drupal.org/project/issues/documentation/ List archives: http://lists.drupal.org/pipermail/documentation/ |
|
|
Re: Tag clouds and documentation
by Addison Berry-2
::
Rate this Message:
Yep, I agree that the way the docs are organized/categorized/found
needs to change in the redesign. I'd love a flexible way for people to get to the docs they need in different ways. This is a major thing that I want us to work with Mark Boulton Design (MBD) on. I am gathering together a list of features/dream requests with regards to docs and hope to post a mail to this list by the end of the week so we can be a bit organized about brainstorming, prioritizing and giving feedback to MBD. I'm so frickin excited we have not just design, but actual IA and UX work going into the redesign. Faceted search is awesome stuff as well and I dare say that is something that the redesign search team will be looking at. Their first hurdle is to figure out how to have robust search across multiple drupal.org sites and I have no idea where something like faceted search is on their radar. Would be awesome if it makes it into the redesign, but I'll leave that to those experts. Doesn't hurt to say that docs team thinks it would be neat-o-keen, though. :-) - Addi On Sep 8, 2008, at 1:58 PM, Lee Hunter wrote: > I don't think there's any way it could be worse than the utterly > inscrutable architecture we have now. > > :) > > Using the Cake example, one click gets you all the database articles. > On the current Drupal.org you would probably have to click *hundreds* > of times (quite literally) before you rounded up everything on > databases (and personally I'd get lost and give up long before I got > there). > > The Cake example, does show one of the limitations in that you might > get an overwhelming number of results, however this is still > preferable to not even knowing where to start. > > To solve the issue of too many results, one approach I really like is > the guided search or faceted search, which is used on quite a few > large and complex sites. In fact, there's a module here: > > http://drupal.org/project/faceted_search > > Faceted search has several advantages, one of which is that you can > see at a glance how your search could be broadened or narrowed by > choosing from a list of options. Using the "database" example, there > might well be too many results to be useful, but the faceted search > would allow me to easily narrow it down by clicking on the "facets" or > related tags (and I'd also see how many articles can be found in each > related tag). > > Re. the redesign project, that's one reason I'm raising this issue > again now, because I think it would be just tragic if the current > non-architecture gets baked into the redesign. To my mind, the total > lack of navigability in the documentation is by far the most pressing > problem with Drupal.org. > > A while back, I'd actually proposed an alternative architecture for > the documentation (http://drupal.org/node/199388) but I'm now thinking > that some kind of organic tagging scheme would work better for this > kind of site. > > Lee Hunter > Technical Editor > > > On Mon, Sep 8, 2008 at 1:37 PM, Steven Peck <sepeck@...> wrote: >> Other than saying 'tags will help' do you have a better hierarchy >> suggestion? >> >> My experience with tags in general on many other sites has been that >> they also pollute search results into rabbit warrens of unrelated >> pages. I am not against tags, just not seeing them as a magic bullet >> currently. I am loathe to just 'tack things on' while we have a >> redesign project starting up. > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ -- Pending work: http://drupal.org/project/issues/documentation/ List archives: http://lists.drupal.org/pipermail/documentation/ |
|
|
Re: Tag clouds and documentation
by Alan Palazzolo
::
Rate this Message:
My two cents on this. I would propose two structures in unison.
1) Formal tagging hierarchal structure, specific categories 2) Free tagging This allows for both ways of finding information. It creates a structure that is necessary for such a large amount of information while also giving opportunity for organic growth. -- Alan http://alanpalazzolo.com/ On 9/8/08 1:23 PM, Addison Berry wrote: > Yep, I agree that the way the docs are organized/categorized/found > needs to change in the redesign. I'd love a flexible way for people to > get to the docs they need in different ways. This is a major thing > that I want us to work with Mark Boulton Design (MBD) on. I am > gathering together a list of features/dream requests with regards to > docs and hope to post a mail to this list by the end of the week so we > can be a bit organized about brainstorming, prioritizing and giving > feedback to MBD. I'm so frickin excited we have not just design, but > actual IA and UX work going into the redesign. > > Faceted search is awesome stuff as well and I dare say that is > something that the redesign search team will be looking at. Their > first hurdle is to figure out how to have robust search across > multiple drupal.org sites and I have no idea where something like > faceted search is on their radar. Would be awesome if it makes it into > the redesign, but I'll leave that to those experts. Doesn't hurt to > say that docs team thinks it would be neat-o-keen, though. :-) > > - Addi > > On Sep 8, 2008, at 1:58 PM, Lee Hunter wrote: > >> I don't think there's any way it could be worse than the utterly >> inscrutable architecture we have now. >> >> :) >> >> Using the Cake example, one click gets you all the database articles. >> On the current Drupal.org you would probably have to click *hundreds* >> of times (quite literally) before you rounded up everything on >> databases (and personally I'd get lost and give up long before I got >> there). >> >> The Cake example, does show one of the limitations in that you might >> get an overwhelming number of results, however this is still >> preferable to not even knowing where to start. >> >> To solve the issue of too many results, one approach I really like is >> the guided search or faceted search, which is used on quite a few >> large and complex sites. In fact, there's a module here: >> >> http://drupal.org/project/faceted_search >> >> Faceted search has several advantages, one of which is that you can >> see at a glance how your search could be broadened or narrowed by >> choosing from a list of options. Using the "database" example, there >> might well be too many results to be useful, but the faceted search >> would allow me to easily narrow it down by clicking on the "facets" or >> related tags (and I'd also see how many articles can be found in each >> related tag). >> >> Re. the redesign project, that's one reason I'm raising this issue >> again now, because I think it would be just tragic if the current >> non-architecture gets baked into the redesign. To my mind, the total >> lack of navigability in the documentation is by far the most pressing >> problem with Drupal.org. >> >> A while back, I'd actually proposed an alternative architecture for >> the documentation (http://drupal.org/node/199388) but I'm now thinking >> that some kind of organic tagging scheme would work better for this >> kind of site. >> >> Lee Hunter >> Technical Editor >> >> >> On Mon, Sep 8, 2008 at 1:37 PM, Steven Peck <sepeck@...> wrote: >>> Other than saying 'tags will help' do you have a better hierarchy >>> suggestion? >>> >>> My experience with tags in general on many other sites has been that >>> they also pollute search results into rabbit warrens of unrelated >>> pages. I am not against tags, just not seeing them as a magic bullet >>> currently. I am loathe to just 'tack things on' while we have a >>> redesign project starting up. >> -- >> Pending work: http://drupal.org/project/issues/documentation/ >> List archives: http://lists.drupal.org/pipermail/documentation/ > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ Pending work: http://drupal.org/project/issues/documentation/ List archives: http://lists.drupal.org/pipermail/documentation/ |
|
|
Re: Tag clouds and documentation
by Patrick Teglia-2
::
Rate this Message:
I, for one, am hoping that faceted_search shows up in the redesign.
I have worked with it, and would say that it is, by far, the best way I have seen to search through copious amount of content. I am uncertain how it performs however, and I am sure that will be a concern. Also, can not Robert Douglass' Apache Solr integration work with faceted_search, giving a fairly powerful overall search? Another thing to keep in mind is that faceted_search works WITH taxonomy terms, so a mix of being able to free-tag something, and use a faceted search to retrieve it could be pretty useful. Thanks, Patrick Teglia CrashTest_ On Mon, Sep 8, 2008 at 12:47 PM, Alan Palazzolo <me@...> wrote: My two cents on this. I would propose two structures in unison. -- Pending work: http://drupal.org/project/issues/documentation/ List archives: http://lists.drupal.org/pipermail/documentation/ |
|
|
Re: Tag clouds and documentation
by christopher calicott
::
Rate this Message:
The thing about tags' effectiveness and search, the way I am seeing
it, is that it is all tied into how well thought-out and structured your taxonomy/IA is. I'm starting work currently on an interactive travel directory site that is essentially based on the taxonomy system in Drupal. For the primary way someone navigates through a site, tags or taxonomy /can/ be a more usable experience for people. Rather than the decade+ old-school way of drilling down into a site, provided your admins understand how to effectively tag new bits of content, users can do what I refer to as "noodling" through a site, where every page they land upon is somewhere they want to be, rather than a single step on the path to arriving where they are trying to go. Free tagging can absolutely kill usability and search results, like you say. I want to be able to give users the ability to tag things and augment the meta information of pages, but I'm thinking the best way to handle this is a balanced or weighted system that measures our site editors' structured descriptions strongly, and then tempers the weight of free tagging, whether done by users or our editors. We don't want to give users' "votes" any less value, so they are weighted the same as editors' votes in the free tagging, but all of the votes are then given a lesser weight with regards to the structured taxonomy for each page that they are initially put into, because tags usually get played fast and loose, and aren't meant to be completely authoritative. Now, this is obviously the documentation list.. I just kind of joined in the discussion here, which feels slightly off-topic, except that I think Taxonomy is something that needs a lot more than simple documentation... Itneeds more of the ideas behind it and documentation of "approaches" and things... I tend to just be silent on the list because Documentation discussion at DrupalCon Boston seemed, frankly, a little "we don't do things that way around here..." and it sucks making helpful suggestions and getting shot down, so I just keep fairly quiet and edit bad grammar, et cetera, occasionally. I really would like to see people like me having a much more clear path to doing bigger edits and additions to documentation, without fear of reprisal. Having said that, if anyone has a place in mind to include some ideas/additions on this topic, please let me know and I'll get on it this week. have a good day, -=- christopher On Sep 8, 2008, at 10:37 AM, Steven Peck wrote: > Other than saying 'tags will help' do you have a better hierarchy > suggestion? > > My experience with tags in general on many other sites has been that > they also pollute search results into rabbit warrens of unrelated > pages. I am not against tags, just not seeing them as a magic bullet > currently. I am loathe to just 'tack things on' while we have a > redesign project starting up. > > On Mon, Sep 8, 2008 at 10:13 AM, Lee Hunter <lee.hunter@...> > wrote: >> That's an excellent example, Tony. >> >> I would imagine that the topic of connecting with databases would be >> one of the most popular subjects on a PHP framework site and, sure >> enough, "database" is the largest item in the CakePHP cloud. When I >> click on "database" I get all the relevant tagged articles. >> >> Contrast that with the user experience on Drupal.org. Searching for >> even the most common topics means that I have to either do a search >> (which is messy and unreliable) or I make a series of attempts to >> crawl down some obliquely-labeled rabbit holes (FAQ, How-to, etc.) >> that lead me into a maze of unhelpful subheadings until I finally >> stumble across enough information to satisfy my need (although I'll >> never know whether or not I've found everything on the subject) or I >> just collapse in exhaustion. >> >> :) >> >> Lee Hunter >> Technical Editor >> >> >> On Mon, Sep 8, 2008 at 12:55 PM, Tony Narlock <skiquel@...> >> wrote: >> >>> See an example here: http://bakery.cakephp.org/ >> -- >> Pending work: http://drupal.org/project/issues/documentation/ >> List archives: http://lists.drupal.org/pipermail/documentation/ >> > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ -- Pending work: http://drupal.org/project/issues/documentation/ List archives: http://lists.drupal.org/pipermail/documentation/ |
|
|
Re: Tag clouds and documentation
by Lee Hunter
::
Rate this Message:
I hear what you're saying about free-tagging and the risk of things
degenerating into a meaningless soup. I think the solution might be to allow free tagging but not have the tags cast in stone. As I mentioned recently on another thread, I think this is where Wikipedia got it exactly right. Anyone can add a "category" (effectively free tagging) but editors are encouraged to aggressively refactor and reword those tags wherever it makes sense. Also a page can appear in multiple hierarchies (you can discover Ronald Reagan by navigating through movie stars, shooting survivors, politicians etc.) That way, you get the world view of the individual user, which is often surprising, idiosyncratic and useful (e.g. when they propose something like "survivors of shootings") and you get the collective wisdom of the other editors that say "Great idea, but let's make the category 'shooting survivors' not 'survivors of shootings' and let's make that a sub-category of "shooting victims". Lee Hunter Technical Editor On Mon, Sep 8, 2008 at 5:00 PM, christopher calicott <purrin@...> wrote: > The thing about tags' effectiveness and search, the way I am seeing > it, is that it is all tied into how well thought-out and structured > your taxonomy/IA is. I'm starting work currently on an interactive > travel directory site that is essentially based on the taxonomy system > in Drupal. For the primary way someone navigates through a site, > tags or taxonomy /can/ be a more usable experience for people. > Rather than the decade+ old-school way of drilling down into a site, > provided your admins understand how to effectively tag new bits of > content, users can do what I refer to as "noodling" through a site, > where every page they land upon is somewhere they want to be, rather > than a single step on the path to arriving where they are trying to go. > > Free tagging can absolutely kill usability and search results, like > you say. I want to be able to give users the ability to tag things > and augment the meta information of pages, but I'm thinking the best > way to handle this is a balanced or weighted system that measures our > site editors' structured descriptions strongly, and then tempers the > weight of free tagging, whether done by users or our editors. We > don't want to give users' "votes" any less value, so they are weighted > the same as editors' votes in the free tagging, but all of the votes > are then given a lesser weight with regards to the structured taxonomy > for each page that they are initially put into, because tags usually > get played fast and loose, and aren't meant to be completely > authoritative. > > Now, this is obviously the documentation list.. I just kind of joined > in the discussion here, which feels slightly off-topic, except that I > think Taxonomy is something that needs a lot more than simple > documentation... Itneeds more of the ideas behind it and > documentation of "approaches" and things... > > I tend to just be silent on the list because Documentation discussion > at DrupalCon Boston seemed, frankly, a little "we don't do things that > way around here..." and it sucks making helpful suggestions and > getting shot down, so I just keep fairly quiet and edit bad grammar, > et cetera, occasionally. I really would like to see people like me > having a much more clear path to doing bigger edits and additions to > documentation, without fear of reprisal. Having said that, if anyone > has a place in mind to include some ideas/additions on this topic, > please let me know and I'll get on it this week. > > have a good day, > -=- christopher > > > > > > On Sep 8, 2008, at 10:37 AM, Steven Peck wrote: > >> Other than saying 'tags will help' do you have a better hierarchy >> suggestion? >> >> My experience with tags in general on many other sites has been that >> they also pollute search results into rabbit warrens of unrelated >> pages. I am not against tags, just not seeing them as a magic bullet >> currently. I am loathe to just 'tack things on' while we have a >> redesign project starting up. >> >> On Mon, Sep 8, 2008 at 10:13 AM, Lee Hunter <lee.hunter@...> >> wrote: >>> That's an excellent example, Tony. >>> >>> I would imagine that the topic of connecting with databases would be >>> one of the most popular subjects on a PHP framework site and, sure >>> enough, "database" is the largest item in the CakePHP cloud. When I >>> click on "database" I get all the relevant tagged articles. >>> >>> Contrast that with the user experience on Drupal.org. Searching for >>> even the most common topics means that I have to either do a search >>> (which is messy and unreliable) or I make a series of attempts to >>> crawl down some obliquely-labeled rabbit holes (FAQ, How-to, etc.) >>> that lead me into a maze of unhelpful subheadings until I finally >>> stumble across enough information to satisfy my need (although I'll >>> never know whether or not I've found everything on the subject) or I >>> just collapse in exhaustion. >>> >>> :) >>> >>> Lee Hunter >>> Technical Editor >>> >>> >>> On Mon, Sep 8, 2008 at 12:55 PM, Tony Narlock <skiquel@...> >>> wrote: >>> >>>> See an example here: http://bakery.cakephp.org/ >>> -- >>> Pending work: http://drupal.org/project/issues/documentation/ >>> List archives: http://lists.drupal.org/pipermail/documentation/ >>> >> -- >> Pending work: http://drupal.org/project/issues/documentation/ >> List archives: http://lists.drupal.org/pipermail/documentation/ > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > Pending work: http://drupal.org/project/issues/documentation/ List archives: http://lists.drupal.org/pipermail/documentation/ |
|
|
Re: Tag clouds and documentation
by christopher calicott
::
Rate this Message:
On Sep 8, 2008, at 3:41 PM, Lee Hunter wrote: > > That way, you get the world view of the individual user, which is > often surprising, idiosyncratic and useful (e.g. when they propose > something like "survivors of shootings") and you get the collective > wisdom of the other editors that say "Great idea, but let's make the > category 'shooting survivors' not 'survivors of shootings' and let's > make that a sub-category of "shooting victims". > > Lee Hunter > Technical Editor Exactly! It's impossible to predict all the ways in which someone might /need/ to find a bit of information so this allows the users to enlighten the editors and the editors to play their role of sprucing up the taxonomy slightly as they see fit (in our case, our policy is that we do some search volume research on variations of the keyword/ category in question and then choose the one most likely to get the traffic and/or searches. In some more rare cases it might make sense to use more than one synonym and then route one to the other more popular one.) -=- christopher -- Pending work: http://drupal.org/project/issues/documentation/ List archives: http://lists.drupal.org/pipermail/documentation/ |
| Free Forum Powered by Nabble | Forum Help |
