User Experience Advantages in Sitecore Development
It’s important for software developers to know the products they work on, both inside and out — the code, the components, the user interface, everything. That way they understand the application both from the technical side as well as the user’s standpoint and can provide greater value to their team at all points in the product lifecycle. Unfortunately, sometimes project constraints are such that the development staff spends the majority of their time working on code and getting to know the product has to take a back seat. By only glancing at the UI here and there during testing, but never really using the product as an end user would, developers lack understanding of what customers feel is good or bad about the software being developed. These sorts of challenges are what make working with the CMS product Sitecore such an excellent experience and such a change from the norm.
Semantic Web – what is it, and how did we get here?
Bud Abbott and Lou Costello in Hit The Ice video 
The modern website can do some amazing things for your business. It’s truly evolved from an online brochure into one of the major marketing engines and key drivers for growing your business.
To understand how we got from simple marketing sites to complex modern web applications, let’s take a quick walk down memory lane.
The web, in its 1.0 flavor, offered static content and little interactivity. A business would translate its traditional marketing collateral into a series of web pages (brochureware) that were rarely updated, and communication was generally one to many (broadcast). This technique was cumbersome and costly to maintain. It also didn’t scale well as sites grew.
To combat this problem the web evolved in the late ’90s into its 1.5 flavor. The introduction of web programming languages (such as Perl, ASP and PHP) and database connectivity allowed for dynamic content that was centralized and easily updated via a web administration system versus a developer. The underlying theme here is that content became easier to manage and publish more frequently. Databases allowed for the introduction of two-way communication on websites via message boards and self-help applications like FAQ’s and forms. The first generation of web software applications — such as content management systems (CMS) and Ecommerce — were introduced. Unfortunately, the cost of entry generally prohibited most small to medium companies from adopting them.
The next evolution (or should I say revolution?) on the web was Web 2.0. For the first time sites allowed users to interact with the website and contribute to its content. Search engine optimization (SEO) became a major factor in any redesign — site structures and content were highly optimized to gain higher organic rankings on search engines. Community features were introduced, including blogs, ratings, wikis, comments, threaded discussions and groups. Technologies such as web services, XML and RSS were added to allow content to be decentralized and syndicated. Sites also became a little smarter, offering different ways to navigate content by offering related or suggestive content and filtered navigation.
The Prince of Tides So, the question is, where are we now? What is the term being used to describe the next generation of web applications? And what technology separates this evolution from its predecessors? The term that the industry has settled on for the next generation website is the “Semantic Web”. Wikipedia has a great summary of this:
The Worlds Fastest Indian divx
The Semantic Web is an evolving extension of the World Wide Web in which the semantics of information and services on the web is defined, making it possible for the web to understand and satisfy the requests of people and machines to use the web content. It derives from W3C director Tim Berners-Lee’s vision of the Web as a universal medium for data, information, and knowledge exchange.
Google’s iGoogle
platform is a great example of this technology. It allows you to create your own, completely customizable web dashboard. You can add custom content tailored to your specific needs via RSS feeds, applications and widgets (from Google and 3rd parties). All of your settings are saved for repeat visits. At its heart the Semantic Web is the introduction of the “smart website.” Content is highly targeted to individual needs and desires and can be accessed via any number of media, including the traditional web browser, PDA or smart phones. It is the dawn of a new and exciting era online — one that empowers us with access to personalized information on demand, helping us keep up-to-date in the increasingly fast-paced lives we lead.
Reviews of popular Open Source CMS solutions
Last month fellow HD blogger, Gretchen, broached the topic of “What is the best CMS?
” which stirred up some good debate in the comments. The question of CMS selection and approach comes up all the time. Everyone has their two cents on whether your project requires you to buy, build or go the Open Source route. To add to the discussion I wanted to reference an article
1492: Conquest of Paradise movie download in the latest edition of Adobe’s Edge newsletter that reviews some of the popular Open Source content management systems.
The article’s list of CMS solutions is, by no means, exhaustive or comprehensive — it only focuses on systems that run on Apache, MySQL and PHP architecture including: CMS Made Simple, Drupal, Joomla!, Wordpress and XOOPS. That being said, it is helpful and a nice quick way to compare and contrast some popular Open Source solutions. Enjoy!
Which Is the Best CMS?
In the last 15 years or so, web content management systems (CMS) have essentially become the only way to build web sites. It makes perfect sense — from large corporate sites to one-page personal web sites, nobody wants to touch code every time they need to change an image or copy.
And the question I hear all the time is simply this: which one is the best one? I suppose it’s reasonable to assume that by now, one system has risen to the top. Sort of like Microsoft Word for word processing. But the truth is, there are literally hundreds of CMS packages out there, and they all do the same thing: update web content outside the site’s source code.
The real question you should be asking is “Which CMS is best for what I need?” Of course, that takes more planning work. Here are the top six things you should consider when selecting a CMS for your site:
1. How much do you want to spend?
You can spend nothing, or you can spend millions on a CMS solution. of course, if you take the nothing route, as in open source, you will spend much more time on in-house development. You will also have more control over what features you have, instead of working around somebody else’s code. At the other extreme: spend lots of money, and you’ll get lots of built-in features, good post-launch support and reliable feature upgrades.
2. Who will be updating your site?
If you’ve got lots of people in multiple locations needing to update content, you’ll need to consider workflow tools. Some CMS packages have good ones, some don’t. You’re going to need multiple user roles (contributor, editor, administrator, etc.) and specific approval steps content must go through before appearing on the site. On the other hand, if it’s just one person running the whole thing, you’re in luck. Don’t worry about workflow.
3. Do you need to publish in other languages?
Some CMS packages have translation tools built in. If you need to publish your content in a number of different languages, make sure you select a CMS that will assist in that process. The tools will not be perfect, and you will still need to have a human translator check for accuracy, but at least you won’t have to translate every word manually.
4. What does your CMS need to work with?
Do you sell product online? Are you using an e-commerce, payment gateway or a product information management system? Make sure you identify and consider outside systems before making any CMS decisions.
5. Consider your platform.
This one’s deceptively simple. If you have 25 .NET developers on staff, don’t select a CMS that only uses Python. If your developers will be learning a new language, try to do it outside a new web site deployment. You’ll be busy enough without having to worry about training.6. Think about the future.Don’t just select a CMS to replace your current site; think about what you might want to do in the next five years. Will you be hiring more content contributors? Reducing your development staff? Assigning more web administrators? Adding an online store? You will need to think all of these things through, or you might be going through the same selection process in a year.
Of course there are plenty of other things to consider when selecting a CMS: can your company support ongoing administration? How much training will you need to do? What are other members of your industry using?
In fact, if you’re in higher education, you’re in luck: UC-Davis did a really interesting survey on which CMS tools colleges are using. The comments alone are an interesting read.
So, if you’re in the market for a new CMS, be thoughtful about it. It might take a little longer up front, but you’ll be glad you did.