Now, perhaps one cold accuse me of being a bit too wordy, but, I am no fan of abbreviations, especially those that happen to be 1. jargon or 2. Computing terms. Which is a bit ironic since I use computers so much. Often, it is better to say Developer rather than devel. I think that we should keep this in ming when adding information to the Drupal website. Also, I hope everyone will consider using a picture, graphic, diagram, or icon once-in-a-while (or may thrice-in-a-while). Images not only attract attention where it is needed but also create visual stimuli for the readers that makes them more likely to stay and explore. A good example of this is mozilla.com
Now, perhaps one cold accuse me of being a bit too wordy, but, I am no fan of abbreviations, especially those that happen to be 1. jargon or 2. Computing terms. Which is a bit ironic since I use computers so much. Often, it is better to say Developer rather than devel. I think that we should keep this in ming when adding information to the Drupal website. Also, I hope everyone will consider using a picture, graphic, diagram, or icon once-in-a-while (or may thrice-in-a-while). Images not only attract attention where it is needed but also create visual stimuli for the readers that makes them more likely to stay and explore. A good example of this is mozilla.com
P.S. Add pictures
I think a certain amount of "dev lingo" is acceptable - as long as it applies only to articles where developers will be reading.
There are some things that can be expressed using "developer slang" much quicker than spelling it out. A developer reading an "implementation details" article may feel much more comfortable with that style of writing. I think we can play this by ear and the lines will draw themselves.
However, abbreviations can be downright-annoying sometimes - especially things like AFAICT, IIRC, or IOW - those are horrendous to translate mentually sometimes.