Heh, this is pretty similar to what my scripts do,
http://www.bay12forums.com/smf/index.php?topic=126953.0 except your work is geared more towards users than modders. For example it uses database on the server and can't be quickly updated for local changes, unlike my scripts. It has more eye candy and I like it that unlike with my scripts, you can sort by columns, but overall it is cluttered and not as readable as my tables. Rows having alternating colours is a nice touch.
* Consider adding check-boxes for what to display. I've run into the problem of having too many columns and solved it with command line options, but with a www server, check-boxes and a button are a more obvious solution. We don't need all the information at the same time, just a way to select the columns we want.
* More human-readable names to columns. Keep them short and maybe add some explanatory text at the bottom.
* Some columns can be combined without impacting readability. For example instead of three structural elasticity columns that display "1", have one named "Elasticity" that displays a combination of "Ch. All", "Ch. Met.", "Thread", then explain it below the table.
* Modders need IDs for things.
* By default, sort everything alphabetically by name.
* For boolean things "Yes" and "No" should be more readable than "1" and "".
I seriously consider resuming work on my scripts, then finding a way to integrate them into one tool that can output a set of locally linked web-pages. It would be especially useful for navigating syndrome and interaction chains. Well, I think I know how to do that, but I need a better architecture than "put everything in one file and have like 5k lines of code and a hundred global variables".