Technical Bank

In this part of the series we'll create the rest of our content nodes (pages) and start adding the XSLT macros to handle things like building the site navigation, and populating the <umbraco:Macro> elements. Also available in this series: Getting Started with Umbraco: Part 1 Getting Started with Umbraco: Part 2 Getting Started with Umbraco: Part 3 Getting Started with Umbraco: Part 4 Creating the Rest of the Content Nodes First we'll add the rest of our content nodes. Remember, Document Types + Templates + content nodes = pages.  All pages in a site should be created as child nodes of the home page in order for the XSLT to work correctly. Right-click on the Home node in the top left hand panel of the back-end and choose Create from the drop-down menu. This will give us the Create dialog; in the Name field enter About Us. The Choose Document Type select box should already be filled with the first available Document Type – Content – this is fine, just click the Create butt

Imagine how great (and maybe mildly spooky) it would be if, every time you were about to make a bad decision, someone would materialize out of the mist and say, “Whoa, there, let’s stop and reconsider this.” Thanks to Gilberto Urueta Sanroman and his article at Scrum Alliance, you may not need such supernatural assistance to avoid mistakes in scrum. He compiles a list of 10 scrum mistakes for your team not to make: Scrum Process Too many tasks in progress Behavior-oriented management Not having a clear goal Making decisions for the team Focusing only on efficiency Trying to centralize control Missing visualization No team-building activities No environment in which to fail Forgetting about quality Heeding the Mist Whether because stories have not matured enough or the deployment system is not ready, tasks can pile up, and if you proceed into the next sprint taking on new stories while the old stories are largely incomplete, you can bet  no one  is going to be happy in the end. Sometime

Andoid N Preview The first update for the  Android N  preview is now available. For now, the update is available through new factory images, but should be rolling out over-the-air (OTA) before long, if it isn’t already, I would imagine. The updates are showing up for the Nexus 5X and Nexus 6P as build NPC56W, while the Nexus 9 is getting NPC56X. The rest of the Nexus line-up isn’t seeing new files just yet.  Android N Preview Part 1 You can grab the new factory images at the links below: Nexus 5X  (56P to 56W) Nexus 6P  (56P to 56W) Nexus 9  (56P to 56X) Nexus 9 LTE  (56P to 56X) Instructions for flashing factory images found  here . Android N Preview Part 2 We don’t know what is included in the update, but this isn’t still a part of preview 1. Our assumption is that this update may reduce some bugs and potentially help performance a bit. UPDATE :  You can also check out interesting Videos in my video collections here  Video Blog

Part of the beauty of owning a Nexus device comes through the regular availability of factory images that can be used to return the device to a factory state. If you root, toss on a ROM, and tinker a bit too much, you may find yourself looking for a last resort to save your phone. A factory image can do that.Think of a factory image as stock, out-of-the-box software for your device. Nexus 5 Boot Loader  Google has been pretty good over the years at making these image files available shortly after they release a new update or version of Android. That situation hasn’t changed with the release of Kit Kat (Android 4.4) or the  Nexus 5 , as Google has already made the N5’s factory images available.  So for those of you who plan to get dirty with your Nexus and may need a savior down the road, we thought we’d make sure you know how to flash .img files to your Nexus 5. The process isn’t difficult, but does require a few adb and fastboot commands. But you are up for that, right? NOTE:  T

In .NET, a masterpage is a template for content pages, where a series of ASPX pages that all use the same masterpage can all share the same base code. Also available in this series: Getting Started with Umbraco: Part 1 Getting Started with Umbraco: Part 2 Getting Started with Umbraco: Part 3 Getting Started with Umbraco: Part 4 Defining the Code in our Base Page Template The Base Page , remember this is the Template and Document Type that all subsequent pages will inherit from, should contain just those elements common to all pages of the site. Open up the BasePage.master file in Visual Web Developer Express (VWD). It will already have a little ASPX code in the file including an <asp:Content> element. This element points to an <asp:ContentPlaceHolder> element in one of Umbraco's masterpages . It is possible to add the code to the masterpages entirely through the Umbraco back-end; when you select one of the Templates in the Settings area, it loads a copy of the