|
Inheriting Web sites: Getting a Web site to a maintainable state
|
Last Update 2008/3/12 8:09
|
Category
Programming
HTML
:
Programming
CSS
:
Programming
Platforms
Web Client
|
Description
In a perfect world, you'd create every Web site you were ever assigned to maintain, improve, and redesign. Unfortunately, in the real world, you're often forced to take on a site someone else designed or constructed.
New jobs, new projects, new assignments, and new responsibilities all carry with them risk. And while you may have a new boss or a new office or a new set of colleagues, nothing is quite so intimidating as being handed a Web site that is now yours to care and feed, having no idea how that Web site was put together. More often than not—especially if you're taking over for a less-experienced Web designer, or worse yet, someone who was just "filling in"—the sites you'll inherit are a tangled jumble of content, presentation, and even some activity. And, of course, the pages are ugly. If there aren't blink tags, there are jumbled styles, font tags mixed with CSS styles, unclosed and misused HTML tags... it can be a mess.
Thankfully, there's a logical approach to turning these sorts of pages into finely tuned, easily maintainable Web sites. This two-part series provides a road map for turning messy and unruly pages into well-structured, organized, maintainable code. In Part 1, you'll learn how to make a site maintainable. In Part 2, you'll organize your site's layout, increase its efficiency, and make sure you're in control.
It turns out that some tried-and-true techniques make a task like this manageable and put you in a position to not just succeed, but to excel. They'll also ensure that you spend the least amount of effort reworking a site, and the most amount of time improving it and keeping it working. Then, if you later get the opportunity to refresh or even redesign a site like this, you can start from well-segmented HTML and CSS, not a mess of convoluted and style-laden HTML.
|
Hits: 37
|
Silverlight Tips, Tricks, and Best Practices
|
Last Update 2008/2/29 7:31
|
Category
Programming
Platforms
Web Client
:
Programming
User Interface / UX User Experience
:
Programming
Silverlight
|
Description
Unless you've been stuck on a desert island for the past several months, you've undoubtedly heard about Silverlight™, the new cross-browser, cross-platform solution from Microsoft that helps you build rich Internet applications and rich, immersive media experiences in the browser. Version 1.0, which combines a XAML rendering engine with a JavaScript API, shipped in September 2007. Version 2.0, which will enter beta soon, will pair an enhanced XAML engine with a version of the CLR that runs in the browser, a Silverlight version of the Microsoft® .NET Framework Base Class Library (BCL), and a managed API. (That's right: C# in the browser!)
Silverlight 1.0 applications are proliferating on the Web, thanks in part to some of the high-profile companies that adopted it early and helped spread the love. The programming model is simple enough for an experienced developer to begin building Silverlight applications in a matter of hours. What's missing for this still very young platform, however, is that wealth of knowledge and resources that accompanies more mature platforms. I've been developing Silverlight apps for more than a year now and have put together a list of best practices that I and other developers on my team use to build better applications.
|
Hits: 24
|
|
|
|