• Examine how pgn4web, XBoard, etc., do PGN parsing
• Display annotations like $1 (mapping of $X -> !, etc.?)
• Handle comments: multi-line and semicolon?
  • Ignore them to start
  • Shouldn't be a whole lot harder to display them below the board
• Ignore recursive variations for now
• Handle FEN strings in tag pairs

Shouldn't be too hard, and would speed up page load times.

Right now, the only way to hide the actions area is to refresh the page.

• Add a checkbox to the Save view
• Conditionally clear headers not present in the UI

Become a PGN database.

Make sure that the site doesn't look terrible on mobile. If necessary, use something like Bootstrap.

This should probably be user-configurable. It would clutter the browser history, but make it harder to accidentally lose work.

I've heard of Garbochess. Is there anything better?

• Ctrl+S to save
• Arrow keys for forward/backward
  Text inputs need to behave normally!

Automatically play through moves.

• Click a button to enable
• Click a button to disable
• Possibly enable on page load

• See how pgn4web does this
• Possibly hook into PGN parsing to emit links for each move: #2.

This would be nice to support, but I don't want to break anyone's links. Needs more thought.

Overlaps with #5.

The current approach to changing views is a hack. There's no need for fancy AJAX features, but model-view separation might be nice.

I'm currently using buttons, which is a bit of a hack.

Read in a PGN file with the HTML5 File API.

Not sure if this is necessary with the "paste PGN" feature.

• Save the game's PGN with the HTML5 File API
• Add UI to set the seven required tag pairs

This probably depends on model-view separation, which would come with #3.

Allow variations and sub-variations. This probably requires using a tree data structure to store moves, instead of a list. Depends on #2.