Convert browse details to sidebar layout
Site cleanup I set out to do a quick and dirty typography overhaul to make things more consistent and a bit cleaner, but I kept running into things I didn't like, so this lead me down something of a rabbit hole of design tweaks to the OSM site. Goals here are to have better content hierarchy, better vertical rhythm, more consistent UI, cleaner markup with less tables, all while keeping the basics pretty much intact. There are a lot of things I didn't touch even though they need to be updated (lots of tables where stuff shouldn't be tables, mostly). Basic overview of changes: I added a new persistent header that helps segment pages. It's now a lot easier to know what you're looking at. The header has a page title, a description, plus a submenu of actions. There is now a pattern of 20px/10px margins and padding for more rhythm and breathing room throughout the site. I know there are other problems here or things I've missed - would love another set of eyes to look over this! I am still getting comfortable working on the site - it's my first time ever digging into a ruby or rails so I'm not familiar with the templating language yet.
Fix data browser navigation tooltips
Improve layout of data browser pages Use float to position the navigation controls and map on the right rather than a table so that we get more consistent positioning and avoid forcing the map of the right hand side of the viewport.
Revert the nofollow attributes - they aren't really needed if sites obey robots.txt and don't do what Firefishy thought they did.
Add some strategic rel="nofollow" attributes to the data browser pages to control what search engines will explore.
Make the changeset navigation use the new fancy «/» arrows instead of <> to be consistent with the history browser itself
Make right hand side of browser view able to grow beyond 250 pixels.
Prevent browser navigation control from wrapping.
Go back to using < and > for navigation instead of the nasty looking unicode arrows which aren't at all consistent with the use of | as the separator. Also remove some of the translations - there is no reason that I can see to allow translations to completely change how the navigation control is laid out.
Don't display a stale "|" pipe if we're at the beginning or end of the list of this user's changesets
* Use ← → instead of < > in changeset navigation * Add tooltips to changeset navigation buttons and make them translatable
Changeset navigation by a particular user's changesets. (Closes #1726)
Rename views to rails 2 style names.