Home / Articles / Adobe ColdFusion / Initial Thoughts on a ColdFusion MX Content Management Project

Initial Thoughts on a ColdFusion MX Content Management Project

Chapter Description

Sit in with the folks at fictional XR Solutions as they plot out a strategy for a content management project.

The Basics of Content Management

Al drops by Sam's office. Teri is next door, hears them chatting, and wanders in. Sam tells her to grab a chair and says, "So, who wants to talk content management?"

Sam draws a sketch on the whiteboard (see Figure I-2.2). Teri says his drawing looks like Mark's and accuses him of plagiarism.


Sam explains his drawing. At the center of any content management system is the actual content, articles. Content can be rendered in all sorts of ways and so presentation is never tied to content. Al is thankful that he took the time to browse that cfc file.

Sam continues, "Articles are just records in a database, that's the easy part. Where it gets tricky is designing underlying data structures so that they are flexible enough to allow data to be used as needed."

Al asks "So why not just store each article in a database table, and then have a screen that allows people to pick from a menu selecting which articles they want displayed on a page, and then render the page dynamically?"

"That won't scale," Teri objects. "If you have hundreds or thousands or even tens of thousands of articles you'd never want to select them individually. You need to group them and allow a group to me selected, if group A is used in a page then articles in group A are displayed."

"Correct," says Sam. "But there is a more important reason to group data. Content management almost always involves some form of access control – restricting or allowing access to data based on security clearance, job, department, membership, or whatever. You'd never want to assign access on a per article basis – you'd do it by group and then put articles in groups."

He walks back to the whiteboard and writes this list:

  • Article. Actual content

  • Category. Logical grouping of articles; articles go into categories

  • Page. A page as seen by the user, made up of one or more categories and laid out as needed

Al asks if an article can be in multiple categories. Teri shakes her head vehemently, and Sam agrees: "It's much too hard to explain that to users. They'll never understand why content is displayed when they remove it from a category, not realizing it is in another. Plus it makes access control an absolute nightmare."

Al suggests, "I guess they could always create additional categories as needed."

As has been discussed, users request pages that are rendered on the fly. Pages contain articles from one or more categories, and exactly what the page will look like will thus depend on the categories included, the articles within a category at the time of the request, and any access control associated with categories.

The discussion moves to articles—what they actually are and how they are stored. Teri explains that there are two basic approaches to data storage:

  • Highly structured. Define fields for all types of data, store headers body, images, and so on in their own fields.

  • Free form. Save the whole article as a block of text.

As Teri explains, there are varying degrees between these two extremes, but the basic question to ask is this: Will all content be so consistent in layout that a tight structure can be used, or will content vary so dramatically that a tight structure will get in the way? The group looks through the samples that Maria gave Sam and unanimously agree that content will have to be free form. Sam notes the following:

Data is free form; we will basically store content as a big text field.

This allows greater flexibility but makes applying formatting trickier.

Need to revisit this one.

Al asks about user preferences and how they are stored and used. The group has differing opinions in this area. Teri says that the only way to truly integrate users with a content-management system is to make users and user management part of the core content-management code. This way users can select desired categories, save preferences, and be tightly integrated with the content itself. Sam disagrees, and walks to the white-board again (see Figure I-2.3).


Sam's diagram suggests that the user system and the content-management system are separate entities that are completely independent from each other. In fact, the underlying data store for users may be an LDAP server, while content may be in a database; there is no requirement that they have anything in common.

Teri disagrees: "They are not as separate as you imply, Sam. If a user sets a preference that says he or she wants Category No. 123, that information needs to be stored somewhere, either with the user or with the content."

They argue back and forth for a while until Sam gives in, kind of. Sam does not want user information stored in the content-management system itself, but user preferences pertaining to content do indeed belong there. So, User No. 10 will have preferences stored along with the content so that when he or she requests specific content, those preferences are taken into account. However, the content-management system will have no idea what a user actually is or who User No. 10 is; that kind of information wouldn't matter at that level. All the content-management system would need to know is that it is User No. 10 who is making the request so it can, for example, filter results appropriately.

Sam updates his whiteboard drawing (see Figure I-2.4).


Sam's phone rings, and the tone of his voice tells Teri and Al that they'd better be off on the other side of his office door. They gesture and leave, and Sam fires off an email to Vijay while on the phone.

3. The Rules Engine | Next Section Previous Section

Adobe Press Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Adobe Press and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Adobe Press products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email ask@peachpit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by Adobe Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.adobepress.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020