Currently it is standard practice to make a separate page for every WoW API function, but in a few cases this pattern has been broken. For example:
- Region:GetLeft(), GetRight(), GetTop() and GetBottom()
- C_Timer.After(), NewTimer() and NewTicker()
How far should we go with this? I personally think these examples make tons of sense, because they are so closely related that anyone interested in one should see all at once.
But here's a list of pages that are currently broken apart... does it make sense to merge them or keep them apart? Why? (To be clear, I don't necessarily advocate merging all of these... I'm trying to stir conversation with lots of examples good or bad.)
- Hiding and showing frames
- Getting information about a buff or debuff
- ... = UnitAura("unit", i[, "filter"])
- ... = UnitBuff("unit", i[, "filter"])
- ... = UnitDebuff("unit", i[, "filter"])
- Aura (API Type) (a page linked by all three, describing their common return value)
- Setting and hooking scripts
- Region (or frame) size and position
- SetWidth(width)
- SetHeight(height)
- SetWidth(width, height)
- width = GetWidth()
- height = GetHeight()
- left, bottom, width, height = GetRect()
- left, bottom, width, height = GetScaledRect()
- left = GetLeft()
- bottom = GetBottom()
- right = GetRight()
- top = GetTop()
I'll go on a limb and say the last example (size and position) is proof that its possible to take merging too far. That would be complicated to put all under one roof!
But would the last example make sense if you merged it those articles into four pages like this?
- SetWidth, SetHeight, SetSize
- GetHeight, GetWidth
- GetRect, GetScaledRect
- GetLeft, GetBottom, GetRight, GetTop (this merged page already exists)