Structural and editorial changes for the website

[SueChaplain]

Suggest various changes to improve the structure and content of the website, including the following items:

• Rename menu Getting Started to About
• Rename menu Guide to Getting Started
• Rename menu item Blogs to Blog posts
• Moved content about "How to configure Eclipse OMR with custom options" from the "Building" topic to the "Configuring" topic
• Changed all text references to JIT to just "Compiler". Left those that imply a source component name of some sort
• Blog posts page: Added 3 blog posts from developerWorks open
• Presentations page: Re-ordered the list, most recent first. Added a link for Mark's Escon slides and added an entry for the Eclipse OMR Tech talk in July 2016.
• Removed the Releases tab from the menu.

[mstoodle]

We should add @charliegracie slides from VMM et al too.

Here are links to articles that came out this year that I'm aware of:
InfoQ interview: https://www.infoq.com/news/2016/05/project-eclipse-omr
Eclipse newsletter in October: http://www.eclipse.org/community/eclipse_newsletter/2016/october/article5.php
Also JAXenter reprint of that article:
https://jaxenter.com/eclipse-omr-building-language-runtimes-cloud-130530.html

Here are links to the OMR presentations I've done in the second half of the year:
dwOpen Tech Talk July 20: https://developer.ibm.com/open/videos/eclipse-omr-tech-talk/
JVM Language Summit Aug 3: https://www.youtube.com/watch?v=w5rcBiOHrB0
VM IL workshop keynote Oct 31: http://www.slideshare.net/MarkStoodley/vmil-keynote-mark-stoodley

[0xdaryl]

Our CASCON 2016 talks:

Open-Source, Language-Agnostic Compiler Technology for Eclipse OMR, Daryl Maier (IBM Canada Lab). [slides]

An OMR JIT for Lua – A Case Study in Simplified IL Generation Using OMR JitBuilder, Leonardo Banderali, Mark Stoodley (IBM Canada Lab). [slides]

[SueChaplain]

@charliegracie If you can post information for your conference/slides, I'll get all these extra ones added to the page tomorrow in a new commit.

[0xdaryl]

Given the importance of some of this collateral, I wonder if we should capture and retain the actual content (within the boundaries of the law) in a more permanent place on the website or repo lest some of the links vanish over time?