Cms Basic

Editor's Notes

• #12: Content has context
• #14: Content has format
• #15: Semaphore flags in the slide read DRTC
• #23: A Template separateS design fm content
• #27: suitable for small sites that don’t change much and don’t require personalization. + fast, because no processing is required lack of flexibility can’t scale beyond a few hundred pages tedious to manage, because content must be updated on every page
• #28: Dynamic Web Site
• #29: you can have a dynamic site that really isn't doing content management at all. In addition, a content management system can just as easily build a static site. For example, that you maintain a large, dynamic Web site that uses advanced scripts to put a user interface on your organization's financial system. The system responds to user requests and dishes out just the right HTML page in response. You'd be hard-pressed to call this setup a content management system — it's really just a Web-based application.
• #30: A CMS application: Sitting safely behind the Web server, this application takes care of collecting content from contributors and managing your content's workflow and administration. The actual architecture varies by product. In some CMS products, you have software on the organization's local area network (LAN) — inside the firewall — for collecting and testing your content, and software outside the organization's LAN on the live Web server for dynamically serving up pages.A repository: Also behind the Web server is a relational or XML data source. The repository holds all your content, administrative data, and any of the resources that you need to build the site (such as graphics and style sheets).A set of flat HTML files: The CMS manages and deploys files to the static part of the site.A live data source (the CMS-generated database): This is located on the Web Server for the dynamic parts of the site. The CMS can deploy data and content from its repository to the CMS-generated database. In this way, even dynamic content can be managed behind the firewall and kept off the server if it is not ready to be seen publicly. In addition, the template pages that access the CMS-generated database can be pages that are created by the CMS.Other data sources: You can connect other sources of data to the Web site that you don't connect to the CMS. A transaction database for conducting sales on the site, for example, you may connect to the Web site but not to the CMS. The other data sources can run completely independently of the CMS (or the template pages) that accesses the sources.Templates: A set of publication templates moves data from any source to the state it needs to be in for the site. In some cases, the data must be put into finished static HTML pages. In other cases, it is put into databases that will live on the Web server.Tip In general, your best bet is to drive as much of your site as is feasible toward static pages. Even if content changes once a day, you're probably better off producing it as HTML files and posting the ones that change to your server daily. Flat pages are tremendously faster and more reliable than dynamic pages. You need compelling reasons to dynamically generate pages — for example, the content is changing minute by minute or you need to personalize the content for each user or user type.
• #31: A full CMS encompasses your site, plus the other publication channels. This CMS includes a print, e-mail, and syndication system.
• #32: Although logically separate, the three parts of the system can involve large physical overlaps
• #33: Collection ProcessAuthoring: create the content from scratch.Acquisition: gather the content from some existing source.Conversion: strip unnecessary information from the content and change its markup language.Aggregation: edit the content, divide it into components, and augment it to fit within your desired metadata system.Collection services: CMS programs and functions that aid the collection process. For example, the collection services might produce the Web forms into which you enter the content for components.