In the mid-2000s, a typical pattern recognition conference website had a file called index.php that served as the single entry point for author instructions. Unlike modern content management systems, this PHP script often contained a mix of hardcoded HTML, inline CSS, and conditional logic to display submission deadlines, formatting rules, and contact information. The page was usually the first result a prospective author saw after clicking “Instructions for Authors” on the conference home page, and it remained largely unchanged for months—except for the occasional frantic update when the deadline was extended.
The structure of these index.php pages was remarkably consistent across conferences in the pattern recognition community. They typically began with a banner image (often a poor JPEG of the conference venue) and a bold heading: “Instructions for Authors.” Below that, a series of <h2> sections covered essential topics: paper length, formatting requirements (PDF or PostScript, font sizes, margins), language (English, occasionally with a note about non-native speakers), and the review process (double-blind, number of reviewers). The page almost always ended with a “Contact” block, listing the programme chair’s email and sometimes a phone number.
The Anatomy of an index.php Author Page
These pages were not simple static HTML. Because they were built with PHP, they could include server-side includes, date comparisons, and even database queries to fetch the latest deadlines. A common pattern was:
- Important Dates – a table with submission deadline, notification date, and camera-ready deadline. The PHP code often compared
date('Y-m-d')against hardcoded strings to highlight past deadlines in red. - Paper Formatting – a link to a ZIP file containing LaTeX templates and style files, along with a note that “papers must not exceed 8 pages including references.”
- Submission Link – a direct URL to the conference’s submission system (often a CGI script or a separate PHP page).
- Ethics and Originality – a boilerplate paragraph about plagiarism and concurrent submissions.
- Contact – an email address obfuscated with JavaScript or a simple mailto link.
One notable feature was the use of PHP conditionals to display different content depending on the current date. For example, before the submission deadline, the page would show a green “Open” badge; after the deadline, it would change to “Closed” and hide the submission link. This dynamic behavior was a step forward from the static HTML pages of the early 2000s, but it also meant that a misplaced if statement could break the entire page.
Common Sections and Their Purpose
While each conference had its own flavour, the sections were surprisingly uniform. The table below lists the typical elements found in a mid-2000s index.php author page:
| Section | Typical Content | PHP Trick |
|---|---|---|
| Important Dates | Deadline, notification, camera-ready | Date comparison for colour highlighting |
| Paper Formatting | Template download, page limits, font | Often a static link |
| Submission | Link to online system or email | Conditional display based on deadline |
| Review Process | Double-blind, number of reviewers | Static text |
| Contact | Chair email, phone | Obfuscation via JavaScript |
The Paper Formatting section was especially critical. Conferences like PRASA (Pattern Recognition Association of South Africa) provided detailed LaTeX style files, and the index.php page often included a direct link to a ZIP archive. The evolution of such pages can be traced through the Camera Ready Submission Guidelines in Mid-2000s Pattern Recognition Conferences and The Messy History of Author Markup in Conference HTML.
The Role of PHP in Conference Management
PHP was chosen for these pages because it was cheap, widely available on university servers, and easy to modify. A graduate student or a junior faculty member would SSH into the server, edit the index.php file with nano, and upload it via FTP. There was no version control; backups were made by copying the file to a .bak extension. This ad hoc approach led to many broken pages, but it also allowed rapid iteration. For example, when a deadline was extended, the organiser could change a single variable—$deadline—and the entire page would update.
The reliance on PHP also meant that the index.php file was often the only dynamically generated page on the conference website. Other pages (e.g., programme, registration) were static HTML. This made the author instructions page a fragile but crucial component. If the PHP interpreter on the server had a different configuration (e.g., register_globals turned on or off), the page could behave unpredictably.
Transition to Static and CMS-Based Systems
By the late 2000s, many conferences began moving away from custom PHP scripts toward static HTML pages or content management systems like Drupal and Joomla. The reasons were clear: security, maintainability, and consistency. However, the index.php author page left a lasting legacy. Its structure—a single page with all essential information—influenced the layout of modern conference submission portals. Even today, many conference websites still have a page titled “Instructions for Authors” that follows the same section order.
One such page, preserved in the PRASA 2001 digital archive, shows a manually updated “Last modified” timestamp of 14 March 2005, a reminder of the era when a single PHP file could serve an entire conference’s author community. That file—index.php—was the unsung hero of mid-2000s academic publishing.