How are you wanting to store the information? XML, Database, Flat files?
This sounds like you don't know exactly what you want. That kind of thinking can kill you when starting projects (large or small) because things can balloon out of control rather quickly. That simple one-page site you wanted to create is now a 32-page masterpiece with ajax capabilities, contact forms, and a blog. My point is, if you don't have a defined plan, you can really hurt yourself in that you will inevitably make changes to the code for some other feature and you will stray from what you started from.
If you just want a tracker for goals in a game, I guess I would have to say in a database style, you'd want a few tables:
-
Year
-
Teams
-
Games
-
Players
-
Goal Types
Then each table would have it's own data. The simple tables (like players, year, goal types, and teams) would be something like:
CREATE TABLE `years` (
`year_id` int(11) NOT NULL AUTO_INCREMENT,
`year` varchar(4) NOT NULL,
PRIMARY KEY (`year`)
UNIQUE `uniqueness` (`year`)
) TYPE=MyISAM;
CREATE TABLE `goal_type` (
`type_id` int(11) NOT NULL AUTO_INCREMENT,
`type` varchar(64) NOT NULL,
PRIMARY KEY (`type_id`)
UNIQUE `uniqueness` (`type`)
) TYPE=MyISAM;
You can see there are only two columns there (an id, and a value). So for players you'd have player_id and name. If you wanted to expand upon that, you could add jersey #, team id, righty/lefty, etc.
The games table would hold your columns to match up team ids, player ids, goal type ids, and periods.
That's one idea. There are other ways to do it based on how you want it done.