Although I don't have control over that (I'm just an admin on the forum), in my experience Processing is used by a lot of people learning code for the first time. Processing is actually meant to be a tool for artists and is used to teach a lot of students who probably would need to see it used in an example to understand.

Totally understand that, and I'm coming from only an intermediate-level of experience with Processing's cousin, Arduino. All the same, the first example for line() doesn't tell anyone anything without the accompanying (and helpful) picture: I mean, if one visits the reference section, they're looking for how something works...I usually check the syntax first and then check out examples, so I'd suggest the following order (to whomever has the capacity to change it, of course):

1. Name
2. Description
3. Syntax
4. Parameters
5. Returns
6. Example(s)
7. Related

I don't agree. Visual people like to see examples first... It gives a good idea / feel of how the function works. Then they can dig in more to see the full syntax and the tiny details. It is along the general philosophy of Processing. If you need to jump to the technical details, just use the End key of your keyboard, or scroll down to the bottom of the page: at least, the design is consistent.