Please don't jump on me, this idea has probably been suggested already, but I didn't find the appropriate page anywhere after doing as much searching as a beginner to Drupal would do, so hence this suggestion.

On the main "Documentation" page, there should be a link to a "Glossary of terms".
This page already exists here but its location was not at all intuitive to me and took me good 20 minutes to find. Moving it up 1 or 2 levels in the hierarcy and giving it some 'love' - ie adding to it or making it more coherent might be a good idea.

Heck lets split each of these words off into their own page so other users can add comments, and we can get some better feedback on these definitions. I was remembering my initial experience with Drupal when I ran away in terror from the word 'Taxonomy' because I could not initially grasp the concept.

I'm willing to put the grunt work into splitting these off if anyone else thinks its a good idea.

Comments

add1sun’s picture

add1sun commented
Status: Active » Closed (duplicate)

There is indeed already an issue for this and user wolfflow is doing a lot of work in this area right now. I'm sure he would love some assistance, so please coordinate with him. Marking this a duplicate, please continue the conversation in the other issue. Thanks

#302433: Add "Terminology" term to "Drupal Handbook" first page

dwees’s picture

dwees commented
Title: Definition of commonly used terms » Split terminology page into separate pages
Status: Closed (duplicate) » Active

I actually had 2 suggestions, one of which has been implemented. My 2nd suggestion was to split that monolithic page into subpages, and then that would allow users to comment on the specific definitions, and improve their individual search ranking.

The other issue was just about the placement of the terminology link, and that has been marked as fixed now.

Wolfflow’s picture

Wolfflow commented

FYI: the 2nd suggestion in @dwees comment #2 my self did questioning in issue: http://drupal.org/node/307996 in point 3 of the listed tasks:

Do you think that the "Common expression & acronyms used on D.O. should be divided in 2 page ( dividing alphabet in two parts) for better consulting?

@add1sum answered:

3. I'm not sure really. that is actually something I would like to ask the usability team or the redesign folks if they have a suggestion. It seems to me, personally, that having it all on one page is better. I like fewer clicks. :-)

this is +1 for me taking in consideration that they may be better implementation suggestions from the
redesign team and us (the Doc-Team).

dwees’s picture

dwees commented

I actually want a separate page for each term. This is for 3 reasons:

1. Improved search friendliness for these important vocabulary terms.
2. Ability to add comments for specific terms, which will improve the definitions in the long run.
3. It becomes more feasible to increase the length of definitions and provide examples, diagrams, etc... when each term is on its own page.

Wolfflow’s picture

Wolfflow commented

Hi @dwees

I like that you have ideas and suggestions about the "Terminology" Structure but, this Project just started.
The first task for this is to collect as much terms that may be unclear for no-native english visitors.

The second is to build in the "Terminology" page notes informing about the best documentation node that gives a simple explanation about a Drupal Term and or a Function procedure, a kind of "Quick" index to resources of our
existent "Handbooks" on Drupal.org.

I do not know in details yet what for new features Drupal.org Infrastructure Team will provide to inscribed
Drupal.org Members further. Also the Redesign-Team is working and planning the new Drupal.org Design.

So I think that the best think yet to contribute is to overview the present list of "Terms", "Expressions" and "Acronyms" so as to have a correct english definitions, correct links (possible Drupal.org internal ones) to the existent documentation.

We will se how this will develop and if required I will divide then first the "Terminology" Pages in more sub-pages.
I don't think that your proposal will be usefully at the moment on this stage of development of the "Common Terminology" project.

Anyway thanks for your feedback

Wolfflow’s picture

Wolfflow commented
Status: Active » Postponed

I will set this on "Postponed", but feel free to add your Ideas, Suggestions etc.
Meanwhile is very important for me to get support of add as much Terms, Expressions, Acronyms and Links-Notes to the already listed items.

In this way we will expand this Section to a usefully "Common Terminology" quick information resource (Similar as an "Index" on Drupal.org) where everyone can profit (Visitors, Members etc.) for finding definitions, explanations
and references to Documentation pages.

So you All are invited to contribute, with adding Terms, Expressions, Acronyms and Links-Notes with comments if you are not part of the Doc-Team, and to add directly if you are!!

Kind Regards

add1sun’s picture

add1sun commented
Issue tags: +Doc IA

I'm gonna nix this issue due to the complete IA reorg, but marking so the comments are part of the IA discussion.

tafit’s picture

tafit commented

The component "Alphabet" doesn't disable some letters, eg. D, so when the user clicks on D nothing happens.

Link: http://drupal.org/getting-started/before/terminology

Should I create a new issue for this?

arianek’s picture

arianek commented

@tafit, that would be great. thanks.

arianek’s picture

arianek commented
Component: New documentation » Correction/Clarification
Status: Postponed » Closed (won't fix)

There's a handcoded letter menu at the top now that does have unused letters disabled - this seems sufficient. For terms that are more high level and require more lengthy descriptions, it's likely they'll fit into other docs pages, so I'm not sure it makes sense to have page-per term organization.

This seems like it's in good shape for now, so I'm going to close this. If someone actually wants to take on restructuring this significantly then a new issue can be opened (or reopen this one).