This one is solely on the players and alliance leaders.
To many emigrees from Planet Bob if you ask me. Brought all that baggage with them.
But why would any one side disarm their diplomacy "for the good of the world". That would require a willingness to lose "for the good of the world", and everyone wants to win too bad for that.
Edit: Other alliances could always wage war against blocs for the sake of defeating blocs.
The minimum wage has not kept pace with inflation due to miserly economic policies by the Right(and to a lesser extent, the Left as well). Asking that the minimum wage buy in 2014 what it could buy in 1960 doesn't seem too socialist or crippling to business to me.
Posted just in the nick of time?
Also, when do we get to accuse EoS of treaty-whoring?
Edit: Noticed its a post by a 0 post guy with no nation. So maybe there's no TW's and maybe there's no treaty either.
I'm tellin ya, just start with bootstrap, and add some button classes(btn btn-primary), add classes to your fields(form-control) and see if its better. If you're using tables anywhere, bootstrap has a nice table class.
Really Ragnar? Advertising for Guardian too?
Seven Kingdoms is the best alliance on Orbis. Why? Dragons.
Also, the Iron Isles are part of the Seven Kingdoms, and who doesn't love the Ironborn?
Personally, yellow makes me think of pee. We should find a cooler color, SK. Something violent. Like Red. Blood and Fire are 2 of our 4 keywords, and both are Red.
Again, we should do a modest increase. If there's no negative consequences, that's proof it works. If it leads to problems, at least its only a small problem. $1 a year for 3 years seems reasonable.
It really is just CSS.
And you can start solely by utilizing the grid system to provide a responsive experience and hide unneeded content on small screens.
And the menu. If you can get the menu to display on top for small screens, in a fixed format, that would be swell.
I can help you write that code sometime.
We really don't need to see source code for this. We can tell you what classes to use on what divs. And then moving forward, on fields and images too.
Displaying resources will be somewhat challenging due to the quantity of data elements to display and the small real estate on a phone. Might want to not display it on every page.
Update some design elements to be more responsive for mobile browsers.
Specifically, using the Twitter Bootstrap framework for styling would be relatively easy compared to manually coding.
I'd request that you start small, perhaps with the trade view. That is the area that is most difficult on a mobile interface.