"First Read" documentation overhaul

[NickolausDS]

Free Flight isn't very customer friendly at first glance. The best way to show off what Free Flight can do is by descending priority:

• Video
• Webplayer Demo
• Screen Shots
• Text

In the above, a video would be the most effective, then the Demo, then Screenshots, then Text. Currently, we have that backwards. The visitor reads our giant wall of text, finds the screen shots, eventually figures out there is a demo, then yells at me for not having a video. It's not a very good way to introduce a visitor to something new they might use.

The Readme.md needs to be overhauled to reflect the priority a little better. Also, for the text portion, the "wall of text" needs to be split up into smaller bits. Maybe a one sentence description, a bulleted list of points about what it can do, a list of requirements, and a small introduction of how the visitor can use Free Flight. I'd like to treat the text portion as the "Final Hook", in which the visitor is already very interested in the product and just wants to find out how difficult it would be to use in their own project.

I'd like to approach text in general as, "The final barrier keeping people from using Free Flight." People need to understand what Free Flight does, and therefore read about it. But they should have to read as little as possible in order to use this project.

[NickolausDS]

I just realized I wrote a wall of text about how walls of text are bad. The irony is deafening.