Office Ribbon Editor's main focus is on editing the RibbonUI for Excel, Word, and PowerPoint. The reason behind this decision lies on the fact that the ribbonUI is managed with XML. Office Ribbon Editor is a feature rich application that includes such features as:

Creating Office 2007 and 2010 documents without the requirement of having Office actually installed. Syntax highlighting and Autocomplete capability. Access to all Office 2007 and 2010 features from the ribbon to the new Backstage feature found in Office 2010.

Since there's been a few discussions here about the MS Ribbon it might be of interest.I am mostly still in the dark ages and using Office 2003 so I haven't tried it.

Standard disclaimer... I am not affiliated with the program or developer in any way.

As a Microsoft developer, I was faced with new challenges when Microsoft introduced the new Ribbon UI in their Office 2007 suite. In the beginning, I was excited with the possibilities, but I quickly became overwhelmed with the amount of work that was required to get a ribbon up and running.

I was extremely thankful when I came across the OpenXMLDeveloper's web site and discovered their tool. Coding became easier, but I soon found myself yelling at the editing tool! This is when Office Ribbon Editor was born. My application is based on OpenXMLDeveloper'sCustomUI Editor.

My goal in developing Office Ribbon Editor was to: Correct issues or failures I found to be annoying.Introduce a better coding environment with helpful tools

This is a little tangential, but In Office 2010 they have "Customize the Ribbon" which (gasp) changes the Ribbon MetaGame for me. My chief complaint against the static ribbon was where they jammed features, which simply wasn't where the muscle memory wanted to go.

But if you can design your OWN ribbon for any app, then I LIKE the ribbon! Because it does in fact reduce clicks to instantly pick *either* of Paste Special Values or Paste Special Formats. Both are way faster than RClick/Paste/Special/____.

But the last secret sauce is get Excel (for example) to "Show ALL features." There's half deprecated features still buried in the code.

It is great to see people talking and interested in my application. Just to clarify, I am not a developer for Microsoft. I develop using Microsoft products. I started with 2003 and now use 2007 and 2010.

I can see the confusion in my text, I should change it .

Thanks again for the props!

The man is a Microsoft developer:

Why develop Office Ribbon Editor?

As a Microsoft developer, I was faced with new challenges when Microsoft introduced the new Ribbon UI in their Office 2007 suite. In the beginning, I was excited with the possibilities, but I quickly became overwhelmed with the amount of work that was required to get a ribbon up and running.

I was extremely thankful when I came across the OpenXMLDeveloper's web site and discovered their tool. Coding became easier, but I soon found myself yelling at the editing tool! This is when Office Ribbon Editor was born. My application is based on OpenXMLDeveloper'sCustomUI Editor.

My goal in developing Office Ribbon Editor was to: Correct issues or failures I found to be annoying.Introduce a better coding environment with helpful tools