I'm new to Drupal, and am looking for advice on how best to structure
a web site I'm exploring moving thereto. My reasons for making the
change include a belief that putting this site into a CMS with a large
ecosystem around it will make it easier to maintain and enhance it in
the future. I obviously have a lot of learning to do before tackling
this job, but would like to get some good ideas of what sub-bits of
Drupal technology I should be trying to learn.
The site (http://ringing.org) is currently written using an ad hoc collection
of JSP files and custom tags, built around a MySQL database, with a
little static HTML and a few Perl and Python CGI scripts thrown in.
The structure of the site is defined by a single, large XML file that
is read and parsed at web server start up, or whenever the file is
changed, and that defines the several hundred pages that make up the
site, and their topology.
The heart of the site is a collection of about 8,000 change ringing
compositions, which are essentially mathematical formulae, each
presented in a tabular format. Characteristic examples can be seen at
http://ringing.org/main/pages/peals/major/spliced-surprise/9-22m.
They are divided up into pages of related compositions. The
distribution in pages varies according to the population of
compositions. For example, all those with the attribute know as stage