The solution is mghDreamweaver linked to here at GitHub, written by Max Hegler.

The only downside is that this is not available through the excellent Package Control from the spooky brain of Will Bond. That said, there is a good reason for this ... and that is the improved (amending that to vastly improved) HTML.tmLanguage file that Max has so brilliantly written. You must follow his instructions and replace the current HTML.tmLanguage file with his. This is the only path to Sublime happiness.

Close out of Sublime before following the instructions from Max.

In his instructions, Max asks you to change the name of the default HTML.tmLanguage file to HTML_original.tmLanguage.

I found that Sublime didn't take to this very well, for one reason or another. I created a new folder within packages/HTML and moved the current one into that new directory. I suggest you do the same. After doing so, paste Max's super excellent HTML.tmLanguage file into the packages/HTML folder.

This way, if you ever want to go back to the inferior default file, you will have it available.

Max doesn't direct you to where this is on Windows 8, so here's that:

For other operating systems, follow the instructions from Max. They work.

You are done and can launch Sumbline Text again at this point

On launch of Sublime, choose view / syntax / HTML

Then choose Preferences / Color Scheme / mghDreamweaver

Happiness should be immediate at this point!

Check out the display difference with the same admittedly questionable code! BooYah!

Note how Max has brought out your input tags and his PHP mark-up stands out as you would expect it! Open up Hegler's HTML.tmLanguage file and compare it to the original to see how he has made your life better. I don't even know the guy, but I wanna buy him a Kolsh at bare minimum.

---------------------------

Last note on Sublime: I paid the $70 for a license myself, and anyone who doesn't decide to pay can just deal with the lifelong guilt of not supporting the super cool people who wrote this amazing program.

Actually the last note: For anyone reading this, if I have screwed up any of the instructions please make a comment on this article so I can correct it for others who might stumbled in here. The internets are full of bad information and I'd prefer this not be part of that miserable problem.

• One pound of dried pinto beans
• 5 cups or so of low sodium chicken stock
• One big white onion
• Some minced garlic
• A few jalapeño peppers
• A pinch or two of cumin
• Some hot water

Let's get started. Put that chicken stock in a pot, and start heating it up over high heat. Chop up the onion nice and fine and do the same to the jalapeño peppers once you deftly scrape out the seeds with a spoon. Once all chopped up real fine, dump them in the chicken broth, which is getting hot by now. Put some minced garlic in there and that dash of cumin powder. Rinse off the dried Pintos in a colander and dump them in the pot. Sit back and bring that to a boil. The whole thing should be just barely covered with liquid. If it's not, add some water or more chicken broth until they are just barely covered. Once we get a boil, turn it way down to a simmer. For the purposes of getting your simmer right, we want to see a nice even bubble around the edges of the pot.

Okay, relax. Go watch the MLB Network or kick back with that Ken Bruen novel you're reading right now. We're going to let that simmer, with the lid slightly askew, for about two hours. Check it from time-to-time. Give it a stir every so often and add hot water as needed to keep them covered. After a couple of hours, give them a taste. Keep cooking them on low until they are to your personal liking.

Happiness happens.

Here's a fine suggestion. Set aside a serving or two of your remarkable Pinto Beans in a smaller sauce pot, set to low heat. Chop up a few slices of green pepper and add them. Add a healthy dash of Tapatío hot sauce. Use a masher of some sort to get those beans into a mashed-up state. Let them cook on low, stirring and mashing them often, until most of the liquid is cooked off. What you have here is essentially re-fried beans. So, throw a couple of corn tortillas in an oiled skillet and heat them up until you can smell the corn. Spread your pinto-mash on a tortilla, grate some sharp cheddar cheese (aged at least one year please) on there and wonder why you haven't been eating this all your life.

One of the things that Nat Geo is trying to accomplish here is to encourage people to post their scores to Facebook. We've written all of this into the script - so if you take the quiz, make sure to check out our nifty bit of code that pushes your result to the Facebok Connect application.

No sooner had we finished this, than Nat Geo was on the horn again for another one! Woo Hoo! The one we are working on now is much more complex, with a hefty supply of animation and interactive elements. It will go live in July, 2010 and the summary will get posted here in the bug lab.

Details for Dorks

In the past, we did interactives such as this exclusively in Flash. For this one, we programmed the entire interactive in javascript and for certain, this will be the way we handle these sorts of projects going forward. It was faster to deploy, and at the end of the day, it looks better than having to reply on a Flash player. Not only that, it runs on hand-held devices, which Flash currently can not.

Getting our final code delivered to the National Geographic server provided an interesting look under the hood of this major site, which AdWeek recently named as website of the year. We were provided with access to the NatGeo CMS (content management system), which allowed us to simply paste our full code straight into and text field, save and then view. Having designed and delivered CMS system for the last nine years or so, it wasn't exactly the most intuative or elegant interface, but at the end of the day, it worked and that's all that really matters, one supposes...