Is it possible to actually make the GIT part of the main menu (Community)?
It is quite cumbersome to move the mouse over Community, then Other Languages and then GIT.
It would save a lot of navigation time if it was possible to get to the GIT faster - considering I do this n number of times a day.
Can you stop elephanting around with the elephanting layout? There was nothing elephanting wrong with it for elephants sake. You're tinkering for the sake of it. Put the bloody lounge link back where it elephanting belongs, put the lounge back above stoopid elephanting Insider and leave the elephanting points table alone! It is a mess!!! Revert! Revert!
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum
Wow, too many "elephanting" in this post. I don't mind them some someone could.
nevertheless, let me add some more bugs to it.
1. The reputation history is showing the points in wrong place(in the column where the reputation category is shown)
2. Where is the GIT? in fact all the "other language discussion" forums is gone itself.
Every now and then say, "What the Elephant." "What the Elephant" gives you freedom. Freedom brings opportunity. Opportunity makes your future.
My tip makes use of code blocks that are in multiple languages. The PRE block on the bottom should look red, like in my alternate (which I plan to delete once I've confirmed that the new feature is up to snuff). In the WYSIWYG while editing the tip, the PRE blocks do look red, but that style information disappears when the tip gets rendered.
I am in the very early stages of trying to come up with an article. For this article, I was thinking about providing the solution in C# and VB.NET, but I don't think the current code blocks can handle it without having 2 separate blocks for each section of code I will explain. I was thinking that it would be nice if we could have Tabbed code blocks (like MSDN)? This could facilitate multiple code language articles, but I could also see some other use cases: If you were explaining a main section of code, have the code in the first tab, then any ancillary classes can be included in tabs behind it.