User blog:LadyAlys/"Information for Developers" Sections on Content Pages

This post is intended for wiki editors so that we can discuss how to best format a new section that will be placed on some of the wiki's Content pages.

For context, here's what I wrote in the Wizards of the Wiki guild a few days ago:

"Excluding the three or four Blacksmiths pages, the wiki is written for users, not for the coders who work on the site or on third party tools. However there's several normal content pages where we could put useful information for coders. For example, in the pets page, we could put the info about feed values; on the avatar page, we could add the information that @hairlessbear and I recently put into the Aspiring Coders guild; the quest page could have a lookup table for quest name to quest key."

I've made a start by putting an "Information for Developers" section on the Cron page.

I can't decide whether Info for Devs should be just above Known Bugs or below it. Do we want to keep Known Bugs at the very bottom of each page, for consistency so that people can find bugs more easily? Or do we want to always put Info for Devs at the bottom to keep it out of the way of non-developer users?

I've included some templated text at the start of the section: Template:Information for Developers. Feel free to edit that!

On the cron page, I've done something that will probably be in most of the Info for Devs sections, so I would like us to work out how to best present it: I've added two links to the script that contains the code. One link is for the live file - the file that will always contain the up-to-date code. The other is for the file as it exists at this moment in time (i.e., the next time we change cron, that file will become outdated). The benefit of the second link is that it can point to the exact line number that cron starts at, so that you know roughly what you are looking for when you look in the live file. You can't link to the exact code in the live file because the line numbers change every time the file is edited. Note that I do not want us updating the line number links very often - it's a waste of our time and would not be reliable anyway since we could easily not notice when code changes made it necessary to change the links. Since we're likely to do this any time we mention a file in an Info for Devs section, I'm wondering if there's a better way of presenting these two links. Perhaps they would benefit from a template that contains the links, and maybe also contains extra information about what else to search for, as I put on the cron page? Suggestions please!! :)