We had a huge, unruly Web site. It just had different graphics, a better-named Web team and more people shoveling on content and applications. Finally, out of desperation, we decided to try a new-fangled thing called a Web content management system.
More than a Web content management system, Octigon President James Smith calls Octane8 a deployment platform. What exactly can you deploy with Octane8? To name a few: public Internet sites, private intranet and extranet sites; sites for the group you'll be collaborating with for the next two weeks; sites with pages that sell; and sites with pages that inform.
If a modern day Rip van Winkle woke up after just a year's sleep, he would be stunned by the buzz around Ajax today. Technology is moving very quickly in this space and whether you are a web author, a CMS developer, or a regular web user, Ajax will make some exciting changes to your world.
Many websites are still publishing content that is not core to their business. The justification is that such content will indirectly deliver benefit. This is not a good idea. Focus on the content that is directly applicable to your organization’s objectives. Any other content confuses. It wastes time and money.
The Santa Claus approach to content management creates a content management software wish list. It believes in the magic of technology to sweep away any and every problem. Typically, those who believe in Santa don't believe in defining their processes, or figuring out just why they need a website in the first place.
A well-designed information architecture with intuitive organization, labeling, navigation, and indexing systems can significantly reduce the amount of time that users spend blundering through the hierarchies of Web sites and intranets. How much is this time-savings worth? The case is clearest for intranets where the users are your employees.
Describes how to use Microsoft FrontPage and Access to build a system for organizing and retrieving feedback from reviewers. The article is intended for those with some experience with Web and database design.
If content strategy isn’t in the current budget, though, how do you convince your client to add money for it? Your client might already realize content strategy can help create measurable ROI. If they don’t, help them understand. After all, relevant and informative content is what their audience wants; content strategy assesses the content they have and creates a plan for what they need and how they’ll get it.
Web site content must be recrudescent, repositorial, refluent, and rectilinear. What? Here's an innovative treatment of the essential attributes of online text. Find out why great web site content generally has these 14 characteristics that start with a "R".
Introduces the breadth of decision-making required in EPSS design. Explores choices and challenges facing designers in the design process, performance cycle, technology constraints, use of storytelling techniques, evaluation, and success factors.
The typical Web redesign results in a better looking more usable site where your information resources are easier to find. But so what? The typical Content Management System (CMS) implementation results in a more efficient process and better organized information. But so what? What does all that really get you? The sad fact is that very few people who install a CMS or redesign a site look beyond these simple justifications to the real reasons why they should organize information and create publications. It's not that these justifications are not important; it's that they are enablers of the more important justifications for managing and delivering content. The ultimate reason your organization manages information is the same reason your organization does any activity-to advance toward its goals. As obvious as this conclusion is, it amazes me how few CM and Web initiatives really address it. In this article, I'll outline one simple, powerful way you can go beyond the immediate efficiency and usability justifications to tie your CM inextricably to the foundations of your organization.
In March 2003, an online survey was conducted of consumer opinion about CMS vendor websites. This was extensively promoted through the CMS mailing lists, and on key CMS websites such as CMS Watch, the Intranet Focus and Step Two Designs sites. In total, 168 responses were made to this survey, representing consumers from across the globe, and in every type of organisation. This briefing provides a high-level summary of the results of the survey.
Content management systems are key to running an efficient website. Keep the development group out of the loop on updating content, and you will move ever so much faster. 'Content' doesn’t need the same kind of source control that scripts and templates need. Specific design suggestions follow.
Content Management is the next step in separating structure from design. What began with Cascading Style Sheets and was furthered by XML, is exploding with the CM environment, where billions were spent last year and more billions are expected to be spent in the years ahead. CM Systems come in many shapes: They can be huge or small, simple or very complex. They range from the very expensive (almost $300,000 for enterprise–wide systems like Vignette or Interwoven and $43,000 per server processor for Microsoft’s CMS to almost free (less than $1,000 for Manila and nothing for Zope). But they are all based on the same idea: CM allows designers to focus on design by building templates. Subject experts build content in a separate environment. The server takes the content, inserts it into the correct template and sends it all, neatly wrapped up, to end users.
There are a wide variety of uses for Wikis and a level of interest in using them that’s matched by an extensive range of Wiki software. Wikis introduce to the Internet a collaborative model that not only allows, but explicitly encourages, broad and open participation. The idea that anyone can contribute reflects an assumption that both content quantity and quality will arise out of the ‘wisdom of the crowd.’
This paper describes the decisions by which the Association for Computing Machinery integrated good features from the Los Alamos e-print (physics) archive and from Cornell University's Networked Computer Science Technical Reference Library to form their own open, permanent, online “computing research repository” (CoRR). Submitted papers are not refereed and anyone can browse and extract CoRR material for free, so CoRR's eventual success could revolutionize computer science publishing. But several serious challenges remain: some journals forbid online preprints, the CoRR user interface is cumbersome, submissions are only self-indexed, (no professional library staff manages the archive) and long-term funding is uncertain.
People are looking for content to help them reach their goals, and you should start any site redevelopment by drawing up a content strategy designed to satisfy the user. We're currently doing this for a couple of our clients, and working through it ourselves now we've finally found the time to revamp our own presence (the cobbler's children and all that).
An Information Model provides the framework for organizing your content so that it can be delivered and reused in a variety of innovative ways. Once you have created an Information Model for your content repository, you will be able to label information in ways that will enhance search and retrieval, making it possible for authors and users to find the information resources they need quickly and easily.
Okay, we've all fiddled with NavBars. In fact, MM's built-in Navigation Bar Builder is pretty sweet for creating NavBars with onMouseOver and onMouseOut behaviors giving your site that professional look. But what if your site changes frequently? One option is to bag the images and stick with a database-driven NavBar that uses a repeat region. We'll look at that approach first. Then we will see how we can replace UltraDev's hardcoded NavBar image behaviors with database-driven links and images.
Designing and indeed front-end development for a website that will have content edited by non-technical users poses some problems over and above those you will encounter when developing a site where you have full control over the output mark-up. However, most clients these days want to be able to manage their own content, so most designers will find that some, if not all, of their designs end up as templates in some kind of CMS. By considering the CMS as you design, you can maintain far more control over the final output. If your designs will be implemented and integrated into the CMS by a developer, then taking control at the design phase will help you to keep control over the design as opposed to leaving decisions to the developer or the content editors.
Many technology companies, consultants, and academics are hyping the future of Web services. But how will this background transfer of data between applications affect the user experience?