::Actually, it would be ''easier'' to follow my suggestion. Right now, you have to alphabetically sort every new request into an ever-growing list. With my suggestion, you would only need one non-brainer step, regardless of how many requests you add: "Add all new requests at the top, regardless of order." And when you archive news, you simply move a sub-headline here a bit further up. And you wouldn't even have to re-order the current list - just wait until tomorrow's mass-archiving (but before you add new requests) and then slap a "=== Wanted pages for archived items ===" sub-header at the top of the current list. | ::Actually, it would be ''easier'' to follow my suggestion. Right now, you have to alphabetically sort every new request into an ever-growing list. With my suggestion, you would only need one non-brainer step, regardless of how many requests you add: "Add all new requests at the top, regardless of order." And when you archive news, you simply move a sub-headline here a bit further up. And you wouldn't even have to re-order the current list - just wait until tomorrow's mass-archiving (but before you add new requests) and then slap a "=== Wanted pages for archived items ===" sub-header at the top of the current list. |