Chapter 6. Configuring Commonly Used Components
How do you author structured content using Smart Forms?
How do you organize content through taxonomy?
How do you use aliasing to improve URL readability?
How do you create language-specific editions of your site?
Once you have a few Web projects under your belt, you will notice that Web projects are unique in their own way. Technical requirements vary significantly from project to project, and for any Web project to be truly successful, it needs to respond to the unique business requirements for each site, incorporating the needs of stakeholders and customers. But focusing on these differences might lead one to assume there is little commonality between them. In reality, this is not true. This assumption focuses on differences of functionality, information architecture, and even business requirements. But it overlooks the fact that the vast majority of websites share common fundamental requirements and they are built upon common technological underpinnings, in spite of their implementation differences. This chapter builds on the content management fundamentals of Chapter 5 by describing commonly used components found in Ektron implementations. The frequency of their use stems from the fundamental requirements of websites, which are:
Content needs: Requirements often drive the need to repurpose information in many ways on the site and across different platforms, to separate data from the presentation, and to define information in such a ...