Traditionally websites and content management systems have used relational databases, and while they have a lot of benefits, managing narrative web content (text, images, and media) in a relational database has always been trying to fit a square peg in a round hole. Imagine a new content management technology designed to store all of the rich semantic structure, meta data and intelligence about your content. A content platform that is better, faster, more flexible, scalable, and cheaper than traditional relational database-backed Web CMS solutions. These benefits and more are available now using NoSQL.
Structured content is nothing new; we’ve been talking about it for years, particularly in relation to creating and storing technical documentation. But the importance of structured content has grown well past the management of technical documents. Structured content is important across the entire organization as it works to create and manage great customer experiences.
Customer demands are growing to the point that a new approach to managing and delivering content is required. Among other things, Web Content Management solutions must deliver engaging, personalized experiences in order to make the cut. So, where do you start when "shopping" for a new WEM solution? We created this Web CMS RFP Guide to help.
Often when organizations are in the process of looking for a new CMS, the technology always seems to take precedence. Certainly, content management technology is essential and should be taken into consideration first and foremost. But there's something else that is very important and deserves more than a simple checkmark and cursory response on an RFP form - the Support Model. Find out why in the final installment of series on ASP.NET Web CMS Solutions.
No topic on ASP.NET CMS platforms would be complete without talking about the database. In an agile decoupled content management and deployment model, a relational database presents challenges. Content needs to be managed in a more structured (or intelligent) manner than a Blob provides. What's required is a flexible content or data model, offering a richer content structure, and that's where NoSQL can help.
In the third installment of our series on ASP.NET Web CMS we talk content: Structured vs blob. In a multi-channel, multi-device world, the ability to reuse content is absolutely critical. Content reuse takes a variety of forms. It could be the updating of content on multiple websites or mobile devices, supporting multilingual requirements, or it could involve content for both digital and print. The idea of creating and managing separate versions of content for each channel/device screams of wasted time and effort. No one is crazy enough to do it this way (we hope!).
In this piece of our series on ASP.NET Web CMS we dive into development models. ASP.NET Web Forms is the traditional development model for ASP.NET. The problem with Web Forms is that it supports a tightly coupled architecture, one where the interface is integrated with the application functionality (code behind). MVC (model view controller) provides a different architectural pattern for development. MVC is the more modern approach to ASP.NET development, and is the future of ASP.NET with full support from Microsoft.
As you evaluate ASP.NET CMS solutions for your company, it's important to understand four key differences and how they impact your online capabilities and web experience road map. In this blog series we'll examine these four differences, explaining why they are important to understand and what each means for your decision process. Let's kick things off with the ASP.NET Web CMS architecture model.
Together with our partner, KJI, a leading provider of translation and localization services, we hosted a webinar on how to ensure your content is developed for a global audience. KJI provided a valuable overview of tips and tricks to writing English with translation in mind, while Ingeniux demonstrated how to translate, manage, and optimize content in the CMS.